Control-Plane Capital's avatar
Control-Plane Capital
.
npub1x9hg...6rta
Truth seeker
Control-Plane Capital's avatar
buckyfonds 11 months ago
I rarely get surprised by anything anymore, but a while back when I started researching AI governance, it shocked me how many institutions are actually aware of where the world is moving without divulging much information. 1) How many market participants already know about the AI governance regime (rough estimates): - High-level "AI governance is coming" awareness: ~60–70% of institutions. - Deep understanding (admissibility, provenance, attestation, court-survivable artifacts): <10%. - Positioned in mispriced bottlenecks (T&D, transformers, legal-evidence tech, attestation silicon): ~5%. 2) How coordination happens without a "smoking gun" Standards + perimeters. - Standards (NGOs, fora, regulators) emit the same verbs: attest, revoke, trace, prove, rollback. - Perimeters (banks, clouds, app stores, ISPs, card networks) flip Acceptable Use Policies; law becomes optional. In other words, financial institutions read the standards, and people don't. That's what's reflected in financial markets, not the media screaming "AI bubble" which is a very surface-level take. Just to give you 1 example (of many), look at EU's AI Act ( ) . image And before you say "it's just the EU". It's not, it's also the US and the entire world. The US governance template (de facto global) is also being rolled out. - The NIST AI Risk-Management-Framework plus the Generative AI profile (NIST-AI-600-1, Jul-2024) is the check-list legal, audit, and vendor teams are implementing (regardless of DC politics). It maps controls for provenance, evaluation, and traceability. So a large share of institutions knows AI governance is coming — you see it in dated laws, Cloud Solution Provider SKUs, silicon roadmaps, enterprise console updates, and financial markets. I have to admit, it is a well-kept secret. While the plebs are busy food fighting, governments are rolling out the next regime. More context: https://controlplanecapital.com/p/why-we-arent-in-an-ai-bubble-top
Control-Plane Capital's avatar
buckyfonds 11 months ago
I've been doing some research on the biggest mistakes we Bitcoiners made as a community — and obviously we got very complacent over time. Instead of listening to podcast hopium and alienating people with "have fun staying poor" narratives, we should've focused on game theory and patched up at least some of the holes. It was always inevitable that Bitcoin was going to get attacked, and things like having close to 100% of nodes run on a single implementation was just silly in hindsight. People are doing more harm than good when posting charts of hashrate going vertical without the context that 2 pools (Foundry and Antpool) are close to 50% of hashrate and for more than 98% of cases, pools, not miners decide which transactions get added to the blockchain. You had most of the Bitcoin community cheering price over payment share; we welcomed ETFs as victory. Paper share rose, self-custody fell. The entire community also cheered Square's surveilled "Bitcoin payments" where every payment generates identity-linked transaction data: buyer, location, device, and amount. All transactions flow through Square/Cash App's KYC/AML perimeter, meaning both sides of the payment are verified. That data fuels risk scoring, fraud models, blacklist propagation, and targeted marketing. Exactly this surveillance value is Square's enduring moat, not the 1% fee. We just got too complacent. I'd say the 5 main mistakes we Bitcoiners made are: 1. Letting arbitrary data compete with money on the base layer (witness discount abetted it). For Medium-of-Exchange you need predictable fees; underpriced junk data is a Denial-of-Service subsidy. 2. Treating privacy as an "expert mode". That guarantees surveillance wins by default. Make privacy invisible and automatic. 3. Under-investing in operational safety (backups, recovery, liquidity UX). Normal users pick custodians when scared. 4. Relying on norms over policy. In a low Gross Consent Product world, policy beats culture. If your mempool policies are naïve, adversaries will price you out. 5. Ignoring perimeter levers (app stores, banks, clouds). If you don't plan redundant routes, the other side will plan your failure. The uncomfortable truth is that Bitcoin's defense can't be "hope users pick hard mode". Defaults decide outcomes. If Bitcoin wants to be mass Medium-of-Exchange, privacy, finality, recoverability, and predictability must be invisible and automatic — and the perimeter must be treated as hostile by default. Until then, paper wrappers will dominate, regulators will "clarify", and L1 will be priced as store-of-value with supervised access, not as everyday cash. The good news: all of that is fixable — but only if it's designed, not preached.
Control-Plane Capital's avatar
buckyfonds 11 months ago
The only thing I am bullish on in regards to Bitcoin is its fiat-denominated price (which is a weird thing to say). Old regime: retail perps set price → parabolic tops, −70% to −85% busts, halving-clock "3 years up / 1 year crash". New regime (post-ETF): CME + ETFs + dealer gamma set price → longer, flatter upcycles, faster but shallower draw-downs (−30% to −55%), macro/liquidity > halving, mean reversion > parabolas. We're already ≈31% below the ATH with constant stop-hunts and very little leverage. Instead of the Bitcoin is "arbitrary data storage" movement, I would've liked to see changes that (1) harden fee predictability, (2) make privacy and self-custody defaults, and (3) blunt perimeter levers. In other words, changes that keep Bitcoin useful as money. However, these are exactly the changes that Bitcoin's developers aren't prioritizing. Instead, we're letting arbitrary data compete with money on the base layer. For Medium-of-Exchange you need predictable fees. Underpriced junk data is a Denial-of-Service subsidy. I was excited about these changes that improve Bitcoin as money, but then I started digging into what Bitcoin Core has been up to and at this point, I'm like "Just stop changing things. You're making everything worse." 😂 More context:
Control-Plane Capital's avatar
buckyfonds 11 months ago
David Bailey's company $NAKA missed quarterly earnings filing and their losses exceed $80 million. image Meanwhile David Bailey's rough comp estimate exceeds $9 million a year 😂 The other execs are also absolutely crushing it. image The only ones who aren't crushing it are Nakamoto's shareholders as the stock is down ~99% from the recent top. image There is probably a lesson to be learned from this. Try to stay away from obvious scams. Also, David Bailey absolutely knew this was going to happen and continued to promote the stock. Nakamoto's PIPE investors got in at $1.12 with no lockup and bought ~455M shares and then dunked on retail while David Bailey and co promoted the stock on all kinds of Bitcoin podcasts.
Control-Plane Capital's avatar
buckyfonds 11 months ago
1) A while back I wrote how Michael Saylor's role in Bitcoin was to: - normalize paper exposure (MSTR), - push "BTC = Store of Value (not Medium of Exchange)" narratives, - refuse to normalize Proof-of-Reserves that would discipline the entire paper stack If Larry Fink was tasked with this job, he'd probably get a lot more pushback. https://controlplanecapital.com/p/why-microstrategys-best-days-are 2) Jack Dorsey's role seems to be to normalize permissioned, surveilled "Bitcoin payments" with Square. With Square, every Bitcoin payment generates identity-linked transaction data: buyer, location, device, and amount. All transactions flow through Square/Cash App's KYC/AML perimeter, meaning both sides of the payment are verified. That data fuels risk scoring, fraud models, blacklist propagation, and targeted marketing. So the surveillance value, not the 1% fee, becomes Square's enduring moat. 3) I also wrote about how Bitcoin Core's developers have been attacking Bitcoin's sovereign/MoE use for a very long time now. From the outside look in, Bitcoin Core is a well-oiled machine. There's barely any dissent. It seems they all embrace the "Bitcoin is arbitrary data storage" narrative. They are solving the problem no Bitcoiner knew they had: "How to store your pictures on other people's computers". 4) 99.9% of Bitcoin influencers seem completely captured or delusional. I tried listening to a bunch of different podcasts recently and 5 minutes in, I end up wondering if I'm taking crazy pills or something. So what's the lesson? The lesson is don't trust, and verify. Do your own research and don't be a sheep. People prioritize their own interests, not yours. Some people are corrupt, most are fallible, and some are both.
Control-Plane Capital's avatar
buckyfonds 0 years ago
I wonder how many Bitcoiners have a good understanding of who holds the actual power and who sets the rules. And this is a topic I'll have to write about but I already alluded to it in ( ). And namely, governance activations show who sets the rules. Past upgrade processes (e.g., BIP9, BIP8, "Speedy Trial") revealed that miners and coordinated developers can accelerate or block changes faster than ordinary users can veto. So power concentrates among aligned institutional actors. Net effect: - Technical ideals matter less than coordination leverage. - Future upgrades will likely follow similar political dynamics. 1) What actually happens in upgrades: - Rule changes need coordination. To activate, you need miners to mine the new rules, big pools to signal, exchanges/custodians to accept deposits, wallet/infrastructure teams to ship updates, and users to run them. - BIP9/BIP8/“Speedy Trial” are coordination levers. They set thresholds and timers that, in practice, let miners + core devs + major infra decide when something flips on — or stalls. 2) Who really has leverage - Miners/pools: Control signaling and block production. If they don't play ball, activation drags. If they coordinate, it can move very fast. - Core maintainers & lead devs: Control what's merged, what binaries ship, and which activation method/warnings land in the "standard" client most people run. - Exchanges/custodians/Payment-Service-Providers: Control where coins flow. If they choose a side, liquidity follows them. That decides practical reality more than forum votes. - Ordinary users: Matter in aggregate, but only if they can withhold liquidity or hash in a coordinated way — which is rare. 3) Why this concentrates power - Coordinating thousands of small users is hard; coordinating a few dozen institutions is easy. - Activation schemes with time windows and thresholds reward actors who can move in lockstep (pools, large infra, top client maintainers). - "User veto" exists in theory (run your own rules), but without miners and exchanges you're on a minority chain with no liquidity. 4) What this means in practice - Technical purity loses to coordination. The "best" design doesn't win; the most coordinated coalition does. - Messaging is part of the game. Activation method choices ("Speedy Trial", LOT=true/false, flag days) are politics encoded in software defaults. - Future upgrades repeat the pattern. Expect negotiations between dev leads, pools, and big venues; users mostly ratify by upgrading after the fact. 5) Bitcoin's upgrades aren't decided by abstract ideals — they're decided by who can coordinate miners, code, and liquidity fastest. That's why power tends to cluster with aligned institutional actors, and why future changes will follow the same political playbook. States would like to keep their monopoly on money issuance and aren't fond of permissionless money. Bitcoin's survival and adoption, as censorship-resistant money, depend on whether its most committed users can detect, coordinate, and counter inevitable policy, market, and social attacks. This is tough to do if you're oblivious to what's happening. It doesn't help that Bitcoin mining is awfully centralized ( ). The solution of course is a more vigilant community and more decentralization everywhere: - miner-selected templates (DATUM/Stratum V2), - more viable client implementations, - privacy and self-custody defaults and better non-custodial payments UX, - routing around perimeters (App-store independence, Cloud independence, ISP resilience, etc), - routine, verifiable Proof-of-Reserves across custodians (anti-Paperization).
Control-Plane Capital's avatar
buckyfonds 0 years ago
Started doing more research on how Bitcoin Core's developers have been attacking its sovereign/Medium-of-Exchange use a while back and it's wild. The post became too long for email just from covering: 1. SegWit (BIP141): The “Witness Discount” and Block-Weight Accounting 2. Taproot (BIP340–342): Easier Complex Scripts and Data Embedding 3. Liberalized Data-Carrier Policies (OP_RETURN and “Standardness”) 4. Replace-By-Fee (RBF): From Opt-In to Broad Default 5. Relay and Mempool Settings that favor Large Players 6. Legal-Risk Externalities shifted to Node Operators 7. Increased Block Weight → Centralization Pressure 8. Convenience Defaults: Assumevalid, Pruning, and Checkpoints 9. Deprecation of Non-Standard Scripts 10. Fee-Market “Purism” — No Priority for Payments 11. Lightning Network Bias — L1 as Settlement Only 12. Governance Activations Show Who Sets the Rules 13. Quiet Merchant De-Feature: BIP70 Payment Protocol Deprecation 14. Removal of “Priority by Coin Age” & Free Relay (historical) 15. Dust Limits & MinRelayFee Floors as Gatekeepers 16. Core v30: OP_RETURN/data-carrier expansion (policy) 17. Core v30: RBF ergonomics tilt further to replaceability (wallet/API surface) 18. Core v30: Multiple OP_RETURNs per tx Have written this in as simple as possible terms for non-developers. Will post later when done. image
Control-Plane Capital's avatar
buckyfonds 1 year ago
Bitcoin Core's attack on Bitcoin's user base is fascinating. As a programmer, one of the first things you'll learn is to create useful abstractions and not leak implementation details onto your user base. This is crucial if most of your user base is non-technical. TL;DR - What happens when implementation details leak to a non-technical crowd When core developers narrate mempool policy, witness discounts, inscription paths, version bits, OP_RETURN limits, and soft-fork mechanics to a mostly non-technical user base, governance "leaks" without ceding control. Users inherit responsibility (anxiety, vigilance costs) but not power (they don't run code audits, write policy clients, or operate pools). In a low Gross Consent Product world, this leak is useful to the Controllers and intermediaries because it: - Expands the social attack surface (narratives, panic, brigading) while concentrating technical leverage (maintainers, pools, relay policy, app-store distribution). - Raises the "cost of being sovereign" (time, knowledge, operational burden), pushing the median user toward paperization (ETFs, custodians, on-ramp wallets). - Creates manufactured "consent cycles" — public comment drama around esoterica (v30 defaults, policy limits) that legitimize changes after the audience tires out. Leaking implementation details to the masses doesn't democratize Bitcoin; it socializes worry and privatizes control. In a low Gross Consent Product regime, that's a feature: it nudges users toward policy-safe defaults while maintaining the narrative of openness. Expect rising paper share, falling realized volatility, steerable settlement via pools/relays, and Medium-of-Exchange throttled in favor of stablecoins/CBDCs. It goes much deeper and I'll cover this in more detail later.
Control-Plane Capital's avatar
buckyfonds 1 year ago
I wrote on article on whether Bitcoin is decentralized and secure or is allowed to look decentralized and secure. Feel free to debunk it. TL;DR Bitcoin is permissionless in code but permissioned in practice by choke-points that governments and large intermediaries either directly control or can cheaply coerce. It’s allowed to look decentralized/secure so long as it functions primarily as a supervised store of value and speculative asset, not a mass medium of exchange outside compliance rails. Bitcoin’s design is decentralized in protocol, but the real-world control surface has shifted into layers above consensus: pools, clouds, app stores, and custody perimeters. These are the quiet levers that steer usage without changing the code.
Control-Plane Capital's avatar
buckyfonds 1 year ago
The question that sent me down the rabbit hole a few months ago: - Is Bitcoin decentralized and secure, or is it allowed to look decentralized and secure? TL;DR Bitcoin is permissionless in code but permissioned in practice by choke-points that governments and large intermediaries either directly control or can cheaply coerce. It's allowed to look decentralized/secure so long as it functions primarily as a supervised store of value and speculative asset, not a mass medium of exchange outside compliance rails.
Control-Plane Capital's avatar
buckyfonds 1 year ago
Something interesting to Game Theory. What would happen in the unlikely scenario that the plebs try to un-capture Bitcoin now that it's so entrenched into the financial system. It's a bit late in the game for it to get the full Monero treatment. Assume a materially higher Bitcoin Community Vigilance & Coordination (CVC): client diversity rises, mempool policy hardens, mining/pool governance decentralizes, anti-paperization/Proof-of-Reserve norms spread, and the community routes around choke points. Things that would be interesting to cover: - What "Operation Un-Capture" looks like in practice - Likely state/industry reaction - Likely outcomes - Price/vol & adoption dynamics - What would work for the plebs (and what backfires) My quick read is that the most likely outcome is a two-tier Bitcoin. - Tier 1 (Compliant BTC): ETF/custodial flows, payment gateways, regulated L2s. Clean UTXO sets fetch slight premium, fast merchant acceptance, low frictions — but full surveillance. - Tier 2 (Sovereign BTC): self-custody, privacy-hardened clients, peer channels; on/off-ramp friction rises, spreads widen, but actual censorship resistance improves.
Control-Plane Capital's avatar
buckyfonds 1 year ago
Most of Bitcoin's success rides on the Community: Suggested Improvements If you consume Bitcoin content, most of what's discussed are protocol-level truths. However, based on my research, Bitcoin's survival and adoption depend on whether its most committed users can detect, coordinate, and counter inevitable policy, market, and social attacks. The Drivers of Success - TL;DR - Community Vigilance and Coordination (CVC): 50% How quickly and effectively the core community mobilizes around threats — through client diversity, mempool policy control, mining/pool governance, anti-paperization norms, Proof-of-Reserves (PoR) culture, and censorship-resistance operations. - Policy-Perimeter Exposure (PPE): 25% The network’s exposure to choke-points such as app stores, banks, cloud providers, internet service providers, custodians, and exchanges — and its ability to route around them. - Economic and Game-Theory Design (EGT): 15% The soundness of incentive structures: fee and issuance security budgets, validator or miner incentives, and containment of Maximal Extractable Value (MEV). - Protocol and Infrastructure Quality (PIQ): 10% The technical foundation: client maturity, developer tooling, code audits, and use of formal verification methods. I've written about this and suggested improvements here: https://controlplanecapital.com/p/most-of-bitcoins-success-rides-on
↑