Testing and Issues
You can test this entry and submit issues during the testing period of the Blockchain Contest contest.
Entries with serious issues will not be able to win the contest, but even minor issues might be important for overall results.
Each step has user friendly explanation on whats exactly happening right now. (Like - you signing order X, which valid within next N hours, it was signed by those participants etc. etc)
Notice, that you cannot send same order twice. If you want to send same amount to same destination again, you should consider making different "expires" value. Because upon sending message to contract it becomes public, anyone could re-send full list of signatures again. But they wont be accepted.
Stay tuned for better user-friendly scripts and updates!
Failed with exit_code=100. Also, this transaction was repeated multiple times, so now the account is almost empty
All required features are implemented.
It is possible to add a signature to order without modifying seqno.
Failed with exit_code=100.
Hash does not protect seqno.
The same signature repeated multiple times would be enough to execute an order.
accept_message() is called before any signature is verified.
The code is split into several files. This is fine, but in the current case, this makes it a bit hard to follow workflow.
For example, set_data is called multiple times during execution but this is hard to notice and there is no simple
way to fix it without refactoring