I have two Trigkey N100’s on the same LAN. Machine A has knots and Datum. I use this to mine via Ocean with a little NerdAXE in solo/lottery mode. On machine B I just have Datum, and would like to pool mine via Ocean with a Nano 3s.
I would like to connect Datum on machine B to knots on Machine A. Having spent countless hours with ChatGPT/Grok/Claude/Perplexity/Google and got nowhere, does anyone have any tips? Or a better way of using Datum to allow solo AND pooled mining.
Unfortunately, Datum Gateway service on Start9 does not expose enough of the Bitcoin RPC configuration options to properly configure authentication with Knots running on a separate system (so you can’t point Datum on machine B to Knots RPC on machine A). This means you will need to do the IBD (and have enough storage space – 2TB or higher presumably) on both machine A and machine B to run a full node on both.
That said, I believe others here on the forum have run both Datum and Public Pool services, and use Datum for pool mining and Public Pool for solo mining on the same server (both using Knots to generate their block templates, if I’m not mistaken)
Thanks Paul, that’s a shame. I do have 2TB+ on both machines so I could have both running knots. The second machine was supposed to be for NextCloud so the more storage the better. I may ditch the idea of solo mining on Ocean and point the little Nerdaxe at some public pool and keep the Nano 3s for Ocean.
I’ll need to setup LND with a channel to your node, then CLN to LND to get the sats via Lightning. What is the min channel amount for yours, 30,000 sats?
If you do Public Pool, I recommend self-hosting it on your server (it is in the Community Registry) rather than pointing it at some 3rd-party hosted solo mining pool. Despite the name, when you self host it, it isn’t technically a “pool” – it just provides the Stratum interface that your ASICs are designed to connect with.
The minimum channel size on my LND node is configured to 10,000 sats, but you will likely need to make it larger than that depending on your configuration to excede the dust limit on the channel reserve. RTL will complain if you set the value too low, and you can gradually increase it until it takes. Most of the channels I’ve been opening lately have required 60,000 sats, so you might find that to be the lower limit. I think that comes from the dust limit being 546 sats, which calculates to 1% of 54,600 (i.e. that may be the actual lower limit, which would explain why 60,000 sats seems to work consistently).
Yep. That is the way I do it…BitAxe’s (1.5 Th/s) pointed at my own hosted Public Pool and the Nano’s, QAxe’s and Q pointed at Datum. Works well but if you want better payouts I’d point anything above 5 Th/s at OCEAN…Just my humble opinion.
Why not point them all at OCEAN? With Shares In Reward Window and Estimated Rewards In Window the combined hash rate of everything you point at OCEAN contributes to both of those.
EDIT: I pretty much said the same thing twice in my 2 comments but in different ways. Sorry about that.
I think that’s a good idea Greg, after all, the chances of the Nerdaxe at 500GH/s winning a block are truly tiny, so better to add it to the 6TH/s from the Nano. I’m just at the start of building a solar setup as electricity here in England costs a fortune! (and the solar kit will come in handy for other things too). The plan is to have it all in a shed at the bottom of the garden, so I’ve just added a wifi extender (one of those Google things) to make sure it’ll all connect. Madness of course as it will take years to recover the cost of the all the panels, chargers, inverters etc but what the heck, it’ll be fun, and one in the eye for the powers that be!
Thanks Paul - really enjoyed your video on setting up Start9, Datum, CLN etc - got me up and running on an old repurposed MacBook, which I’ve now ditched (and completely ruined taking the 2TB drive out!) for the Trigkey’s.
Yep. Madness…I’m right there with you. I’m trying to figure out how to go solar and power the Q and them Nano’s 24/7. Id need 2000 watts continuous power though…which looks expensive if I were to go the route of portable power stations with battery packs.
Right now I only run when power cost me 0.077 us cents per kWh - that’s weekends and 18 hours a day during week but would sure be nice to get that cost amortized down to 0.03 over say…10 years. Madness!
There is a thread here where we collectively discuss setting up our own pay channels and not use Pauls LND. It’s worth a read. @Fletcher and I have a pretty good system going between Core and LND…and with Fletcher’s guidance it seems ThunderHiub is a pretty good specific management tool for Lightning over Ride the Lightning…but I use both…plus the Alby hub. I think I have access to too many things
Sorry I don’t know the thread off hand but an easy search should find it. Gotta start with a few sats though…I think I started with 250,000 if not more. I opened a 60,000 sat channel between LND and Core…and between MegaLith LSP, ACINQ and Megalith .me (small channels) on the LND node I wanna say 200,000 total? Cant recall…but I had to open up larger channels because the payout from OCEAN ranges from 5,000 sats a day to 18,000 sats if OCEAN payout becomes problematic
Thats about 5 pence per kw/h - here it’s about 25 - 5 times higher! But we have a lunatic government. You can see why I’m keen on a solar powered mining operation
Funnily enough I found some info on a new solar / battery system called Ecoflow today, more portable and a cheaper setup costs than previous solutions, https://www.youtube.com/watch?v=IX8rSqhigSs&t=1s
Renogy do what they call ShadowFlux panels which are more resistant to having bits in the shade - more expensive than regular panels, but worth it I think to squeeze out every little photon. Thanks for the links by the way
Thanks Greg, I recall reading that thread a while ago. I do find this Lightning channel business a tad complicated, so I’m really glad I found this forum. AI is mostly useless for this I’ve found, leading to shouting matches and hurling insults at ChatGPT (but strangely satisfying )