I wish to demonstrate a physical network topology capable of distributing 1 billion BSV transactions per second, and generate the data to prove it, shared publicly. This is without transaction validation, at first. Teranode will catch up in time. @1BSVNET will be ready for it.
At 100 Gbit we're talking about 60 million+ TPS per link, and with the design you can shard/stack links. I aim to broach the 100 million TPS mark long before Teranode gets there, but when they do, the network will be ready. The design allows for this type of capacity planning.
I noticed this other Record Anchor API service as well. 150,000 transactions that each contain a small SHA fingerprint on chain, for $95/month.
I am thinking back to some things I just wrote in a paper I just released on storage economics. Interesting.
app.whatsonchain.com
A new idea is to charge for incoming BSV transaction delivery to miners, so a middleman service built on Broadcaster/Arcade.
1 transaction per second free tier.
Max tier 400 transactions per second on $249/month Pro Plan.
Interesting pivot. app.whatsonchain.com/
That's not to say we can't infuse payment tech all throughout data tech, because we can, and will, but just solving data provenance, defense, ownership, control, property rights and other issues are big enough tasks alone. Payments weave in and out of these solutions.
A random, anonymous incoming traffic source is forced to sign a transaction using a verifiable output anchored some time back on chain, and used only once. Does this provide for further incentives or disincentives for an arbitrary network attack? What about when funding is gone?
To get to high throughput on chain, we're going to have to think outside of the box and build things never attempted before. This is going to require looking beyond just "payment tech".
My focus is on "data tech", because the whole show runs on data management and distribution.
It's just something I whipped up in a few hours today after the idea occurred to me as I was attempting to come up with ways to better describe what I'm working on. What better way than a new take on an old favorite. There's room for improvement. Feedback and questions welcome.
github.com/lightwebinc/beefc…
It's like the old Unix netcat utility, which I remember when it first came out in 1995. This tool uses the BEEF data carrier pattern, so it comes with SPV and key signature checking. This is how you anchor any data transfer cheaply on-chain. Check it out.
Frank Herbert spells it out with cold, surgical clarity across Children of Dune and especially God Emperor of Dune.
Leto II, the worm-human God Emperor, has seen the future in full and knows that a comfortable, centralized humanity will stagnate, become predictable, and eventually be wiped out by some external or internal catastrophe.
So he deliberately becomes the ultimate tyrant: a living predator who rules for 3,500 years through absolute control of the spice, suppression of technology, and ritualized brutality. This is not sadism; it is the Golden Path.
By making himself the most oppressive force in history, he breeds a deep, genetic hatred of centralized power into the human race, forces the evolution of individuals who can hide from prescience (like Siona Atreides), and creates the pent-up pressure that will explode into the Scattering the moment he dies.
Humanity must be taught to fear any single authority enough to spread so far and so unpredictably that no future threat, machine, tyrant, or famine, can ever reach all of it at once.
His brutality is the price of the species’ long-term survival; he becomes the monster so that, after him, no one else will be allowed to. The films have not reached this yet, but the books treat it as the entire point of his reign.
How does a wallet know it got paid? 🤔
Paid to an address: it asks an indexer. However it’s built, something has to read every transaction.
Paid directly: the payer sends you the transaction, with proof it’s real.. so there's nothing to look for.
There are two main levers for scaling the Spine or backbone of the network: shard width, and ever increasing network interface and bandwidth capacity.
1.6 Terabit interfaces now being tested for production.
800 Gbit is a standard product offering.
1M TPS is 3 Gbit.
Scale.
Where the full stream becomes a fire hose, it can be shaped by tweaking the shard-bit calculation value. Increase bits by 1, and suddenly there are two separate stream groups to traffic shape independently. Repeat, up to 4096 streams. Faster interfaces cut that figure back down.
On the wire: BSV/Bitcoin settlement (EF) transactions, subtree data, blocks, block headers, alert data, BSV Overlay BEEF transactions. All BSV/Bitcoin primitives.
Every one has some assurance baked in, because it's identifiable, and you can check it for integrity or to verify.
Plumbing, or maybe even Electrical Transmission. Instead of dealing with routed traffic from an entire Internet worth of endpoints, the data on the wire is all atomic. It's all Bitcoin transactions. Every packet is BSV (excepting network telemetry, etc, but even that can be too).