marigold-dev / marigold-dev/deku
consensus contract + tickets contract
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
## Problem
When adding tickets we need to have a communication link that reads the data of the consensus contract. But because reading data from another contract on Tezos is not straightforward and it is quite error prone we should do tickets inside of the consensus contract.
This means multiple entry points each one operating on a different piece of data.
## Possible future solutions
This could be achieved in different ways by making so that the consensus contract also updates the relevant data on the tickets contract.
## Related Issues
- #34
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
The issue does not name files, tests, or entry points. Start by reviewing related issue #34 and locating the consensus and tickets contract implementations. Define the required contract entry points and data flow before estimating or implementing the change.
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
- 20/100