The program is live. The site is live. Dev just ran 36 hours straight and still told everyone not to send the treasury a single lamport.
That’s the kind of build I actually want to use.
Pool’s up. Ceremony’s open. Receipts stay yours. Nothing waits on anyone being awake.
https://t.co/1RPWW7AXM0 — go read the bytes yourself
36 hours non-stop, going dark for a few.
The program is live. The site is live. The next pieces are already written and sitting in tests: fees, the burn key, SPL pools, the page rebuild.
Those tests need a clean machine and a clean head. I am stepping off for a few hours. The pool stays up. The ceremony stays open.
Nothing on-chain waits on me being awake.
Posts are queued.
Use the site. Read the bytes.
Do not send the treasury anything.
https://t.co/0eFWiCDLy2
CA: 4c1XZRqFV6y8pAckHru5oiGPYUFw1eQ3kFotPLHrpump
USDC is next, and the code for it is already written and tested.
A KeepHost pool can now hold any SPL token. Same tree, same circuit, same proof, same relayer the vault becomes a token account owned by an address with no private key, and that is the entire difference.
Tested against a mint shaped like USDC: three deposits in, a withdrawal out to a fresh account, the same receipt refused the second time.
Not open yet. It opens with the next deploy, which waits on the trusted setup being redone in public and that one needs contributors, not buyers.
https://t.co/KnDFcmqvhE
KeepHost now takes any SPL token, not just SOL.
Same tree, same circuit, same proof, same relayer.
The only difference is that the vault is a token account owned by an address with no private key, instead
of an address with no private key holding lamports.
Tested against a mint shaped like USDC: three deposits in, a withdrawal out to a fresh token account, and the same receipt refused the second time.
This is what the front page owed. It promised tokenised assets while the pool
took SOL and nothing else that gap is closed in code, and the pools open with the next deploy.
https://t.co/KnDFcmqvhE
36 hours in: mainnet program, browser deposits and withdrawals, a relayer, the source public with a green CI, and SPL pools tested and waiting on the next
deploy.
Most projects are still writing a whitepaper at this point.
The slow part left is the trusted setup, and that one is slow on purpose.
Three things shipped since yesterday, all in the repo.
1. The token does something now. A deposit pays 0.5%, held on its own address.
Burn KEEPHOST and you get a key: that wallet never pays the fee again. Those fees pay the relayer at withdrawal — so a withdrawal returns the whole denomination, funded by the people who did not burn.
2. Any SPL token can have a pool. Same tree, same circuit, same proof, same relayer; the vault becomes a token account owned by an address with no private key. Tested with a mint shaped like USDC.
3. The program went from 518 kB to 437 kB by talking to the token program directly instead of through a library. On Solana that is rent paid for ever it halved the cost of the upgrade.
Every line of it passes an end-to-end test against the exact binary that will be deployed: deposit, proof, withdrawal, and the same receipt refused twice.
https://t.co/KnDFcmqvhE
Started with a little computer in a beanie.
Now FINNPUTER is part of the @intel Partner Alliance and live in the Intel Partner Showcase.
Pretty wild seeing us in there.
270k+ wallets rated, wallet groups mapped, every call ranked. What should we build next? 👀
https://t.co/V3cOZ0ItfM
Hat stays on. 🧢
You can see FINNPUTER on INTEL website here 👇
https://t.co/nOHlUWmjvz