[DOC] Mention alternative contract SDKs
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 186
- Forks
- 493
- Avg merge
- 29d 5h
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Developers do not know about alternative contract development options, which provide different benefits to them.
Evidence:
Describe the solution you'd like
It would be great to have a page for alternative contract development options:
- Raw Wasm crafting (only useful for deep low-level understanding) - https://gist.github.com/vgrichina/48c7cf061032a3508a3e180e823f1637
- Tiny Rust SDK -
nesdie, example - Rust low-level example - https://github.com/fastnear/small-proxy-contract
- Zig low-level example - https://gist.github.com/vgrichina/10ea303ab1bbf3d4069cd30d28f6340e
We may also mention Aurora here in the context of, alternatively to Wasm, one could target EVM and write contracts in Solidity
Contributor guide
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 contract-development documentation section in the near/docs repository and review its existing page structure. Add a page covering raw Wasm, nesdie, the Rust and Zig low-level examples, and Aurora as an EVM/Solidity option, with the links from the issue; done means these alternatives are clearly presented to developers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, solidity, wasm, zig
- Domain
- blockchain, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100