base on Reference client for NEAR Protocol <br /> <br /> <p align="center"> <img src="docs/images/logo.svg" width="240"> </p> <br /> <br /> ## Reference implementation of NEAR Protocol [![Build][build-badge]][build-url] ![Stable Status][stable-release] ![Prerelease Status][prerelease] [![codecov][codecov-badge]][codecov-url] [![Discord chat][discord-badge]][discord-url] [![Twitter][twitter-badge]][twitter-url] [![Telegram Group][telegram-badge]][telegram-url] [build-badge]: https://github.com/near/nearcore/actions/workflows/ci.yml/badge.svg?branch=master [build-url]: https://github.com/near/nearcore/actions [stable-release]: https://img.shields.io/github/v/release/nearprotocol/nearcore?label=stable [prerelease]: https://img.shields.io/github/v/release/nearprotocol/nearcore?include_prereleases&label=prerelease [ci-badge-master]: https://badge.buildkite.com/a81147cb62c585cc434459eedd1d25e521453120ead9ee6c64.svg?branch=master [ci-url]: https://buildkite.com/nearprotocol/nearcore [codecov-badge]: https://codecov.io/gh/near/nearcore/branch/master/graph/badge.svg [codecov-url]: https://codecov.io/gh/near/nearcore [discord-badge]: https://img.shields.io/discord/490367152054992913.svg [discord-url]: https://discord.com/invite/nearprotocol [twitter-badge]: https://img.shields.io/twitter/follow/NEARProtocol [twitter-url]: https://x.com/NEARProtocol [telegram-badge]: https://cdn.jsdelivr.net/gh/Patrolavia/telegram-badge@8fe3382b3fd3a1c533ba270e608035a27e430c2e/chat.svg [telegram-url]: https://t.me/cryptonear ## 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][open-web-url]. 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: - [JS Client library][js-api] to connect to NEAR Protocol from your applications. - [Rust][rust-sdk] and [JavaScript/TypeScript][js-sdk] SDKs to write smart contracts and stateful server-less functions. - [Several essential repositories](https://github.com/near/dx) to guide you in building across Near's Open Web Platform. - [Numerous examples][examples-url] with links to hack on them right inside your browser. - [Lots of documentation][docs-url], with [Tutorials][tutorials-url] and [API docs][api-docs-url]. - [NEAR Protocol formal specification][nomicon-io], and [docs for nearcore developers][nomicon-io]. [open-web-url]: https://techcrunch.com/2016/04/10/1301496/ [js-api]: https://github.com/near/near-api-js [rust-sdk]: https://github.com/near/near-sdk-rs [js-sdk]: https://github.com/near/near-sdk-js [examples-url]: https://github.com/near-examples [docs-url]: https://docs.near.org [tutorials-url]: https://docs.near.org/tutorials/welcome [api-docs-url]: https://docs.near.org/api/rpc/introduction [nomicon-io]: https://nomicon.io ## Join the Network To learn how to become a validator, checkout [documentation](https://near-nodes.io/validator/staking-and-delegation). ## Contributing The workflow and details of setup to contribute are described in [CONTRIBUTING.md](CONTRIBUTING.md), and security policy is described in [SECURITY.md](SECURITY.md). To propose new protocol changes or standards use [Specification & Standards repository](https://github.com/nearprotocol/NEPs). ## Getting in Touch We use Zulip for semi-synchronous technical discussion, feel free to chime in: https://near.zulipchat.com/ For non-technical discussion and overall direction of the project, see our Discourse forum: https://gov.near.org ", Assign "at most 3 tags" to the expected json: {"id":"6113","tags":[]} "only from the tags list I provide: []" returns me the "expected json"