Web3 dev/Builder, contributing to open source, host @ Ecogist. wolf🐺. Builder @sfdstacks . Dm is open for partnerships. Tea or coffee?

Joined September 2019
After 16 weeks of RIGOROUS grind at @Web3Bridge, participating in their Zero Knowledge program; My team built a full shielded token stack on EVM for private token transfers and I’m sharing both a demo video (Privacy native wallet extension + User facing dApp UX) and the technical paper in this post. Architecture: Noir circuit + Barretenberg/Aztec UltraHonk proving + Solidity verifier + relayer + client-side note discovery. Model: UTXO-style notes with - commitment = Poseidon(owner_pk, token_field, amount, blinding), - Nullifier-based one-time spends (nullifier = Poseidon(spending_key, commitment)), - Depth-20 incremental Merkle tree + rolling root window, fixed public input lanes, and mode-gated constraints for transfer/unshield. - ShieldedERC20Pool (multi-token allowlisted pool) with routed encrypted note delivery (RoutedCommitment) using ECDH + HKDF-SHA256 + AES-GCM, and channel/subchannel for note discovery. Design goal is explicit: private in-pool state transitions with verifiable integrity, while shield/unshield remain honest public boundary actions. If you watch the video + read the paper, you’ll see both the privacy native wallet extension and the user facing dapp full loop working end-to-end: shield → private transfer(s) → note scan/decrypt → nullifier checks → unshield. Big shout out to the mentors holding our hands throughout the duration of the program. The knowledge passed has been invaluable. @WiseMrMusa, @only1franchesco, @Oba_Ddev, @Dev_esayayo. Next steps for us are; - Production hardening and compliance-by-design - Formal security review/audit of circuits/contracts/relayer, wallet key-management hardening (secure enclaves/HSM-backed options), relayer auth + anti-replay protections - Performance tuning for proof latency/UX. - In parallel, we’ll implement a compliance layer that preserves base protocol privacy while enabling jurisdiction-aware controls at the app edge (sanctions/geo screening for boundary actions, risk scoring/transaction monitoring, optional disclosure and auditable consent flows for regulated contexts), alongside legal review and phased rollout with testnet pilots before mainnet. Read technical document here: drive.google.com/file/d/1oDq… References / lineage: (@Zcash) Zcash protocol (UTXO commitments, nullifiers, shielded value flow) (@Ztark_Labs) STRK20 shielded token design direction (@aztecnetwork) Aztec/Barretenberg UltraHonk proving system Noir language/tooling for circuit authoring.
9
13
1
53
2,530
0xKenzman🥷🐺 retweeted
Where’s your money sitting right now? If it’s on @solana , @avax , @base , @arbitrum or @Polygon , you can already move it into Stacks through Hermes. $USDC, $SOL , $AVAX, $ARB, $POL and more can come across in one flow and land as $STX or $USDCx. You don’t have to approve a contract or hand over control. Hermes has a simple send-and-receive model you send what you want to move, and it arrives on the other side in seconds.
5
5
2
25
733
0xKenzman🥷🐺 retweeted
We hosted a community builder call to walk through Scaffold Stacks, with participants building alongside us. With @kenzman18 guiding the session, everyone built a full Stacks dApp of their own using the stacksdapp CLI, with AI agents assisting along the way. By the end, every participant had deployed a contract to Stacks testnet and published their frontend to Vercel. They worked through project setup, connected Clarity contracts to the frontend, generated hooks and deployed. Scaffold Stacks gives builders (New and Existing builders) a practical path through those steps, so they can spend less time wiring the project together and more time building the product. The screenshots are from the call, with the community building in real time. If you’re building on Stacks, YOU NEED Scaffold Stacks: scaffoldstacks.mintlify.app 🟧
4
5
19
357
0xKenzman🥷🐺 retweeted
We cooked 🟧 That’s the tweet.
1
1
15
198
0xKenzman🥷🐺 retweeted
Just joined up a build session with @kenzman18 and @sfdstacks where I built Capstone, an NFT & token launchpad built on Bitcoin using Stacks designed to give creators one-transaction drops with all sales and mints anchored straight into Bitcoin L1. capstone-stx.vercel.app/
1
3
6
115
0xKenzman🥷🐺 retweeted
I spent a session with @kenzman18 building CivicProof on @sfdstacks , and I documented my experience with stacksdapp. The biggest takeaway? Good tooling lets you spend less time on setup and more time building the product. Here's what I learned 🧵
4
3
16
213
0xKenzman🥷🐺 retweeted
A large enough quantum computer could break the ECDSA signatures securing many blockchains today. @StarkWareLtd's STARK proofs take another path: they rely only on hash functions. On @Starknet we're pushing two fronts: faster proofs and cheaper post-quantum signatures. 🧵
2
11
2
34
752
0xKenzman🥷🐺 retweeted
No more waiting for Bond capacity allocation to open to start earning Bitcoin staking rewards. Deposit BTC into StackingDao and mint stBTC now 👇 Start earning BTC while your BTC stays liquid to deploy in Stacks DeFi, like Zest Levered Bitcoin staking vault or Biotflow LP.
Start earning Bitcoin Staking yield on @Stacks today. stBTC deposits no longer require waiting for a bond window.
1
3
11
377
Troves now supports privacy end to end with shadow accounts. Shielded tokens can earn yield in Troves vaults while staying private, with no onchain link back to your main wallet. How it works: 1. Shield funds in Ready, Xverse or Bramble. That balance sits in Starknet’s STRK20 privacy pool. 2. Turn on Private mode in Troves. Your wallet derives a commitment for Troves, and each vault gets its own shadow account computed from that commitment and the vault’s ID. Separate vaults use separate addresses, unlinked to each other and to your wallet. 3. Deposit. One transaction moves funds from the privacy pool to the vault’s shadow account and deposits them. Your wallet builds the proof. 4. Withdraw. Ekubo LP vaults return funds to your shielded balance in one step. Hyper xSTRK, the Boosted vaults and the Evergreen vaults redeem asynchronously: request the withdrawal, then collect it back to your shielded balance once it settles, typically within 1-2 hours. Available in private mode: > All active Ekubo LP vaults, including STRK/USDC, STRK/ETH and the strkBTC pairs > Hyper xSTRK > WBTC Boosted and USDC Boosted > The Evergreen vaults Live now at app.troves.fi
8
9
9
41
7,349
0xKenzman🥷🐺 retweeted
Private yield generation is now live on Troves. Earn yield through automated vaults and Ekubo strategies without publicly linking your positions to your main wallet. Powered by STRK20 Shadow Accounts.
Troves now supports privacy end to end with shadow accounts. Shielded tokens can earn yield in Troves vaults while staying private, with no onchain link back to your main wallet. How it works: 1. Shield funds in Ready, Xverse or Bramble. That balance sits in Starknet’s STRK20 privacy pool. 2. Turn on Private mode in Troves. Your wallet derives a commitment for Troves, and each vault gets its own shadow account computed from that commitment and the vault’s ID. Separate vaults use separate addresses, unlinked to each other and to your wallet. 3. Deposit. One transaction moves funds from the privacy pool to the vault’s shadow account and deposits them. Your wallet builds the proof. 4. Withdraw. Ekubo LP vaults return funds to your shielded balance in one step. Hyper xSTRK, the Boosted vaults and the Evergreen vaults redeem asynchronously: request the withdrawal, then collect it back to your shielded balance once it settles, typically within 1-2 hours. Available in private mode: > All active Ekubo LP vaults, including STRK/USDC, STRK/ETH and the strkBTC pairs > Hyper xSTRK > WBTC Boosted and USDC Boosted > The Evergreen vaults Live now at app.troves.fi
7
11
2
70
4,587
0xKenzman🥷🐺 retweeted
One of Starknet’s unfair advantages in a post-quantum world: native Account Abstraction. Crypto agility at its finest.
20
21
5
121
9,772
0xKenzman🥷🐺 retweeted
The last 12 staking cycles have been very prolific in $BTC rewards. Over 400M $STX every cycle.
3
13
368
0xKenzman🥷🐺 retweeted
Your AI agent now has a fully functional wallet, on @Stacks 🟧 Check balances. Send blockstack:native or swap to sBTC. All from the command line. The Xverse Agent Wallet gives your AI agent its own self-custodial account on Stacks. Just one command to set up. What will you do with it? xverse.app/agents
15
22
5
157
6,248
0xKenzman🥷🐺 retweeted
Bitcoin-native finance on Stacks, end of Q3 numbers 🟧
4
16
2
106
8,443
0xKenzman🥷🐺 retweeted
99.95% voted YES. The community has spoken. Starknet moving toward an independent post-quantum L1 is gaining overwhelming support. 4 days left. The next chapter of Starknet is taking shape.
9
9
1
45
1,249
Should Starknet become an independent post-quantum L1? I've been following the ongoing @Starknet governance vote on whether the network should explore becoming an independent post-quantum L1, and I think there's a much bigger conversation here than simply whether Starknet should leave Ethereum. Personally, I'm in favour of exploring the possibility. But I also think we need to be careful not to confuse technological ambition with a clear security advantage. Here's how I see it. One of the strongest arguments for Starknet becoming an independent L1 is the ability to control its own security roadmap. Today, Starknet operates as an Ethereum L2. This means that even if Starknet successfully makes its own cryptographic components quantum-resistant, some critical parts of its security still depend on Ethereum. For example, Starknet can adopt post-quantum signature schemes through native account abstraction, and its STARK proving system already relies on hash-based cryptographic assumptions. But settlement, data availability, and the Ethereum bridge introduce dependencies that Starknet cannot independently upgrade. So the argument for independence makes sense. Why build a network capable of preparing for a post-quantum future if its security ultimately depends on another network's upgrade timeline? However, there's an equally important question that I don't think should be overlooked. What exactly are we giving up in exchange for that independence? Ethereum provides more than a place for Starknet to settle transactions. It provides an established security infrastructure, a large economic security budget, and an ecosystem that has spent years developing its decentralization and consensus mechanisms. Becoming an independent L1 means Starknet would need to assume responsibility for those things itself. And that is no small undertaking. It's one thing to build a network whose cryptographic assumptions can withstand known quantum attacks. It's another to ensure that the same network is sufficiently decentralized, economically secure, resistant to censorship, and capable of reaching reliable consensus without depending on Ethereum. For the average user, the distinction is simple: being protected against a future quantum attack means very little if the network becomes easier to manipulate or disrupt today. For developers and infrastructure operators, the questions become even more interesting. What would the consensus architecture look like? How would validators participate in securing the network? What happens to existing applications and liquidity? How would bridges be secured, especially when interacting with networks that have not completed their own post-quantum transitions? And perhaps most importantly, can Starknet establish a security model that is demonstrably strong enough to justify moving away from Ethereum? I think these questions deserve rigorous research rather than assumptions. There's also an interesting strategic dimension to this. Starknet has spent years establishing itself as an Ethereum scaling network. Moving toward an independent L1 would represent a significant evolution in its identity, its relationship with Ethereum, and potentially how developers think about building on it. That could create opportunities, but it could also introduce fragmentation and new responsibilities that need to be understood before making such a transition. My position is that Starknet should absolutely research becoming an independent post-quantum L1. But research should not be mistaken for a commitment to migrate. And that's an important distinction in the current vote. A YES vote is a vote to investigate the possibility, not an authorization to leave Ethereum. I would particularly like to see comparative research on the security guarantees of both architectures, the economic cost of operating an independent network, the implications for existing applications, and whether there are intermediate approaches that preserve Ethereum's security advantages while improving Starknet's post-quantum readiness. Because the goal shouldn't simply be to become the first post-quantum L1. It should be to build a network whose security, decentralization, and long-term sustainability can stand up to serious scrutiny. If that research ultimately demonstrates that an independent Starknet is the better architecture, then I think there's a compelling case for pursuing it. But if remaining an Ethereum L2 while progressively strengthening post-quantum security provides better guarantees, that outcome should be equally acceptable. Technology should dictate the direction, not the narrative. And I think the willingness to explore both possibilities, with proper research and community involvement, is what makes this governance discussion worth paying attention to.
Should Starknet become an independent L1? It's time for the community to have its say. STRK stakers and delegaters can now participate in the first, non-binding governance vote on this potential transition 👇 governance.starknet.io/#/s:s…
2
6
2
20
675
ZK-STARKs time: The ZK STARK whitepaper came out in 2018 (alongside a main component, called FRI). At that time, we already saw that Elliptic curve based ZK SNARKs can solve privacy for blockchains, and it seemed to be all that the world hoped for. So, why a completely new construction? what was top of mind for us? The main advantages of ZK STARKs were the following: • Transparency (the T of STARK) -- This means no "toxic waste" setup, as needed in the ceremony in the case of SNARKs. This is very important for trust. To explain -- There is no trusted set up, so transparent ZK-STARKs can be trusted even if used by Darth Vader. • Post quantum safety -- Back in 2018, not that many spoke about the quantum threat and how it may destroy elliptic curve cryptography. But ZK STARKs are post quantum secure and in fact require only the existence of a secure hash function. This turned out to be important in our day and age of super intelligence and its threat to standard hardness assumptions like those underpinning RSA, DH, ECDSA, Lattice based constructions etc. • Field-agnostic -- The ZK-SNARKs of Zcash required very specific algebraic strucutres (finite fields) and large ones at that. STARKs, on the other hand, work over literally all finite fields, including binary ones and small prime fields, which is better for efficient computation time. To the non-mathematicians, this means much greater speed and scale. For instance, we clocked M31 field arithmetic (used by our latest and greatest STARK prover, S-two) to be 100x faster than the arithmetic we used for our first generation prover which required a 256-bit field(!). • Scalability -- The fact that they work over any field, plus the lack of need for a trusted setup, means that we didn't need to change anything in the onchain verifier even as we scaled and scaled again the size of computations we handled. Summarizing -- transparency, post-quantum security, efficiency and scale were the huge benefits that ZK STARKs offered the world in 2018. By now, they've become the gold standard for safe ZK scale and privacy. THE END
29
36
5
219
7,628
0xKenzman🥷🐺 retweeted
Q4 has three jobs: 🟧 Grow the BTC bonded each month 🟧 Put that BTC to work across ecosystem apps 🟧 Ship Epoch 4.1 in early December
7
22
3
105
9,691
This is how a quantum computer will break quantum-vulnerable cryptographic systems👇
28
40
5
243
18,835
An interesting thought experiment, especially when you consider what it means for the future of blockchains and networks like Starknet. One thing worth exploring further is that we've spent decades building digital infrastructure around the assumption that certain mathematical problems are computationally infeasible. What happens when that assumption no longer holds? For blockchains, the implications go beyond encryption. We would have to reconsider how transactions are authorized, how ownership is established, and how networks prove that a computation was executed correctly. Now, STARK proofs are built around cryptographic hash functions rather than the elliptic-curve assumptions that quantum computing threatens. That distinction becomes incredibly important in a world where discrete logarithms are no longer difficult to solve. But here’s an interesting piece: Starknet's native account abstraction. Since accounts are programmable smart contracts, signature verification isn't permanently tied to one cryptographic scheme. Accounts can adopt post-quantum signatures without requiring the entire network to undergo a hard fork. We've already seen experimental implementations of this using Falcon-512. Of course, this doesn't automatically make every component of Starknet quantum-resistant. Existing account signatures, certain hashing mechanisms, and dependencies inherited from Ethereum still need to be addressed. And that raises a broader question. What does a genuinely post-quantum blockchain look like when we consider the entire system, rather than just its proving mechanism? Because securing the validity of computation is one problem. Securing ownership, communication, interoperability, and the exchange of secrets between parties is another. Even if we successfully build payment networks around hash-based proofs and post-quantum signatures, the original question of establishing private communication channels without vulnerable public-key assumptions remains. Perhaps the most interesting possibility is that the next generation of cryptographic infrastructure won't simply replace today's algorithms with quantum-resistant alternatives. It may force us to rethink how trust, identity, and secure communication are established in the first place. @Starknet offers an interesting foundation for exploring part of that future, particularly because cryptographic flexibility is already built into its architecture. The bigger question is whether the rest of our digital infrastructure can evolve with the same flexibility. And perhaps that's the kind of research we should be doing long before the threat becomes practical.
As a researcher, I like to think about what-if scenarios, so let's consider one here: what if there is no more public-key encryption? Public-key encryption is used in countless ways in our daily lives, including online shopping, banking, and protecting anything we want to keep private from the rest of the internet. What if the mathematical problems that underpin public-key encryption (factoring, discrete log, lattice problems, decoding of codes) are all easy to solve because of mathematical breakthroughs by artificial intelligence or quantum computers? What happens to internet commerce? I see two worlds: 1. We rely on trusted intermediaries to send us keys for encryption. There is no more public-key encryption, and all we have is symmetric encryption like AES. In this case, we need trusted third parties to send counterparties dedicated keys for encrypting. 2. A second possibility that I like better relies on hash-based zk-STARK systems to create digital signatures that depend only on the hardness of hash problems. In this world, you could still have payment systems and internet commerce for sending payments, but you'll need to solve the challenge of easy, direct encrypted channels between counterparties.
5
1
11
516