Lightweb Inc. 🇺🇸 Infrastructure Engineering Unbounded Solutions for a Small World (TM)
Texas, USA
Joined February 2011
- Tweets5.2K
- Following113
- Followers1.5K
- Likes10.3K
Light retweeted
I've been focused on development of my new AI harness/OS @EdwinPai so I haven't been on X for a while.
The reason the mempool exists is to receive transactions so the first seen rule can be followed. Those transactions are then processed and added to blocks as quickly as possible.
Teranode processes transactions and adds them to subtrees/blocks as soon as they are received so a mempool is no longer needed.
The savings of immediate processing and subtree communication is superior to using a mempool because it's more efficient, and importantly, it accelerates the positive flywheel effect of node game theory:
Nodes receive as many transactions as possible and build subtrees as quickly as possible while hashing as quickly as possible to win the next block with as many transactions as possible to get the biggest block reward they can.
They are then incentivized to reinvest their earnings into their computing and networking infrastructure to be as competitive as possible and to earn as much profit per block as possible.
The result of this is the holy grail of computing systems which is a system that gets more efficient the more it's used.
It's the win-win-win relationship Satoshi carefully crafted in the original white paper: peer-to-peer electronic cash that's competitively maintained so individuals retain privacy, data provenance, and data ownership; the system gets cheaper and requires less energy to use as usage if it increases; and, node operators earn more while simultaneously being strongly incentivized to provide the best experience possible in order to earn more
A vault whose hosts never hold a key. bsecret keeps ciphertext only, refuses everything but the re-key once a removal is acknowledged, and lets an auditor verify every grant, version and rotation against block headers alone.
1bsv.net/patterns/bsecret.pd…
Light retweeted
Multicast is an Internet Protocol mode of transport that allows a user and the network to transmit one data packet to multiple recipients quickly and at once, without having to retransmit.
Unicast is the one-to-one complement of this, that most internet traffic rides on today.
I haven't run anything with PHP since like, 2006. People are really still doing this?
It's like trying to keep CGI scripts alive. I mean, there was a time period where that was okay. That time has long passed.
Traditional Observation: ISPs don't support MP-BGP at the edges and therefore won't support multicast over internet.
Engineering path: Force multicast through a specific frame type only, and carry actual multicast traffic over a separate topology formed on top, peered directly.
So when you want to step up like you know something more than I do, as if I haven't tested my own work, then prepare to walk away not feeling as big as you did before you served up your ill-informed opinion.
I'll talk about this network engineering stuff all day long.
Light retweeted
Just having a real, solid thing like a UTXO (spent or not) to identify flows in order to apply rate limiters is huge.
Traditional IP packets do not come with this feature when every packet is different, such as with large-scale, coordinated Distributed Denial of Service attacks.
How about a simple web request?
"I want to see CatPicture.jpg. Whoever can deliver it to me the fastest gets paid."
That's possible when you're sending the request to many listeners at once, and it's very lightweight, and bounded by economics by being anchored to a blockchain.
One issue I see with the current (not future) state of SPV:
Checks are about 10x slower in JS than in Golang.
