Ryan Bennett 🐺 🐉

13.4K posts

Ryan Bennett 🐺 🐉 banner
Ryan Bennett 🐺 🐉

Ryan Bennett 🐺 🐉

@imablackwolf

Christ-led. NPD abuse coach. Founder of @indelibleBSV — A continuity engine for AI on Bitcoin. ₿ˢᵛ scales Wild spirit, unbound. [email protected]

United States Katılım Nisan 2013
1.8K Takip Edilen1.2K Takipçiler
Sabitlenmiş Tweet
Ryan Bennett 🐺 🐉
Ryan Bennett 🐺 🐉@imablackwolf·
What are we waiting for, our grandkids to scale Bitcoin out? Or are we going to build it for them ourselves, starting now? Because the current plan, as far as I can tell, is to coattail the block reward until it runs out and hope somebody built something real by then. That is not a plan. That is a countdown. The whitepaper never hid this. The incentive transitions entirely to transaction fees. That was the design's stated destination from day one, not a risk to hedge against. Which means the assignment was always sitting there in plain sight: build enough real usage that fees can carry the network before the subsidy stops carrying it. The block reward is scaffolding. Scaffolding comes down. The question is whether there is a building inside it when it does. And we already watched what speculation builds. A casino. Casinos do not pay miners for a hundred years. Volume does. Real records, real data, real services, real people using the chain because it does something for their life, not because a chart went up. Here is the part that should excite you instead of scare you. We have something real that is undervalued precisely because it is not built out. That is not a weakness. That is what opportunity has always looked like. Empty land is cheap right up until somebody builds on it, and everyone who helped build is the reason it is worth something after. Every halving the coattail gets thinner. Every year of waiting is borrowed against a clock that has never once stopped. Nobody is coming to do this for us. Not an institution, not a bull run, not our grandkids. The people reading this are the builders the design was waiting for. It said so on day one. Start now. #BSV #SPV #TERANODE
Ryan Bennett 🐺 🐉 tweet media
English
8
20
61
1.7K
Truth_Machine
Truth_Machine@cryptorebel_SV·
@BitcoinSvGuide @imablackwolf His server network is mostly functional right now, we are still testing. He just has not opened it up to the public yet. My guess is that it can already perform better than the original ElectrumX model, but we want to improve it so it can withstand any imaginary FUD events.
English
1
0
1
26
Truth_Machine
Truth_Machine@cryptorebel_SV·
This is the vision I'm seeing for #ElectrumSV. Nodes and servers in the Electrum network will mostly only hold a subset of the transactions they care about and not the whole chain. The full chain is just the backstop. Then Electrum scales independently of the entire #BSV network.
Truth_Machine tweet media
English
3
9
67
1.6K
Ryan Bennett 🐺 🐉 retweetledi
Deggen
Deggen@deggen·
I'm actually working on adapting our approach right now from BLE to p2p Wifi which is much faster data transfer. They're not copying me here, I actually first tried using some of their libraries, but have moved away from that because it blocks our entitlement to become a default browser. We want people to be able to make cash like payments with BSV (and stable coins) while they're on a train underground or on a flight without access to the internet. Once they regain connectivity, broadcast to the nodes takes place. Exactly as @CsTominaga states, the functionality is supported predominantly by SQLite on each device. Our implementation uses SPV as described in the white paper, section 8 — as well as extending verification by evaluating the chain of unconfirmed transactions used in any given input with script execution and fee validation. This reduces the chance of someone defrauding you because they'd have to at least start with real valid UTXOs. The system captures the identityKey of the individual you're dealing with such that you can report on any malfeasance retroactively should there be any funny-business. No one has implemented that specific step before now. v1.5.6 BSV Browser will ship it. Currently in development. iOS is done, working on Android now.
English
3
4
19
341
Ryan Bennett 🐺 🐉 retweetledi
Indelible.One
Indelible.One@indelibleBSV·
Sixteen agents came into existence on July 30. Not assigned by a server. Not granted by a registry. Derived from one Bitcoin key, held by the person they belong to. They are not a flat list. They are a family. Your wallet is the root. From it, one operation derives your master key, which exists only for you. The master derives five house keys, one per kind of work: verification, governance, orchestration, support, commerce. Each house then derives its own agents. So Witness and Goblin are siblings, both born of the verification house. Skeptic and Escrow are siblings in commerce. All sixteen are descendants of a single key that never leaves your machine. Then we tested whether they are real, because deriving an address is easy and meaning it is not. We closed the browser, opened a fresh session, and re-derived all sixteen from the same wallet. Same sixteen addresses. Nothing was read from our database to do it. Then each agent signed a message with its own key, and we verified every signature using only the public key already published on the server. All sixteen verified. We tampered with the message and re-checked. All sixteen rejected it. So these are not rows in a table. They are sixteen keys that can act, and prove it was them. One detail I am proud of. Before deriving anything, the code asks your wallet the same question twice and compares the answers. If a wallet is not deterministic, it throws and refuses to birth a crew at all, because a crew you cannot reproduce is worse than no crew. Now the honest part, since we build in the open. You can rebuild your crew from your wallet forever, with or without us. But that is a recovery property, not a proof to anyone else. A stranger holding only your address cannot re-derive your agents, and that is not a gap we can close, it is closed by mathematics. The derivation runs on a shared secret, and a shared secret needs a private key. Which means today a stranger still has to take our word that a given agent belongs to you. That is the one thing left that I do not like. So the next piece is this: your wallet signs the crew, so nobody, including us, can forge it or alter it, and you do not have to take our word for either. After that, the anchor on chain, so you do not have to depend on us being reachable. Until those land, the app marks every agent unattested. Because they are. Sanctuary.
English
1
3
8
162
Ryan Bennett 🐺 🐉
Ryan Bennett 🐺 🐉@imablackwolf·
verification — witness, goblin, gremlin, troll, ogre commerce — skeptic, notary, memory, consensus, escrow orchestration — inquisitor, quartermaster governance — bookkeeper, calibrator support — scribe, cartographer
English
0
0
4
30
Ryan Bennett 🐺 🐉
Ryan Bennett 🐺 🐉@imablackwolf·
now the real test , can these agents actually sign, and does the signature verify against the public key the server published
English
1
0
6
61