I see Braiins has launched a rent-a-hash program so to speak. $39/PH/day.
Just off the cuff this seems like a pretty decent deal considering to buy a PH worth of machines and then feed it electric would cost more than $39 a day? I did set a bid and am sending the hash to my OCEAN account for a test run. What you think @paul
I haven’t run the math yet taking into account the “One Big Beautiful Bill” change that lets you offset deprecation of the ASIC on your taxes, but on the surface, this sounds like it might be more cost efficient. Do they let you rent without doing KYC? Besides supporting OCEAN (and likely the MASF when it is finalized), another reason to do this would be to build your non-KYC stack if that can be achieved with this option.
Yes…no KYC. There are several pools that you can point to also but I was glad to see OCEAN available.
As for the One Big Beautiful Bill - yes…that is a factor to be sure. I bought a Antminer S21 Pro 234TH and plopped it down at Sazmining last week. Nice to see Saz make OCEAN and Datum available as well…bummer though I cant use my OCEAN username but oh well (for now). With the One Big Beautiful Bill that $5200 spent for setup and purchase it will be nice to recover that cap-x.
Do they pay out over lightning or only base layer? No KYC is excellent, but thinking adversarily, if their records and logs were to be siezed at some point, a base-layer address could be traced on chain to try and associate it with the rest of your non-KYC stack (payout over lighting would break that link). I suppose if it is base layer payout only, you could pay out to your lightning node’s base layer wallet, use it to open a channel or splice into an existing channel, then send to Boltz over lightning to swap it into a fresh cold storage address. Taking a ride through the lightning network breaks the on-chain tracability.
Braiins in non-custodial. The payout is OCEAN pool (your lightning channel). Braiins is strictly hash
A update:
Hash is coming in at a rate that increased the payout beyond the lightning channel size. This is new for me to be sure. Does a lightning channel accept what it can or is the whole transaction denied?
The whole transaction will fail with a “no suitable routes” (or however that error is worded). For large inbound (and outbound for that matter), having multiple channels to different well connected nodes is important (to support split routing of smaller chunk sizes)
That was sneaking around in my head when I asked the question. I should have good enough routing peers (MegalithMe and MeagLith LSP) but the LND/Core channel is only 60K. I will have to stay on top of the payouts and cross fingers the payout doesn’t exceed at a time.
Thank you sir.
You can always add a second channel between your LND and CLN nodes. If you do that, though, open it from the LND side to avoid the bug where CLN never broadcasts the channel open transaction.
I can do that easily but so I’m clear…a second channel will add to the “receive” side of the Boltz already established on the original channel? Not a great thread to discus Lightning so I’m trying to keep it brief as you have many threads discussing that.
If you open the channel from the LND side, it will be 100% inbound capacity from CLN’s perspective (which you want in this case). That means you have the capacity to receive more payouts from Ocean before you need to clear inbound capacity (via Boltz,exchange, for example). I believe the original BOLT 12 offer you configured with Ocean should still work (it is tied to your node, not any particular channels IIRC)