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
Currently, this endpoint returns all confirmed unspent boxes residing in an address. A parameter is needed to also include unconfirmed boxes. I think it should include boxes with ergotrees belonging to the respective address queried.
The use case for this would be to generate chained transactions where offchain service does not know prior box(es) used. For example when ergo mobile connects with a dapp to submit a transaction, the dapp uses unspent boxes by address to retrieve input boxes. If a ergo mobile user wants to interact several times with a dapp in a short period of time it will not be possible due to double spend errors. Having the unconfirmed addition will allow for dapps to have quick successive transactions for mobile users.
The text was updated successfully, but these errors were encountered:
@ApexTheory It is already implemented by @jellymlg . However, I also need a flag such that it returns boxes which are not currently spent in the mempool.
For example, let's say Address A has only one box, box A. I send box A to Address B. The outputs are two boxes, one that goes to B, and one that is change, which goes to A. This transaction is now unconfirmed.
Right now, I want to send to Address C. If I use the api to get boxes at Address A, it will return two boxes. The original box which is currently being spent and the change box which is available for use.
The flag required should only return boxes which are not in the process of being spent. In other words, none of the boxes should be in the input of transactions in the mempool.
Currently, this endpoint returns all confirmed unspent boxes residing in an address. A parameter is needed to also include unconfirmed boxes. I think it should include boxes with ergotrees belonging to the respective address queried.
The use case for this would be to generate chained transactions where offchain service does not know prior box(es) used. For example when ergo mobile connects with a dapp to submit a transaction, the dapp uses unspent boxes by address to retrieve input boxes. If a ergo mobile user wants to interact several times with a dapp in a short period of time it will not be possible due to double spend errors. Having the unconfirmed addition will allow for dapps to have quick successive transactions for mobile users.
The text was updated successfully, but these errors were encountered: