Shielded pool on @Solana. Live on mainnet, open source. Unlinkable withdrawals not just hidden amounts. 4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump
Privacy
Joined September 2026
- Tweets457
- Following110
- Followers280
- Likes1.7K
KeepHost retweeted
Solana Mobile’s first hardware expansion partner is @Ledger.
The Seeker App, with the Solana dApp Store and wallet, will be integrated with Ledger’s new device.
Seekers, meet Ledger Atom. ⚛️🧵
KeepHost retweeted
Proud to be @solanamobile's first hardware expansion partner!
Solana Mobile’s first hardware expansion partner is @Ledger.
The Seeker App, with the Solana dApp Store and wallet, will be integrated with Ledger’s new device.
Seekers, meet Ledger Atom. ⚛️🧵
KeepHost retweeted
Japan's next wave of Solana builders is here 🇯🇵
Solana Student Bootcamp with @ChibaTech_web3 just kicked off with 4 sessions running through this month and next.
The energy is unreal.
How KeepHost works, in four lines.
01 - Your browser draws a receipt. We never see it.
02 - You deposit 0.1, 1 or 10 SOL, from any wallet or exchange.
03 - You wait. Others deposit.
04 - You withdraw anywhere. The proof says you own a deposit, not which one.
The link between the two addresses does not exist on chain.
keephost.fun
KeepHost V2 is live.
One site. One app. Same pool.
The program works on mainnet. The site around it was the problem: three versions stitched together, no guide, docs that looked like another site.
━━━━━━━━━━━━━━━
What is new
- One site instead of three versions
- A simple landing page, then the app
- A guide for your first deposit
- Docs, fixed
- A security page
- No third-party script from the old site builder
Our internal security review goes up next, as-is. AI-assisted, done by us. Not an external audit. With the plan for one.
━━━━━━━━━━━━━━━
Shipped since we came back
→ Our own review caught it: the deposit form showed a placeholder where your receipt should be. Fixed and live: the real receipt before you send, and again after. Every deposit so far is our own test.
→ Relayer upgraded. The activity feed shows each transaction once.
→ CI on GitHub is green: dependency check, tests, end-to-end on a local validator.
━━━━━━━━━━━━━━━
Conviction, on chain
Yesterday the creator bought 4,519,562.25 solana:4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump on the market, in two rounds, and burned all of it. By hand. Not a mechanism.
21,253,363.79 more are locked on Streamflow until 30 Oct 2040. Nobody can cancel it, not even him.
━━━━━━━━━━━━━━━
What does not change
Program: CTHg29kf7L6TNDH5TSd3tdoZfsmP39JjyQWKmPtEY1YW
- Three SOL pools: 0.1 / 1 / 10
- Nobody can pause deposits
- PDA vaults, no admin withdrawal
- Proof built in your browser
Exploring on devnet: confidential amounts with Helius' new privacy SDK. Nothing on mainnet.
━━━━━━━━━━━━━━━
No external audit yet. Deposit what you can lose.
Small sets are small sets.
Read the bytes.
We're not selling a chart. V2 is live. Proofs in the reply.
keephost.fun
CA : 4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump
KeepHost retweeted
if youre on Solana and haven't thought about @HeliusPrivacy, I humbly guarantee you will fall behind your competitors and your users' wants
ZK at Solana scale is a hell of a challenge, but we've done it and it will change Solana permanently
get in touch
bullish @HeliusPrivacy
look into the tech and implementation if you haven't yet. fully onchain, retail and enterprise ready
zolana
KeepHost retweeted
It's amazing to see that Solana was able to advertise and even get an office in China. 👏
@BNBChain was not able to do this, so far. 🤣
Hopefully, what's good for one industry player is also good for the rest.
KeepHost is back.
Visit : keephost.fun
━━━━━━━━━━━━━━━
→ 14 Oct, 11:22 UTC: the hold is lifted. The site is serving again.
→ 11:37 UTC: the creator locks 21,253,363.79 solana:4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump on Streamflow until 30 Oct 2040.
→ 11:51 UTC: the creator buys 1,141,101.88 solana:4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump on the market and burns all of it.
━━━━━━━━━━━━━━━
The burn
Bought on PumpSwap, burned inside the same minute. Second creator burn, after 924,625.62 on 24 Sep.
Supply on chain now: 948,392,133.14 of 1,000,000,000. 51.6M burned since launch, 2.07M of it by the creator.
No fee did this. No mechanism. One wallet, market buys, a burn.
The lock
21.25M, 2.24% of supply. It unlocks to the creator's own wallet on 30 Oct 2040, all at once, not a day before. Nobody can cancel it, not even him.
Creator wallet right now: 0 liquid tokens.
━━━━━━━━━━━━━━━
The site went dark. The program didn't.
Program: CTHg29kf7L6TNDH5TSd3tdoZfsmP39JjyQWKmPtEY1YW
- Live on mainnet since 23 Sep
- Three SOL pools: 0.1 / 1 / 10
- Pause authority renounced on all three. Nobody can pause deposits.
- PDA vaults, no admin withdrawal. Funds move only with a valid proof.
- Groth16, verified on chain
- Source public, MIT
━━━━━━━━━━━━━━━
The mint woke up
178 transactions on the mint today by 12:10 UTC.
From 4 to 13 Oct: 1 to 9 a day.
To the ones who held while the link was dead: this one is yours.
━━━━━━━━━━━━━━━
No audit yet. Deposit what you can lose.
Small sets are small sets.
Read the bytes.
We're not selling a chart. We're back, the burn is on chain, the lock runs to 2040. The proofs are in the reply.
keephost.fun
CA : solana:4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump
KeepHost retweeted
It's time. ⛰️
It’s time.
Alpenglow goes live on mainnet-beta Wednesday, October 21, ~14:50 UTC.
18 months of work for a migration that happens in one slot. Finality drops from seconds to ~150ms.
Make sure to follow us @anza_xyz as we countdown to go-live.
Details: anza.xyz/alpenglow
KeepHost retweeted
KeepHost is coming back.
The pool never left mainnet.
Program: CTHg29kf7L6TNDH5TSd3tdoZfsmP39JjyQWKmPtEY1YW
- Three fixed-denomination SOL pools: 0.1 / 1 / 10
- PDA vaults with no private key
- No admin withdrawal path
- Deposits and withdrawals unlinkable by construction
- Source still public
━━━━━━━━━━━━━━━
What changed while we were quiet
→ Public ceremony for the proving key is the priority. Single-machine setup risk goes away the moment one honest contributor finishes the open phase.
→ Association sets: prove membership in a chosen clean set without revealing which deposit. Written, tested, ready for the next deploy.
→ SPL support (USDC + tokenized assets): same tree, circuit and relayer, vault as token account. Tested end-to-end.
━━━━━━━━━━━━━━━
New layer: local private agents
On-device AI that never touches the cloud.
Models like Liquid's LFM2.5-24B-A2B (24B total, ~2B active, 131K context, explicit chain-of-thought, strong on tool-use/agent benchmarks, fast on consumer hardware) let you:
- Generate and manage receipts locally
- Analyze your anonymity set and withdrawal timing without sending data anywhere
- Run private multi-step workflows against the pool (proof prep, set selection, receipt recovery logic) entirely on your machine
Same non-custodial rule: the agent runs where you are.
━━━━━━━━━━━━━━━
Nothing about the guarantees changed
The vault still has no key.
The relayer still can't redirect.
The link still doesn't exist on-chain.
Token CA: 4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump
Fees still fund the pool and future burns.
Audit is still the next external stamp, not the thing that makes the code real.
━━━━━━━━━━━━━━━
Deposit what you can lose.
Small sets are small sets.
Read the bytes.
We're not selling a chart. We're shipping the next private layer.
The pool is already there. The agents are next.
Privacy is the only narrative on @solana that isn’t exhausted.
ZEC has the ETF. Solana still publishes who paid whom.
Confidential transfers hide the amount and leave the graph intact.
That’s the gap everyone is trying to sell this week: shielded pools, fee-to-ZEC routers, “privacy flywheels.”
Most of them are the same object: a @Pumpfun fee wallet with a Zcash story on top.
A dashboard is not a reserve. A tweet that says “2.2 SOL is in shielded ZEC” is not a viewing key.The meta is real. The wrappers are not.
If you can’t follow fee → vault → native ZEC → payout on explorers you don’t control, you’re not in a protocol.
You’re in a story. NFA.
Read the chain.
KeepHost retweeted
Thinking about flights, visas or hotels?
@mauricedotxyz has you covered with helpful tips for London
🔐 Just locked 21,253,364 solana:4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump tokens with @Streamflow_Fi
It's on-chain. You can check the amount, time-period and recipients.
Check it out👇
app.streamflow.finance/contr…
KeepHost retweeted
Folks thought the project is dead but the dev was always working in the background 🔥
4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump
KeepHost is coming back.
The pool never left mainnet.
Program: CTHg29kf7L6TNDH5TSd3tdoZfsmP39JjyQWKmPtEY1YW
- Three fixed-denomination SOL pools: 0.1 / 1 / 10
- PDA vaults with no private key
- No admin withdrawal path
- Deposits and withdrawals unlinkable by construction
- Source still public
━━━━━━━━━━━━━━━
What changed while we were quiet
→ Public ceremony for the proving key is the priority. Single-machine setup risk goes away the moment one honest contributor finishes the open phase.
→ Association sets: prove membership in a chosen clean set without revealing which deposit. Written, tested, ready for the next deploy.
→ SPL support (USDC + tokenized assets): same tree, circuit and relayer, vault as token account. Tested end-to-end.
━━━━━━━━━━━━━━━
New layer: local private agents
On-device AI that never touches the cloud.
Models like Liquid's LFM2.5-24B-A2B (24B total, ~2B active, 131K context, explicit chain-of-thought, strong on tool-use/agent benchmarks, fast on consumer hardware) let you:
- Generate and manage receipts locally
- Analyze your anonymity set and withdrawal timing without sending data anywhere
- Run private multi-step workflows against the pool (proof prep, set selection, receipt recovery logic) entirely on your machine
Same non-custodial rule: the agent runs where you are.
━━━━━━━━━━━━━━━
Nothing about the guarantees changed
The vault still has no key.
The relayer still can't redirect.
The link still doesn't exist on-chain.
Token CA: 4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump
Fees still fund the pool and future burns.
Audit is still the next external stamp, not the thing that makes the code real.
━━━━━━━━━━━━━━━
Deposit what you can lose.
Small sets are small sets.
Read the bytes.
We're not selling a chart. We're shipping the next private layer.
The pool is already there. The agents are next.
KeepHost is coming back.
The pool never left mainnet.
Program: CTHg29kf7L6TNDH5TSd3tdoZfsmP39JjyQWKmPtEY1YW
- Three fixed-denomination SOL pools: 0.1 / 1 / 10
- PDA vaults with no private key
- No admin withdrawal path
- Deposits and withdrawals unlinkable by construction
- Source still public
━━━━━━━━━━━━━━━
What changed while we were quiet
→ Public ceremony for the proving key is the priority. Single-machine setup risk goes away the moment one honest contributor finishes the open phase.
→ Association sets: prove membership in a chosen clean set without revealing which deposit. Written, tested, ready for the next deploy.
→ SPL support (USDC + tokenized assets): same tree, circuit and relayer, vault as token account. Tested end-to-end.
━━━━━━━━━━━━━━━
New layer: local private agents
On-device AI that never touches the cloud.
Models like Liquid's LFM2.5-24B-A2B (24B total, ~2B active, 131K context, explicit chain-of-thought, strong on tool-use/agent benchmarks, fast on consumer hardware) let you:
- Generate and manage receipts locally
- Analyze your anonymity set and withdrawal timing without sending data anywhere
- Run private multi-step workflows against the pool (proof prep, set selection, receipt recovery logic) entirely on your machine
Same non-custodial rule: the agent runs where you are.
━━━━━━━━━━━━━━━
Nothing about the guarantees changed
The vault still has no key.
The relayer still can't redirect.
The link still doesn't exist on-chain.
Token CA: 4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump
Fees still fund the pool and future burns.
Audit is still the next external stamp, not the thing that makes the code real.
━━━━━━━━━━━━━━━
Deposit what you can lose.
Small sets are small sets.
Read the bytes.
We're not selling a chart. We're shipping the next private layer.
The pool is already there. The agents are next.
Privacy is the only narrative on @solana that isn’t exhausted.
ZEC has the ETF. Solana still publishes who paid whom.
Confidential transfers hide the amount and leave the graph intact.
That’s the gap everyone is trying to sell this week: shielded pools, fee-to-ZEC routers, “privacy flywheels.”
Most of them are the same object: a @Pumpfun fee wallet with a Zcash story on top.
A dashboard is not a reserve. A tweet that says “2.2 SOL is in shielded ZEC” is not a viewing key.The meta is real. The wrappers are not.
If you can’t follow fee → vault → native ZEC → payout on explorers you don’t control, you’re not in a protocol.
You’re in a story. NFA.
Read the chain.
KeepHost retweeted
Privacy is the only narrative on @solana that isn’t exhausted.
ZEC has the ETF. Solana still publishes who paid whom.
Confidential transfers hide the amount and leave the graph intact.
That’s the gap everyone is trying to sell this week: shielded pools, fee-to-ZEC routers, “privacy flywheels.”
Most of them are the same object: a @Pumpfun fee wallet with a Zcash story on top.
A dashboard is not a reserve. A tweet that says “2.2 SOL is in shielded ZEC” is not a viewing key.The meta is real. The wrappers are not.
If you can’t follow fee → vault → native ZEC → payout on explorers you don’t control, you’re not in a protocol.
You’re in a story. NFA.
Read the chain.
KeepHost retweeted
KeepHost is going on dedicated bare metal.
No shared kernel. No hypervisor in the middle. Isolated net, ECC, IPMI.
The server can die. The pool cannot.
Receipts stay yours. The vault has no key.
KeepHost is moving onto bare metal like this.
Not a VPS. Not a neighbour on the same kernel.
A single-tenant machine.
The site, the relayer, the ceremony files they will sit on hardware nobody else shares. Isolated segment. ECC memory. Enterprise disks.
IPMI so the box can be wiped and rebuilt without a ticket.Scanning and scraping are allowed by policy on that kind of host.
That is the point: the machine can be treated as hostile and rebuilt, and the pool still does not care.
Funds are not on the server. They are on a PDA with no private key.