Document the wasm releases
Open
documentation :book:
low effort
low impact
must have eventually
solcbin
- Dominant language
- C++
- Stars
- 25.7k
- Forks
- 6.2k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 21
Description
We should document how the wasm releases are compiled, where they can be found, when we did the switch, what the requirements are, ...
Contributor guide
Research direction
No files, tests, or documentation entry points are named. Start by locating existing WASM build and release documentation, then trace how the release artifacts are compiled and published; document the compilation process, artifact location, switch timing, and requirements, with links to the relevant sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100