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
Send rewards to users. The two rewards are generated from different activities, so they need to be sent separately. However, the amount of the rewards is the same, resulting in two identical actions in the same transaction.
Unfortunately, on the current version the deduplication happens based on the act_digest per action inside a transaction. Removing the deduplication can greatly increase storage needs for all operators due to misuse of receipt notifications and also spamming.
We are working on improved processing and optimizations for future releases.
@devmoondev my recommendation for the smart contract developer is to use a different memo if this data is important to be indexed, this will make the act_digest be different and you should get both actions in
@devmoondev my recommendation for the smart contract developer is to use a different memo if this data is important to be indexed, this will make the act_digest be different and you should get both actions in
Thank you for your patient reply. This problem can be avoided once discovered, but for those who encounter it for the first time, there will be a lot of misunderstandings, thinking that their coins are lost. I currently separate actions into different transactions.
Case
Send rewards to users. The two rewards are generated from different activities, so they need to be sent separately. However, the amount of the rewards is the same, resulting in two identical actions in the same transaction.
Sample code
Querying the data in ES reveals that there is only one action record in this transaction, and the second will be lost.
The text was updated successfully, but these errors were encountered: