Research
Timechain
Search Donate
Sponsors
Cake Wallet, private Bitcoin and Monero walletSideShift.ai, no-signup crypto exchangeOrangeRock, non-custodial bitcoin spot and perps tradingBraiins Hashpower, buy and sell Bitcoin hashrateLayer Two Labs, drivechains for Bitcoin
S17 · E3 · 3:54:48

The Zano Devs on Private Tokenization (S17 E3 Full Article)

27 Jan 2026 · by Vlad Costea · 6 min read
Published at block 933,906
Cover art for S17 E3, Zano Devs on Private Tokenization
MP3 (322 MB)

The audio keeps playing while you browse the site.

Read the transcript31,414 words, every line links to the minute it was said

Ask this episode

Embed this episode

Paste this on your site or blog. It is a small player that streams from here: no trackers, no cookies, no ads.

Preview the player

This interview happened because I made a mistake. In my conversation with Tyler Spalding, I described Zano as a fork of Monero, and the Zano team wanted to set the record straight. So I invited the two core developers, Andrey Sabelnikov and Valeriy "Val" Pisarkov, for a live stream.

Roger Ver has been excited about Zano on this show for a while, so I wanted to check the claims myself, including the uncomfortable ones. The original show notes have the short version.

CryptoNote Roots

Andrey worked on the original CryptoNote code, but he distances himself from how Bytecoin launched. "The way it was launched, it didn't felt fair for majority of community who was observing it. And it wasn't felt fair for me, myself. That's why I left it right after it was launched to do my own thing."

From Hidden Amounts to Zarcanum

Val explained how Zano caught up with modern privacy. Monero added hidden amounts to CryptoNote, and Val called that "a huge milestone in the history of the cryptocurrency." Zano wanted the same, but it already had hybrid proof of work and proof of stake.

That created a problem. In their staking model, "you need to disclose the amount, the stake amount when you publish a staked block." Fixing it "was unexpectedly difficult for me." The result was Zarcanum, with help from koe, "who at that time was core developer at Monero and a brilliant mind behind the Seraphis protocol." They presented the paper "at MoneroCon and Monerotopia."

Then came confidential assets, "so you can transfer arbitrary assets in the transaction in an anonymous way." It's "not clear which amount is being transferred and not clear what type of assets are being transferred."

The Staking Privacy Finding

I asked about a recent finding that stakers could be exposed. Val clarified: "It's not about the math, not about the anonymity and the privacy that is actually in the math protocol." It's at the network level, because bigger stakers produce more blocks, and block timing can be tied to IP addresses.

Security is getting harder. "AI tools became insanely smart," and bug reports through Immunefi keep the small team busy. "We are just a few guys at the core team."

Is Zano a Monero Fork?

So, the question that started it all. Val was precise. "There are some, maybe several lines of code that actually was copied from Monero," always with credits. For "ring signature scheme Pedersen commitments, range proofs, we share a lot with Monero, but we diverged at a very early point, and now we have all the technology implemented differently."

Andrey said even Monero developers have noticed. Luke Parker once asked "why is Zano code base so different from Monero code base?"

Fair enough. I stand corrected.

Despite the tension between the two communities, Andrey gave Monero real credit. "Well, they're doing a great job on improving technology. We have to give them this." He called it "a really truly community-driven project," and Quinten added that "we also have a lot of overlap still."

The Premine Question

Some critics call Zano a scam because of its premine, which the team still uses for staking to fund development. Andrey disagrees. "I think premine is a very fair way to fund the project because it comes from emission, which is basically from the pocket of every single holder of the project." In his view, "it's not fair to build a project on donations."

Zano also came out of Boolberry, Andrey's earlier project, through a swap. "I was doing Boolberry alone with zero experience." He thought great code would be enough, "but running a project, it's a lot of different things. And I just burned out at some point."

He's honest about weaknesses too. "We actually suck at marketing, it's true."

Listings and the Head of Growth

Quinten van Welzen, known as Mr. Kwibs, joined later to talk about exchanges. Privacy assets are hard to list, since exchanges see them as "a risk to list privacy assets." So the team is making integration easier.

Bridging Bitcoin With MPC

One idea Roger liked is bridging bitcoin into Zano for privacy. Val explained the base: "Everyone can create their own confidential asset and control their emission. And the transferring of this asset inside the Zano blockchain is anonymous."

For big assets, a single key is too risky. Val used my name as an example: "When Vladcoin on Zano has a private key that controls all the emissions and all the stuff." Multi-party computation "allows to do this," by spreading the key among many participants. Zano also supports Ethereum-style keys, which is "much easier to implement for services."

Andrey was clear Zano doesn't run the bridge. "Someone built a project that does the bridging." Bridgeless "is L1 itself. It's built on Cosmos," with validators who take part in the MPC.

Scaling and Quantum

The big goal is throughput. "I think the strategic goal is to solve the problem of TPS. That's the biggest problem for the most private privacy blockchain." He expects sharding or parallelization rather than faster transactions.

Val is thinking about quantum computers too, specifically to "mitigate harvest now decrypt later," since data on the network today "could be stored and then be broken using a quantum computer in the far future."

Privacy Isn't Just Cat and Mouse

I suggested privacy is always a cat-and-mouse game. Val disagreed. "I think that privacy things and privacy tech is a fast-evolving field. And it's not always like a cat-and-mouse game." Some encryption will be "extremely hard to break, indefinitely." His reason was simple: "Because I believe in math."

Andrey was more cautious about older privacy data. Decoy-based systems can weaken as exchanges and leaked wallets reveal more, so "there's going to be less decoys left in the ring." His view: "the perception should be that the privacy is a temporary thing always, due to technology growth." I appreciated hearing two developers on the same team disagree on air.

Gateway Addresses

To connect with DEXs and bridges, Zano added gateway addresses, which are public like Ethereum accounts. Andrey admitted, "It's a trade-off with the privacy." To limit spam, registering one costs money. Val said "in two steps, this privacy trade-off will be mitigated": first, anonymity on top of gateway addresses, then full-chain membership proofs, which are "a very complicated task."

Hiring is the bottleneck. "To hire someone who is familiar with the codebase, it's like the chances are not high." But the priorities are clear: consensus, full-chain membership proofs and the gateway address, "because it's holding integrations."

Not Married to a Technology

Andrey described the team as "a group of individuals with common goals, with a common vision, and with different backgrounds." He added, "we're not married to specific technology." Quinten agreed: "Zano adapts really quickly to whatever tech is best." Andrey also believes proof of stake is where things are heading, saying "I've seen that Zcash was talking about proof of stake."

What Makes This Episode Worth Listening To

I like it when a team shows up to correct me and brings the technical receipts. Whatever you think of altcoins, Zano is trying to make private assets and private staking work, and that's interesting research. Listen and judge the arguments yourself.

You can read the full transcript, the original show notes, or visit Andrey Sabelnikov's guest page.

Listen to Andrey Sabelnikov and Valeriy Pisarkov on Spotify, Apple Podcasts, and More

Time stamps:

  1. 00:01:19– Setting the record straight
  2. 00:02:53– Leaving Bytecoin
  3. 00:05:12– AI and security reports
  4. 00:06:44– A few guys at the core team
  5. 00:08:45– Catching up on hidden amounts
  6. 00:09:43– Disclosing the stake
  7. 00:10:32– Zarcanum and koe
  8. 00:10:47– Confidential assets
  9. 00:13:40– Hiding your IP when staking
  10. 00:15:44– Not about the math
  11. 00:18:28– Proof of work's blind spot
  12. 00:22:16– Third-party analysis
  13. 00:24:12– So different from Monero
  14. 00:25:42– A few lines of code
  15. 00:44:09– Defending the premine
  16. 00:52:18– Boolberry and burnout
  17. 00:58:46– We suck at marketing
  18. 01:00:59– Exchange listings
  19. 01:16:48– Someone built a bridge
  20. 01:18:51– Confidential assets explained
  21. 01:20:14– Ethereum-style keys and MPC
  22. 01:41:46– Vladcoin and MPC
  23. 01:43:41– Bridgeless on Cosmos
  24. 01:58:27– Solving TPS
  25. 02:02:16– Harvest now decrypt later
  26. 02:12:38– Not always cat and mouse
  27. 02:15:12– I believe in math
  28. 02:18:03– Fewer decoys over time
  29. 02:22:41– Common goals
  30. 02:29:17– Not married to a technology
  31. 02:45:33– A lot of overlap
  32. 02:50:14– Credit to Monero
  33. 02:53:50– Gateway addresses
  34. 02:56:40– Two steps to more privacy
  35. 03:23:13– Hiring and priorities

Verify this episode

This is the SHA-256 fingerprint of the MP3 as published here, timestamped in the Bitcoin blockchain with OpenTimestamps. If one byte of the file changes, the fingerprint changes.

SHA-256
add455b14be0f2d6668e92d8d50238c50015a896cbae1726ae2fdff7f20c2fbc
Proof
2026-01-20_s17_e3_zano_devs_andrey_val_on_private_tokenization.mp3.ots · all episode hashes (proof)
Status
Anchored in Bitcoin block 974,312
Timestamped
After release. The episode came out on 20 Jan 2026, but this proof was made on 3 Nov 2026 and anchored in block 974,312, so it proves this exact file existed by 3 Nov 2026, not on the release date.
How to check it yourself
  1. Download the MP3 and the proof into the same folder.
  2. Run sha256sum 2026-01-20_s17_e3_zano_devs_andrey_val_on_private_tokenization.mp3 (on a Mac: shasum -a 256 2026-01-20_s17_e3_zano_devs_andrey_val_on_private_tokenization.mp3). The result must match the SHA-256 above.
  3. Install the OpenTimestamps client (pip install opentimestamps-client) and run ots verify 2026-01-20_s17_e3_zano_devs_andrey_val_on_private_tokenization.mp3.ots. It hashes the MP3 again and checks the proof against your own Bitcoin node, then prints the block and the date the file existed by. Without a node, ots info 2026-01-20_s17_e3_zano_devs_andrey_val_on_private_tokenization.mp3.ots shows the block height to look up in any block explorer.

Share: X · Email · Link

Related

Comments

Comments run on my own server. No trackers, no tracking cookies.

0:000:00