Timeline for Understanding Transactions
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 4, 2019 at 1:01 | comment | added | stan14 | I know the implementation side, I am programming eos smart contracts for like 1 year before now. I am just asking for a paper I am writing about Eos and so as to clarify the fields :) | |
| Oct 3, 2019 at 22:59 | comment | added | cmadh | you don't neccessary need to add it to the transaction. If you for example automatically send rewards to holders of a specific token every night and just call a single action for that which does the rest for hundrets of accounts, depending on your implementation you don't have to add the receipients to the action-parameters. All you need is to call require_receipient([valid_eos_account_name]) from within your contract. | |
| Oct 3, 2019 at 22:44 | vote | accept | stan14 | ||
| Oct 3, 2019 at 22:44 | comment | added | stan14 | Ok so an additional field would be added to the trx object in that case.How this field would called? recipients or receivers? thank you | |
| Oct 3, 2019 at 21:45 | comment | added | cmadh | The trx-example you provided above is the scheme of a typical "issue"-transaction and while issuing a token there are no additional accounts and therefore no receivers involved. To notify a receiver you would add require_recipient(receiver) to your smart contract. | |
| Oct 3, 2019 at 13:20 | comment | added | stan14 | about the receivers statement. How does the node for which account to run the apply() method if its not in the trx? | |
| Oct 3, 2019 at 3:41 | history | answered | cmadh | CC BY-SA 4.0 |