<asset, value>pairs on different times.
<asset, value>pair within the Merkle tree, the index of the
<asset, value>within the leaves array of the Merkle tree, and the parameters of the Merkle tree), and the oracle contract has to attest for the global proof data (the timestamp, the root of the Merkle tree, and the oracle service public key), which would send the Fixed Payout contract an attestation token which will give the redeemer the right for the collateral when found in the wallet of the Fixed Payout contract, since the attestation token is the embodiment of the attestation of the oracle on the occurrence and details of the event.
"Issue"command while providing it with a dictionary in the message body which contains the following data:
"Collateral"field in the message body) which were provided to it in the TX by the issuer, and will mint and lock to the issuer the same amount of position tokens of both kinds (so if the issuer supplies the contract with
mcollateral tokens - the contract will mint and lock to the issuer
mBear tokens and
mBull tokens based on the event).
"Redeem"command while providing it with a dictionary in the message body which contains the following data:
<asset, value>pair to the root of the tree
<asset, value>pair in the Merkle tree
"OracleContractId"which commits to the data specified in
"Position"- to redeem a Bull position provide the contract with Bull tokens, and make sure the attested value is above the price specified in
"Price"or equal to it; to redeem a Bear position provide the contract with Bear tokens, and make sure the attested value is below the price specified in
"Timestamp"is within the time bounds specified in
"AuditPath"is valid for the Merkle root specified in
"Root"for the leaf given by the
"Ticker"key with the specified
"Value"in the specified
[[event data ; position]]
"Cancel"command and send the contract an equal amount of both position tokens, the same amount of collateral will be sent back to you and the given position tokens will be destroyed.