Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 0082-ETHD-ethereum-data-source.md #2277

Open
wants to merge 1 commit into
base: colosseo_II
Choose a base branch
from
Open

Update 0082-ETHD-ethereum-data-source.md #2277

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion protocol/0082-ETHD-ethereum-data-source.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ Select {
3. Create a market to use an external data source to terminate a market and an ethereum oracle to settle the market (<a name="0082-ETHD-017" href="#0082-ETHD-017">0082-ETHD-017</a>)
4. Create a market to use an open oracle data source to settle a market and an ethereum oracle to terminate the market (<a name="0082-ETHD-018" href="#0082-ETHD-018">0082-ETHD-018</a>)
5. Chain events should only be sent when the filter is matched, this can be verified using an API and the core/data node events (BUS_EVENT_TYPE_ORACLE_DATA) (<a name="0082-ETHD-019" href="#0082-ETHD-019">0082-ETHD-019</a>)
6. Ethereum oracle data sources should only forward data after a configurable number of confirmations (<a name="0082-ETHD-020" href="#0082-ETHD-020">0082-ETHD-020</a>)
6. Ethereum oracle data sources should only forward data after a Ethereum finality is assured (<a name="0082-ETHD-020" href="#0082-ETHD-020">0082-ETHD-020</a>)
7. Create 2 markets to use the same ethereum oracle for termination say DS-T1 but two different ethereum oracles for settlement DS-S1 and DS-S2. Now trigger the termination ethereum oracle data source. Both markets should be terminated and the data source DS-T1 is set to DEACTIVATED and the data sources DS-S1 and DS-S2 are still ACTIVE. Now settle market1. DS-S1 is set to DEACTIVATED and DS-S2 is still active. (<a name="0082-ETHD-021" href="#0082-ETHD-021">0082-ETHD-021</a>)
8. Create a market to use an ethereum oracle for termination configured such that - it expects a boolean value True for termination and the contract supplying the termination value is polled every 5 seconds. Set the contract to return False for termination. The market is not terminated. The data source is still ACTIVE and no BUS_EVENT_TYPE_ORACLE_DATA events for that ethereum oracle spec are emitted. Then set the contract to return True for termination. The market is terminated and an event for BUS_EVENT_TYPE_ORACLE_DATA for the ethereum oracle data spec is received and the ethereum oracle is set to DEACTIVATED. (<a name="0082-ETHD-022" href="#0082-ETHD-022">0082-ETHD-022</a>)
9. One oracle data event is emitted for data that matches each data source - Create 2 markets with ethereum oracle settlement specs that use the same settlement key such that - the first settlement spec expects settlement data to be greater than 100 and the second expects greater than 200. Now send it a settlement data of 300. One single event BUS_EVENT_TYPE_ORACLE_DATA for the settlement data is emitted for each matching ethereum oracle data sources i.e. in this case, two oracle data events will be emitted - one for each settlement data source. Both markets are settled and both the data sources are DEACTIVATED. (<a name="0082-ETHD-023" href="#0082-ETHD-023">0082-ETHD-023</a>)
Expand Down
Loading