Anym Bck

977,429 BCK to 767,430 #Forkgivening

@plebhash as soon as #forkgivening

wen OP_CTV? wen covenants?

github.com/gnostr-org/gno… #gnostr #nostr #nip340 #nip34 cc: @NodeHello @nvk @not_brian_troll @reardencode FROST Quorum integration decentralized signing of software release code and versioning. This enhances trust and resilience in the software supply chain.

Weaponizable peer-review is a thing of the past thanks to -kapnet.

BTC ReferenceNet bitcoind -kapnet Track magic bytes within solved + under-solved blocks to validate incoming relayable TXXM traffic. Bitcoin scales fractally 80-byte work-linked headers contain merkle commitments to 80-byte OP_Return weakwork tickets to append elsespace.

@Pledditor @adam3us Transcend, encourage 110net to manifest as an intentional new direction. Coach miners into demonstrating hashrate sovereignty, extending the chain they wish to User Activate.

Bitmex Research, Adam Back, Shinobi, etc... have been excellent bitcoiners, who've dedicated large amounts of their personal time the past 6-8 months patiently educating to the most ignorant plebs on this website why BIP-110 is a terrible idea, why it's dangerous, and why it won't activate, and I think now we are at that point where everybody whose mind can be changed, has already been changed. the debate has grown stale, the people who made their entire identity out to be "bitcoin has failed unless my fork happens" are cringe as fuck, and it's time to start blocking you guys because i'm tired of seeing your ignorant posts on my feed everyday. please make it easier for me to identify who to block by typing your angry replies below: 👇

@RandyMcMillan @BlockHostOS @TheBoozles Miner-Untouched Forkless Drivechains MUFD. So none of the drawbacks of BIPs 300/301, but all of the experimentation. Properly typed OP_Return messages (like Runes) hashed in templates commoditize blockspace at sub-difficulty work levels depending on demand for the protocol.

@anymBCK @BlockHostOS @TheBoozles sounds like drive chain or something?

how can you take this seriously? #bitcoin

@kaspakekius @ayebytes Thanks for the R&D🫡

@ayebytes Memepool become Kaspa DAG🤣

one of the changes expected to be included in Core 31 is Cluster Mempool transactions in the mempool are nodes with fee, weight, and dependencies. this creates a DAG (directed acyclic graph) structure where transactions are interdependent. any valid block must respect these relationships and include ancestors when selecting a transaction this leads to the Maximum Ratio Closure problem: selecting a closed subset that maximizes fee relative to weight, and turns block construction into a graph optimization problem previously, the mempool was treated as a flat set of independent transactions and now the Cluster Mempool groups connected transactions and evaluates them as graphs this impacts CPFP, fee estimation, and RBF algorithms (become more complex due to graph interactions) release notes: github.com/bitcoin-core/b…

@BlockHostOS @TheBoozles @RandyMcMillan No, the long term solution is more chaintips of smaller blocks all mergemined with BTC. bitcoind -kapnet

@TheBoozles @RandyMcMillan The long term solution is larger blocks and more space for scripts.

@adam3us @hodlviking @hodlonaut Governance is coming. #forkgivening -kapnet

@hodlviking @hodlonaut this is a confused governance attack. bitcoin doesn't have and must not have governance. you guys learned nothing from the block-size wars, which were actually about a business cabal trying to impose governance on the necessarily un-governable.

Bitcoin’s next critical battle is GOVERNANCE. @hodlonaut just dropped the first piece of a nuclear investigation: How a small, tightly-knit network quietly built, exercised, and defended informal power over Bitcoin Core. Recruitment pipelines. Funding capture. Social armor. The exact mechanism that turned “leaderless” into something else. The 2025 Knots surge was the network fighting back. If we don’t get governance right going forward, we don’t keep sound money.

@simulx4 @BITVOLT @saylor Monetizing patience at the protocol level means rewarding UTXO keyholders with hedlbit balances to use or sell for sats. From the minds that brought you #aggwit there's also HedlBits that pay for alt p2p bandwidth in -kapnet.

@BITVOLT @saylor and $ibit are doing their level best to make sure this doesn't happen it's an uphill battle and it's actually being lost, imo

Taking Bitcoin into cold storage is a revolutionary act. If enough people do it we win.

@Singekino_Miner What's wrong with Libbitcoin?

Blinded by 'liberty,' this fool can’t even recognize his own interests. Peak libertarian brain rot. 😮‍💨

Forking the repo is not enough. Decentralize node varieties by forking the entire UTXO set, as needed.

Nice to see the CTV+CSFS thread included in this week’s Bitcoin Dev Project TLDR. What matters most to me is that experiment-driven discussion is making it into the conversation. @Bitcoin_Devs

-kapnet BIPs cooking MVP deadline for weakwork-gated, hedl-bit metabolising chaosnet framework: BTC block 977429

@rohanpaul_ai -kapnet fixes this

New research proves that current AI agent groups cannot reliably coordinate or agree on simple decisions. Building teams of AI agents that can consistently agree on a final decision is surprisingly difficult for LLMs. But problem is that developers frequently assume that if you have enough AI agents working together, they will eventually figure out how to solve a problem by talking it through. This paper shows that this assumption is currently wrong. Even in a friendly environment where every agent is trying to help, the team often gets stuck or stops responding entirely. Because this happens more often as the group gets bigger, it means we cannot yet trust these agent systems to handle tasks where they must agree on a correct answer. ---- Paper Link – arxiv. org/abs/2603.01213 Paper Title: "Can AI Agents Agree?"

@SlyGoomba -kapnet fixes Bitcoin

Im going back into full time orange pilling. Doomers have been winning, Bitcoin fixes this.

Got annoyed by Tailscale requiring 3rd party accounts, so created Nostr VPN. It signals over nostr relays and creates a wireguard / boringtun network. Builds for Macos and Linux. Using it between my Macs, but haven't tested extensively yet.

After three breaches, I stopped trusting “we promise” apps and built @darkfolioapp--- a portfolio tracker that is verifiably private. Full story, screenshots, verification guide, and my $10k pledge to @torproject and @rstormsf's defense, in the article below. 👇