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
The SDK should use a special API to select which utxos to use as inputs, instead of directly picking utxos from the full set. This is important for ensuring consistent behavior across SDK's and the ability to implement efficient dust mitigation strategies such as random-improve.
For inputs, the API will take:
owner: The Address of the utxo owner spend_query: Vec<(AssetId, Amount)> The total amount of each asset type to spend max_inputs: u8 The max number of utxos that can be used
Success:
Return a list of utxos <= max_inputs that will satisfy the amounts to be spent.
Errors:
If the spend amount is higher than the available balance of the owner.
If reaching the spend amount requires the list of utxos to be greater than max_inputs
The text was updated successfully, but these errors were encountered:
@digorithm this is done, and will be available in the next release. Integration testing could start using the published docker image from master branch.
* Clean up comments and code
* Additional comment format
* Minor comment formatting
* Update comment text
* Simplify test storage maps
* Simplify sparse test storage maps
The SDK should use a special API to select which utxos to use as inputs, instead of directly picking utxos from the full set. This is important for ensuring consistent behavior across SDK's and the ability to implement efficient dust mitigation strategies such as random-improve.
For inputs, the API will take:
owner
: TheAddress
of the utxo ownerspend_query
:Vec<(AssetId, Amount)>
The total amount of each asset type to spendmax_inputs
:u8
The max number of utxos that can be usedSuccess:
Return a list of utxos <= max_inputs that will satisfy the amounts to be spent.
Errors:
max_inputs
The text was updated successfully, but these errors were encountered: