ORNode: Token events from transaction which executes multiple mint events are not handled correctly

[sim31]

The way it currently works in ornode is that on proposal execute events it goes through event log to find all token transfer events... If proposal type is one of the recognized mint prop types, it fills in token metadata using data from attachment of that proposal (like mintReason and group num). This means that if transaction executes multiple proposals that mint Respect, it will end up overwriting token data with info from one of the proposals (the one which is executed later) or inserting duplicate award records...

Idea: specify propId in mint data?

[sim31]

Started fixing this, where I stopped: when ornode does not have full proposal data, it will not know which prop execution should add which awards... The results would be duplicate awards being added.

I think proper solution for this should include testing:

• Create orclient feature to execute all passed / un-executed proposals in one tx (will need a smart contract for this);
• Then test current ornode to see what happens
• Fix it;

Ideally should test and fix the aforementioned case where node does not have full proposal data.