You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 12, 2022. It is now read-only.
If using internal management, suggest using Betsy and nothing else is necessary. If a pure integration is desired, then increasing the minimum receive is required.
RPC account_info -> grab the frontier (which will be the previous block to your send)
Ask DPoW for work using that hash (the frontier)
RPC Send with the given work
Alternative (advanced):
(Same)
RPC block_create
Work from DPoW
RPC process
For both cases there is an exception - if the account is not created yet, there will be no frontier. In this case the public key should be used, which can be grabbed from RPC account_key.
Finally, keep an eye on the CPU usage during your sends and receives to make sure there is no PoW being re-generated. This would not happen with the advanced method.
The text was updated successfully, but these errors were encountered:
Rough start:
If using internal management, suggest using Betsy and nothing else is necessary. If a pure integration is desired, then increasing the minimum receive is required.
Alternative (advanced):
For both cases there is an exception - if the account is not created yet, there will be no
frontier
. In this case the public key should be used, which can be grabbed from RPC account_key.Finally, keep an eye on the CPU usage during your
send
s andreceive
s to make sure there is no PoW being re-generated. This would not happen with the advanced method.The text was updated successfully, but these errors were encountered: