Cancelled for Q3 - Evaluate for Q4? Can community work on this?
Lets's see about moving this to Q4
Measure benchmark contract sizes before and after
Likely shared by Contract Runtime team
FAQ, Best Practices, possibly a progressively complex example exists outlining key concepts and practices
Define Fungible Token standard that is suited for Async Runtime composability.
Rework NFT Standard for Async Runtime Composability
- Expose general contract information such as description, source code
- Document Simulation Testing
- Introduce strict types.
Ability to compile contracts with `no_std` to decrease contract binary size
- Rework local examples
- Remove unnecessary dependency from `wasm` target.
Allows to get promise results that could fail or return invalid format
- Add rust doc examples to persistent collections
- Publish a doc with best practices
- Better use of Traits instead of global methods of `ext_contract` macro
A landing page exists in near-sdk-rs or docs (or both) describing how to write contracts so that they're easily upgradable. Also, how to upgrade a contract using tricks like #[init] to upgrade contracts.
Switch Runtime config to an updated config
- Simplify a way to add new host methods to Wasm Runtime through a feature and a protocol upgrade.
This allows logs to be used for Events
- Demonstrate how to use indexer as an example for a simple dApp
Setup a bounty/contract to create a Docker that setups a local node, explorer, wallet and indexer.
New updated fees are released to the mainnet
10 videos are published on Youtube
A video about Unit testing, Simulation testing and Testnet testing are published
A video(s) about Accounts and Access Keys with walkthrough NEAR examples.
A page/document with best-practices is published and regularly updated