#near #polyfill #blockchain #reason #another #protocols #std


This crate contains polyfills which should really be in std, but currently aren't for one reason or another

14 releases (7 breaking)

new 0.22.0 May 17, 2024
0.21.2 Mar 14, 2024
0.20.1 Jan 23, 2024
0.19.0 Dec 21, 2023
0.15.0 Nov 21, 2022

#872 in Magic Beans

Download history 960/week @ 2024-01-29 1081/week @ 2024-02-05 1205/week @ 2024-02-12 1223/week @ 2024-02-19 993/week @ 2024-02-26 1117/week @ 2024-03-04 1195/week @ 2024-03-11 1132/week @ 2024-03-18 1317/week @ 2024-03-25 1281/week @ 2024-04-01 1321/week @ 2024-04-08 1308/week @ 2024-04-15 1451/week @ 2024-04-22 1010/week @ 2024-04-29 1255/week @ 2024-05-06 1444/week @ 2024-05-13

5,245 downloads per month
Used in 40 crates (4 directly)


109 lines

Reference implementation of NEAR Protocol

Buildkite Stable Status Prerelease Status codecov Discord chat Telegram Group

About NEAR

NEAR's purpose is to enable community-driven innovation to benefit people around the world.

To achieve this purpose, NEAR provides a developer platform where developers and entrepreneurs can create apps that put users back in control of their data and assets, which is the foundation of "Open Web" movement.

One of the components of NEAR is the NEAR Protocol, an infrastructure for server-less applications and smart contracts powered by a blockchain. NEAR Protocol is built to deliver usability and scalability of modern PaaS like Firebase at fraction of the prices that blockchains like Ethereum charge.

Overall, NEAR provides a wide range of tools for developers to easily build applications:

Join the Network

The easiest way to join the network, is by using the nearup command, which you can install as follows:

pip3 install --user nearup

You can join all the active networks:

  • mainnet: nearup run mainnet
  • testnet: nearup run testnet
  • betanet: nearup run betanet

Check the nearup repository for more details on how to run with or without docker.

To learn how to become validator, checkout documentation.


The workflow and details of setup to contribute are described in CONTRIBUTING.md, and security policy is described in SECURITY.md. To propose new protocol changes or standards use Specification & Standards repository.

Getting in Touch

We use Zulip for semi-synchronous technical discussion, feel free to chime in:


For non-technical discussion and overall direction of the project, see our Discourse forum:



stdx crate contains polyfills which should really be in std, but currently aren't for one reason or another.

No runtime deps