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
Аbstract
Currently there is no trivial way to get how much WAVES sponsor pays for his sponsored asset in fees in transactions.
Motivation and Purposes
It hard to maintain the state of sponsorships database, lets use stateChangesById in the way you did for invoke script transactions.
Specification
Enhance GET /debug/stateChanges/info/{id} where sponsored asset is used for a fee to get stateChanges as how much WAVES was really paid in exchange for sponsored asset.
The text was updated successfully, but these errors were encountered:
phearnot
changed the title
[FEATURE] Enhance stateChangesById for sponsored transactions
Enhance stateChangesById for sponsored transactions
Oct 16, 2019
Hi Dmitry!
Ability to give such information is connected to storing additional data in the nodes DB. Which is not needed in most cases.
Maybe we implement it later with some optional node extension.
Аbstract
Currently there is no trivial way to get how much WAVES sponsor pays for his sponsored asset in fees in transactions.
Motivation and Purposes
It hard to maintain the state of sponsorships database, lets use stateChangesById in the way you did for invoke script transactions.
Specification
Enhance GET /debug/stateChanges/info/{id} where sponsored asset is used for a fee to get stateChanges as how much WAVES was really paid in exchange for sponsored asset.
The text was updated successfully, but these errors were encountered: