Oddbean

PSA: The functionality of multiple Fedimint federations is significantly degraded due to severe DNS issues. It seems to be the case that some federation guardians have an XYZ domain that the DNS registrar has taken over. Freedom One and Bitcoin Principals appear to have one guardian offline due to this. Unfortunately, despite the server and keys for these guardians being intact, there is no way for the DNS of a guardian to be swapped out after the fact. We became aware of this issue last week and then became aware that multiple federations are experiencing this: https://github.com/fedimint/fedimint/issues/5482/ Given the critical state of these federations, with one guardian out of four being permanently offline, it's essential that if you have funds in these federations, you should withdraw them immediately. Unfortunately, we're unaware of other public federations, so you must withdraw to another lightning or on-chain wallet. From our experiences, intermittent/connectivity issues can occur with guardians, and this may result in errors if not all three remaining guardians are consistently online. No other guardian of these federations has XYZ or other domains like it. So, if you're having issues, please try again later. Unfortunately, not much can be done on the Mutiny side, so we're removing the federation setup flow in the UI as a first step. Sorry for the inconvenience.

It's not anywhere near centralized enough for that argument to be valid, and the market will respond as soon as they attempt to seize miners to produce empty blocks (this is the attack vector) - fees go up until enough hashpower comes online to mine non-empty blocks.

Until there is public, determined competition between nation states for domination of the mining space its a very real threat. The US is *quite* adept at leveraging its position in even hostile jurisdictions. There is no place on earth that both 1,takes bitcoin seriously enough and 2,hates the US enough that miners can feel secure enough to bring large hash online there. And of course, one jurisdiction isn't enough. We need many. So tbh, it's stupid to dismiss that attack vector. Sure you'll probably still be able to eventually get your tx mined. But the network will NOT function as advertised.

You're describing the hash war phase. The network will not work as advertised, but only for a certain period of time until either the state or the market capitulate. Here watch this: https://youtu.be/X_xgmVLyB94?si=UhSN5Cmjzbk9Tyvs

Right. As I said, its a legitimate threat until we get to that phase. It's another front of state KYC/AML laws designed to undermine bitcoins censorship resistant properties. And they're being generally successful.

I hope there is. Regulators are quite accomplished at avoiding direct confrontation and instead gradually adjusting expectations over years. Bitcoiners normalization, and even encouragement of, KYC being case in point.

People look at this and see nothing wrong with using DNS-based image urls or url-based relay hints inside our posts. They are never going to come after our content, right? Riiight? nostr:nevent1qqs07vzaf20nkacc3qp0j2hjzjyynfynf9q9qpa9d23uf7n7prt2cdqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygxlzue8wxp0x92ax7enqggm580y4q2spspdr90fvnu3hem5ajt8pqpsgqqqqqqsqjmpl4

l think I just lost about 100K #sats nostr:nprofile1qqsd79ejwuvz7v246danxqs3hgw7f2q4qrqz6x27je8er0nhfmykwzqpz4mhxue69uhhyetvv9ujumn0wd68ytnzvuhs9025sn #federations be careful #nostrplebs out there 😐 #bitcoin #nostr nostr:nevent1qqs07vzaf20nkacc3qp0j2hjzjyynfynf9q9qpa9d23uf7n7prt2cdqpz4mhxue69uhkummnw3ezummcw3ezuer9wchsygxlzue8wxp0x92ax7enqggm580y4q2spspdr90fvnu3hem5ajt8pqpsgqqqqqqs4hfpqn

I had it hang like that after latest update. Ended up with a force closed channel a few days ago. May be separate to the degraded function of fedimint. I went thru the process of closing the wallet on first device and reloading by seed on another device then closed it all the way out. Then deleting everthing on the first device and reloading it on the first by seed. Only use from one device at a time.

The problem is, if you don't already have a channel, you're stuck. Mutiny is automatically transferring all on-chain transactions to the federation, not to the wallet on-chain address. Is it supposed to work that way? This has happened to me twice already. I now have ~500k stuck in the freedom one federation, and I cannot create a channel because my on-chain balance is too low. Also, your recent patch doesn't seem to work when you select the option to send to another wallet. The confirm send button is muted and doesn't do anything. Here's a recording taken a few days ago: https://v.nostr.build/POVV7.mp4

Maybe I'm naive, but I feel like keys both private and public are circulating enough to feel normalised. A generation or two and we'll all just use public keys and hash identifiers. We'll have local directories of them in our phones. Then we'll use a peer to peer discovery network to find each other (keet) and all will be well with the world. Maybe advertisers will put qr codes or something else alongside their ads with public keys for their websites. Maybe I'm having a heat stroke.

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.

An update to our apps have been made that should help performance when a single fedimint guardian is down. Please continue withdrawing out of the Freedom One and Bitcoin Principals federation. The LN gateways might be experiencing heavy load so try on chain if you need to. Getting plenty of reports of successful withdraws so far today, try again if you had issues before. The fedimint team is working on short and long term solutions but for now it's best to withdraw and remove the federations. We have turned off lightning addresses for now too. Sorry for the issues. nostr:nevent1qqs07vzaf20nkacc3qp0j2hjzjyynfynf9q9qpa9d23uf7n7prt2cdqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygxlzue8wxp0x92ax7enqggm580y4q2spspdr90fvnu3hem5ajt8pqpsgqqqqqqsqjmpl4

Still having this problem. Is it fixed? nostr:nevent1qqs07vzaf20nkacc3qp0j2hjzjyynfynf9q9qpa9d23uf7n7prt2cdqpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsd79ejwuvz7v246danxqs3hgw7f2q4qrqz6x27je8er0nhfmykwzqrqsqqqqqpx6nsrn

Update: A small hotfix has been deployed restoring connectivity to all known federation guardians with this issue. A longer term fix is in progress and will probably be in the next major fedimint release. Huge thanks to the team there! Remember, fedimint is still early but still very promising. We thank everyone testing out this software and providing feedback and patience 🙏 nostr:nevent1qqs07vzaf20nkacc3qp0j2hjzjyynfynf9q9qpa9d23uf7n7prt2cdqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygxlzue8wxp0x92ax7enqggm580y4q2spspdr90fvnu3hem5ajt8pqpsgqqqqqqsqjmpl4