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.
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.
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
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.
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
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.
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
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
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
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
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
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.
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
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
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
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
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
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
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