paritytech / paritytech/contract-dependency-manager
Feedback Collection
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 3
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
2/15/26
- contract source should be uploaded to bulletin & be verifiable
2/24/26
- wants to be able to call on-chain functions from cli
- should be possible to implement this with auto-complete using ABI
2/26/26
- contract source should be uploaded to bulletin & be verifiable
- frontend code should be on-chain & verifiable as well
- frontend code is not necessarily verifiable the same way contract code is. But its interesting to think about peoples expectation for frontend related features, so we should probably lean into that, especially with solid frontends in templates.
- should this & dotns be the same underlying 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 reviewing the feedback about bulletin verification, CLI access to on-chain functions through ABI auto-completion, verifiable frontend code, templates, and whether this and dotns should share an underlying contract. No files, tests, or entry points are identified, so first define the scope and acceptance criteria with the maintainers. Done should specify which requested capability is being implemented and how it will be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, cli, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100