Apparently there's no way for me to see these messages. Pretty ghey for a censorship resistant protocol, if you ask me.

No. Orange-washed commies can GFT ✌️
I verified both the X thread and the linked issue from the Bitcoin repository, and he didn't dox himself in 2023.
He was actually complaining about Marco Falke doxing him in a comment of said issue. A comment that since then has been scrubbed from GitHub (his link is now partially broken).
Verdict: 🤡 🤡 🤡 🤡 🤡
I don't work for you. And apparently Mechanic saw fit to give you a second chance so it's also an irrelevant request now.
If it was up to me you'd still be banned, that's all anyone needs to know.
BTW I'm an admin in the Knots and Fork Talk group now.
Learn to behave like a normal person or I'll kick you out of Fork Talk, too.
A normal soft fork is designed to wipe out the old chain. It can start as a chainsplit if it's contentious (.e.g a UASF situation), but it will heal the split on activation.
There we go.
7 signers (so far) for Knots v29.2.knots20251010.
https://github.com/bitcoinknots/guix.sigs/tree/knots/29.2.knots20251010
more than 10 signatures: https://bitcoincore.org/bin/bitcoin-core-30.0/SHA256SUMS.asc
only your sig: https://bitcoinknots.org/files/29.x/29.2.knots20251010/SHA256SUMS.asc
anyone can verify that themselves, weird thing to lie about
I attested all Knots releases since v25.1. knots20231115.
Haven't attested v29.2.knots20251010 yet because it just came out. Thanks for the reminder.
This is business as usual. https://blossom.primal.net/77a30fff244c87ffc5d77b3453ba51a2402edd3772b17cbcd00a225a7b103337.mp4
nostr:nprofile1qyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99uq3wamnwvaz7tmxwfjkuuewdehhxarjxyhxxmmd9uqzqla9dawkjc4trc7dgf88trpsq2uxvhmmpkxua607nc5g6a634sv56rwqxt de vez en cuanto firmo eventos de Nostr con mi clave privada y los retransmito, luego existo.
Thanks!
My only interest in FPPS is that it seemed easier to implement than PPLNS and especially TIDES, with its payouts to miners directly from the coinbase tx.
But now I've realized you could send all the rewards from the coinbase tx to a pool operator's address and still implement PPLNS payouts.
Got a minimal DATUM “pool” talking to datum_gateway (interop demo)
TL;DR: datum_gateway being open source is enough to build your own pool. EGPOOL is a minimal proof — not production.
Datum_gateway is open source and the protocol is right there in the code. My take: if you can read the protocol, you can build your own pool.
Before arguing, I wanted to try it. So I hacked together a tiny Python prototype called EGPOOL. It speaks the DATUM protocol and can handshake, push CONFIG, and round-trip shares with the gateway — no Ocean pool code involved.
What I proved (all from the public datum gateway code):
• Framing: 4-byte XOR’d header + payload
• Handshake:
- proto=1 HELLO: sealed to pool LT X25519, signed by client LT Ed25519
- proto=2 RESP: sealed to client SESSION X25519, signed by pool LT Ed25519
• Channel (cmd=5):
- Box(serverSessSK, clientSessPK) w/ 24-byte nonce from nk + client session pk
- Nonces increment per message (LE 6×u32)
• CONFIG 0x99: signed by pool SESSION key, applied by gateway
• Share submit 0x27 ↔ response 0x8F: round-trip works
My test setup
EGPOOL pool server <-> DATUM GATEWAY -> Bitcoin node
I connected a bitaxe miner to DATUM Gateway.
I saw gateway handshake with pool server and accepting shares from miner.
Datum Gateway logs from my run:
Handshake response received.
DATUM Server MOTD: Welcome to Python DATUM Prime (prototype)
client configuration cmd received from DATUM server
DATUM Pool Coinbase Tag: "EGPOOL"
DATUM Pool Prime ID: a1b2c3d4
DATUM Pool Min Diff: 65536
Starting Stratum v1 server
---
quick disclaimer — this is a test rig, not a real pool
This is just an interop demo to show the protocol surface is enough.
A production pool still needs all the boring-but-critical stuff: reliable networking & reconnects, user/worker auth, proper vardiff and duplicate detection, real accept/reject plumbing, accounting backed by a DB, coinbaser v2 with real splits, the 0x50 validation path (stxids → by-id → full set), signature discipline (LT vs session), rate limiting/DoS guards, key management/rotation, metrics/alerts, etc
Want to understand more about the protocol?
check my GitHub
https://github.com/electricalgrade/sv2/blob/main/doc/Datum_Protocol_Spec.md
#Bitcoin #Mining #DATUM
What kind of database do you think would appropriate to store and efficiently access this kind of information?
Also do you think it would be too difficult to evolve this PoC into a realistic FPPS DATUM pool?
#vlog 23
Why I'm Against Covenants
https://blossom.primal.net/29e096bb6acdef0b6cb8fb974712a60048a41e21c9796ad971aa0a43b37fe72a.mov
fukin' based
But the scammers are there :')
Reminder: banning VPNs amounts to banning the Linux kernel in the UK, as it contains the source code of Wireguard and its full functionality.
For those who don't know Wireguard, it is arguably the best VPN software written to date.
They're even crypto haters in the broad sense (who can really blame them?): https://forums.eveonline.com/t/isk-for-bitcoin/481662
Primed to be disrupted.



