12
Carlos
123456785ee7815751c28004e6cef4398e1256f94a93bf51f90018e28accbfb4
Working on https://oak-node.net

Thank you sir!

IMO the biggest obstacle to running LN nodes is channel management. Some promising solutions are coming, but will take a while.

For less tech savvy people, the "Uncle Jim" model is probably best right now. But even here new solutions are coming: Greenlight from Blockstream lets you run your own LN node in the cloud, non-custodially. So its getting easier to run non-custodial nodes as well.

Oak is mainly for node runners, so if you have ideas or features you think are worth exploring, let me know.

Broke : Mine BTC by running a low power wallet

Woke : Mine BTC by selling fiat from custodial bank-owned fiat wallet

Bespoke : Have your CPUs on standby to mine Nostr vanity pubkeys, ready to go as soon as your LN wallet confirms you've been paid

---

Last bit is about https://lab.oak-node.net/powpub , working on the marketing message lol

Re: newbie friendly, Alby has a simple "recurring payments" offering, very newbie friendly (but I think its custodial). nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x can correct me if I'm wrong on that.

Oak Node has had Shadowy LN Tips since 6 months or so: nostr:note1qqqg4tylv66ecf3cdr7tudhvqq03furkggvaxh54kyf7f0n9mp6qzrlhaa

Lets you "zap" any note by simply liking it. Works from any Nostr client. Sats sent non-custodially, from your own Umbrel.

Agree, NWC is awesome!

Oak Node has it since more than a year. Runs on Umbrel, so non-custodial.

https://oak-node.net

Also supports setting a specific text in the recurring payments description (ending up in the invoice memo), so the service provider receiving those payments can assign those payments to a subscription with minimal effort.

Replying to Avatar Felix

I have nostr:npub17xwygpls3lp7nv540u5syuhkmrpwhtjc23cy5ql4jqrhnw925ejqccncvd which supports dalle2, stable diffusion and a mj like model (not the original one). Problem is it always crashes after a few hours due to a threading error I couldn't yet figure out

Threading error in the nostr code? Or in the AI API code?

If the first, I can recommend this nostr library : https://github.com/rust-nostr/nostr/ . I've been using it for a while in multi-threaded apps, never had a problem.

From 2 wallets: own node + Wallet of Satoshi

Definitely possible to do.

For example, the storage provider could listen on Nostr for "proof of storage" requests.

The client (who originally sent the file) could send a challenge every 24h using the scheme above. When answering the challenge, the provider can also sent a BOLT11 invoice, covering the cost for the next 24h. If the client pays it, the provider keep storing it. If the client fails to pay, the provider can delete the file after some grace period.

In a sense, the client is "paying by the day".

Ah I think you mean the "nostr relay with PoW pubkey admission" experiment you did a while back, min 32 bits or so.

I thought you meant the link posted above experiment.

Either way, when the spam gets crazy enough, IMO people will look for PoW solutions. Maybe we're not there yet, but It's a matter of time.

Can I ask which client you used and how it didn't work?

Yes, most won't mine their own vanity pubkey, but some might pay for one, which is good news for service providers.

For the unverified users, why not automatically whitelist PoW pubkeys above a certain threshold?

People could

- mine themselves using rana or nostril (proof of work, they would not want to risk throwing that to waste by getting their key banned for going against your ToS), or

- pay a miner to mine one for them using PoW Pub ( https://lab.oak-node.net/powpub ). Running a miner could be an extra source of revenue for easyNostr.

Either way it could be an easy way to keep spammers at bay.