oasisprotocol / oasisprotocol/oasis-core
Economics around Pre-execution: who pays for pre-execution, transaction aborts due to mis-predicted read/write sets, etc.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
With the horizontal scheduling design, we need to determine the economics:
[ ] Who pays for pre-execution to get predicted read/write sets?
[ ] If a txn aborts because the real read/write set differs, who pays for the aborted execution? Do we re-submit into the queue (and do we recompute the read/write sets [who pays])?
[ ] Who pays for the transaction scheduler, merge, and other "internal" committees? Are these optional? Can others submit transaction results to merge?
For each of these design questions/choices, what are the API changes (if any) needed to handle them?
Are there other economic design questions / choices?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the horizontal scheduling design and the three listed economics questions. Map each decision to any required API changes, including handling predicted read/write sets, aborted transactions, and internal committees. Done means the economic choices, remaining questions, and API impact are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100