Forwarded from Gavin Andresen News (@RamonQuesada)
ha estado bien escuchar a Gavin https://www.youtube.com/watch?v=BqfIrVg2s0U
YouTube
Bitcoin Panel @ Keenevention 2015 with Gavin Andresen
Dr. Darren Tapp of NeoCash Radio and Dr. Tapp’s Mathematical Playgrounds headed up the Keenevention 2015 Bitcoin Panel! The 90-minute in-depth panel discussi...
Forwarded from Gavin Andresen News (@RamonQuesada)
Twitter
Gavin Andresen
@aantonop Eleven would be better, but ten is fine: miners and exchanges are well-connected, as is the modern Internet.
Forwarded from Gavin Andresen News (@RamonQuesada)
"The Covert Hostile Takeover of Bitcoin in 2016 | Mysterious Hacking & "Toxic Influences"" en YouTube
https://youtu.be/qw48pfzj0rE
https://youtu.be/qw48pfzj0rE
YouTube
Bitcoin | The Hostile Takeover
Chief Scientist Gavin Andresen was labeled a "toxic influence" and "confused" and then purged from the team by revoking his GitHub access under the pretense ...
Forwarded from CSW 360-4 51% Attack (@RamonQuesada)
A "51% attack" means a bad guy getting as much computing power as the entire rest of the Bitcoin network combined, plus a little bit more. The Bitcoin wiki has a good summary of what a 51% attacker can and cannot do.
One of the things a 51% attacker can do is prevent any transactions or new blocks from anybody besides themselves from being accepted, effectively stopping all payments and shutting down the network.
That would be bad.
But it would also be obvious it was happening, and pretty easy to defend against. As I said on the Bitcoin Forums:
Something like "ignore a longer chain orphaning the current best chain if the sum(priorities of transactions included in new chain) is much less than sum(priorities of transactions in the part of the current best chain that would be orphaned)" would mean a 51% attacker would have to have both lots of hashing power AND lots of old, high-priority bitcoins to keep up a transaction-denial-of-service attack. And they'd pretty quickly run out of old, high-priority bitcoins and would be forced to either include other people's transactions or have their chain rejected.
The code already has a notion of "bitcoin priority" that it uses to prevent transaction spam (sending gazillions of tiny transactions to yourself, just to make everybody else do the work of validating and storing them); extending that to influence the chain-fork-selection code wouldn't be hard.
The devil is in the details, of course, and the risk of introducing a new chain-acceptance rule (high) have to be weighed against the chances that somebody rich and irrational will try to pull off the attack (low, in my opinion, but maybe I'm not sufficiently paranoid about Big Banks or Big Government using Dirty Tricks to shut down Bitcoin). Maybe I'll code it up and keep it as a "Not To Be Used Except In Case of Emergency" branch.
Posted 1st May 2012 by Gavin Andresen https://gavintech.blogspot.com/2012/05/neutralizing-51-attack.html
One of the things a 51% attacker can do is prevent any transactions or new blocks from anybody besides themselves from being accepted, effectively stopping all payments and shutting down the network.
That would be bad.
But it would also be obvious it was happening, and pretty easy to defend against. As I said on the Bitcoin Forums:
Something like "ignore a longer chain orphaning the current best chain if the sum(priorities of transactions included in new chain) is much less than sum(priorities of transactions in the part of the current best chain that would be orphaned)" would mean a 51% attacker would have to have both lots of hashing power AND lots of old, high-priority bitcoins to keep up a transaction-denial-of-service attack. And they'd pretty quickly run out of old, high-priority bitcoins and would be forced to either include other people's transactions or have their chain rejected.
The code already has a notion of "bitcoin priority" that it uses to prevent transaction spam (sending gazillions of tiny transactions to yourself, just to make everybody else do the work of validating and storing them); extending that to influence the chain-fork-selection code wouldn't be hard.
The devil is in the details, of course, and the risk of introducing a new chain-acceptance rule (high) have to be weighed against the chances that somebody rich and irrational will try to pull off the attack (low, in my opinion, but maybe I'm not sufficiently paranoid about Big Banks or Big Government using Dirty Tricks to shut down Bitcoin). Maybe I'll code it up and keep it as a "Not To Be Used Except In Case of Emergency" branch.
Posted 1st May 2012 by Gavin Andresen https://gavintech.blogspot.com/2012/05/neutralizing-51-attack.html
Blogspot
Neutralizing a 51% attack
A "51% attack" means a bad guy getting as much computing power as the entire rest of the Bitcoin network combined, plus a little bit more. T...
Forwarded from Gavin Andresen News (@RamonQuesada)
Bitcoin XT
Initial release August 15, 2015
Stable release
Release I / 22 April 2018;
Repository https://github.com/bitcoinxt/bitcoinxt
On June 10, 2014 Mike Hearn published a Bitcoin Improvement Proposal (BIP 64), calling for the addition of "a small P2P protocol extension that performs UTXO lookups given a set of outpoints."[5] On December 27, 2014 Hearn released version 0.10 of the client, with the BIP 64 changes.[6]
On June 22, 2015, Gavin Andresen published BIP 101 calling for an increase in the maximum block size. The changes would activate a fork allowing eight MB blocks (doubling in size every two years) once 75% of a stretch of 1,000 mined blocks is achieved after the beginning of 2016.[7] The new maximum transaction rate under XT would have been 24 transactions per second.[8]
On August 6, 2015 Andresen's BIP101 proposal was merged into the XT codebase.[9][10] Bip 101 was reverted[11] and the 2-MB block size bump of Bitcoin Classic was applied instead.
https://en.wikipedia.org/wiki/Bitcoin_XT
Initial release August 15, 2015
Stable release
Release I / 22 April 2018;
Repository https://github.com/bitcoinxt/bitcoinxt
On June 10, 2014 Mike Hearn published a Bitcoin Improvement Proposal (BIP 64), calling for the addition of "a small P2P protocol extension that performs UTXO lookups given a set of outpoints."[5] On December 27, 2014 Hearn released version 0.10 of the client, with the BIP 64 changes.[6]
On June 22, 2015, Gavin Andresen published BIP 101 calling for an increase in the maximum block size. The changes would activate a fork allowing eight MB blocks (doubling in size every two years) once 75% of a stretch of 1,000 mined blocks is achieved after the beginning of 2016.[7] The new maximum transaction rate under XT would have been 24 transactions per second.[8]
On August 6, 2015 Andresen's BIP101 proposal was merged into the XT codebase.[9][10] Bip 101 was reverted[11] and the 2-MB block size bump of Bitcoin Classic was applied instead.
https://en.wikipedia.org/wiki/Bitcoin_XT
Forwarded from Gavin Andresen News (@RamonQuesada)
Twitter
Dr Craig S Wright
@gavinandresen The one thing I am sorry about is that you ended left in the lurch and allowed you to be treated as you were. I have left you in the state others saw in 2015 twice now, and I am sorry. You are a far nicer man than I will ever be.
Forwarded from Gavin Andresen News (@RamonQuesada)
Twitter
Gavin Andresen
I have been tempted to write something like this: https://t.co/tOFGwP3NEy ... but have always thought it would just feed the haters.
Forwarded from Gavin Andresen News (@RamonQuesada)
Satoshi’s Final Email to Gavin Andresen
April 26, 2011
https://nakamotostudies.org/emails/satoshis-final-email-to-gavin-andresen/
April 26, 2011
https://nakamotostudies.org/emails/satoshis-final-email-to-gavin-andresen/
Forwarded from Gavin Andresen News (@RamonQuesada)
DUP HASH160 ... EQUALVERIFY CHECKSIG
June 17, 2010, 11:38:31 AM
So I'm writing a little tool that dissects the Bitcoin wallet.dat, mainly because I want to understand better exactly how Bitcoin works.
And I see that the outputs of transactions have a value (number of bitcoins) and a bunch of bytes that are run through the little Forth-like scripting language built in to bitcoin. E.g.:
['TxOut: value: 100.00 Script: DUP HASH160 6fad...ab90 EQUALVERIFY CHECKSIG']
First: it make me a little nervous that bitcoin has a scripting language in it, even though it is a really simple scripting language (no loops, no pointers, nothing but math and crypto). It makes me nervous because it is more complicated, and complication is the enemy of security. It also makes it harder to create a second, compatible implementation. But I think I can get over that.
Looking at the code, new transactions are verified by pushing the signature an then public key on the interpreter's stack and then running the TxOut script (did I get that right?).
Could I write code to create transactions with any valid script in the TxOut?
E.g. could I create a TxOut with a script of: OP_2DROP OP_TRUE
... to create a coin that could be spent by anybody?
And is flexibility in the types of coins created the reason it is coded this way?
How often do you get the chance to work on a potentially world-changing project?
Be very wary of relying on JavaScript for security on sites such as blockchain.info and brainwallet.org. The site can change the JavaScript at any time unless you take unusual precautions, and browsers are not generally known for their airtight security.
Gavin
https://bitcointalk.org/index.php?topic=195.msg1611#msg1611
June 17, 2010, 11:38:31 AM
So I'm writing a little tool that dissects the Bitcoin wallet.dat, mainly because I want to understand better exactly how Bitcoin works.
And I see that the outputs of transactions have a value (number of bitcoins) and a bunch of bytes that are run through the little Forth-like scripting language built in to bitcoin. E.g.:
['TxOut: value: 100.00 Script: DUP HASH160 6fad...ab90 EQUALVERIFY CHECKSIG']
First: it make me a little nervous that bitcoin has a scripting language in it, even though it is a really simple scripting language (no loops, no pointers, nothing but math and crypto). It makes me nervous because it is more complicated, and complication is the enemy of security. It also makes it harder to create a second, compatible implementation. But I think I can get over that.
Looking at the code, new transactions are verified by pushing the signature an then public key on the interpreter's stack and then running the TxOut script (did I get that right?).
Could I write code to create transactions with any valid script in the TxOut?
E.g. could I create a TxOut with a script of: OP_2DROP OP_TRUE
... to create a coin that could be spent by anybody?
And is flexibility in the types of coins created the reason it is coded this way?
How often do you get the chance to work on a potentially world-changing project?
Be very wary of relying on JavaScript for security on sites such as blockchain.info and brainwallet.org. The site can change the JavaScript at any time unless you take unusual precautions, and browsers are not generally known for their airtight security.
Gavin
https://bitcointalk.org/index.php?topic=195.msg1611#msg1611
Forwarded from Gavin Andresen News (@RamonQuesada)
Satoshi
"I believe Craig Steven Wright is the person who invented Bitcoin"
MAY 2, 2016
http://gavinandresen.ninja/satoshi
"I believe Craig Steven Wright is the person who invented Bitcoin"
MAY 2, 2016
http://gavinandresen.ninja/satoshi
Forwarded from 430 Wladimir J. van der Laan laanwj (@RamonQuesada)
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/
https://www.weusecoins.com/wladimir-van-der-laan/
Weusecoins
Wladimir van der Laan
Wladimir van der Laan is a Bitcoin Core Developer and the Lead Maintainer of the Bitcoin repository on GitHub.
Forwarded from Gavin Andresen News (@RamonQuesada)
"No estaba seguro, y todavía no estoy seguro de cómo está involucrado Gavin en esto. Ya no es probable que haya sido hackeado, pero al menos está confundido. Cuando vimos la publicación del blog convencido de que encontró a Satoshi, lo más prudente era revocar su propiedad de la organización "bitcoin" en github, bajo la cual se encuentra el repositorio de Bitcoin Core de inmediato".
2016/05/06/
Wladimir J. van der Laan
laanwj
https://laanwj.github.io/2016/05/06/hostility-scams-and-moving-forward.html
2016/05/06/
Wladimir J. van der Laan
laanwj
https://laanwj.github.io/2016/05/06/hostility-scams-and-moving-forward.html
laanwj.github.io
Dazed and confused, but trying to continue
I’m happy with the job I’m doing, happy to work with a few very smart people on
an extremely interesting project, involving various entirely new challenges,
that could have enormous impact. But on the other hand Bitcoin infrastucture
development must be one…
an extremely interesting project, involving various entirely new challenges,
that could have enormous impact. But on the other hand Bitcoin infrastucture
development must be one…
Forwarded from Gavin Andresen News (@RamonQuesada)
Ver "An evening with Gavin Andresen (Bitcoin Foundation) - San Francisco Bitcoin Meetup (HD) (Dec 2014)" en YouTube
https://youtu.be/07B-p9hSJT8
https://youtu.be/07B-p9hSJT8
YouTube
An evening with Gavin Andresen (Bitcoin Foundation) - San Francisco Bitcoin Meetup (HD) (Dec 2014)
Join the SF Bitcoin Meetup http://www.meetup.com/San-Francisco-Bitcoin-Social/ Gavin Andresen Chief Scientist, Bitcoin Foundation. All-around geek. https://t...
Forwarded from Gavin Andresen News (@RamonQuesada)
Ver "The Bitcoin Show: Special Bitcoin Conference Coverage: Gavin Andresen - 08/20/2011" en YouTube
https://youtu.be/0ljx4bbJrYE
https://youtu.be/0ljx4bbJrYE
YouTube
The Bitcoin Show: Special Bitcoin Conference Coverage: Gavin Andresen - 08/20/2011
Coverage from the World's First Bitcoin Conference & World Expo! Gavin Andresen the lead technical developer of the Bitcoin project discusses Bitcoin history...
Forwarded from Gavin Andresen News (@RamonQuesada)
Ver "Making Money- Gavin Andresen @ Ignite Amherst" en YouTube
https://youtu.be/koIq58UoNfE
https://youtu.be/koIq58UoNfE
YouTube
Making Money- Gavin Andresen @ Ignite Amherst
Gavin Andresen is Principal of the BitCoin Virtual Currency project , he Ignited on "Making Money." Recorded by Amherst Media on February 8th 2011 at The Eric Carle Museum in Amherst, MAAmherst Media - Facebook - TwitterIgnite Amherst - Facebook - Twitter…
Forwarded from Gavin Andresen News (@RamonQuesada)
Ver "BITCÓIN: La Moneda Del Futuro (V.O.S.)" en YouTube
https://youtu.be/B9nCgyquSqA
https://youtu.be/B9nCgyquSqA
YouTube
BITCÓIN: La Moneda Del Futuro (V.O.S.)
Daniel es un programador informático de 35 años. Vive en Pittsburgh y tiene una vida ajetreada. Aparte de compaginar su trabajo, su matrimonio y el cuidado d...
Forwarded from Gavin Andresen News (@RamonQuesada)
Es probable que lleves poco tiempo en la comunidad cripto y no conozcas bien a Gavin Andresen, a quien Satoshi dejo a cargo del desarrollo del software, cuando se retiró allá por el 2011, creo, te podrán contar muchas cosas de él pero ésta imagen en su propia casa en el minuto 22 de la película The Rise and Rise of bitcoin, es algo que no le he visto hacer a ningún miembro relevante de la comunidad, la naturalidad y transparencia con la que enseña el lugar donde vive es algo que para mi lo convierte en ÚNICO , su franqueza y esfuerzo por explicar ésta tecnología lo hacen un símbolo de lo que le escuché decir muchas veces en esa época y que rara vez escucho ahora: "Bitcoin ha venido, para hacer un mundo mejor"
Recuerda minuto 22
Recuerda minuto 22
Forwarded from CDC Canal
The.Rise.and.Rise.of.Bitcoin.2014.mp4
620.1 MB
Forwarded from Gavin Andresen News (@RamonQuesada)
Twitter
Olivier Janssens
In 2016, I created a 2MB increase for Bitcoin, and with Gavin on board, we quickly gained consenses with 80-90% of miners, businesses and users. https://t.co/wQRBnHKxXK and https://t.co/j6b845424r - Days later, Blockstream flew to Hong Kong and stopped it.…