/ˈstiːɛl/ ⚡

@TwitterSupport Why?

This is the social media equivalent of stopping withdrawals during a bank run.

Massive self-own, reeks of weakness. twitter.com/TwitterSupport…

Seems like a good time to remind people that the Federated place is hopping, and it’s time to leave here. My new username is in my profile.

👌

the fuck

RIP Twitter I am literally laughing out loud right now

@lopp #justcypherpunkthings twitter.com/sti__l/status/…

Running nostr

Looking at ways to add more anonymity to nostr

Running nostr

@peterktodd @GrassFedBitcoin @francispouliot_ @LayahHeilpern Granted, I don't fully understand the mathematics behind BCH, cryptographic hashing is a more well-known and perhaps conceptually easier primitive, but implementation-wise, Bech32+Bech32m verification is not that complex with some 20 lines of Python code.

@sti__l @GrassFedBitcoin @francispouliot_ @LayahHeilpern In other words, for all practical purposes the old scheme was every bit as good as the segwit one. 1/4billion ≈ 0 The new scheme can identify where errors are. But IMO, that wasn't enough of an advantage to make it worth the complexity.

I've been sending crypto around the world for years now and I still get a mini heart attack that it's gonna be lost forever in case I did one digit wrong... Anyone else?🤣

@GrassFedBitcoin @peterktodd @francispouliot_ @LayahHeilpern Old addresses have a checksum that detects any errors with a failure chance of 1 in 4 billion addresses. Segwit addresses have _guaranteed_ detection of any error affecting at most 4 characters, with a failure chance of at most 1 in 1 billion addresses for larger errors.

@peterktodd @francispouliot_ @LayahHeilpern it just gets harder to create a valid checksum if making a typo with native segwit addresses right? 1 in 4 billion was it?

@kodylow @francispouliot_ @LayahHeilpern Example: tb1qxxlzwzf6h6887hf5hnkq4sdcfs52s8s7jl5evp tb1qxxlzwzf6h6887hf5hnkq4sdcfs52s8s7jl5evqqqqqqqqqqqqqqqqqqqqp A bit of a "stretch", as noted by @Truthcoin

@kodylow @francispouliot_ @LayahHeilpern Segwit v0 addresses are restricted to either 42 or 62 characters, so adding just one or a few "q"s would still invalidate the address. You would have to add a string of 20 "q"s to a 42-character address, which would be rather visually obvious.

When you get an email from the police and it look likes this. You know who owns them and who they work for, a bunch of shitty lobby organization.

@fokawolf @thegrugq Ronal Mcdonal

This Toilet is Currently Out of Order. 2019

@AchimWar @Truthcoin I must have offended the Algorithm

@Truthcoin @sti__l Right about the flagging - I was unable to see previously (which is how I ended up posting the same thing)

Intriguingly, this site will allow you to use the integer 2^256 as an ECDSA private key, despite it being larger than FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFE BAAE DCE6 AF48 A03B BFD2 5E8C D036 4140 #Range_of_valid_ECDSA_private_keys" target="_blank" rel="nofollow noopener">en.bitcoin.it/wiki/Private_k… I wonder what it is doing? @adam3us

@Truthcoin I.e., inputting private key 000000000000000000000000000000014551231950B75FC4402DA1732FC9BEBE will result in the same public key (039166c289b9f905e55f9e3df9f69d7f356b4a22095f894f4715714aa4b56606af)

@Truthcoin 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF mod 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141 = 0x000000000000000000000000000000014551231950B75FC4402DA1732FC9BEBE

@lopp Still a risk of a greedy dishonest hop that has already witnessed the preimage.

* Invoice expires in 1 hour. * No need to worry about being the "second to pay" since the invoice will only be accepted once.

Let's do an experiment. The first person who sends 200k sats ($80) to this lightning invoice will receive a pair of tickets to tonight's Dodgers game @ Twins. Section 5, row 7 behind dugout. You'll have to prove payment by providing the payment hash & preimage.