oasisprotocol / oasisprotocol/oasis-core
Deterministic builds
Open
Nobody has claimed this yet.
c:build
p:2
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
ENCLAVEHASH needs to be consistent across independent builds. Otherwise clients have no way to verify that the source code matches up to the enclave
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
No files, tests, or entry points are named. Start by locating how ENCLAVEHASH is produced during independent builds and determine what build inputs affect it. Done means independent builds produce a consistent ENCLAVEHASH that clients can use to verify the source code matches the enclave.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100