-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request - expose an interface to retrieve all affected addresses from a transaction #2252
Comments
Hmm... seems I was mistaken when I said there is already an internal mechanism to get affected addresses for a transaction. The history store in fact only indexes by sender and recipient :( core-rs-albatross/blockchain/src/history/history_store.rs Lines 955 to 976 in fe7c294
Probably what I remember was just an idea, instead of implemented. |
Here is what I remembered: the
|
It will be difficult to make this accessible from the transaction itself. @redmaner: Does the Log mechanism solve your problem? |
Why is this difficult to make accessible from the transaction itself while the data is encoded in |
+1 on this feature request. The stakers will see their wallet balance miraculously increase with each payout from my pool, therefore payouts cannot be seen/tracked in the web-wallet. I think a use-case for this request could be for annual tax declarations (in some countries people have to declare their staking income). I will of course have a record of these transactions in my db of pool payouts, but I plan to truncate this several times per year (depending on size). |
Current transactions returned over RPC include the
from
andto
fields but these fields do not always cover all affected addresses in the transaction.For example:
from
field is set to pool X and the recipient is set to the staking contract. The address of staker A has to be parsed fromrecipientData
This issue requests either of two things:
staker_address
in the transaction, so we always know which staker is affected by a staking contract transaction and / orThe text was updated successfully, but these errors were encountered: