EOSIO.Contracts v1.8.3 Inline Multi-Signature Patch 2 Release Notes

This patch builds on top of EOSIO.Contracts v1.8.3 Inline Multi-Signature Patch Release

Amendment (#517) of eosio.msig (#504)

An issue arises when a user proposes a transaction with non-zero delay_sec. Doing so will execute the deferred transaction instantly. To solve this problem we propose a way to emulate the behavior of a deferred transaction with this implementation.

eosio.msig Behavior (#517)

The changes are two-fold:

1. The number of delay seconds is used to calculate the earliest possible execution time of the action exec once the approvals of the proposal have been satisfied. The earliest execution time is the point in time at which the proposal has been satisfied plus the delayed seconds specified in the transaction header of the packed transaction. Also note, that if a proposal reverts its status of having the approvals satisfied, then unsatisfied, and then satisfied once again, the earliest execution time will get recalculated.
2. The given transaction (in the action propose) is executed immediately upon the user performing the action exec as a sequence of inline actions, but only if the the proposal has been approved and the given number of delay seconds has passed. Otherwise, the execution of the action exec fails.

Dependencies

This patch release builds on top of EOSIO.Contracts v1.8.3 Inline Multi-Signature Patch Release. Please refer to that document for required details.

Disclaimer: All repositories and other materials are provided subject to this IMPORTANT notice and you must familiarize yourself with its terms. The notice contains important information, limitations and restrictions relating to our software, publications, trademarks, third-party resources, and forward-looking statements. By accessing any of our repositories and other materials, you accept and agree to the terms of the notice.