Joined December 2021
- Tweets923
- Following748
- Followers131
- Likes8.1K
btcViking retweeted
Anakin becomes so invested in advancing the political agenda of a weird old grandpa that he loses his wife and becomes estranged from his children. So yes, very good allegory for young right-wing men
The prequels, at the end of the day, are about a young man trying to claim what is rightfully his. And he’s treated with suspicion, contempt, or even outright hatred because of it.
He wants skill, power, influence, order, hierarchy etc. and isn’t afraid to tell people that. He kills the guilt that he used to feel for wanting what he should have.
It’s remarkable how relatable all of this actually is for many young men. Made to feel guilt for who or what they are. Denied what is rightfully theirs by birth. Villainized by a weak, corrupted, aging Republic that has long outlived its usefulness.
Fortunately, everyone seems to be on the same page on this. We’re going to reclaim what is ours.
btcViking retweeted
Let’s clear up a misunderstanding.
“BTC is pristine collateral”
It is for them, NOT for you.
When you borrow, front the stinkiest dogshit collateral they will take.
For example your home loan... The bank doesn’t even know how much it’s worth. Takes months to sell. They pray you don’t default, it’s a risk for them.
BTC as collateral. They know what it’s worth EVERY SECOND OF THE DAY OR NIGHT. Insta-liquidation is easy. They are incentivised to liquidate, charge penalties and roll the money to the next borrower.
So remember… when you borrow let them take your dogshit.
btcViking retweeted
Today is the 10 year anniversary of the production release of @opentimestamps
I created OpenTimestamps in a few weekends because I was frustrated that no-one else had created such an obvious and necessary tool. Since then it has become the global standard for secure timestamps: if you ask an LLM how to create a timestamp, it'll almost certainly suggest using OpenTimestamps.
OpenTimestamps has grown to the point where everything from art, to forum posts, to software releases, to war crimes evidence is getting timestamped with OpenTimestamps. Along with some applications I won't be able to talk about for at least a few years... fortunately that data is timestamped!
While I have no way of knowing for sure how many documents in total are getting timestamped per second – merkle trees – I can say that as of the past two weeks (beyond that I automatically delete logs) the public calendars I run have averaged about 5 timestamp requests per second from about 60,000 distinct IP addresses. I have no idea what all these people are using OpenTimestamps for. But clearly it's getting fairly popular!
Thanks goes out to @realSimpleProof, $TIME, and all the people who have donated directly to the public calendars for their support. OpenTimestamps costs a few hundred a month to run now, along with my time. Without your help keeping OpenTimestamps running would be a lot more painful. If you want to donate, you can do so right here:
alice.btc.calendar.opentimes…
Thanks also goes to @RCasatta and @BULLBITCOIN_ for running two of the four public calendars. They're one of the reasons why OpenTimestamps doesn't have a single point of failure. Finally, thanks goes to the many people who have contributed code to OpenTimestamps over the years, including entire libraries in languages like java and JavaScript that I have no experience with. In fact, the majority of OpenTimestamps clients are quite possibly using code I didn't write at all!
petertodd.org/2016/opentimes…
btcViking retweeted
Should we refer to the particular strain that ravaged so many 110ers as the Dunning-Fred-Krueger effect, in honor of this guy?:
btcViking retweeted
This is some wild hairsplitting and misdirection.
You absolutely did fall back to weak entropy, and the yasmarang implementation you put in libngu was even weaker than the one in MicroPython (because yours used hardcoded constants): github.com/switck/libngu/blo…
You were warned about this particular issue by me and at least one other person 4 years before me.
Oh wow as a no one with only a fewish tweets I really wonder what I did to have gia block me. NVK I know, but this one was surprising and funny.
2
28
btcViking retweeted
I am making myself available for one on ones to help handhold coldcard users through migrating funds to whatever is available to them. I will first make an explainer video, then start reaching out to those who reply here asking for help. It will be impossible to get on personal calls with everyone, but I will get to as many as I can.
Nathan @theBTCmentor has also been doing this tirelessly. We will call on the rest of our Mentor team to carve out time where they can as well. If you personally believe you'll need a hand after the explainer video let me know. I'll be checking back in as soon as I'm finished and uploaded. It may take a bit of time.
Until then, here are some options:
-move funds to any other hardware you have that isn't a Coldcard
-move funds to a hot wallet temporarily
-use updated coldcard firmware to generate a new key (probably my least favorite option at the moment), but Nathan did make an explainer video on this because it's a few extra steps
Back with more soon.
btcViking retweeted
Adding to this: Anyone closer to UK/EU time that needs help, feel free to book a call using bitcoinerconsulting.com/book
In the "anything to help prepare" box say it's because of the Coldcard bug, and my help is completely pro bono.
btcViking retweeted
NVK is currently deleting old posts from 2020 to try to clean up the history. Screenshot them while you can. They will all be gone soon.
btcViking retweeted
Regarding the Coldcard entropy bug – many folks are explaining what happened but I wanted to take a minute to explain why it may have happened.
It's a disastrous situation and our heart goes out to all the Bitcoiners affected.
Here's a timeline of events:
On July 28 2020: @FoundationHQ announced our first Passport hardware wallet and noted that we were building on Coldcard firmware which at the time was GPLv3 licensed (FOSS license).
On July 30 2020: NVK publicly said he regretted choosing GPL because Coldcard now had a “clone” and that they would change things in future updates. teapawt.net/nvk/status/12888603458…
On November 18 2020: Coldcard added its MIT + Commons Clause license, prohibiting commercial products substantially derived from the software. github.com/Coldcard/firmware…
On January 8, 2021: Coldcard firmware 3.2.1 formally announced, “License changed from GPL to MIT+CC on files for which the GPL doesn’t apply.” CC is the "Commons Clause" license addendum which is "source available" instead of FOSS.
On March 1, 2021: The “First pass w/ libNgU” commit removed the GPL @Trezor-derived crypto libraries and replaced them with libNgU. That same 120-file commit changed seed generation code. libNgU was licensed with a novel “Licensed for Bitcoin Only” license.
On March 17, 2021: Version 4.0.0 announced that all crypto and BIP39 code had been replaced and that the “last remaining GPL code” was removed. blog.coinkite.com/version-4.…
github.com/Coldcard/firmware…
Our best understanding right now is that the entropy bug was collateral damage from this major overhaul of the codebase.
To be clear, this overhaul was not solely about licensing. Coldcard also cited technical goals including adopting Bitcoin Core’s libsecp256k1, faster AES and SHA implementations, and reproducible builds.
But the timeline establishes two things:
(1) Foundation’s launch was the obvious impetus for Coldcard’s licensing change, and
(2) removing the remaining GPL code was an explicit goal of the subsequent v4 rewrite.
We don't know by how much the licensing pressure affected the scope or timeline of the rewrite. All we can determine is that the entropy bug was introduced inside the same 120-file commit that removed the old GPL code dependencies.
This quoted post is unavailable.
Quote tweeting this bc NVK has me blocked just like anyone else who says anything slightly negative about them or slightly positive about @SeedSigner. Luckily when I used my mk3 I used an old generated seed from ledger.
Myself and Nathan @theBTCmentor will be going live regarding this shortly. Some practical demos to help as we go along as well. Stay tuned for links.
1
173
btcViking retweeted
Prolly the most goated bitcoin essay ever.
Extremely advanced level of understanding even in 2011 when it was published.
If you haven’t read it you need to.
Thank you @gwern.
gwern.net/bitcoin-is-worse-i…
btcViking retweeted
I’m coming out in support of BIP-110. Here’s why I changed my mind:
1) Bitcoin is money. We cannot let it be polluted with spam. Adopting BIP-110 is like wearing your mask during COVID. It might not stop the spread but it is super important to try even if the method isn’t very effective.
2) Bitcoin is too important to trust with one organization, Bitcoin Core. Instead, we should trust one well-meaning individual, Luke. This is preferable because Luke is infallible, and I trust infallible individuals more than fallible organizations.
3) Knots has something like 50k more lines of code than Core. More code means better code. Better code means better Bitcoin. Better Bitcoin means better money. I haven’t reviewed the code but it was written by Luke, so I know I would like every line.
4) Bitcoin Core won’t listen to my criticisms of their code. I haven’t spent much time reviewing the code and my knowledge is limited, but I think that they should listen to everything I say because I really care about bitcoin. Luke also won’t listen to me but he’s infallible so it’s fine.
5) I want everyone to think that I care about Bitcoin more than they do.
6) Dark money. IFYKYK.
7) @adam3us isn’t even Satoshi
We've got geniuses over here
I spent months helping @JohnCarreyrou crack the identity of Satoshi. We went far beyond surface-level evidence, collecting hundreds of thousands of internet mailing list posts from 1992-2008.
Here are three analyses we performed to find someone who didn’t want to be found:
49
