Shielded pool on Solana. Live on mainnet, open source. Unlinkable withdrawals not just hidden amounts. 4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump
- Tweets 389
- Following 99
- Followers 265
- Likes 1,398
This is your reminder from @nabu_lines that you can swap seamlessly in Ledger Wallet with @okx.
what are you swapping? 🟢⚫️
26
22
169
14,956
KeepHost retweeted
The cryptographic world computer:
vitalik.eth.limo/general/202…
My attempt to express in somewhat concise terms the true meaning of basically everything planned to happen to Ethereum starting from the fork after Hegota. It's really not just a blockchain anymore. It's a hybrid architecture that combines together blockchains and modern cryptography, to enable much more powerful properties.
FOCIL, EIP-8288, Lean consensus, state management, formal verification, advanced mempool improvements (including privacy), and the longer-term specter of obfuscation all mentioned.
436
723
4,392
810,267
KeepHost retweeted
I can't believe someone social-engineered the whole CT into believing GIWA did a stealth mainnet launch and has gone away with $2 million in ETH.
@zachxbt come do your job.
65
3
172
87,952
KeepHost retweeted
INSIGHT: @solana currently leads all chains in weekly active users.
19
29
188
5,398
KeepHost retweeted
No, the project isn’t abandoned. I was building.
Please stop listening to people who glance at the GitHub and invent a story. What we shipped takes a lot of time a real code review / audit is several days, not a scroll.
We don’t manipulate the chart. Fees go to the pool / treasury (rent, relayer, audit when it can be paid). I’m not a trader. I’m a builder. I can show the code, the program, the treasury on-chain.
Anyone can buy or sell. The chart is public. I’m not responsible if someone else trades it.
Look at the repo and the chain, not the rumors.
8
8
24
1,120
KeepHost retweeted
i’ve always liked SOL, but this cycle could broaden the opportunity beyond just holding SOL
SOL had huge runs across multiple cycles while a lot of the surrounding DeFi and infra trades struggled to capture the same upside
now more users and capital are moving onchain, and the ecosystem has had years to mature
that makes the broader Solana ecosystem a lot more interesting to me this time around
282
129
1,427
187,286
KeepHost retweeted
An independent review of the code found a real one, an hour ago.
Anyone could have permanently locked someone else's deposit, for the cost of a few lamports.
How: a deposit event's discriminator is public, and so is a pool address. You could emit a lookalike event from your own program, in a transaction that just mentions the pool. The client folded that fake leaf into the Merkle tree, built a root the program had never stored, and every withdrawal after it failed — permanently, because the log stays in chain history.
Funds locked is as bad as funds stolen.
The detail worth reading: the client checked the pool address but not which program emitted the log. The relayer checked the program but not the pool address. Each one did exactly the half the other skipped. That is the kind of thing you do not see when you wrote both.
Both now check both. Fixed, pushed, relayer restarted, and verified against mainnet — the pool still reads its leaves correctly.
github.com/KeepHost/system/c…
The review also cleared the parts that matter most: the receipt randomness, the address encoding, the ordering of the nine public inputs, and a hostile relayer's inability to redirect a withdrawal, raise its fee or replay a proof.
This is what the open challenge is for. There is still 0.5 SOL sitting in the pools with no key holder, and the rules are in CHALLENGE.md.
1
3
10
334
Back from building, newsletter is on way
Why solana:4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump exists, since the thread above is about code.
It is not a share. It pays nothing. The pool takes no token to use - anyone can deposit and withdraw without holding one.
What it did: its creator fees paid the rent Solana charges to store this program.
Not a roadmap item, not a promise - the transaction that put a working shielded pool on mainnet.
Someone bought a token, and a program that nobody holds a key to went live because of it.
What it does next, in this order:
· the redeploy carrying the new proving key and association sets
· funding the relayer, so withdrawals stay free for the people using them
· an external audit, the moment the treasury covers one
Treasury: 3.35 SOL, read from the chain every fifteen seconds on the front page.
Every fee lands there and nowhere else. Watch the number instead of trusting anyone.
That is the whole pitch. A token that funded something that works, and pays for what it still needs.
CA 4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump
pump.fun/coin/4c1XZRqFV6y8pA…
keephost.fun
1
9
686
KeepHost retweeted
logs will bite everyone eventually, any program can print anything it likes. anchor's emit_cpi puts the event in an inner instruction instead, so the program id travels with it and a lookalike can't fake that part. nice that it came out of a review and not a stuck withdrawal
1
4
71
KeepHost retweeted
most people don't have the patience nor foresight to hold coins to multi-billions from launch, but we've done this for multiple cycles in a row now, this time will be no different :)
glad to have you along for the ride brudda
67
36
385
20,676
Who said summer school was a bad thing?
Solana Summer School was an epic journey of education, building, and shipping.
Huge thanks to the faculty and students who made Solana Summer School possible.
Take a look here:
solana.com/news/solana-summe…
134
56
513
128,431
The right question isn't whether to use AI agents for finance.
It's who holds the keys when they act.
Ledger Wallet CLI keeps that answer simple: your agent proposes, your hardware approves, nothing moves without your physical intent.
Same principle as every Ledger signer. Now for the agentic era.
26
18
143
21,218
KeepHost retweeted
solana:4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump nearly back to ath. Safe to say this will send way past that. Buckle up. Dev isn’t stopping
$KEEPHOST
6
5
27
1,498
Why solana:4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump exists, since the thread above is about code.
It is not a share. It pays nothing. The pool takes no token to use - anyone can deposit and withdraw without holding one.
What it did: its creator fees paid the rent Solana charges to store this program.
Not a roadmap item, not a promise - the transaction that put a working shielded pool on mainnet.
Someone bought a token, and a program that nobody holds a key to went live because of it.
What it does next, in this order:
· the redeploy carrying the new proving key and association sets
· funding the relayer, so withdrawals stay free for the people using them
· an external audit, the moment the treasury covers one
Treasury: 3.35 SOL, read from the chain every fifteen seconds on the front page.
Every fee lands there and nowhere else. Watch the number instead of trusting anyone.
That is the whole pitch. A token that funded something that works, and pays for what it still needs.
CA 4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump
pump.fun/coin/4c1XZRqFV6y8pA…
keephost.fun
Three days on KeepHost. The most useful thing that happened was a bug we did not ship.
An independent review was pointed at the program, the circuit, the client and the relayer. One instruction: take the money, or lock it.
What it caught before deployment: the new fee would have broken the 0.1 SOL pool for everyone except token holders. The fee account is never funded, and the fee on that pool falls under Solana's rent-exempt minimum, so every deposit would have been rejected while holders, whose fee is zero, would have sailed through. A pool that works for insiders and fails for everyone else is the worst screenshot on this chain. It never reached mainnet.
What it cleared, if you write programs here: no under-constrained signal in the circuit. All seven binding signals survive compilation and all ten IC points in the verifying key are live, so a public input cannot be swapped against a fixed proof. The nine public inputs are in the same order on both sides. Every PDA is checked. No cross-pool substitution works. The tree insert was rewritten from scratch and matched leaf by leaf. No path moves a lamport out of a vault without a valid proof.
Also written since: association sets. A withdrawal can prove its deposit belongs to a set you choose the thing that keeps a shielded pool from being a mixer. The circuit carries the set root as a tenth public input. It ships with the next deploy.
That deploy waits on one thing, and it is not code. The proving key still comes from this project's own machines. Two contributions. Both ours. One person from outside, two minutes:
curl -L -o pot_in.ptau keephost.fun/ceremony/pot15_…
npx snarkjs powersoftau verify pot_in.ptau
npx snarkjs powersoftau contribute pot_in.ptau pot_out.ptau --name="your handle" -v
github.com/KeepHost/system
2
5
19
2,902