Loading video...

Video Failed to Load

Go Home

Satoshi Nakamoto. When he launched Bitcoin Jan. 2009 the Bitcoin protocol was: A MINER A NODE A WALLET All in one and it ran on a PC. halfin Hal Finney ran it on Windows. On a "spare" computer. With a CPU. No one in that early time envisioned there...

12,476 views • 11 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

satoshi never existed. nobody writes code like that. not that clean, not that surgical. the early bitcoin codebase doesn’t read like code from some anonymous guy on the internet. bitcoin's early codebase looks like it was handed to us. the whitepaper came out six weeks after the 2008 crash. that's not enough time to dream up a working distributed consensus system, let alone build one. then there’s secp256k1. not secp256r1, the curve everybody used. k1 was obscure, weird, and a terrible choice if you were just following convention. but it also happened to be one of the hardest to backdoor. and then satoshi disappears. roughly a million btc, untouched. people don’t walk away from that kind of money unless the money was never the point. because maybe bitcoin was never just money. what it actually did was create a global incentive to build compute. millions of people, in every country, pouring capital into hardware and electricity to chase block rewards. no state could have coordinated it that fast. no company could have justified it. a protocol paying out internet money gets people moving. then nvidia happened. the same GPUs pushed into the world for mining turned out to be perfect for large-scale parallel compute. the same hardware appetite bitcoin created ended up helping make modern deep learning possible. bitcoin launches in 2009. imagenet breaks things open in 2012. three years. bitcoin was the bootloader. and we’ve been running the install script.

tetsuo

53,736 views • 4 months ago

a contractor in Shenzhen priced a ¥12,470,900 hospital contract, about $1.7m, in one afternoon and beat firms carrying forty people he explained how he did it: the bid consultancy he used to pay took three days and ¥46,000 for the same envelope. he did this one alone, off one screen, at 11.4% margin, uploaded before the 17:00 cutoff 214 pages of tender documents read, 68 binding clauses pulled out, 9,485 building parts loaded, 14 places found where a duct and a beam sit in the same cubic metre, deepest one 38mm, all of them fixed, 3,318 lines of quantities priced and the package encrypted and uploaded before the 17:00 cutoff this is Graph Engineering: the job gets cut into small nodes, one narrow task each, wired so that one node's output is the next node's input, and any node is allowed to stop the whole run. it turns a model that answers you into a machine that finishes the job: - give every node one job and one output. a node doing two things fails at both and you cannot tell which one broke - put the cheapest rejection first. his qualification node reads clause 7.4, foreign-owned firms barred, and ends the run four seconds in, before anything expensive touches the model - what moves between nodes is a file. the model travels as a model, the quantities as a table, the price as a number - build exactly one loop: the checker finds 14 collisions, the fixer drops the duct 550mm, the checker runs again, and nothing moves on until the count is zero - cap that loop, or a graph will grind on three impossible clashes until the deadline passes - keep one node whose only job is to say no, and give it authority over everything above it - log each node's output on its own, because when the price comes out wrong you need to know which node believed the wrong thing - run the expensive nodes last, always the catch is that a graph is an extremely confident machine: point it at an outdated rate book and it prices an entire hospital off it without a single node noticing, because no node is asked to doubt the input, only to process it so the nodes that earn their keep are the ones that reject, and almost nobody builds those first bookmark this, the full build with all nine nodes and what each one hands to the next is written out in the article ↓

Argona

38,189 views • 13 days ago