MainView
Report abuse
Use this data
Sign up for free
Key Results
Lead
Quarter
2021 Q3
Count16
1
Hackathon support plan and schedule has been published and executed for Hackathons occurring in Q3.
2
Publish the table of contents for the Rust 1.0 book to the internal/external communities for review and feedback.
3
Publish a zero-to-hero document for a Web2.0 developer building their first contract. Prove the concept with feedback from hackathon participants.
4
Improve create-near-app to use lang-specific project setup.
5
Zig and Grain SDK alpha releases.
6
Publish multi-token standard in conjunction with community development and support.
7
CLI modular framework is released and documented.
8
CLI validator functionality is released as a module within the new CLI framework.
9
CLI 2.0 specification is documented and released to the internal/external communities.
10
CLI alpha version is released for internal consumption and feedback.
11
CLI support for price feed (Cross Functional) --Need more information about this.
12
Sim tests have been deprecated. Cross-functional teams have been informed and educated.
13
Release Beta Sandbox with documentation.
14
Contract internals (methods/return vals ) can be found by users. (Metadata ACI)
15
Contract sizes are reduced
16
Contract gas/storage costs are reduced
17
Reduce contract costs 2x (calls, deployments, etc) without sacrificing safety
18
NEAR SDK documentation covers all things from ToC
19
There are no kludges in the interop between near-api-js and nearcore
20
Zero boilerplate while writing contracts using NEAR SDKs
21
Simulation tests can dry run state and accurately estimate storage and gas
22
New projects do not have interruptions requiring direct team input while developing
23
Persistent collections are clear and explained where differences exist with typical collections
24
NFT standard is plug-and-play
25
Storage Management is plug-and-play
26
New Fungible Token Standard
27
NFT Standard
28
Define Contract Metadata Standard
29
Improve Simulation Testing
30
Introduce strict types for balances, gas, etc
31
Introduce `no_std` mode
32
Improve examples
33
Improve contract compilation time
34
Introduce `callback_result` macro
35
Add examples to Rust Docs
36
Publish Best Practices
37
Improve high-level cross-contract API
38
Contract upgradability: examples, advice
39
Upgrade Runtime Fees Config
40
Ability to add new host methods
41
Add alt-bn128 curve as host methods
42
Support Binary logs
43
Explain how to use indexer
44
[Bounty] Docker for local development including indexer
45
Improve/fix fees config on mainnet
46
Record educational content about Contracts
47
Record educational content about Testing
48
Record educational content about NEAR specific concepts
49
Publish contract development best-practices
Objectives
1) Empower new NEAR developers to more easily build on NEAR
4
Objectives
2) Expand language/standards support for NEAR
2
Objectives
3) NEAR CLI is a strength for developing on NEAR
5
Objectives
4) Contract diagnostics experience matches Ethereum experience.
3
Objectives
5) Release path for highly optimal contracts
2
Quarter
2021 Q2
Count9
Objectives
Complex projects know how to build on NEAR
5
Objectives
Complex projects know how to start building on NEAR
2
Objectives
NEAR standards library comparable with OpenZeppelin
2
Quarter
2021 Q1
Count19
Objectives
Define Standards
3
Objectives
Improve NEAR SDK Rust
10
Objectives
Improve Runtime
4
Objectives
Showcase Indexer
2
Quarter
2020 Q4
Count5
Objectives
Improve Runtime
1
Objectives
Scale NEAR-specific knowledge
4
Cannot adjust frozen columns; click to learn more or reset
Type
Completeness
Notes
Committed
100%
Committed
100%
Aspirational
45%
Aspirational
0%
Committed
50%
Committed
50%
Committed
100%
Committed
80%
Committed
100%
Aspirational
80%
Aspirational
0%

Cancelled for Q3 - Evaluate for Q4? Can community work on this?

Committed
50%
Committed
100%
Aspirational
0%

Lets's see about moving this to Q4

Committed
50%

Measure benchmark contract sizes before and after

Committed
70%
Aspirational
3%
Committed
40%
Committed
15%
Aspirational
5%
Aspirational
20%

Likely shared by Contract Runtime team

Aspirational
25%

FAQ, Best Practices, possibly a progressively complex example exists outlining key concepts and practices

Committed
70%
Committed
100%
Aspirational
100%
Committed
100%

Define Fungible Token standard that is suited for Async Runtime composability.

Committed
100%

Rework NFT Standard for Async Runtime Composability

Aspirational
0%

- Expose general contract information such as description, source code

Committed
90%

- Document Simulation Testing

Aspirational
0%

- Introduce strict types.

Aspirational
80%

Ability to compile contracts with `no_std` to decrease contract binary size

Committed
30%

- Rework local examples

Aspirational
0%

- Remove unnecessary dependency from `wasm` target.

Committed
0%

Allows to get promise results that could fail or return invalid format

Aspirational
0%

- Add rust doc examples to persistent collections

Committed
0%

- Publish a doc with best practices

Aspirational
0%

- Better use of Traits instead of global methods of `ext_contract` macro

Committed
0%

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.

Committed
0%

Switch Runtime config to an updated config

Aspirational
100%

- Simplify a way to add new host methods to Wasm Runtime through a feature and a protocol upgrade.

Aspirational
100%


Aspirational
0%

This allows logs to be used for Events

Aspirational
100%

- Demonstrate how to use indexer as an example for a simple dApp

Committed
50%

Setup a bounty/contract to create a Docker that setups a local node, explorer, wallet and indexer.

20%

New updated fees are released to the mainnet

100%

10 videos are published on Youtube

0%

A video about Unit testing, Simulation testing and Testnet testing are published

0%

A video(s) about Accounts and Access Keys with walkthrough NEAR examples.

0%

A page/document with best-practices is published and regularly updated

49 records

Alert

Lorem ipsum
Okay