Skip to content

Issues: near/NEPs

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

94 Open 63 Closed
94 Open 63 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Questions about NightShade document
#565 opened Sep 29, 2024 by xiaolese1
Explain what Simple Bounty template is for
#561 opened Aug 23, 2024 by mfornet
2
Shared contract code
#556 opened Aug 5, 2024 by bowenwang1996
17
On minimally volatile gas pricing
#544 opened Apr 26, 2024 by ilblackdragon
Reduce storage staking price by 10x S-rejected A NEP that was rejected by a working group.
#540 opened Mar 26, 2024 by bowenwang1996
11
Privacy with Chain Signatures
#531 opened Feb 18, 2024 by ilblackdragon
6
Wrapped NEAR v2
#530 opened Feb 14, 2024 by ilblackdragon
Proposal for web3-compatible wallets support A-NEP A NEAR Enhancement Proposal (NEP). S-review/needs-sme-review A NEP in the REVIEW stage is waiting for Subject Matter Expert review. WG-protocol Protocol Standards Work Group should be accountable
#518 opened Nov 15, 2023 by alexauroradev
20
Runtime triggers
#516 opened Nov 5, 2023 by bowenwang1996
37
Runtime: enable key prefix scan A-NEP A NEAR Enhancement Proposal (NEP). T-runtime About NEAR Protocol Runtime (actions, Wasm, fees accounting) WG-contract-standards Contract Standards Work Group should be accountable
#515 opened Oct 30, 2023 by robert-zaremba
4
Security Policy violation Branch Protection allstar
#512 opened Oct 22, 2023 by allstar-app bot
2
Problems with storage staking
#505 opened Sep 8, 2023 by akhi3030
7
Chain Signatures
#503 opened Sep 6, 2023 by DavidM-D
@akhi3030 @bowenwang1996
8
Atomic/Isolated/Synchronous transaction execution
#497 opened Aug 13, 2023 by norwnd
1
Guideline for bytes encoding for JSON input and outuput types (smart contracts) WG-contract-standards Contract Standards Work Group should be accountable WG-tools Tools Working Group should be accountable.
#490 opened Jul 25, 2023 by robert-zaremba
1
[DISCUSSION] Account extensions WG-protocol Protocol Standards Work Group should be accountable
#478 opened Apr 26, 2023 by firatNEAR
9
Change the implicit account creation flow after the introduction of zero balance account
#462 opened Feb 16, 2023 by bowenwang1996
2
[Discussion] add Royalties and Payouts mechanism to Multi Token standard
#453 opened Jan 27, 2023 by uncle-T0ny
nft_tokens exceed gas limits
#449 opened Jan 19, 2023 by codingshot
4
[PROPOSAL] Replace secp256k1 with pure Rust package libsecp256k1
#443 opened Dec 17, 2022 by russellwmy
[PROPOSAL] Audit for Circom-Ed25519 for standardization of NEAR ZK Light Client
#440 opened Dec 6, 2022 by garvitgoel
7
Support individual NFT metadata logs / dynamic NFTs
#438 opened Nov 24, 2022 by telezhnaya
1
Update spec to add support for alt_bn128_g1_multiexp, alt_bn128_g1_sum, and alt_bn128_pairing_check functions
#426 opened Nov 10, 2022 by akhi3030
Empty page on Transaction WG-protocol Protocol Standards Work Group should be accountable
#397 opened Sep 24, 2022 by zlog-in
1
Consider simplifying MT Metadata structure
#367 opened Jun 24, 2022 by telezhnaya
1
ProTip! Add no:assignee to see everything that’s not assigned.