Events are inheritable members of contracts. When you call them, they cause the arguments to be stored in the transaction’s log - a special data structure in the blockchain. These logs are associated with the address of the contract, are incorporated into the blockchain, and stay there as long as a block is accessible. The Log and its event data is not accessible from within contracts.
GoodWallet
pollForEvents
method, we can listen for logs in an almost real time manner. pollForEvents
is periodically polling for events like the specified event (filters by the specified event) up to the current blockchain block, and perform callback on them.pollForEvents
receive a callback which processes the list of events received from the filtered query.Transfer
funds from the account.Transfer
funds to the account.receiptUpdated
flag, and to "transferTo" are subscribing to receiptReceived
flag.balanceChanged
flags are invoked also.Transfer
(from or to) event is processed. As well, entitlement (amount to be claimed) is re-queried and updated accordingly.GoodDollar.initialMove()
method is called and successfully executed.GoodDollar.transfer()
specifying destination address, email, mobile or username.GoodDollar.transferAndCall()
.GoodDollar.transfer()
, GoodDollar.transferAndCall()
.0x0
. And at the end of the migration process, ownership is transferred to the GoodDollarReserve
contract.GoodDollarReserve
contract is also added.GoodDollarReserve
, the deployer account is being removed. **onTokenTransfer
method.0x0
. And at the end of the migration process, ownership is transferred to RedemptionFunctional
contract.GoodDollar
, GoodDollarReserve
and OneTimePaymentLinks
are added to the list. During application lifetime, when a user has been validated (email, mobile and Face Recognition).