mlabs-haskell / mlabs-haskell/majority-multisign
On-chain optimizations
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Unfortunately majority-multisign doesn't handle too many pub keys. 10 is the hardcoded max, removing this hard limit I reached 13 signatures, but over that I got budget overspent errors.
We could try optimizing the on-chain code with the few known tricks in Slab, or even try to rewrite it in Plutarch.
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 reproducing the hardcoded 10-key limit and the budget overspent errors reported beyond 13 signatures, then inspect the on-chain code and the Slab optimization techniques mentioned. Compare those options with a possible Plutarch rewrite; done means supporting more public keys without exceeding the on-chain budget.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100