oasisprotocol / oasisprotocol/oasis-core
Byzantine node should have a test for malicious txn sched signing different batches
Open
Nobody has claimed this yet.
c:testing
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
There should be a test where the transaction scheduler signs different batches for the same compute committee to test the code in addOpenComputeCommitment in go/roothash/api/commitment/pool.go.
Details
Verification for this malicious behaviour on the Ekiden side is in PR #1908.
Acceptance Criteria
- Test exists.
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 go/roothash/api/commitment/pool.go and the addOpenComputeCommitment code path. Review PR #1908 for the Ekiden-side verification, then locate the existing transaction scheduler and compute committee tests. Done means a test covers a malicious scheduler signing different batches for the same compute committee.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 39/100