Last Notes
Yea, sustainability is definitely a big question, I assume at some point they’ll have to add ads (or a premium option) like everyone else. If they manage to redundant’ize the hosting before then (assuming that’s something they want), though, they may end up just eating all of nostr’s features….
Don’t forget that Ripple was the largest donor to the largest non-party/candidate superpac in the last election cycle. If you thought they weren’t going to get a seat at the table (and ice out Bitcoiners), you weren’t paying attention.
Is there any more info available here? I’m somewhat surprised to hear (and Google doesn’t seem to have any results for) a TLD seizing a domain outright. I could see a shitty registrar (GoDaddy or whatever) doing so, however.
Ugh this is also wrong. QCs are a threat *both* to coins and to mining.
I believe they might in the EU, but at least in the US, no. (Don’t think they support lightning in NY, though)
This is very much a misread of the spec. #note1ehv…yfwp
It still makes you select which wallet you’re using as step one (lol what?), but doesn’t push any Bitcoin Cash nonsense anymore. It just shows you a lightning invoice and that’s it (if you select a Lightning wallet).
Not as a full-timer, but I’ve helped several hardware wallets in the design stage and have built Bitcoin wallets (and basically every other kind of Bitcoin protocol) over the past ~14 years.
No no, for offers. Imagine Nostr app wants to zap using BOLT 12. It does a system open for bitcoin:?lno=lnoffer&pop=proofcallback, but it ultimately needs the proof to include “Bob zapped with emoji🫠”. So either the proofcallback has to include the private key or that original URI has to include the string to sign.
I am once again imploring people to stop quoting “facing XX years” claims unless someone actually filled out the federal sentencing guidelines form and have a realistic quote.
Those numbers are always completely made up, usually by more than 10x!
Holy shit. I mean it was bound to happen eventually but god bless those poor 60 souls at DCA tonight.
Big day for long form writing for me today. Phew.
Shouldn’t really be a huge deal? The node will just connect outbound from a new IP instead.
I’ve always just selected Phoenix, cause then it’ll give me a lightning invoice, but its behavior is very GeoIP-dependent. If you’re outside the US/in NY you might struggle (try a VPN).
Except you aren’t…it’s very (cryptographically) easy to build a hardware wallet which cannot steal your coins*! But no one does, that’s absurd!
* without cooperating with your computer/phone.
TIL nginx, by default, caches gzip’d responses and ignores the accept-encoding in the request when serving from cache. What a strange default 🤦♂️
You can definitely include a GSM chip for cheap, but now the device board actually looks visually different, which people can identify, even if admittedly relatively few would. Still, if you did this en-masse it’d likely be discovered before too long, whereas a malicious firmware likely would not.
It works cause I’m always mad!
Indeed, OCEAN’s approach leaves a long trail in the DB. I addressed this a bit more in the note below, but I think in practice the (bulk) withdraw you’d do with ecash would end up having similar privacy issues as today’s approach. You obviously can’t withdraw each single sat by itself (the fees would dominate, even on lightning), so you bulk-withdraw in batches. You’d have to have every user have the same bulk-withdraw randomization logic, with fresh BOLT12 (or different ecash mints) to withdraw to each time (otherwise you’d have clear fingerprints in the withdraw batches). And even then I’d bet with enough BOLT 12 blinded paths you’d be able to cluster most withdraws :/.
This just isn’t as simple as you’re thinking. I agree there’s a world where on an extreme margin this could improve privacy, but it’s a really tiny margin and a pool motivated to go look would probably be able to see through almost all of it :/
#nevent1q…slh4
Ha, fair. I’m well protected, trust me :)
Please go reread my note?
You should tell Strike this. That’s really embarrassingly slow!
His book came out *after* this “all started happening to him”. He’s just an asshole who’s sad he lost and can’t accept it.
(Sure prison time of that long for tax evasion is probably not right either, but there are worse miscarriages of justice)
Fair enough. I guess I just hope we can get to a place where folks like Mutiny don’t have to ever consider leaving the US. And that means playing the game, both political lobbying (usually not money, to be clear, mostly just outreach, but also direct ad buys, etc) and using the courts to push back on overreach. I’m sadly not sure what other approach exists given the state will use force to get their way.
We aren’t in ZIRPland any more (tho we may be there soon at the rate the economy is going…)
They’re really not, though. Also important to point out that you can’t “just” withdraw all your tokens piecemeal as the fee to do that (even over lightning) would dominate, and the intermediate hoops through the lightning network plus withdraw steps would almost certainly be a unique fingerprint. I’m quite confident you’d end up with zero additional privacy against a pool that really dug into it. #nevent1q…f2cn
That is not the only instance they’re talking about. That’s just the new one from today. Here’s three specific instances the UN is objecting to, all from the Guardian article from yesterday. https://image.nostr.build/59b14a3f73dd32ecb9be35a9f3890c5431ac781fe929f277b40dec4c99bb1bf3.jpg https://image.nostr.build/e1352d1c5a75f8cd05feb8922ae13cb8b61461b67b565cbcad36ea1563ba4843.jpg https://image.nostr.build/83cb8200c759a80ec4a7872674de1e14074d3596f69e309c4034256ef4b63074.jpg
Today you can see the lightning nodes that ship fixes for novel attacks quickly (eclair and LDK, which did some force closures as a result of the fix) and those that don’t respond to security issues after months.
This paragraph maybe, but self-custody is used several other times in the same article.
It may be better than the UX of “select which shitcoin you want to pay with” first, but, yea, boy it’s terrible….
Sure, but even before that it’s not hard to imagine simpler protocols that still work in a non custodial manner, or even trivial adaptations to lnaddress to do so.
Then I’m definitely done caring about bitcoin. I mean sure some people just want the 21M cap and they’ll be happy, but those of us who wanted to be able to send value to others without being censorable….
I can’t, cause others never shipped a fix so I shouldn’t disclose issues that aren’t mine.
What a great response. Didn’t even bother to read the explainer that goes through all the details. #nevent1q…gdpa
You can vote write-in and vote literally “none of the above” (or anyone, my grandfather has recently taken to voting for his friend down the street).
Bears zero responsibility. At the time of the post the IRS was *already* investigating Roger very seriously. #nevent1q…ue8s
One team is led by a fraud who thinks he knows how to handle a sword, the other hires an actor who can dress up in a puppet outfit and convincingly hold a sword. We are not the same. https://image.nostr.build/ebe171cabf0cd2820da3c97d687225246664ea70f15e12417c7264d44c27f356.jpg
Ha, if this is true another Trump administration will be worse for Bitcoin than the current Biden one 🤦♂️ https://image.nostr.build/17daa5d6e6e976744ddd064c437e2c3c135db0d5abed093108151c1399e5d46c.jpg
Executive orders are only allowed to set new policy for the executive branch. They cannot set new law or impact things outside of the executive branch (except by cutting government contracts and the like).
> > it removes an entire class of liabilities that need to be tracked. The business owner no longer needs to be concerned with unredeemed shares.
WHAT?! No pool should ever, ever, ever not track the total liabilities in each ecash epoch. Sure, they can *in theory* stop tracking individual shares, but they still need to track the total shares and the shares redeemed to ensure bugs in the ecash system don’t bankrupt them.
> we can do better
Sadly, users want, like, a UI that tells them their hashrate and monitors their devices and such. That should be run locally, on that I assume we agree, but actually building that is the hard part here, not anything related to ecash. The ecash part doesn’t improve complexity here, you move the tracking locally but you still have to build it (and it’s harder to build cause you have to build it to run on the miners end)!
> Most of my Twitter/X feed became stuff I just didn't want to see, and the platform really got in my way in trying to find content I did want to see that I decided to just delete my account.
Anecdotally I’ve heard this kind of thing a lot. I don’t think we have good public stats, though. I’m skeptical they have good stats either, tbh, given the prevalence of fairly convincing AI bots due to LLMs.
Custodial. Or, if you prefer, multisig-custodial.
Trust Models (refer back to this when someone claims their thing is “non-custodial”, note that privacy is a different spectrum)
* Holding Funds On Chain
* Trusting you can get a transaction confirmed in some time horizon where your balance is way higher than the on chain cost (LN)
* Trusting you can get a tree of many transaction confirmed in some time horizon where your balance is way higher than the on chain cost of the whole tree (in-round Ark for high-ish balances, rollups for *very* high balances after some future soft-fork)
^ non-custodial
v custodial
* Trusting you can get a tree of transactions confirmed in some time horizon where your balance is similar to the on chain cost (in-round Ark for moderate balances, rollups for most folks after some future soft fork)
* Trusting 1-of-N with keys (rollups with BitVM)
* Trusting N-of-M to do something honestly once in a TEE (statechains maybe?)
* Trusting N-of-M to do something honestly once (statechains/statechains-on-Ark)
* Trusting N-of-M with keys (Liquid, Fedimint)
* Trusting 1 entity with keys (Cashu, Coinbase, …)
You are selling bitcoin to buy things, this makes BitPay a broker under the rules put forth, which means they have to KYC you and report your sale to the IRS. It’s a bit less clear whether a merchant who sells for Bitcoin directly has to, but they could get caught up in it too.
Seems a stretch given the order doesn’t actually force “irreversible destruction of data”, it forces “irreversible destruction of a *copy* of data”
I think having an algorithmic feed resonates with people a hell of a lot more, certainly drove early adopters.
Any method of cooperatively building a nonce (eg stuff things do for FROST, it’s the same problem).
Sure, they may not be that fast in constant-terms, but square root is still a *huge* speed up. Worse, that speed up gets bigger with more work, so reorging a few blocks at a time is even cheaper. The real question here is how many qbits do you actually have - it’s possible that we can change the PoW to SHA256x10000 instead of x2 and crank up the qbit requirement to make it impractical for quite some time.