ElectricalGrade

Started with BTC hobby mining in June 2025 . Learning and exploring btc,lightning

[ElectricalGrade @ElectricalGrade]

🚀 Hi X Bitcoin community ! , sharing my DIY Bitcoin home‑mining journey using Bitaxe and DATUM on the OCEAN pool. I cover setup tips, pool insights, hashrate benchmarks, and my solo‑mining path

Follow along and subscribe: https://t.co/kdnQwAipJk ⚡️

#Bitcoin #DATUM

[ElectricalGrade @ElectricalGrade]

@GrassFedBitcoin @adam3us My take is that node shud runners get the freedom to choose

Bigger problem is mining decentralization

Mining pools could easily use datum_gateway but will not as it hits their pvt mempool & control over miners (hashers)

[ElectricalGrade @ElectricalGrade]

@oomahq @wk057 @adam3us @JuergenStrobel @findebatematt @BTCYaLater @LukeDashjr @blue_matt @DEMAND_POOL @KenobiGeneral5 Yes .. pool owners should write their own.
Datum to miner can be sv1/sv2(mining protocol only)
Datum to pool is open protocol & pools can implement this TODAY
I created a mock pool & documented protocol also

https://t.co/YvEjLYeaYC

[ElectricalGrade @ElectricalGrade]

@_DavidSFreeman The mining protocol of sv2 can be added to datum which allows miners to talk sv2 mining protocol
Check below 👇

[ElectricalGrade @ElectricalGrade]

Noise protocol is used in stratum v2 for connection handshake and further communication
First prototyped this in python.
Datum gateway is C
So started with noise-c.
Got the basic handshake with NX working between server and client

I will post more details on Nostr

[ElectricalGrade @ElectricalGrade]

@_DavidSFreeman It’s mining interface for stratum v2 template providers not full implementation of sv2

DATUM does not need this interface as it does not need template providers

[ElectricalGrade @ElectricalGrade]

@SatsScholar https://t.co/GreGdbeXql

[ElectricalGrade @ElectricalGrade]

@wk057 He just proved 2 things
1)without mempool policy it’s a disaster(libre)
2)without decentralized mining even mempool policy falls short (f2pool)
My ML detected this as malware as soon as block was mined
Today AV don’t look at db but if this continuous cloud AV will scan btc db

[ElectricalGrade @ElectricalGrade]

@wk057 He just proved 2 things
1)without mempool policy it’s a disaster(libre)
2)without decentralized mining even mempool policy falls short (f2pool)
My ML detected this as malware as soon as block was mined
Today AV don’t look at db but if this continuous cloud AV will scan btc db

[ElectricalGrade @ElectricalGrade]

@mkuegi @stolsvik @adam3us @SledgeTheTV @peterktodd @GrassFedBitcoin @BitcoinKnobs @r0ckstardev You just cannot prune only opreturn
Block validation will fail
Pruned block nodes have a place but can never be a replacement for full node
We should encourage more and more users to run full nodes else a cabal can easily hijack

[ElectricalGrade @ElectricalGrade]

@stolsvik @adam3us @mkuegi @SledgeTheTV @peterktodd @GrassFedBitcoin @BitcoinKnobs @r0ckstardev Yes
But we need full nodes so that when new nodes join they can validate
There are some techniques like Non interactive proof of PoW which mitigates this but it’s not there in bitcoin
When you start a new node you have to download and validate before you prune

[ElectricalGrade @ElectricalGrade]

@stolsvik @adam3us @mkuegi @SledgeTheTV @peterktodd @GrassFedBitcoin @BitcoinKnobs @r0ckstardev No. Pruning is only for uTXO set so that your RAM usage is lower but OP-RETURN can never be pruned from a block on disk
You can prune blocks (pruned node) but not just op return
So if opreturn is spam you will store it in disk
It’s needed for initial block validation

[ElectricalGrade @ElectricalGrade]

@LukeDashjr Yes full node is a must

I have also built a small utility. It subscribes to zmq and publishes on zenoh. Subscribers can get these even if they have flaky connection

[ElectricalGrade @ElectricalGrade]

@LukeDashjr Yes. Separate the consensus and policy parts. This will make life easier to push policies.
Better handling of database and uTXO growth

[ElectricalGrade @ElectricalGrade]

🧪 Homomorphic Encryption over Nostr — PoC

Paillier scheme + custom Nostr event kind 555
Clients add encrypted integers, relay stays dumb

https://t.co/fhynTzQ10n

[ElectricalGrade @ElectricalGrade]

🛠️ Spin up Bitcoin Knots + DATUM Gateway in Docker Compose.
No more juggling configs — just docker-compose up and you're live with a proper Bitcoin node + Datum Gateway.
Built this for myself, but figured someone else might want it.
Run infra, not drama

https://t.co/hp7Cj30Bx0

[ElectricalGrade @ElectricalGrade]

@_PyBlock_ That is because you downloaded binary . The https://t.co/ob2cljOhgB is removed from 29.x

[ElectricalGrade @ElectricalGrade]

My Bitcoin knots node is updated , datum pointing to new node and small miners are back into business

I don’t download exe, I build from sources

I also have docker support and can launch knots and datum using
docker compose

[Bitcoin Knots @BitcoinKnots]

Bitcoin Knots 29.1.knots20250903 released! 🎉

Be sure to verify your download(s)!

https://t.co/lvSATtwcQ3

[ElectricalGrade @ElectricalGrade]

This is the beauty of datum
You have your own node and gateway ..

[Jason Hughes @wk057]

@skot9000 Akshually... when the workers are behind DATUM, I actually don't have that information. They're solo mining the block on their own. The UA doesn't need reporting to the pool.

I this case the miner came forward and said it was a QAxe++.

[ElectricalGrade @ElectricalGrade]

Knots v29.1 released 🚀

Have you upgraded yet ?

Check my Nostr post for highlights

[ElectricalGrade @ElectricalGrade]

@adam3us @bigshiny90 Sv2 today adds a bunch of complexity in pool side & need translator if miner does not update FW
I like datum architecture. Its simple for both pool & miner
sv2 mining protocol can be supported in datum
But any move away from sv1 is a win

[ElectricalGrade @ElectricalGrade]

@oomahq @GrassFedBitcoin 😀😀 and thank you for sharing with us so that we can add docker support