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
S16 · E31 · 3:22:36

S16 E31: Andrew Camilleri "Kukks" on Ark, BTCPay Server & Open Source Bitcoin Software

29 Jun 2025 · by Vlad Costea · 11 min read
Published at block 903,141
Cover art for S16 E31, Andrew Camilleri ”Kukks” on Ark, BTCPay Server & Open Source Bitcoin Software
MP3 (278 MB)

The audio keeps playing while you browse the site.

Read the transcript31,219 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

The power went out in my building twice during this stream, and both times Andrew Camilleri kept talking into the void until I came back. He did not seem bothered. Andrew, better known as Kukks, is the CTO of Ark Labs, a long-time contributor to BTCPay Server, and the person who got Monero support and the WabiSabi coinjoin plugin into it. We went for three hours and twenty-two minutes, and I had a list of questions about Ark that I did not get through, because every answer opened another door.

Before we got to the protocol, I wanted to know where he stands in the coin wars, since his history runs through an Ethereum proposal in 2018 and a Monero integration. He settled that in the first few minutes. "I'm only a Bitcoin person at this point," he said. The rest of the episode is a tour of what he is building on top of it, what he is not building, and where the soft-fork conversation has left him.

I also set a secret word for listeners, which we agreed would be "Cookies." Say it to me if you meet me at a conference.

From a Monero Plugin to Everything Virtual

Andrew's route to Bitcoin ran through BTCPay Server, and the Monero work in particular. "Monero was basically the stepping stone I needed to get the infrastructure fleshed out for the plugin system that is now available in BTCPay," he told me. Before that plugin system existed, supporting another coin meant arguing with the maintainers over whether it belonged in the codebase at all. Now, he said, "Nobody is shouting at them for building a plugin on BTCPay. I think it's the best of both worlds. Freedom of choice and stuff, so."

He says BTCPay users sometimes message him out of nowhere in DMs to mention how much they process. I asked what the scale looks like, and he said users have messaged him in random DMs saying they move "millions of dollars every month through this." Kukks and Pavlenex were on S11 E1.

Then the Ark question. How do you explain it to someone who has never heard of it? "The easiest way to describe Ark is that we make everything virtual," he said. A transaction output becomes a virtual UTXO, a VTXO. The mempool becomes a virtual mempool. And "instead of blocks, you have batches." Transactions move between users in those batches "except these transactions will never hit the chain," at least until someone needs them to.

I asked whether this was a Lightning killer, because that is the framing I keep seeing on social media. "It's not a Lightning killer. It's not replacing Lightning," he said. He also said payments are not the end goal: "is not the end goal for us."

Why Lightning Is Not Enough

If Ark is not out to replace Lightning, why build it? His answer was about the person writing the wallet. "Integrating a Lightning node into your app or wallet is like almost a nightmare or unfeasible for the most part, especially if you're on a mobile device," he said. Wallet developers today work around that with custodial setups or with swaps through Liquid and Boltz, and neither is what anyone wanted when they started.

He also thinks something important dropped out of Bitcoin along the way. "What happened to escrow in Bitcoin? It almost completely disappeared at this point," he said. His argument is that Ark makes escrow viable without the fee-related business risk that hangs over every on-chain escrow service, since a service that has to pay a fee every time something moves cannot price a small trade sensibly.

I pushed on the miners: if all of this happens off chain, who pays them? He said that is not the model. "I don't think we're going to be the ones paying the miners, to be honest. It's like one Bitcoin transaction with one input, one output almost," and he expects roughly 200 VTXOs hanging off each on-chain output. He also had a rule for his own coins: "If you're HODLing, use on-chain. There's no second best there."

Expiry, Liquidity and Who Runs the Server

This was the part I was least sure I understood, so I asked him to go slowly. Operators front the liquidity for VTXOs, which means they need that money back eventually. "The expiry is kind of a way for the operator to say, hey, okay, I gave you money. I need to get my money back at some point, right?" That is why users have to refresh periodically. VTXOs also have a pre-confirmation state before a batch settles, and for that window he suggested trusted enclaves could produce attestations from the operator.

I asked what stops an operator from simply cheating, and he said the incentives point the other way, because cheating "is kind of dumb for an operator because your entire business model relies on not doing that." He expects five to ten Ark operators in the world, and he was emphatic about what it should not look like: "It's not going to be like, oh, I'm running this in my local community on my Raspberry Pi. Please don't do that kind of thing." On whether an Ark network will emerge among operators, his reply was "We're not looking to create a network," and on interoperability between operators he called it "a bit, I don't know, non-existent, maybe."

Centralization is the point he volunteered himself: "that's our weakest point is centralization." The history behind that, he said, is that earlier coordinator-based designs ran into the same wall: "nobody wanted to run the coordinator." I connected that to TumbleBit and he took the comparison willingly. "A very supercharged TumbleBit, if anything," he called Ark, and he added that "Ark is basically a child of Taproot." The longer-range hope he mentioned is "the channel factory dream," which Ark's structure points toward without promising.

For a different slice of this design space I had Burak Keceli on in S14 E1 to talk about Ark and Bitcoin second layers.

No Rollups, No Drivechains, No New Opcodes

I asked him the question I ask every Layer 2 person: why this and not drivechains, or a ZK rollup? On drivechains, his objection was fragmentation. "It's kind of like a super fragmented environment," he said. On rollups, he said Ark avoids the cryptography entirely. "We don't do any zero knowledge proofs, none of that crazy magic, which intimidates a lot of people, myself included." What Ark uses is MuSig2.

I brought up the recent ColliderScript research, which tries to get covenant-like behavior without a soft fork. He described it as "a bunch of nerds having fun with research," and said it felt like fun and not a product plan. The OP_CAT push from Taproot Wizards he liked less, saying "Having people jumping around on stage and looking like clowns does not really make you look very serious."

What he does think is that Ark works now, with the opcodes Bitcoin already has. "What we can do now is more than enough at least to get started," he said, and later, "There's a lot you can do, even with just basic Bitcoin. It's just people try to take the easy way out." If CTV were available he would use it. But he is not betting the company on a fork: "If you're building a business that relies on a soft fork, you're not gonna make it."

Taproot, Soft Forks and Giving Up on Change

Early in the stream he had already told me he has "kind of given up on the idea that we'll ever get any real change in Bitcoin," and later he came back to it: "I'm just not very optimistic with getting anything into Bitcoin." I asked about Taproot, since we both lived through that activation. He said "People oversold Taproot," and that the community "kind of pushed it a bit too fast."

I have talked with a lot of people about this fight, including Andrew Poelstra on OP_CAT versus CTV in S15 E17. Andrew's position sits somewhere beside both camps: build with what exists, and treat a new opcode as a bonus.

His one concession to the other chains was this: "I appreciate a lot of the research that came out of Bitcoin Cash." And on the broader culture of building, "You can just do things, just build something."

Arkade OS and Synthetic Assets

I introduced him on the show as the "executor of Arkade OS," and he confirmed the job title he has now: "I am basically the CTO of Ark Labs now." Arkade is an Ark instance with extra features layered on, and the headline one is Arkade Script. It is, in his words, "our secondary Bitcoin script interpreter, but we added all the opcodes to it." That brings introspection and 64-bit arithmetic. His promise about it was: "We don't water it down. We don't oversell it."

I pulled up the Mutinynet reference wallet he sent, and my browser flickered black and white the moment I opened the link. Andrew's diagnosis was that I should quit Firefox, which I am not going to do.

The things he wants to build are financial. "Bitcoin is great collateral. People love to hold Bitcoin," he said, and he walked me through synthetic assets and non-interactive swaps on Liquid. He was careful to say that parts of it are "mostly a proof of concept," so nobody should treat today's demos as production products. His pitch for where it ends up is money "without bank accounts attached to them without crazy mumbo jumbo secretive cults managing the whole thing."

Privacy, Treasuries and the $200,000 Ceiling

I asked how much privacy Ark can offer. He pointed out that Chainalysis runs dedicated teams on swap detection, and said "Chainalysis has dedicated departments just for swap detection." His view is that coinjoin at WabiSabi scale already provides a decent baseline.

On the corporate Bitcoin craze he did not hold back. "This whole treasury company thing is just madness, honestly, to me," he said, and he argued that some of those arrangements "are some form of nation-state attack."

On the question of whether Bitcoin success is measured by price, he said "I think success has been very much accomplished, I would say," and "It can't just be like oh number go up, I don't think people care enough for that." Asked for a ceiling on this year's price: "I'll say 200k max absolute Max."

On the culture side he said "I gave up trying to onboard new Bitcoiners a long time ago," and "Fuck the banks. Yeah, that's that's the OG way of saying it. But we can't say that anymore because the banks are basically Bitcoiners at this point." I asked where that leaves the cypherpunk spirit, and he said the only fix for crowded spaces is separate ones: "the only way to remedy the situation is to give them a space where it doesn't fuck up everyone else's experience."

Shiba Inu Tips in Istanbul

Somewhere in the second half we wandered into Istanbul, 2022. Andrew was at a restaurant, told the staff he would like to pay in Bitcoin, and heard back the thing every Bitcoiner dreads. "You go to pay at the restaurant and you tell them you want to accept Bitcoin we'll tip you it's like Shiba Inu, Shiba Inu I'm like why," he said. I told him about a street musician in the same city who took Bitcoin tips and converted them to Turkish lira on the spot, so not everyone there is waiting for a dog coin.

He owns a shirt for his own contribution to the dog economy. "And that's coming from me, I have my original Dogecoin NASCAR shirt from 2014. So it's just, it's, it's, please don't use it as money. It's literally a joke." The shirt is from 2014, which is also roughly when the Maltese exchange sold him his first Bitcoin, after he spent his early years writing RuneScape bots.

On trusting things he cannot see, his instinct runs toward the physical. About an exchange, he said "It was like, okay, why not? It's like, if if these guys take my money and run, I can find their office and burn it down or something." And on black-box systems generally: "This big big black box is scary to me." Lightning has the luxury of a mature ecosystem that Ark does not yet have: "We don't have the same luxury, right, as Lightning." Later, on the self-custody lesson: people "just don't grok it until they actually get robbed."

I asked what changes the picture soonest, and he said a coming event "will probably recalibrate a lot of people's mental model," arriving "very soon." Then I asked how he feels about the whole thing after three hours. "I'm pessimistic on the behavior of people," he said, "I am optimistic about Bitcoin."

Listen to Andrew Camilleri "Kukks" on Spotify, Apple Podcasts, YouTube, and More

Time stamps:

  1. 00:00:49– Introduction & Andrew’s Background
  2. 00:01:46– Getting Into Bitcoin & Altcoin Integrations
  3. 00:03:02– Focusing on Bitcoin & Monero Plugin
  4. 00:04:04– BTCPay Plugins & Community
  5. 00:04:22– Bitcoin’s Imperfections & Altcoin Use Cases
  6. 00:04:55– Pessimism & Stagnation in Bitcoin Development
  7. 00:05:16– Introduction to Ark & Its Evolution
  8. 00:06:10– Ark’s Technical Evolution
  9. 00:07:31– Ark’s Impact on Developer Morale
  10. 00:07:36– What is Ark?
  11. 00:09:08– Ark’s Virtual Ledger & Dust Problem
  12. 00:09:59– Off-Chain Payments & User Experience
  13. 00:11:07– Lightning Network vs. Ark
  14. 00:13:21– Custodial Lightning & Ark’s Broader Goals
  15. 00:15:13– Escrow & Multisig Use Cases
  16. 00:16:09– Bitcoin’s Usability & Fee Volatility
  17. 00:16:51– Miners & Second Layer Economics
  18. 00:19:08– Drivechains & Network Fragmentation
  19. 00:21:38– Rollups, ZK Proofs, and Simplicity
  20. 00:25:53– CTV, Musig2, and Soft Forks
  21. 00:28:12– OP_CAT, Collider Script, and Efficiency
  22. 00:32:38– Cost, Privacy, and Coinjoin
  23. 00:36:12– Stablecoins, Payments, and Swapping
  24. 00:38:14– Privacy, TumbleBit, and Ark’s Superiority
  25. 00:41:03– Expiry, Operators, and User Experience
  26. 00:44:14– Becoming an Ark Operator
  27. 00:47:31– Fedimints, Liquid, and Privacy
  28. 00:49:41– Security Against Operator Theft
  29. 00:51:31– HODLing, Expiry, and Automation
  30. 00:53:37– Payment Finality & Pre-Confirmation
  31. 00:57:49– Government Attacks & Decentralization
  32. 01:02:51– Ark’s User Experience & Wallet Integration
  33. 01:05:11– Lightning Interoperability & Partnerships
  34. 01:07:48– Arkade OS & Arcade Script
  35. 01:13:06– Underrated Use Cases: Escrow & Synthetic Assets
  36. 01:18:29– BTCPay Server’s Impact & Bitcoin Payment Adoption
  37. 01:22:23– Speculation, Regulation, and Medium of Exchange
  38. 01:24:20– Litecoin, Extension Blocks, and Privacy
  39. 01:26:01– Coinjoin, Amounts, and Privacy Pools
  40. 01:29:09– Bitcoin Upgrades, CTV, and Developer Frustration
  41. 01:34:27– Soft Fork Politics & Overselling Upgrades
  42. 01:41:53– Payments, Credit Cards, and Onboarding
  43. 01:44:11– Stablecoins, Speculation, and Fiat Mindset
  44. 01:48:48– Taproot Assets, Altcoins, and Control Tokens
  45. 01:52:17– Early Bitcoin Days & Escrow
  46. 01:54:53– Gaming, Digital Money, and Bitcoin Adoption
  47. 01:59:15– Speculative Attack & Fiat Demand
  48. 02:00:01– Supercycle Skepticism & Price Predictions
  49. 02:02:22– Hard Forks, Big Blockers, and Research Value
  50. 02:24:40– NFTs, Ordinals, and Free Market Transactions
  51. 02:36:28– BTCPay Plugins & Comparison to LNBits
  52. 02:43:14– Zero Conf, RBF, and Payment Risks
  53. 02:47:41– Ark’s Future: Liquidity & Decentralization
  54. 02:49:25– Testing Ark & Reference Wallet
  55. 02:51:00– Browser Wars & Internet Evolution
  56. 02:56:26– Scaling Bitcoin Payments & Libra Comparison
  57. 02:58:10– Tipping, Custodial Wallets, and Ark’s SDK
  58. 03:02:12– HODL Culture vs. Spending
  59. 03:06:07– Optimism, Pessimism, and User Adoption
  60. 03:08:13– Lightning’s Complexity & Ark’s Simplicity
  61. 03:11:18– Competition Among Layer 2s
  62. 03:14:13– Ark’s Launch, Operators, and Liquidity
  63. 03:16:08– Ark Operator Incentives & Fee Structure
  64. 03:17:08– Testing, Following, and Final Thoughts

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
ef132b6a42e580dbe74f6cda5808e855b20ed801db1a367ffbaed24d339d28e4
Proof
2025-06-28_s16_e31_andrew_camilleri_kukks_on_ark_btcpay_bitcoin_open_source_software_final.mp3.ots · all episode hashes (proof)
Status
Anchored in Bitcoin block 974,312
Timestamped
After release. The episode came out on 28 Jun 2025, 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 2025-06-28_s16_e31_andrew_camilleri_kukks_on_ark_btcpay_bitcoin_open_source_software_final.mp3 (on a Mac: shasum -a 256 2025-06-28_s16_e31_andrew_camilleri_kukks_on_ark_btcpay_bitcoin_open_source_software_final.mp3). The result must match the SHA-256 above.
  3. Install the OpenTimestamps client (pip install opentimestamps-client) and run ots verify 2025-06-28_s16_e31_andrew_camilleri_kukks_on_ark_btcpay_bitcoin_open_source_software_final.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 2025-06-28_s16_e31_andrew_camilleri_kukks_on_ark_btcpay_bitcoin_open_source_software_final.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