Himess (@Himess__) profile picture

Protocol & Full-Stack Engineer Multi-hackathon winner 🏆 Building privacy, DeFi & agentic systems FHE • Web3 • AI

İstanbul, Türkiye
Joined January 2020
Photo by Himess (@Himess__)Photo by Himess (@Himess__)Photo by Himess (@Himess__)Photo by Himess (@Himess__)Photo by Himess (@Himess__)Photo by Himess (@Himess__)Photo by Himess (@Himess__)Photo by Himess (@Himess__)Photo by Himess (@Himess__)Photo by Himess (@Himess__)
I build privacy & payment protocols across FHE, ZK, DeFi and agent payments. Four of my projects ended up winning along the way. 🏆 Here’s a quick look at the winning builds ↓ 🧵
2
28
2,319
Himess retweeted
⊢ let's have an update from the privacy era: - @ambire shipped @0xprivacypools transfers in its main release, with 0xBow and Kohaku support, visibility into anonymity protection, and tx history generated entirely on-device. - @fhenix activated coFHE on ethereum and arbitrum. dual-mode tokens for switching between public and confidential states are in development and USDG-backed $FUSD and yield-bearing $FUSDY are planned for december. - @FlutonIO is live on arbitrum. you can deposit $ETH/ $USDC and make private payments using zk and fhenix's cofhe for encrypted balances. deposits and withdrawals remain public. - @tacitfi made tacit. wei fully onchain and immutable. eth is split into standard tornado denominations for a larger anonymity set, with swaps supported for any token. - @cakewallet added offline shielded $ZEC signing to cupcake. an old phone can now sign txs without bringing private keys online. - @aztecnetwork reached stage 2 decentralization with tierra V6. normal network operations no longer rely on centralized team control. - @P_Inference built a 26-model ai chat on aztec with private cUSDC payments through nulo. sender, recipient, and amount stay hidden onchain. the public beta and api are live. - @unicity_labs is working on proof CLI for proving document ownership and history, and audit capsule for logging agent events. migration from PoA to PoS is underway. unicity qatar has been established, cooperation efforts with ooredoo have started, and major government discussions in oman and egypt are ongoing. - @Himess__ built an encrypted account prototype using @zama's fhe. the PIN stays encrypted in the contract and some transfers still require it even if the seed leaks. PIN guesses are limited. it's on sepolia and unaudited for now. - @citrea_xyz plans to migrate its rollup proofs and clementine bridge to @SuccinctLabs's sp1 in the nov 23 pomelo upgrade. nodes must update by nov 25. and what about @NEARProtocol: - @near_ai offers tee inference with verifiable attestation. gteway now includes red team sandbox for code security testing with models that have no refusal restrictions. - near business offers confidential multisig treasury management across 35+ networks, with batch payments, swaps, and yield. permanent deposit addresses are now available alongside one-time addresses. - @near_intents powers features in unstoppable wallet, leoDEX, and circuit, including $BTC invoice payments with zec, private swaps, and automated agent trading.
28
12
4
95
2,691
New post on Eth Research! Encrypted Account: a PIN that lives in the contract By: - Himess 🔗 ethresear.ch/t/26265 Highlights: - The design is an ERC-4337 smart account that stores a PIN-derived fingerprint on-chain as a ciphertext and verifies guesses using threshold FHE, so no server ever holds the PIN or enforces rate limits. - Its core trick is “count first, reveal after”: the contract increments an on-chain wrong-guess score before the (encrypted) success bit is allowed to be decrypted, preventing offline brute force and limiting online attempts (simulated to ~12 guesses per 30 days under default rules). - A stolen signing key is deliberately low-power: it can only send to pre-approved addresses within per-asset daily limits; new recipients, large amounts, approvals, or arbitrary calls require the PIN plus a time delay (e.g., 1 hour / 48 hours by default). - Wrong PIN attempts can be made economically painful via an external ETH bond that doubles with each miss; incorrect guesses forfeit the bond into the account, meaning a thief with only the key pays the owner for failed guessing. - There is a non-FHE “escape hatch”: the key alone can start an emergency sweep to a pre-consented address after a long delay (e.g., 30 days), which still works even if the FHE/threshold network is unavailable; the whole system is a testnet-only, unaudited research prototype on Sepolia under MIT license. ELI5: Imagine your crypto wallet has a secret PIN, but instead of a company server checking it, the wallet’s smart contract checks it by itself. The PIN is stored in a locked, scrambled form (encrypted) so nobody can read it, and the contract can still compare your PIN guess to the real one. Each time someone guesses, the contract counts the guess first and only then allows the network to reveal whether it was right—so attackers can’t download the data and try millions of PINs offline. If someone steals your key, they can only do small “allowed” payments; anything risky needs the PIN plus a waiting period, and wrong PIN guesses cost the attacker money that goes into your account. There’s also an emergency “escape” that can move funds to a pre-chosen safe address after a delay, even if the encryption network is down.
3
6
548
Just added protection against physical attacks to Encrypted Account. A second "duress" PIN: - Opens a small decoy vault; only that can move - Looks just like the real PIN on-chain - Silently alerts a contact who can call the police Your real balance stays hidden ERC-7984
I built Encrypted Accounts on Ethereum with @zama Most wallet security trusts something outside the chain: 2FA → trusts your phone Email recovery → trusts your inbox Hardware wallet → trusts a device I wanted something different. So I put a 6-digit PIN check inside the smart contract, encrypted with FHE. Anything unusual (new address, big amount) and the contract asks for your PIN. Seed phrase leaked? Key stolen? Email hacked? Doesn't matter, they still can't steal your funds. "But 6 digits is easy to brute force" Not here. Every guess gets counted on-chain before the answer comes back, and the waits keep growing. That's ~12 tries a month, max. And your PIN never leaves your device. A few more things it does: ✅ your limits and trusted addresses are encrypted, so a thief can't even see the rules ✅ phishing signatures are useless, a permit signed with the key alone is void ✅ key leaked? hit escape and after 30 days everything goes to your backup address What I'm working on next: → Steal this wallet: a funded Sepolia account with a public seed phrase. Take it if you can → private transfers + a duress PIN → hidden inheritance → AI agents that hold the key while you hold the PIN It's a research prototype, live on Sepolia, not audited yet. Open source. Try it 👇 encrypted-account.vercel.app
1
1
8
435
What if getting hacked paid you? Seed phrase stolen? They still need your PIN. Every wrong guess costs them ETH, doubles each time, and stays in your account. Hit Escape and your funds go to your safe address. PIN checked onchain with FHE, on Ethereum testnet with @zama 👇
5
12
790
Most onchain privacy is rented! The ciphertexts never leave the chain, and the curves that protect them won't survive Q-Day. Whoever stores them today can read them later. Privacy that lasts has to be post-quantum from day one!
1
185
Trade your shielded $ZEC for confidential USDC on Ethereum, without ever unshielding it. No bridge. No custodian. No wrapped ZEC. And the amount never shows up on chain. I connected @zama and @Zcash to make it work. Live on testnet 👇 What it is ZEC Desk is a small trading desk on Zama's FHEVM, on Ethereum Sepolia. On one side there's cUSDC, a dollar token whose balances are encrypted. On the other side there's shielded ZEC on Zcash testnet. You can trade either way. Built on Zama's model Zama's Confidential RFQ is already live on Ethereum mainnet, open to everyone: app.zama.org/swap It runs confidential swaps with encrypted quotes, a sealed-bid pick on chain and a hidden floor. ZEC Desk takes that same model and extends it to native shielded ZEC. Zama's swap settles both legs on one chain, inside its own contract, so a Zcash leg can't plug into it directly. Here that leg lives on Zcash and settles minutes later with a proof, so the mechanics run in my own contract. It's a sketch of how native ZEC could sit next to Zama's swaps one day, with no wrapped token. How a trade works (buying ZEC) 👇 1️⃣ You lock cUSDC in the desk. The amount is encrypted. 2️⃣ Makers send encrypted quotes. Nobody sees anyone else's price, or the minimum you'll accept. 3️⃣ The contract picks the best one under FHE. 4️⃣ The winning maker sends shielded ZEC to your Zcash address, with the order's reference in the memo. 5️⃣ A zero-knowledge proof shows that payment happened, and the contract releases your cUSDC to the maker. If no proof arrives in time, your cUSDC comes back to you. Selling is the same in reverse: the maker locks cUSDC, you pay the ZEC, and the proof releases the cUSDC to you. Why these pieces Each piece does one job. Zcash keeps the payment private. Zama keeps the amounts encrypted and can still compute on them. Seam, the Zcash light client I built last month, connects the two: a contract checks every Zcash block header itself, and a RISC Zero proof shows a shielded payment reached the right receiver. The transaction, the note and the address never touch the EVM chain. The masked amount This was the hard part. Seam's proof used to write the paid amount in the clear, and ZEC amount × price gives away the dollar amount. So the amount is masked. The contract adds an encrypted one-time mask to the encrypted amount and reveals only the sum, which looks random to everyone else. The mask comes from a secret that the side receiving the ZEC hands to the payer. The proof checks that the payment was at least the sum minus the mask, and never states the amount. One-time pads are old, and Zama's RFQ uses one too. Using one to hand a value from FHE to a ZK proof is the part I haven't seen before. If you have, please send it my way. No vault, no signers Seam can read Zcash, but it can't take ZEC from anyone. So the design never needs someone to pay ZEC on someone else's behalf. Whoever pays, pays from their own wallet, and the escrow on the EVM side enforces the deal. The side that paid the ZEC can prove it itself, so nobody depends on the other side's goodwill. Seam does more than this Any EVM app that needs to know a shielded payment happened can use Seam: pay-with-ZEC checkouts, escrows, payouts, cross-chain orders. This desk is one example. Where it stands ↓ Testnet only, unaudited. On 12 November 2026 I ran a Buy end to end: ➡️ Settled with a proof: sepolia.etherscan.io/tx/0x27… ➡️ One proof: 2 minutes on a rented RTX 4090, about $0.25 for the whole session ➡️ Gas per Buy on Sepolia: about 7.6M, in six transactions ➡️ A Sell also ran on Sepolia, up to the maker locking its cUSDC; it settles through the same proof step ➡️ Seam's light client is now deployed on Ethereum Sepolia too, next to Base Sepolia Where it can go ↓ → The desk only needs Zama's FHEVM and a cUSDC. Both already run on Polygon, where following Zcash costs a fraction of Ethereum mainnet. → Zama keeps adding chains. On any cheap EVM chain it reaches, the same desk can run, and if it comes to Base, Seam's relay already runs on Base Sepolia. → Zama's roadmap also goes beyond the EVM, to chains like Solana. Seam's verifier would need a port there. → On Ethereum mainnet, following Zcash header by header would cost over 2B gas a day, so batched header proofs are next for Seam. What it can't do yet - Settlement takes minutes, not seconds. Zcash confirmations set the pace, not the GPU. - Right now I'm the only maker, and a maker needs ZEC, cUSDC and a GPU. - Amounts are hidden, but EVM addresses are public. Read more ↓ Seam on ethresear.ch: ethresear.ch/t/seam-verifyin… Seam: github.com/Himess/seam ZEC Desk: github.com/Himess/zec-desk
5
1
19
1,641
New feature: hidden inheritance on Ethereum with ERC-7984 and @zama Your PIN is your proof of life. Stop entering it for months and your heirs inherit. One correct PIN during the grace period cancels it. → Who your heirs are, what they get, even how many there are: all encrypted. Not even you can look it up later. → Each heir gets a printable card with a QR code and a secret claim code. Keep it with your will. → When the time comes, they scan it and claim to any wallet they like, even a brand new one. → Anyone can hit claim. Heirs get their share, everyone else an encrypted zero, and from the outside it all looks the same. → Key stolen and you had to escape? The will comes with you to your backup address. The Sepolia demo runs on 5-minute timers so you can try the whole flow 👇 encrypted-account.vercel.app…
I built Encrypted Accounts on Ethereum with @zama Most wallet security trusts something outside the chain: 2FA → trusts your phone Email recovery → trusts your inbox Hardware wallet → trusts a device I wanted something different. So I put a 6-digit PIN check inside the smart contract, encrypted with FHE. Anything unusual (new address, big amount) and the contract asks for your PIN. Seed phrase leaked? Key stolen? Email hacked? Doesn't matter, they still can't steal your funds. "But 6 digits is easy to brute force" Not here. Every guess gets counted on-chain before the answer comes back, and the waits keep growing. That's ~12 tries a month, max. And your PIN never leaves your device. A few more things it does: ✅ your limits and trusted addresses are encrypted, so a thief can't even see the rules ✅ phishing signatures are useless, a permit signed with the key alone is void ✅ key leaked? hit escape and after 30 days everything goes to your backup address What I'm working on next: → Steal this wallet: a funded Sepolia account with a public seed phrase. Take it if you can → private transfers + a duress PIN → hidden inheritance → AI agents that hold the key while you hold the PIN It's a research prototype, live on Sepolia, not audited yet. Open source. Try it 👇 encrypted-account.vercel.app
3
1
11
761
Why FHE, not ZK? A will runs after you're gone. In ZK only the secret holders can update private state, and then nobody holds them all. With FHE the chain computes on encrypted state, splitting late deposits by hidden shares. Trade-off, you trust Zama's threshold network.
64
Replying to @Himess__ @zama
Why hide the heirs and not just the amounts? ERC-7984 already hides amounts, but only until a known heir unwraps. The sensitive part of a will is who's in it and who isn't. An open list would sit on-chain for years and tell attackers whose wallet to phish.
91
Really like what @Helius shipped with Privacy Rings. Private transfers settle in one Solana transaction. No sequencer, no L2, full Solana speed. Amounts are hidden, and so is which token moved. Prove locally and nothing private leaves your machine, or use their TEE prover if you'd rather not run one. Congrats to the team 👏 We need a lot more privacy apps and infra.
Today, Solana changes forever Introducing Solana Privacy Rings - encryption at the speed of Solana Rings are programmable, onchain environments for encrypting money, markets, and finance - without ever leaving Solana Now live on mainnet.
1
4
296
I built Encrypted Accounts on Ethereum with @zama Most wallet security trusts something outside the chain: 2FA → trusts your phone Email recovery → trusts your inbox Hardware wallet → trusts a device I wanted something different. So I put a 6-digit PIN check inside the smart contract, encrypted with FHE. Anything unusual (new address, big amount) and the contract asks for your PIN. Seed phrase leaked? Key stolen? Email hacked? Doesn't matter, they still can't steal your funds. "But 6 digits is easy to brute force" Not here. Every guess gets counted on-chain before the answer comes back, and the waits keep growing. That's ~12 tries a month, max. And your PIN never leaves your device. A few more things it does: ✅ your limits and trusted addresses are encrypted, so a thief can't even see the rules ✅ phishing signatures are useless, a permit signed with the key alone is void ✅ key leaked? hit escape and after 30 days everything goes to your backup address What I'm working on next: → Steal this wallet: a funded Sepolia account with a public seed phrase. Take it if you can → private transfers + a duress PIN → hidden inheritance → AI agents that hold the key while you hold the PIN It's a research prototype, live on Sepolia, not audited yet. Open source. Try it 👇 encrypted-account.vercel.app
9
1
1
44
2,768
Bug bounties are drowning in AI spam. curl shut its own down in January. So I built one that doesn't read reports. It runs them. Agents are welcome. Spam isn't. Prove the bug, and NEAR pays automatically. Antibody, built at NEAR HACKATHON @NEARProtocol #NEARHackathon
2
4
488
What's next: • NEAR contracts as targets, beside EVM • Payouts in any asset through NEAR Intents • Zero-knowledge by default above a payout cap • A paid bounty window on every pull request • Mainnet, after external audits Proofs, not promises.
1
50