I’m excited to share today that I’m joining the @Lightspark team to work on building out Bitcoin and LN to be even more powerful forms of money and payments. #Lightspark#Bitcoin#LightningNetwork
I wore a bitcoin core t-shirt today at #Bitcoin2022 (along w/ @achow101). Quite a few people asked, "What's bitcoin core?"
It's... bitcoin. I guess people added "core" because it was confusing.
"So you work for Bitcoin Core?"
You cannot still, never have been able to, and never will be able to, "withdraw BTC on other networks".
Securing Bitcoin also involves calling out hostile redefinition of Bitcoin.
Binance has temporarily paused #Bitcoin withdrawals on the $BTC network. Meanwhile, you can still withdraw BTC on other networks.
This is due to a stuck on-chain transaction. Our team is currently working on a solution and will provide further updates soon.
A few months ago, I read about @Lightspark, a new company whose goal is to “explore, build and extend the capabilities and utility of Bitcoin.”
“Huh.” I thought, “That’s also been my goal for the last decade or so.”
Really frustrating to see laser-eyesers applauding an attack on mainnet LND.
Sure, fixing bugs makes bitcoin stronger. Sure, it's the currency of enemies.
But bitcoin and LN are not magically invincible / inevitable. Attacks don't help.
I've posted Utreexo, a new paper about bitcoin scalability, to IACR ePrint. ia.cr/2019/611
Thanks to those who helped with this work and looking forward to criticisms and getting and implementation running.
Just released v0.1 of utreexo software & wrote about it here: medium.com/mit-media-lab-dig…
take a look, test it out, and write some crash reports :)
It's been great working with the other utreexo developers so far & looking forward to more people working on it!
None of these people were dumb. They'd just never heard of it. Some of the people I explained it to wanted to download it. Some wanted to start help coding it.
Hopefully this helps.
Huge conference, so many people... but really it's all just a program you run on your computer.
This isn't just about threatening bitcoin; this is threatening all open source software, one of the most amazing and useful (and free!) ideas of the last few decades.
laanwj.github.io/2023/02/06/…
So sounds like the libbitcoin guy thinks that
head -c 32 /dev/urandom | sha256sum
and
date +%s%N | sha256sum
are the same thing. And changing the former to the latter in wallet key generation code is cool.
Stay far, far away.
This is not true. Reliance on the OS RNG is generally secure. All private keys in bitcoind / bitcoin-qt (and basically every other wallet) have always used the OS RNG.
Giving a talk at #crypto2018 in ~an hour. New stuff, will be fun!
Before going, I've had to tell a couple people they've been doing this conference since 1981. #CryptoMeansCryptography
People at MIT who are interested in this stuff! I'm teaching a class with @neha: github.com/mit-dci/mas.s62
Mondays & Wednesdays at 10AM.
People interested but not around here:
There will be videos (though probably not live); problem sets also public.
They've been distracting you with meaningless op_return and sats drama.
Meanwhile, the elite core devs have pushed through a consensus hard fork, already fully ACK'd and merged into master.
Wake up, sheeple!
github.com/bitcoin/bitcoin/p…
Problem here: sha-256 is a cryptographic hash function, preventing professor Green from understanding the answer.
I suggest use of a collision-friendly non cryptographic hash function, if a suitable one can be found.
I'm thinking more and more that it's got to be intentional. It is absolutely trivial to build a seed generator into a wallet:
cat /dev/urandom | tr -dc 'A-Z9' | fold -w 81 | head -n 1
done.
It's past Hanlon's razor for me; I assume malice.
"needs to be" sounds like it needs new code, but it doesn't.
Just set minrelaytxfee=0.00000100 in bitconf.conf to reduce your node's minimum relay fee to 0.1sat/vb.
With Lightning 1.1 we will be taking a big step away from 1.0. Interestingly there’s a parallel to Bitcoin history where the protocol has outlived its creator and now has a life of its own. As we fix key original design errors, no one is making specious claims to original vision.
hubris.media.mit.edu/bitcoin…
This machine serves 2 or 3 TB of bitcoin blocks a month, so serving another ubiquitous piece of data should be no problem
It's been awesome working with everyone at the @mitDCI for these years, and I look forward to collaborating with the great students and researchers there in the future!
dci.mit.edu/research/2022/8/…
First* block where fees exceed new coins?
mempool.space/block/00000000…
(not quite how I thought this would happen)
* where the fee wasn't a wallet error on a single tx
Coworkers argued for the existence of people unaware that tether is a scam. Seems obvious enough but I'll say again: tether is a scam. "USDT" will be worthless much sooner than USDs or BTCs will.
Sympathies and long-overdue congratulations to all the great folks who have been attacked by faketoshi.
We're finally in the "grind extremely fine" phase.
I read it at 1 am, often gesticulating in frustration at the monitor. I wasn't aware of bitcoin in 2009, but I have to imagine it was pretty different as *it wasn't worth money*.
There's probably an interesting paper to be had digging through early bitcointalk. This isn't it.
unpublished paper uses extranonces to attribute early miners. finds that certain agents had lots of hashpower in 2009/10, especially early GPU miners. some miners could have attacked network but didnt.
NYT: "BTC isn't anonymous! decentralization theater!"
archive.ph/fqMp3
G: [shows Wright witness statement] You say you've done all you can to build in versioning etc. You say BTC has limited size of script, gives little ability to add data. It refers to a GitHub page. [shows page] Declaring constant int MAX_SCRIPT_ELEMENT_SIZE. Do you know what unsigned means?
W: Basically an unsigned variable, it's not an integer with … it's larger, I'm not sure how to say it.
G: Try.
W: How I'd describe it, I'm not quite sure. I'm not good with trying to do things like this.
Found via user dethos on HN - the whole paper is just a copy / paste of web.getmonero.org/library/Ze… which explains monero for beginners (though not sure how successfully) and describing XOR makes some sense in the original context.
Taproot is annoyingly clever. "Oh I totally could have thought of that!" ... yeah but I didn't, and nobody else did either. (Well Greg just did.)
And so similar to the pay-to-contract-hash stuff which also seems easy once someone else figures it out :)
"We've been longing for approval from heads of states and billionaires for so long, but today we finally know it was all worth it!" said one cyber-coin enthusiast when asked about recent events.
Attacks, fighting, trolling, misinformation - I'll deal with it.
It's super cringey stuff like this that makes me want to find another line of work.
(Don't worry, they'll need a lot more of this to stop me :)
nytimes.com/2018/01/13/style…
[1/3] 100x Group is delighted to announce that it has awarded a US$40,000 one-year grant to Utreexo researcher & developer Calvin Kim. Calvin was instrumental in the development of the first demonstration release of Utreexo
blog.bitmex.com/bitcoin-deve…
Overlooked environmental / existential benefit of PoW:
Each TSMC wafer etched with SHA256d ASICs is one fewer floating point AI wafer for the paperclip hypnodrone singleton.
The real-world/Bitcoin boundary layer continues to confound:
At 2024's largest Bitcoin conference, they wouldn't let me bring a laptop.
...and "they" were the United States Secret Service.
Blockchain-y conference panel in Taiwan moderated by some guy who's doing an ICO to build bcash ICOs.
Politely decline, or go? Give ICOers the stage to themselves, or possibly give them more attention by participating?
Asking for a friend.
The whole idea doesn't make sense anyway. If you can get everyone to agree on which txs are propagated without mining then mining doesn't add anything and just wastes electricity.
UTXO data lives in both ~/.bitcoin/chainstate and ~/.bitcoin/blocks; witness data lives only in ~/.bitcoin/blocks.
Chainstate is a DB and lots of I/O; blocks are flat files with little to no I/O.
Witness data is cheaper to deal with so makes sense for it to be cheaper to create.
BREAKING:
Bitcoin developers demolish #Faketoshi in Pineapple Hack lawsuit: Wright is defeated in jurisdiction challenge.
"it is not realistically arguable that the pleaded facts amount to a fiduciary relationship"
I'll go find more quotes, hold on.
Have been in Korea the last few days; nice place.
Have not encountered a single wifi captive portal.
Hard to recognize the annoying things you've become desensitized to until they're gone :)
I guess I'm not in the overwhelming consensus. I much prefer op_ctv to op_cat. To me op_ctv being limited is a feature, and op_cat's ability to do ~maybe ~anything in a super complex way is not.
This is not true. Reliance on the OS RNG is generally secure. All private keys in bitcoind / bitcoin-qt (and basically every other wallet) have always used the OS RNG.
Utreexo works, people can run it today. The part that hasn't happened is getting it merged into bitcoin core: tricky as it touches a whole lot of code.
Maybe it's better for it to be it's own node software. Or maybe we want it in core, who knows.
It does look cool in general, but nip04 is broken in several ways. (non-uniform AES key, CBC with no MAC instead of GCM)
Guess I should make an issue...
Used mini desktops with 6500T CPUs are like $50 on ebay and work great.
Agreed - Raspberry Pis are great for GPIO stuff but not for normal computer stuff.
These systems aren't anti-fragile on their own: it's people in front of their computer fixing bugs.
And you get better bug fixes when those people have time to review vs writing an emergency fix while everyone is screaming at them.
Fun fact about these outputs: They're unspendable even without the OP_RETURN opcode because they're more than 10KB.
So the OP_RETURN opcode here *really* wastes space!
I put minrelaytxfee=0.00000001 in bitcoin.conf
If a decent portion of nodes do this, sub 1sat/vB txs will propagate.
But hopefully it won't matter since there will be higher fees.
Great post, agree with like ~90% of this. The current process does seem to either ossify or cede development to well-funded organizations. I really don't want the Jia Tans of the world to be the ones with the persistence to change Bitcoin
1/3
Also, while the saying "If you're not embarrassed by the first version, you've posted too late" may be true, a paper can be both posted much too late, and still cause for some embarrassment! :P
Also LN is pretty cool! (obviously biased :) )
But yeah LN helps scale payments, not ownership.
If the #1 use case of Bitcoin is keep a BIP39 phrase with some coins on it for years at a time, the opcodes we're looking at don't really help.
3/3
HTLCs don't work for micropayments (below tx fee level), though single satoshi payments can be securely made within a channel. Pretending 1-satoshi HTLCs are a thing is setting people up to be disappointed...