Bitcoin Protocol Role Models
MAY 25, 2016
Blog personal de Gavin Andresen
http://gavinandresen.ninja/bitcoin-protocol-role-models


A couple of months ago, I was having Yet Another Argument with a Bitcoin Core contributor about the one megabyte block size limit.

I had asked: “what other successful Internet protocols impose arbitrary limits on themselves similar to the one-megabyte limit?”

His answer was “there are limits on the size of the global routing table in the Border Gateway Protocol (BGP) protocol.”

BGP is the protocol routers use to decide what to do when they get a data packet bound for an IP address like “111.12.1.1” – they send it to China (111.12.1.1 belongs to the China Mobile Communications Corporation right now).

So I went and skimmed through the BGP protocol documents. Then read the wikipedia page on BGP. And had the opportunity to talk with Justin Newton, who participated in the debates on Internet scalability fifteen years ago.

And found that there are no protocol-level limits on the size of BGP routing tables. There is no place in any BGP specification I can find that says “Routing Tables Shall Be No More Than Eleven Gigabytes Big.”

BGP is interesting, because it is a completely different way of doing decentralized consensus than Bitcoin. Instead of proof-of-work, BGP’s consensus is built on real-world trust relationships between people operating the networks that make up the Internet. That works surprisingly well most of the time, especially considering the stunning lack of security in the BGP protocol.

There are limits on routing table sizes, but they are not top-down-specified-in-a-standards-document protocol limits. They are organic limits that arise from whatever hardware is available and from the (sometimes very contentious!) interaction of the engineers keeping the Internet backbone up and running.

I haven’t been able to find a widely-used Internet-scale protocol that arbitrarily limits itself. The closest I’ve found is the Simple Mail Transport Protocol (SMTP) which has a SIZE header that a server can use to specify the maximum email message size it will accept. The arbitrary limit chosen by the SMTP designers is 99,999,999,999,999,999,999 bytes (just under 100 exabytes).

The HTTP 2.0 spec explicitly discusses denial-of-service attacks, but doesn’t impose hard limits: “An endpoint MAY treat activity that is suspicious as a connection error of type ENHANCE_YOUR_CALM” (I can’t help imagining the server as a California Surfer saying “enhance your calm, dude!)

That’s a well-designed spec. Trust that smart developers will fix scaling or denial-of-service issues as they arise– and, if for some unforeseen reason it turns out they can’t, trust that there will be either an amendment to the spec or a "best practices” document to fix the problem(s).

Satoshi
"I believe Craig Steven Wright is the person who invented Bitcoin"
MAY 2, 2016

http://gavinandresen.ninja/satoshi

[bitcoin-dev] Eli Dourado on "governance"
Gavin Andresen
Mon Aug 3 2015 https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/009878.html

MAY 5, 2015
Will a 20MB max increase centralization? "I chose 20MB as a reasonable block size to target because 170 gigabytes per month comfortably fits into the typical 250-300 gigabytes per month data cap– so you can run a full node from home on a “pretty good” broadband plan." http://gavinandresen.ninja/does-more-transactions-necessarily-mean-more-centralized

[bitcoin-dev] What Lightning Is
Gavin Andresen
Sun Aug 9 2015
Previous message: [bitcoin-dev] What Lightning Is
Next message: [bitcoin-dev] What Lightning Is
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
While we're on the subject of payment hubs / lightning network...

I'd love to see somebody write up a higher-level description of what the
user experience is like, what communication happens underneath, and what
new pieces of infrastructure need to get built to make it all work.

A use-case to start with:

A customer starts with eleven on-chain bitcoin. They want to pay for a nice
cup of tea. Walk me through what happens before/during/after the
transaction, assuming I have a lightning-enabled wallet on my iPhone and
the tea shop has a lightning-enabled cash register.

Assume neither the customer nor the tea shop are technically sophisticated
-- assume the customer is using an SPV wallet and the tea shop is using a
service similar to Bitpay.


Gavin Andresen https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010072.html

"Apenas con unos meses en el cargo principal de Bitcoin Core, el desarrollador participó en una conferencia de tecnologías emergentes, organizadas por la CIA.

Para él, esta invitación reflejaba el interés del gobierno en Bitcoin, y la consideró una oportunidad para demostrar que los principales objetivos de la criptomoneda creada por Nakamoto son compatibles con los objetivos del gobierno. ..."

https://www.criptonoticias.com/analisis-investigacion/gavin-andresen-desarrollador-bitcoin-recibe-testigo-nakamoto/

From mid-2010 until April-2014, Gavin Andresen maintained control of the Bitcoin Core GitHub repository and was considered Bitcoin’s lead developer. On April 8, 2014, Andresen stepped down and van der Laan agreed to take over as Lead Maintainer of the Bitcoin repo. His salary is paid by MIT’s Digital Currency Initiative, where he works on Bitcoin development with Andresen and Cory Fields
https://www.weusecoins.com/wladimir-van-der-laan/

Te acuerdas de Gavin Andresen, al que Satoshi lo dejó a cargo del mantenimiento del Bitcoin?
Pues él también es partidario de los bloques grandes!!!!

Deal with it!!!!

https://twitter.com/gavinandresen/status/1155815750134915072?s=19

in these 16 minutes of audio is "the mother of the true", please take the time to listen to the audio carefully, it is in .3gpp format I suppose that with any mobile you can listen perfectly, I would love to see the audio transcribed to text, It is much more than revealing !!!!!
The original podcast is in the article by Andrew O'Hagan


The Satoshi Affair.
Andrew O’Hagan in the #LRB:
June 30, 2016
https://www.lrb.co.uk/v38/n13/andrew-ohagan/the-satoshi-affair


The people mentioned in the audio are:
- Gavin Andresen, whom Satoshi left in charge of software maintenance.
https://t.me/GavinAndresen1

nCrypt:
https://t.me/joinchat/AAAAAEVaX1Svb5ELSMHQiQ
Company that paid Gavin's trip to London to do the cryptographic test, to prove that Craig was Satoshi, the company is currently closed, it is likely to be owned by Robert S. MacGregor

Robert Scott MacGregor
https://t.me/joinchat/AAAAAFfVGRJmxxGxuQt0yA
Canadian - Estefan's friend

Squire Mining LTD & Stefan Matthews
https://t.me/joinchat/AAAAAFBaY1T97tMJYhhNtw
Stefan Matthews - currently runs a BSV mining business

Stefan Matthews:
https://t.me/joinchat/AAAAAFktyBI_wdMebiehFQ
meet Craig from the time of Craig as cybersecurity

Craig Wright Cybersecurity
https://t.me/CSW_Cybersecurity

Ramona the current wife of Crig

Craig Wright - Satoshi Nakamoto?
https://t.me/joinchat/AAAAAEbFuqsykt-sLEzD2g

en estos 16 minutos de audio está "la madre del cordero", por favor tomaros la molestia de escuchar el audio con detenimiento, está en formato .3gpp supongo que con cualquier móvil se puede escuchar perfectamente, me encantaría ver el audio transcrito a texto, es mucho más que revelador!!!!!
El podcast original se encuentra en el artículo de Andrew O’Hagan


The Satoshi Affair.
Andrew O’Hagan in the #LRB:
30 June 2016
https://www.lrb.co.uk/v38/n13/andrew-ohagan/the-satoshi-affair


Las personas que se mencionan en el audio son:
- Gavin Andresen, a quien Satoshi dejo a cargo del mantenimiento del software.
https://t.me/GavinAndresen1

nCrypt: Empresa que pagó el viaje de Gavin a Londres para hacer la prueba criptográfica, para demostrar que Craig era Satoshi, actualmente la empresa está cerrada, es probable que fuera de propiedad de Robert S. MacGregor
https://t.me/joinchat/AAAAAEVaX1Svb5ELSMHQiQ

Robert Scott MacGregor - Canadian - amigo de Estefan
https://t.me/joinchat/AAAAAFfVGRJmxxGxuQt0yA

Lectura altamente recomendada para este verano, prepárate para lo que viene!!!

The Satoshi afaire.
Andrew O’Hagan
30 June 2016

Telegram Channel
The Satoshi afaire.
Andrew O’Hagan
30 June 2016

https://t.me/joinchat/AAAAAEbzbs2V8nGVDbtPkg

https://sourceforge.net/projects/bitcoin/files/README.txt/download?

"Later, Gavin Andrsen (through reddit) gave details of this verification process for CW
Craig signed a message that I chose (“Gavin’s favorite number is eleven. CSW” if I recall correctly) using the private key from block number 1.
That signature was copied on to a clean usb stick I brought with me to London, and then validated on a brand-new laptop with a freshly downloaded copy of electrum.
I was not allowed to keep the message or laptop (fear it would leak before Official Announcement).
I don’t have an explanation for the funky OpenSSL procedure in his blog post". https://medium.com/@BlockByBlock/will-the-real-satoshi-please-stand-up-c97a670c4055