Kirite

KIRITE is delivered as a Chrome extension, much like Phantom or MetaMask. You install it, click the icon in the toolbar, and use it as a normal Solana wallet. The only difference is that every transfer can go through the privacy layer. You don't need to know what a deposit, pool, or nullifier is to use it. Turn on privacy, paste the recipient's address, press send. That is all you have to do. The amount is encrypted, so no one outside can see it. The recipient's address is replaced with a one-time stealth address, so the real recipient is never exposed. A transfer happens in two steps. First, you send funds to a relayer. Then the relayer forwards them to the recipient. Because the two steps are signed by different signers, a block explorer cannot directly link "who sent to whom".

@soldatofortuna Let me check it out.

@KiriteDev Hey guys have you looked at concurrently launching a Firefox extension, not google but where I prefer to launch wallets for the privacy

chrome extension is in review. development continues in parallel. next: a telegram wallet bot. the point is two layers of privacy stacked together. layer 1 (off-chain): telegram handle replaces your wallet address. nobody asks for or sends to a solana address. layer 2 (on-chain): stealth address derived per transfer. no link between sender and receiver in the ledger. both layers running at once is a step closer to complete privacy.

@_dt777 I think opening a Telegram community would be the right move. I'll make an announcement about it soon.

@KiriteDev Do we have an X chat for the community ?

@AlphaGems_17 Our team is giving it our all. I'll keep making time to stay in touch with you all even while heads-down building.

@KiriteDev Good to see you finally reach out but this is really unacceptable. Need better communication and transparency if you guys are serious about the success of this project!

@BleatingSeal we'll share the moment development is complete. unlike chrome, the telegram bot doesn't require any approval process.

@KiriteDev Looking forward. When will the telegram handle wallet be ready ?

@AlphaGems_17 We'll share an update shortly.

@KiriteDev Hey Dev can we get a TG run buybot and do raids? So we can get some more attention!!!

KIRITE is delivered as a Chrome extension, much like Phantom or MetaMask. You install it, click the icon in the toolbar, and use it as a normal Solana wallet. The only difference is that every transfer can go through the privacy layer. You don't need to know what a deposit, pool, or nullifier is to use it. Turn on privacy, paste the recipient's address, press send. That is all you have to do. The amount is encrypted, so no one outside can see it. The recipient's address is replaced with a one-time stealth address, so the real recipient is never exposed. A transfer happens in two steps. First, you send funds to a relayer. Then the relayer forwards them to the recipient. Because the two steps are signed by different signers, a block explorer cannot directly link "who sent to whom".

@Riobaba7 Project's still in progress. Team's sleeping, will pick it back up around lunch.

@KiriteDev How could you go offline since..how do you want investors to trust your project when you aren’t being active

All documentation has been finalized. All tests have been completed. We're now waiting on final approval from Google, and development is on track.

No, it's not a relay network. KIRITE is a cryptographic privacy protocol running directly on Solana L1 — users sign and submit transactions themselves. Privacy comes from encrypted amounts, a shared commitment pool, and one-time stealth addresses, not from routing through relayers. A permissionless relayer layer can be added on top later for sender-side anonymity and gasless UX, but it's not required for the core privacy guarantees.

@KiriteDev Is it permissionless relay network?

3 things we hide: the amount you send the connection between sender and receiver the receiver's identity how it works: amounts get encrypted before touching the chain. the network sees a locked box, never a number. your deposit joins a shared pool. when you withdraw, matching the two sides is mathematically impossible. every payment generates a fresh one-time address. your real wallet stays invisible. all verified by math. zero-knowledge proofs running on solana's native L1 privacy primitives.

@KiriteDev Yo cool concept or wtv but does it just encrypt who the sender sent the crypto to?

We are in the process of updating our documentation to include a comprehensive usage guide for the KIRITE extension, along with detailed explanations of each feature and the mechanics behind them.

1/ KIRITE extension usage guide. 2/ Install the KIRITE extension from the Chrome Web Store, then create a new wallet or import an existing one with your seed phrase. Set a lock password for the extension, and your setup is complete. 3/ KIRITE works as a standard Solana wallet, just like Phantom or MetaMask. You can send SOL and SPL tokens, swap, and connect to dApps the same way you would with any ordinary wallet. 4/ To send privately, open the extension and turn on the Privacy toggle at the top. Paste the stealth meta address the recipient shared with you, enter the amount, and press Send. The extension handles encryption, commitment, proof, submission, and confirmation on your behalf. Once the completion screen appears, your transfer is done. 5/ On the receiving side, open the Receive tab and copy your stealth meta to share with the sender. To check incoming transfers, open Scan Inbox and press Start Scan. When a MAC-verified entry appears, press Sweep to move the funds into your main balance. 6/ After the transfer, you can look up your main address on Solscan and see that no direct trace of the transaction is left on it. The chain only records two independent transactions: the sender's deposit to the relayer, and the relayer's transfer to a one-time stealth address.

Our Solana program is live on mainnet. We are connecting it to the service now, and will publish a step-by-step guide as we go. Thanks for following along. solscan.io/account/4bUHrD…

If you are unsure about our project, please hand our GitHub link to an AI and ask it to read the code. We are confident in what we have built.

We would like to kindly ask one thing. Please look at the project itself, rather than at someone else's words. The contract address is public. The GitHub is open. 28 of 28 on-chain tests have passed. There is no admin withdrawal function, no multisig override, and no emergency drain. If you read the code yourself, you will see that a rug is not structurally possible with KIRITE. And if you are able, please take a look at how other privacy protocols work today. With other protocols, making a single private transfer means first depositing into a pool, then waiting, copying a nullifier receipt, saving it somewhere safe so it is not lost, switching to a new wallet, pasting the receipt back in, and only then being able to withdraw. In KIRITE, we have designed it so that the user never has to see any of this. Paste the address, enter the amount, press send. That is all. Deposit and withdrawal happen quietly inside the protocol, and the nullifier is a value that the user does not even need to know exists. This is precisely the part we have spent the last two months on. Rather than shouting, we believe it is faster to show you the design and the code directly. The mainnet deployment is currently underway. After launch, we would be truly grateful if you could try it once for yourself. Until then, the code and the tests will speak on our behalf.

We are currently in the process of deploying to mainnet.

We would like to respectfully inform you that the previous launch was not from our team. Unfortunately, a bot sniped and deployed it ahead of our official launch. We sincerely apologize for the confusion, and we kindly ask for your caution. However, we would like to respectfully confirm that this time, the launch is indeed official and has truly been conducted by our team. Thank you very much for your kind patience.

@SlipstreamPR @bleeko_eth Yes, we can confirm that today's launch is indeed official.

dex paid. solscan.io/tx/2RpLbz749d2…

@bleeko_eth We would like to respectfully inform you that this was not launched by our team. Unfortunately, a bot sniped and deployed it ahead of our official launch. We sincerely apologize for the confusion, and we kindly ask for your caution.

@KiriteDev Hearing you deployed a token 9 days ago, what’s up with that?