nemecis

Bitcoin Cash's 1-minute block proposal: Are we rushing toward the finish line? I've been following the 1-minute block proposal (gitlab.com/0353F40E/fablous), and while I support the concept in principle, I'm increasingly hesitant about the push toward the November 15 Chipnet activation and lock-in. Faster confirmations could be a meaningful improvement for bitcoin-cash:native, especially for DeFi and other applications that depend on confirmed transactions. But supporting the idea and being confident that it's ready are two very different things. My biggest concern isn't necessarily the proposal itself. It's the process and the urgency surrounding it. We're changing one of the most fundamental properties of Bitcoin Cash. This involves considerably more than producing blocks 10x faster. There are changes to timelocks, infrastructure requirements, network behavior, and potential security implications that deserve extensive scrutiny. And frankly, I'm uncomfortable with the amount of social momentum being built around meeting the November 15 deadline. Public endorsements are valuable, but popularity isn't technical validation. We should be encouraging critical review, not creating an environment where raising concerns feels like standing in the way of progress. This also raises an important question about Chipnet. The proposal is scheduled to activate on Chipnet six months ahead of mainnet. That's supposed to give us time to discover problems before they affect real users. But what happens if we discover something serious? Under the modern CHIP process, we haven't had to navigate a major redesign following Chipnet activation. That doesn't mean we'll never need to. If the design is effectively locked in on November 15, how much flexibility remains to address fundamental issues discovered afterward? And who decides whether a finding warrants a patch, a revision to the CHIP, or postponement of mainnet activation? I think these questions deserve clear answers before the lock-in date in 10 days. More importantly, I want to see the BCH community aggressively stress-test Chipnet. Not just run a few transactions and confirm everything appears to work. I mean deliberate, adversarial testing. Push the network to its limits. Challenge assumptions. Test abnormal conditions, node behavior, timelocks, infrastructure compatibility, and potential resource-exhaustion scenarios. Invite developers, miners, infrastructure operators, and security researchers to actively try to break the proposed upgrade in a coordinated testing environment. The objective should be to uncover problems, not merely demonstrate that the implementation works as intended. Findings should be documented, independently reviewed, and addressed before the upgrade is considered mainnet-ready. And if serious issues require revisiting the design, we should be willing to revisit it, even if that means missing May 2027. I recognize the tremendous amount of work developers have put into this proposal, and I don't want that effort to go unappreciated. But BCH has made substantial technical progress over the last several years. CashTokens, covenants, and VM improvements are still opening doors that the broader industry has barely explored. We shouldn't feel pressured to rush fundamental consensus changes simply because faster block times are attractive or because there's momentum behind a particular deadline. When presented with the option of either a rush job or a delayed release, I'd rather see BCH take another year to get something right than spend years dealing with the consequences of getting it wrong. Chipnet should be where we try to break things, not where we begin assuming everything will work. And if we aren't prepared to change course based on what we discover there, what exactly are we testing for? As the old @Blizzard_Ent mantra goes - "It's ready when it's ready"

One-minute blocks on bitcoin-cash:native? Not yet. CHIP-2025-03 rescales real problems instead of solving them, and shifts costs nobody has measured. My minimum ask: no lock-in on Nov 15. notyet.leobeltran.com/

🔬 Full Bitcoin Cash mainnet validation with Knuth — here are the numbers. Every block. Every transaction. Every script. Every signature. ✅ 974,756 blocks validated ⏱️ 5h 2m of active runtime 🔐 Signature verification calls recorded: • 1,003,773,400 ECDSA • 198,156,859 Schnorr • 1,201,930,259 total Over 1.2 billion signature verification calls. No checkpoints above genesis. No assumevalid. Full script validation from block 1. For context: an IBD with checkpoints takes under 1 hour. This run included all historical script and signature checks. 🖥️ Ryzen 9 9950X3D · 60 GiB RAM · NVMe #BitcoinCash #BCH #Knuth

Heroe anónimo impide asalto en 7Eleven. Los buenos somos más.

Por tu seguridad, Chrome escaneará tu portapapeles Google ha anunciado que Chrome incorporará una nueva función de seguridad que analiza el contenido del portapapeles para detectar amenazas, especialmente estafas tipo "ClickFix". Esta medida forma parte de la Protección Mejorada de Navegación Segura (modo opcional) y utiliza un modelo avanzado de Gemini ejecutado en los servidores de Google. Cuando el usuario tiene activada la Protección Mejorada y copia un comando potencialmente peligroso (por ejemplo, instrucciones para ejecutar en PowerShell o la terminal del sistema), Chrome envía una versión procesada y depurada del contenido a los servidores de Google para un análisis de comportamiento. Si se detecta riesgo, el navegador muestra una advertencia antes de que el usuario lo ejecute. Según Google, el contenido se limpia de información personal identificable antes de abandonar el dispositivo, no se almacena y no se utiliza para entrenar modelos de IA. La recopilación se limita al mínimo necesario para identificar amenazas. La función no analiza todo lo que se copia, sino solo comandos sospechosos asociados a este tipo de estafas.

Se parece a las ideas que se me venían a la mente para "mejorar" cosas en #Bitcoin cuando tenía como 17 años entre 2014 y 2015 jaja Los Bitcoin-Blake2b me dan tanta risa 🤣🤣

Vinix's ISO size has gone down from 1 GB to just 100 MB! This was achieved by removing Firefox, X11, debug info, and many other packages that can be easily installed. An yes, Vinix doesn't need X11 to run, it has its own WS. vinix-os.org blog.vinix-os.org/post/42/vi…

CashRiders Stage II starts now 🤘🔥 2 new riders onboarded. 12/20. 🛵💚 There’s real interest, questions, and great energy from the riders. This is starting to grow for real. Help keep it moving with CashRains 🌧️ munia.cash/community/cash_ri… Bitcoin Cash: Real Bitcoin for Real People.

Bro was clearly impressed 😂

You might think tokens can't be mined with Proof of Work, but PHOTON is a CashToken on the Bitcoin Cash network that can be mined with a GPU ⛏️ The basic idea is that BCH covenants can enforce the mining rules and release token rewards when valid work is found. I built Pickaxe Miner to help those who want to mine CashTokens with just a few clicks. It's open source and works on both Windows and Linux. github.com/CyberAshven/picka…