Grantscommunity & ecosystem bucket · 10% of supply · 20M SNCT / year
0
SNCT reserved for builders · no equity · no control · unspent rolls forward

Ten percent of the supply funds people who ship privacy infrastructure the ecosystem needs. Grants go to working code on or for the network — not to decks.

202620M
202720M
202820M
202920M
203020M
annual cap · unspent balance rolls into the next year
01What gets funded
01high priority

Privacy dApps

Applications that use the shielded-transfer primitive — private payroll, confidential voting, sealed auctions, private DeFi.

02high priority

Developer tooling

SDKs, frameworks, test infrastructure, deploy scripts and wallets that make building on Sanect faster.

03medium priority

Bridges & integrations

Cross-chain bridges, oracle integrations, DEX protocols and liquidity connectors.

04medium priority

Research

Cryptographic research, privacy-preserving protocols, formal verification of the shielded pool.

05open

Education & content

Technical tutorials, workshops, translated docs and content that grows the developer base.

06open

Security & audits

Independent reviews of protocol components, formal verification, secure-development tooling.

02Size your grant

How big is the work?

Pick the honest scope and the tier follows. Tiers are about deliverables and review path, not about how much you would like.

Micro
up to5,000SNCT

Individual contributors. Tutorials, small tools, one-off integrations, translations.

milestonessingle deliverable
timeline1–2 weeks
approval~1 week
reviewed bycore contributors
Builder
5,000 –50,000SNCT

Small teams or solo devs. dApp MVPs, SDK features, tooling, research papers.

milestones2–4 milestones
timeline1–3 months
approval~2 weeks
reviewed bycore contributors
Protocolgovernance vote
50,000 –500,000SNCT

Established teams. Major integrations, full products, cryptographic research.

milestones4–8 milestones
timeline3–12 months
approval~4 weeks
reviewed bygovernance vote

Grants above Micro disburse per milestone. All funded work is open source.

03How to apply

Straightforward. No gatekeepers.

Applications live on GitHub so the process is public and the history is auditable. This is the shape of a good issue.

grant-application · issue template
Title: [grant] <project name>

Tier:        Micro | Builder | Protocol
Category:    Privacy dApp | Tooling | Bridge | Research | Education | Security
Team:        <handles — pseudonymous is fine>
Deliverables:
  1. <milestone, with a definition of done>
  2. <milestone>
Timeline:    <weeks per milestone>
Ask:         <SNCT, per milestone>
Address:     0x…
Links:       <repo, prior work>
01
Check scope and pick a tier

Make sure the project fits a funded category and size the grant to the work — the sizer above is the honest starting point.

02
Post in #grants

Three to five sentences: what you are building, why it matters for Sanect, what you need. Community feedback first.

03
Open a GitHub issue

Tag it grant-application. Include the project, team background (pseudonymous is fine), deliverables, timeline, and an SNCT address.

04
Review

Micro and Builder grants are reviewed by core contributors; Protocol grants go to a governance vote.

05
Ship and get paid

Deliver milestones publicly, receive SNCT on completion. All funded work is open source.

Ship something the network needs.