Nostr Web Client

I want to offer different lightning backends for Strom in general: LND (for umbrel or voltage), LDK, CLN, LNbits, Breez/Greenlight. Kinda plug and play. For Strom-as-a-Service different backends options would require different fee models, hosted LND/CLN nodes being the most expensive.

But Strom itself is being written in Go, which I think also works with AWS serverless. It could work, though I plan to integrate nostr also, which would mean it's a websocket client listening for events...

Have to think about it more.

steepdawn974 2y ago

So: user scans & pays the unique lnurl-p QR of a Charge Point ➡️ the LN backend issues a "start the charge" command through a OCPP bridge software ("Strom") ➡️ the CP returns the payable amount via the OCPP bridge to LN backend, which issues an invoice to the users LN wallet , right?

Can't you just build an OCPP plugin ("Strom") for LNbits, to do all that??

LNbits already has most of the components you need:

- Accounts. Each CP operator get its own LNbits wallet ("account") where the can and and maintain their own CPs, through the OCPP plugin

- Lnurl-p/w functionality

- supports already every LN backend

- Accounting and Reporting

- SaaS deployment possible

The OCPP plugin would be reponsible to establish the websocket to each CP when a charge is initiated, and translate Lightning (lnurl) <-> OCPP commands.

Or What say you, nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg

Reply to this note

Please Login to reply.

Discussion

No replies yet.