Supporting the ongoing innovation of the NEAR Protocol.

Protocol

# Who are we\\nWithin the NEAR ecosystem, Protocol refers to the layer 1 blockchain, the foundation of NEAR ([ref](https://nomicon.io/Architecture)); contributors of Protocol mostly work on nearcore Github repository, containing critical implementation powering NEAR protocol blockchain including chain, sharding, network, storage and runtime. Through various researches, investigations, and rigorous discussions, we aim to build secure, reliable, and scalable blockchain infrastructure, where the vision of Blockchain OS and innovative Web3 apps can live on. \\nIf you are interested in how NEAR blockchain works and want to make contributions, this is the place for you!\\n\\n# What is this space about\\nThis space aims to serve as an entry point to individuals, experts, and organizations who are interested in contributing to the ongoing innovation of the NEAR protocol. You will be able to find information about ongoing community programs, access to relevant documentations, and communication channels for you to participate in.\\n\\n# Community Groups\\nAs of now, the Protocol community consists of two groups: working group(PWG) and community group.\\n## Protocol working group\\nThis formal group is a selected committee of subject matter experts who make official decisions on proposals related to the NEAR protocol. They follow a strict process to review proposals, recommend funding to DAO or grant programs, and hold grant takers accountable. They engage with the broader community to understand their needs and encourage ideation. Due to its significance, we pay special attention to the member selection process and make sure that each member can bring unique perspectives and experiences to improve NEAR protocol. With great power comes great responsibility.\\n\\n### Current committee members\\nA protocol working group member will constantly seek a community member with deep expertise on how protocol works. When a qualified candidate is discovered, the committee goes through the nomination and alignment process to send an invitation.\\n\\nCurrent committee members are as follows:\\n* Bowen Wang ([Pagoda](https://www.pagoda.co/))\\n  * Near social: [woben.near](https://near.social/#/mob.near/widget/ProfilePage?accountId=woben.near)\\n  * Github: [bowenwang1996](https://github.com/bowenwang1996)\\n* Marcelo Fornet\\n  * Near social: [marcelo.near](https://near.social/#/mob.near/widget/ProfilePage?accountId=marcelo.near)\\n  * Github: [mfornet](https://github.com/mfornet)\\n  * Telegram: mnaeraxr\\n* Marcin Michalski ([Matter Labs](https://matter-labs.io/))\\n  * Github: [mm-near](https://github.com/mm-near)\\n* Michael Birch (Aurora)\\n\\n### Responsibility\\n* Make decisions on Near Enhancement Proposals(A.K.A NEPs)\\n* Budget allocation for protocol development initiatives including RFPs, security audits, etc. This includes review of funding requests.\\n* Steer the general direction of protocol development\\n\\n### Communication channels\\n* Attend Protocol work group calls\\n  * Please refer to Events tab\\n* Message on Telegram channel: [link](https://t.me/NEAR_Protocol_Community_Group)\\n* Post on NEAR.org and tag [Pagoda](https://near.org/near/widget/ProfilePage?accountId=pagodaplatform.near)\\n\\n## Protocol community group\\nCommunity group is an open group providing a space for anyone interested in changes to the NEAR protocol. Unlike the Protocol working group, the community group does not require any commitment or membership. It focuses on offering a place where members can freely ask questions, seek/offer support, exchange ideas and initiate discussions. All contributors to nearcore repository, including [Pagoda](https://www.pagoda.co/) protocol team members, are implicit members of the community, and actively participate in community discussions.\\n\\n### Ongoing projects\\n* [Protocol roadmap](https://medium.com/nearprotocol/q1-protocol-roadmap-update-progress-and-changes-e2d61626e4a1)\\n* Github \\n  * [Major projects](https://github.com/near/nearcore/labels/C-tracking-issue)\\n  * [Discussions](https://github.com/near/nearcore/discussions)\\n  * [PRs](https://github.com/near/nearcore/pulls)\\n* [Sponsored projects](https://near.social/#/devgovgigs.near/widget/gigs-board.pages.community.Sponsorship?label=protocol)\\n\\n### How to participate\\nThere are several ways to participate in community activities. Here are common examples. \\n#### You have a feedback to share with developers or want to initiate a discussion\\n* Create a topic in [Zulip pagoda/core stream](https://near.zulipchat.com/#narrow/stream/295558-pagoda.2Fcore)\\n* Protocol community group discussion board\\n\\n#### You want to know more about the NEAR protocol and have questions\\n* Ask a question in [Zulip pagoda/core/questions topic](https://near.zulipchat.com/#narrow/stream/295558-pagoda.2Fcore/topic/questions)\\n* As a question in [Protocol telegram](https://t.me/NEAR_Protocol_Community_Group)\\n* Protocol community group discussion board\\n* Post your question on [Near social](https://near.social/)\\n\\n#### You want to learn about NEAR protocol by working on a simple issue\\n* Request an onboarding task in [Zulip pagoda/core stream](https://near.zulipchat.com/#narrow/stream/295558-pagoda.2Fcore)\\n* Check out Github issues labeled with good-first-issue: [link](https://github.com/near/nearcore/labels/C-good-first-issue)\\n\\n#### You want to talk to Pagoda protocol team\\n* Simply start a conversation in [Zulip pagoda/core stream](https://near.zulipchat.com/#narrow/stream/295558-pagoda.2Fcore) and tag @ protocol\\n\\n#### You want to know more about proposals on protocol specification\\n* Visit [Github NEP board](https://github.com/orgs/near/projects/51/views/3) to see open/completed proposals\\n* Read through [Near Enhancement Proposal guideline](https://github.com/near/NEPs/blob/master/neps/nep-0001.md) to learn about NEP approval process how to submit a proposal\\n\\n#### You have an idea and want to request funding\\n* Please check \\u{2018}Event\\u{2019} tab\\n\\n#### You have found a bug on NEAR and want to claim reward via bug bounty program\\n* Please check \\u{2018}Event\\u{2019} tab\\n\\n### Communication channels\\n* Attend periodic Protocol community group calls\\n  * Please refer to Events tab\\n* [Telegram channel](https://t.me/NEAR_Protocol_Community_Group)\\n* [Zulip](https://near.zulipchat.com/#narrow/stream/295558-pagoda.2Fcore)\\n\\n# Documents\\nProtocol community maintains several documents/wikis so community members can stay informative and efficient to find what they are seeking for. Here are major worth noting ones.\\n\\n* [Guide to nearcore development](https://near.github.io/nearcore/index.html): Explains how each part of nearcore operates, e.g. how state sync, garbage collection, epoch works, how storage layer interacts with the layers on top, etc.\\n* [Nomicon](https://nomicon.io/): Near protocol specification\\n* [Near nodes](https://near-nodes.io/): Explains how near node works and how one can become a node operator \\n* [Near doc](https://docs.near.org/develop/welcome): Walks you through on how to develop on top of NEAR protocol, e.g. how to build a smart contract on NEAR\\n* [Rust](https://www.rust-lang.org/learn): Learn Rust, the programming language NEAR protocol is written in

	Receipt	Action	Method	From		To	Value	Gas Limit

거래 세부 정보

Overview

Execution Plan

Enhanced Plan

Tree Plan

Receipt Summary