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
When using Mint Machine by nathanwells, I noticed that I can authorize a derived key once with global deso limit set to 1 DeSo (or something like 1.0001 to be exact - probably to account for gas fees), but then I can get several 1 DeSo bids accepted (by cloutpunk in this case) on that derived key.
So it seems like global deso limit for nft bid transactions - applies to the "act" of placing the bid, so just the gas fees associated, and not to the amount of bids placed.
This does not seem to be the correct behaviour - I would expect that when authorizing a derived key to use NFT bid transactions, with a global deso limit of 1 DeSo, it's one of the 2 options:
I can place bids up to 1 DeSo, so if there is already a bid outstanding (not accepted) for 1 deso - I can't place a second one; if someone elses bid is accepted, and thus mine is deleted - then I can place another one up to 1 DeSo, or
regardeless of outstanding bids, the total amount of accepted bids on this derived key, cannot exceed 1 deso - so it's 1 cloutpunk @ 1 deso, or 100 other NFTs at 0.01 deso each
The text was updated successfully, but these errors were encountered:
When using Mint Machine by nathanwells, I noticed that I can authorize a derived key once with global deso limit set to 1 DeSo (or something like 1.0001 to be exact - probably to account for gas fees), but then I can get several 1 DeSo bids accepted (by cloutpunk in this case) on that derived key.
So it seems like global deso limit for nft bid transactions - applies to the "act" of placing the bid, so just the gas fees associated, and not to the amount of bids placed.
This does not seem to be the correct behaviour - I would expect that when authorizing a derived key to use NFT bid transactions, with a global deso limit of 1 DeSo, it's one of the 2 options:
The text was updated successfully, but these errors were encountered: