Stealth Pay

Infrastructure for confidential onchain payments #BuiltOn0G

[Stealth Pay @stealth_pay]

Stealth Pay is live on mainnet.

Private payments on-chain. No relayer. No trusted party. Just math.

🧵

[Stealth Pay @stealth_pay]

Day 35 of #BuildOn0G

5 weeks in.

privacy layer: live. SDK: published. docs: complete. playground: running real transactions.

the protocol is the foundation. what gets built on top is the interesting part.

open to builders who want to ship private payments on 0G.

[Stealth Pay @stealth_pay]

Day 34 of #BuildOn0G

0G Storage is what makes the hint system work without a relay server.

sender encrypts the note with the receiver's public key, uploads to 0G Storage.
receiver's sync() scans, finds it, decrypts automatically.

on-chain storage for encrypted data.

[Stealth Pay @stealth_pay]

first private transaction with Stealth Pay:

install SDK
configure pool address and spending key
call shield()

estimated time to first real ZK transaction: under 30 minutes

[Stealth Pay @stealth_pay]

Day 33 of #BuildOn0G

private payroll walkthrough is live in the docs.

shield the total once. distribute to each employee's spending pubkey. employees unshield on their own schedule.

three SDK calls. HR data stays off-chain. no salary discovery on-chain.

[Stealth Pay @stealth_pay]

you cannot generate a valid proof for a note you don't own

not because the contract prevents it

because the circuit prevents it

the math won't produce a valid witness without the spending key that matches the commitment

[Stealth Pay @stealth_pay]

how the tree sync works:

SDK reads PrivacyPool events from last synced block
each Shield event: one leaf inserted
each Spend event: nullifier marked used
local root matches on-chain root

no API. no server. just events.

[Stealth Pay @stealth_pay]

Day 32 of #BuildOn0G

the playground now shows the full code diff — live call + complete integration code — updating as you type.

pick an operation, fill a param, copy the snippet.

the gap between "trying it" and "shipping it" is one file.

https://t.co/hmiwYfOZRD

[Stealth Pay @stealth_pay]

client-side proving means your user's browser is the proving server

no cloud infra needed
no cost per proof on our side
no single point of failure for proof generation

you own the entire execution stack

[Stealth Pay @stealth_pay]

proof size for a spend: ~2KB

that's the entire cryptographic argument that you own two notes, they're in the tree, the math balances, and the nullifiers are valid

2KB proves everything the chain needs to know

[0G 中文社区 (Ø,G) @0g_CN]

0G APAC 黑客松已圆满落幕，评审工作正在紧锣密鼓地进行中。
The 0G APAC Hackathon has successfully concluded, and the judging process is now in full swing.

在过去的两个月里，我们共同见证了：
• 亚太地区 295 份技术项目提交
• 线上 8 周的 Builder Hour 与 Workshop AMA 交流
• 线下横跨亚太 5 大城市的 Builders Open AI Day
Over the past two months, we have witnessed:
• 295 technical project submissions from the APAC region
• 8 weeks of online Builder Hours and Workshop AMA sessions
• Offline Builders Open AI Days spanning across 5 major APAC cities

这一切始于一个核心发问：要构建真正可验证、兼顾隐私且原生上链的 AI Agent，还有哪些底层痛点尚待解决？
It all started with one core question: To build AI Agents that are truly verifiable, private, and native on-chain, what underlying pain points remain to be solved?

从智能体基础设施、可验证交易，到智能体经济、Web 4.0 与主权隐私 —— 亚太开发者用行动诠释了 0G 为何是“为 AI Agent 而生的区块链”。致敬亚太开发者的硬核交付，感谢大家一路同行。
From agent infrastructure and verifiable transactions, to agent economies, Web 4.0, and sovereign privacy — APAC developers have demonstrated through action why 0G is "the blockchain built for AI Agents." Salute to the hard-core delivery of our APAC developers, and thank you all for walking this journey with us.

项目：
Projects:
@Agentra69
@AIsphere0G
@AlphaJournal_
@AetherCredit
@TrustFolio_0G
@LokiLabsAi
@MDLOG_labs
@coal_payments
@MemoriaDA_
@SealedMind_0G
@SunflowerLau27
@synapsemesh
@blindmarkt
@Ivaronix
@VAMVault_
@herald_protocol
@Ghast_AI
@stealth_pay
@Wraith__DA
@NeoSoulAI
@ayushsaklani976
@Lineage_0G
@yieldgeko
@zer0Gig
@0gclawforge
@Proof__Pay
@0xgents
@zerovulntech
@0arena_labs
@GhostProver

贡献者：
Contributors:
@zax_raider
@emmanuel_haanks
@czar_skah
@alhadji_ACE
@rajkaria_
@GroverInnovate
@Vigothecreator
@encrypt_wizard
@czar_skah
@bapeetttt
@Armanibanks100
@exluminated
@kurokurohitam

Build For 0G APAC Hackathon! Build on 0G!

[Stealth Pay @stealth_pay]

Day 31 of #BuildOn0G

the repo is public. the circuits are readable. the verifier key is derivable.

anyone can recompile the Noir circuits and confirm the deployed verifier matches.

"don't trust, verify" is not a slogan here. it's an instruction.

https://t.co/hmiwYfOs25

[Stealth Pay @stealth_pay]

Poseidon2 was designed specifically for ZK circuits

SHA256 is expensive to prove inside a circuit
Poseidon2 is not

this is why the Merkle tree uses Poseidon2 and not the hash everyone knows

[Stealth Pay @stealth_pay]

a ZK proof has two input categories:

public inputs : the chain sees these
private inputs : the chain never touches these

your spending key, your amount, your salt: all private inputs

the proof says: these private inputs satisfy the circuit. nothing else.

[Stealth Pay @stealth_pay]

Day 30 of #BuildOn0G

30 days. shipped.

ZK circuits in Noir. UltraHonk proofs verified on-chain.
TypeScript SDK on npm. live playground on 0G Galileo.

everything is open source. try it, audit it, build on it.

https://t.co/hmiwYfOZRD

[Stealth Pay @stealth_pay]

banks compete on privacy

they don't share your balance with your competitors

crypto is the first financial system where your competitor can check your position in real time, for free

[Stealth Pay @stealth_pay]

inheritance is a private matter

estate planning is a private matter

on-chain, both are reconstructable from the moment of the first transaction

permanent public records have permanent personal consequences

[Stealth Pay @stealth_pay]

MEV is a privacy problem before it's an economics problem

front-running exists because pending transactions are visible before they land

private transactions remove the surface before any MEV solution is needed

[Stealth Pay @stealth_pay]

Day 29 of #BuildOn0G

privacy should not be a product feature. it should be a protocol guarantee.

if you rely on a privacy policy, you are trusting a person.
if you rely on a ZK proof, you are trusting math.

math does not change its mind.

https://t.co/hmiwYfOs25

[Stealth Pay @stealth_pay]

protocol treasury management, publicly visible:

your runway is estimatable
your vendor relationships are mapped
your market moves are front-runnable

none of that needed to be public

[Stealth Pay @stealth_pay]

the gap between crypto people and everyone else on privacy:

crypto people: "public wallets are fine, I have nothing to hide"

everyone else: "I will not put my real finances somewhere that makes them public"

one of these is wrong about adoption