Nostr Web Client

Léo 1mo ago

I have sent the update to all platforms now.

If not already available, it will be once the maintainers merge/add the update.

🪢

nostr:note12tzhd20jy7354mel7yrup7p05wyp8dre3mkfa0knc0egztfv6gwqnlly5e

Replying to

Dathon Ohm

After much discussion and consideration, I have decided to remove the reactive deployment method and the legal/moral motivations from the BIP document.

I still think those things are important and the reactive deployment may become necessary in an emergency, but I want to continue building consensus and those features were hampering progress.

I hope to have the new draft ready in the next day or two.

Thanks to everyone for your support so far.

Léo 1mo ago

Thanks for all the good work!

Replying to

Léo

Top notch nerd question, is there any node runner on the DN42 network?

I just launch my node there on my own AS but not a single peer :(

Léo 2mo ago

Come say hello!

Léo 2mo ago 💬 2

Top notch nerd question, is there any node runner on the DN42 network?

I just launch my node there on my own AS but not a single peer :(

Replying to

ODELL

the latest core release was signed by over ten people

the latest knots release was only signed by you

Léo 2mo ago

Others are coming, including myself.

I sign all release of Knots since v25.1.

Replying to

Tauri

Can’t really say what his PoV is. The mainstream take seems to be that Knots is just as bad as Core, since most people assume Knots users simply trust Luke more than Core devs. That’s true to some extent, but some of us have been in the trenches since 2023. We didn’t follow Luke because he’s likeable or an OG; we argued with him plenty (especially Mechanic and Matt Kratter included).

For me, the real wake-up call came from nostr:nprofile1qqs8ha7ms0mny284ma46xjzf72hel42t74jmtttf3trssfymxyq8ngqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqppamhxue69uhkummnw3ezumt0d50300jw long before any of this blew up - back when Knots was run by maybe 50 people. We had to unlearn a ton before getting on board with the anti-spam stance. We even built wtfhappenedinfeb2023.com to help others understand the issue instead of just “trusting the science.”

IMO Odell, like many others, hasn’t actually done the work or is just too biased. Either way, it’s disappointing how he acts like everything’s fine when it obviously isn’t.

Léo 2mo ago 💬 1

Glad to have met you during this epoch. In Feb 2023, I learned what being a node runner truly means!

Replying to

aco

yeah, still not working. it goes to the fallback.

Léo 2mo ago 💬 1

Ok please share your config and/or logs in DM so I can help you debug the issue

Replying to

aco

nostr:nprofile1qqs0m40g76hqmwqhhc9hrk3qfxxpsp5k3k9xgk24nsjf7v305u6xffcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszynhwden5te0dehhxarj9e3826tvvshs0j4exe I’m trying to configure my DATUM and it’s not hashing. Not sure what’s up, I was following the instructions.

Léo 2mo ago 💬 1

Let me know if your are still encountering issues.

Replying to

BITCOINALLCAPS 🐦 🐦 🐦

Fun with a bitaxe pointed at ocean pool

Léo 3mo ago 💬 1

Not running datum?

Replying to 50bdea8d...

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

Léo 3mo ago

OMG you are cooking! 🔥

Léo 3mo ago 💬 4

Knots 29.1 available on start9 market place! 🎉

Replying to

Neo

Léo 3mo ago 💬 1

Enjoy! 🧡

Replying to

Neo

no,my ideea is to have your mempool.guide in S9 too

Léo 3mo ago 💬 1

Yeah that what it does. 😅

I’m just telling you that if you run mempool guide with knots 29.1 start9 will complain but you can safely ignore this.

Replying to

Léo

Right here sir

https://github.com/Retropex/mempool-startos/releases/tag/v3.3.0-dev2-mdg

Léo 3mo ago 💬 1

I didn’t think of the dependency version, it will also warn about the knots version but you can safely ignore.

I will fix it next release.

https://github.com/Retropex/mempool-startos/blob/044954befae7fd972d20e989e1a09d23fbae2138/manifest.yaml#L65

Replying to

Neo

Or maybe is time to push your mempool.guide to start9

Léo 3mo ago 💬 1

Right here sir

https://github.com/Retropex/mempool-startos/releases/tag/v3.3.0-dev2-mdg

Replying to

Neo

Mempool dependencies for knots max 29.0.0 and knots is 29.1.0

Léo 3mo ago 💬 2

Oh yeah can’t do much about that, they need to update their package.

But anyway mempool should work normally.

Replying to

Neo

I installed before verified and imported your gpg key 🔐,all is ok,only minor issue is the version attention from electrum.

Thank you!

Léo 3mo ago 💬 2

What was the issue?

Replying to

Neo

Hi Leo,I have error on Start9 with Knots 29:failed to open database path....builds does not support Berkeley DB database format

When I disable wallet then all is ok.

Now the v29 disappeared from your GitHub and so I downgraded back to v28 .

Léo 3mo ago 💬 2

https://github.com/Retropex/knots-startos/releases/tag/v29.1.knots20250903

Don’t forget to verify your download!

Léo 3mo ago

Studying bitcoin is also studying history, just saying 😂

Replying to

Neo

Hi Leo,I have error on Start9 with Knots 29:failed to open database path....builds does not support Berkeley DB database format

When I disable wallet then all is ok.

Now the v29 disappeared from your GitHub and so I downgraded back to v28 .

Léo 3mo ago

Yes the version with bdb is coming soon!

Léo 5mo ago 💬 1

nostr:npub1qmw7jhczdr8yqy5t7u72d6z4v7u9va5gaff0ynwd2u6wwlzs7tvs694er8 is there an option to change the country I’m connected to after purchasing a subscription?

Replying to

Tauri

Oh they fixed the “node” app that applied to just Bitcoin Core?

Léo 5mo ago

No :(

Léo 5mo ago 💬 6

The new knots app on Umbrel is out!