events
when something meaningful happens within the smart contract that the smart contract wants to communicate to dapps and other smart contracts. The developers of the smart contract decide when these events are emitted. For example - when somebody sends an ERC20 token - the token contract will emit a Transfer
event containing all of the data about the transfer.bet(address,uint256,bool)
0x20d932006281d267f137cd3921b707c2097e1f041b1291181cc3d0e86f449ebb
_
don't work for now_, _like for example "name": "_side"
will not work, and you'll have to change it to "name": "side"
in order to make it work."Sync_historical (Optional)
option will be disabled and no historical data will be saved. It is possible to contact support to upgrade your account to enable saving it anyway but think hard about whether it's actually necessary before doing so. It's possible to handle the events in real-time without saving the data to the database.tableName
. Boo-urns! Yes, this is inconvenient, but how plugins work will be changing soon anyway when the custom plugin platform is released and this will then be reexamined (so at least there's that to look forward to!).price
is equal to 80000000000000000
:{"eq": ["price", "80000000000000000"]}
sender
= 0x0
AND receiver
= 0x0
sender
= 0x0
OR receiver
= 0x0
sender
= 0x0
AND amount
= 1000
) OR (receiver
= 0x0
AND amount
= 100
)<name>_decimals
fields to run comparisons (like greater than/less than):watchContractEvent(options)
. You can call it using the master key.