Skip to content

feat: sharded FT contracts with deterministic addresses#1376

Draft
mitinarseny wants to merge 14 commits into
near:masterfrom
mitinarseny:feat/sharded-fungible-token
Draft

feat: sharded FT contracts with deterministic addresses#1376
mitinarseny wants to merge 14 commits into
near:masterfrom
mitinarseny:feat/sharded-fungible-token

Conversation

@mitinarseny

@mitinarseny mitinarseny commented Jul 13, 2025

Copy link
Copy Markdown
Contributor

Reference implementation of Sharded Fungible Token contracts

Originally discussed at: near/NEPs#607 (comment)
To be included in: NEP-636: Sharded Fungible Token standard

@github-project-automation github-project-automation Bot moved this to NEW❗ in DevTools Jul 13, 2025
@mitinarseny mitinarseny changed the title feat(sft): reference implementation feat: Sharded FT with deterministic addresses Jul 13, 2025
@mitinarseny mitinarseny changed the title feat: Sharded FT with deterministic addresses feat: sharded FT with deterministic addresses Jul 13, 2025
@mitinarseny mitinarseny changed the title feat: sharded FT with deterministic addresses feat: sharded FT contracts with deterministic addresses Jul 24, 2025
Comment thread examples/sharded-fungible-token/wallet/src/lib.rs Outdated
@ilblackdragon

Copy link
Copy Markdown
Member

Exciting progress here.

Given this is introducing new token standard - we should probably have the standard for that in NEP as well.
As part of that standard one request from my side is to think through how we can have private balances and transactions in the new standard.

Onchain privacy is becoming more important, especially with more adoption of crypto as payment rails. Given this new standard will require effectively full ecosystem overhaul - wallets, tooling, exchanges, it's a good time to think through all of the changes we would like to make.

gagdiez pushed a commit to near/NEPs that referenced this pull request Oct 10, 2025
Originally discussed at:
#607 (comment)

Read the NEP:
https://github.com/mitinarseny/NEPs/blob/deterministic-account-ids/neps/nep-0616.md

Reference implementations:
* `nearcore`: near/nearcore#14080
* `near-sdk-rs`: near/near-sdk-rs#1376

---
### NEP Status (Updated by NEP Moderators)

Status: Review

SME reviews:
- [x] @birchmd
#616 (review)
- [x] @mfornet
#616 (review)

Protocol Work Group voting indications (❔ | 👍 | 👎 ):

* [👍] @birchmd:
#616 (comment)
* [👍] @mfornet:
#616 (review)
* [👍] @bowenwang1996:
#616 (comment)

Meeting Info:

📅 Date: Wednesday Sep 24, 5pm UTC
✏️ [Register](https://luma.com/6r54kmpz?tk=lr8IIi)
@mitinarseny mitinarseny force-pushed the feat/sharded-fungible-token branch from 327ebe5 to fecf296 Compare December 26, 2025 16:59
@codecov

codecov Bot commented Dec 26, 2025

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 0% with 53 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.61%. Comparing base (de5c436) to head (efb2158).
⚠️ Report is 72 commits behind head on master.

Files with missing lines Patch % Lines
...standards/src/sharded_fungible_token/minter/mod.rs 0.00% 24 Missing ⚠️
...standards/src/sharded_fungible_token/wallet/mod.rs 0.00% 22 Missing ⚠️
...act-standards/src/sharded_fungible_token/events.rs 0.00% 5 Missing ⚠️
...t-standards/src/sharded_fungible_token/receiver.rs 0.00% 1 Missing ⚠️
...ards/src/sharded_fungible_token/wallet/governed.rs 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1376      +/-   ##
==========================================
+ Coverage   80.52%   80.61%   +0.08%     
==========================================
  Files         107      114       +7     
  Lines       15591    16955    +1364     
==========================================
+ Hits        12555    13668    +1113     
- Misses       3036     3287     +251     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: NEW❗

Development

Successfully merging this pull request may close these issues.

4 participants