sedited / sedited is on Nostr

In short: The gpg version I had running back then still used sha1 has a default digest to generate the base signature attesting to the first subkey generated automatically during key generation. Like a good citizen, I changed the default digest algorithm to something strong, generated the remaining [a]uth and [e]ncrypt subkeys with this configuration, and changed the expiry on all of them. Turns out, gpg never refreshes the base signature even you tell it to update a subkey, or change its configuration. So when the Bitcoin Core commit signature verifier ran with a strict no weak algos policy it tripped over this weak base signature.

2025-11-28 07:07:58 UTC

I was a bit hopeful the last few months that the proposed soft fork will change this dynamic, but I no longer think so. One side needs people to run with their vision, while the other side is content with doing nothing. That's why I think its militancy will not die down. In all likelihood it will be a schism present for years to come.
#nevent1q…g6at

2025-11-14 13:24:59 UTC

- reply

That's some nice tooling, had to slightly tweak your example to include the correct imports, but ran all of them. Nix is magic in the sense that this would have been really annoying to setup by myself and now it just works .

2025-11-14 07:55:50 UTC

We've run into this problem where the same code built through our reproducible builds infrastructure has these weird registry switchups between running the build environment on an x86 machine and an aarch64 machine. At this point I would pay for someone to explain what is going on here. It doesn't make sense to me. https://github.com/bitcoin/bitcoin/pull/33775#issuecomment-3523047473

2025-11-04 16:27:04 UTC

Didn't expect this today: The bitcoin kernel API is now in Bitcoin Core's master branch! A decade of effort for various contributors and three years from myself: https://github.com/bitcoin/bitcoin/pull/30595
Looking forward to an ecosystem of implementations, full nodes, and tools being developed around it!

2025-10-26 08:33:00 UTC

Well, if there is going to be a soft fork, which seems increasingly likely now, this conflict might be resolved after all.

2025-10-09 17:14:03 UTC

Missed the asmap launch again 🫣

2025-09-12 08:12:32 UTC

Running bitaxe+sv2translator+sv2pool+sv2template provider+mining interface+bitcoin-node v30rc1.

2025-09-10 13:39:03 UTC

- reply

Then they'll patch and carry on.

2025-09-10 12:25:55 UTC

There is no resolution mechanism for the relay policy dispute. My hunch is this fight will persist for a long time. It is likely in my view that the share of knots nodes running on the network will keep growing as a result.