Standardize DeWeb contracts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] Add [Smart-Contract](https://github.com/massalabs/DeWeb/tree/main/smart-contract) to [standards](https://github.com/massalabs/massa-standards/tree/main/smart-contracts/assembly/contracts) ...not sure about this
- [ ] Export and generation of [DeWeb SC bytecode ](https://github.com/massalabs/DeWeb/tree/main/cli/src/lib/website/sc) like for the [deployer](https://github.com/massalabs/massa-web3/tree/main/scripts/deployerGeneration) --> this might be chellenging as the wasm might often change (?) since it should be exported from standards ?
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
Compare the DeWeb smart-contract directory with the massa-standards smart-contracts/assembly/contracts directory first. Then inspect cli/src/lib/website/sc and massa-web3/scripts/deployerGeneration to determine how contract bytecode is exported and generated. Done means the DeWeb smart contract is standardized and its bytecode generation path is defined and working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, wasm
- Domain
- blockchain, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100