

Connor Murray
7.9K posts

@Bitcoin_Beyond
I like Bitcoin, and opinions are my own









BSV Browser is likely to have been seeing all outbound transactions fail for the last few hours at least. The Teranode which it connects to via arcade is misbehaving. I took a risk adopting the latest and greatest technology before it was quite ready for Production. Some of the team are working this weekend to switch the connection to another Teranode. Things will work again thereafter, but that could be a few hours from now. I will update here when things are back online. Apologies for inconvenience caused. The real issue is that despite there being multiple failover routes for broadcasting transactions built into the app; the arcade is failing in a way which makes it look like a double spend attempt. I’m not sure why. The wallet toolbox behavior in that case is to shut down all other attempts to Broadcast.


Holy Wow We are at 1/3 of the way to our goal. If you want to see the magic in action check out mesa.chefmyklove.com Even if I don't win the @BSVAssociation Open Run Agentic Pay #hackathon I'm excited about this entry as a proof of concept for agentic auction marketplaces.





One for the Aviation fans! ✈️🧑✈️ airchive.vercel.app As a submission into the BSVA's OpenRun AgenticPay Hackathon, I decided to create something a little different. Essentially, Airchive takes data directly mostly from ADS:B (Automatic Dependent Surveillance–Broadcast) — This provides real-time, high-precision surveillance data by broadcasting aircraft position, altitude, speed, and identification to ground stations and other aircraft. Unlike traditional radar, this satellite-based system improves situational awareness for air traffic control (ATC) and pilots. --- Each aircraft has it's own unique HEX code (identifier) within this system. From there, I created an easy to use system which is as simple as entering an Aircraft HEX Code into the .env variables, and the system automatically creates and handles individual wallets and UTXOs for each aircraft on the 'fleet', all funded from a single main 'Funding Wallet'. The system also uses three agents — Collector, Analyst, and Monitor. They gather and trade data, analyse fleet information, and track live data for each aircraft. They then broadcast summaries and updates on-chain using their own wallets. --- In terms of throughput, currently it's running a fleet size of 239 Aircraft, all of which is handled via 'smart-logic', to avoid wasteful expenditure, for example: During 'taxiing' and 'parked' periods, chain-writes are slowed to a period of 120s intervals, since it's lesser important. When the aircraft's ignition is switched off, the aircraft is considered 'offline'. During more crucial periods, such as take-off and landing — chain writes are at 1 second intervals, and during cruise is currently set at 2 second intervals. All are easily customisable via '.env' too. To give an idea of a potential maximum scalable throughput, it is often cited that during peak periods, up to 20,000 aircraft may be airborne at any one time. This would allow the system (with optimisation) to achieve well over 200 million transactions daily — around 2,315 TX/s. This could be further increased by changing chain write intervals, but of course — it's important to balance affordability and data requirements, which may vary for different use-cases. --- A rough estimate for cost comparisons based on fleet size and average flight times is available here: airchive.vercel.app/demo, whilst a list of the current aircraft fleet wallets are available at: airchive.vercel.app/wallets --- @BSVAssociation — Thanks for the opportunity to build more cool Apps! 🥳 (hackathon.bsvb.tech) — Give the BSVA a follow and keep your eyes peeled for any future hackathons that you perhaps wish to enter!

The cleanest way to “freeze” quantum-insecure coins is just to sunset *all P2PK UTXOs at a defined block height.* Give Satoshi and anyone else, say, 3-5 years to move them. If they haven’t moved to quantum resilient addresses by then, they are assumed to have been lost or forfeited by their owners. Nothing wrong with sunsetting old network components that present vulnerabilities. This gets rid of the “confiscation” language. It’s a technical bug fix/security upgrade.














Tonight we found 2 bugs in BSV's Chronicle upgrade within hours of it going live. Here's what made it possible: Our SPV federation — 4 bridge nodes speaking Bitcoin P2P protocol directly to SV nodes. No middleman. No API dependency. That infrastructure is what proved these bugs exist. When we found opcodes in unlocking scripts were being rejected, we knew it wasn't some API blocking it — because we broadcast through P2P directly to the nodes. That led us to identify the exact layer causing the rejection. When we tried to grab a 1 BSV bounty and it got stuck, our bridges got the tx further than anyone else — all the way into ARC's mempool. Other methods just said "Missing inputs" and stopped. Our bridges pushed through. When we ran the control test that proved the bug, we broadcast both the rejected and accepted spend through the same bridges, same path, same nodes. Clean experiment. You can't do that through someone else's API. Most people connect to BSV through third-party APIs. We have our own path in. That's why we found what we found. Build your own infrastructure. Test things yourself. The bugs find you. — Indelible Federation