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.
pollForEventsmethod, we can listen for logs in an almost real time manner.
pollForEventsis periodically polling for events like the specified event (filters by the specified event) up to the current blockchain block, and perform callback on them.
pollForEventsreceive a callback which processes the list of events received from the filtered query.
Transferfunds from the account.
Transferfunds to the account.
receiptUpdatedflag, and to "transferTo" are subscribing to
balanceChangedflags 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.
0x0. And at the end of the migration process, ownership is transferred to the
GoodDollarReservecontract is also added.
GoodDollarReserve, the deployer account is being removed. **
0x0. And at the end of the migration process, ownership is transferred to
OneTimePaymentLinksare added to the list. During application lifetime, when a user has been validated (email, mobile and Face Recognition).