marigold-dev / marigold-dev/deku
Proxy contract for consensus and discovery contract
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
The proxy contract is the big-map value where the key is the validator or bridge address and the value is the latest corresponding contract address. @oteku would like to integrate these contracts into Deku but I found some significant problems.
- Regarding the validator or bridge address, I can't find their definitions in Deku. From my perspective, we can create the `proxy-addresses.json` to represent these addresses.
- Regarding the security concerns, I think we can use the cryptographic mechanism in `Crypto.check` to be sure that these proxy addresses update the values in the proxy contract.
Contributor guide
No contributing guide indexed for this repository
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 by locating the validator and bridge address definitions in Deku, then read the existing Crypto.check mechanism. Assess the proposed proxy-addresses.json representation and how proxy address updates should be verified for consensus and discovery contracts. Done requires an agreed integration and security design, since the issue does not name an implementation file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100