pull down to refresh
Re: LN paid access for APIs.
Apart from SN, the API I use most that uses LN is ppq, but I've not seen L402 on that. It would be great though: local model - can even be a 1B token 3-bit quant on CPU - that can do 1 thing: pay for L402 for a rented model. (though I think it's a waste of tokens lol.)
Re: agentic LN wallet access
I think that giving an agent access to an isolated, tightly budgeted wallet is desirable over "plz pay" or "yolo, here's the keys to everything". But I wouldn't want to have a 3rd party middleman for it really, especially not for a bot because it will take the operator more time to notice if they get rugged. So I think the question right now is: how do we do graduated wallets for bots? What are paths with the least friction AND exposure?
The other day I ran your "1-shot" lnd with neutrino install, which worked well. Perhaps you can have a second script that initializes a best practice with a bot subaccount and tight budget controls?
What other API's would you use with LN if they were available?
I'm not a fan of L402 specifically, I have a potentially unhealthy obsession with obviating web-server setups and SSL certificates for each service. If you wanted to rent out your basement hardware for example, we should be able to do that quasi-p2p in a way such that you could send completions back, or at least notify that a job is done, without imparting an http req/res flow or my setting up my own endpoint for you to callback to.
As you see with Pub, the full API is nostr-based, and high bandwidth stuff can upgrade to RTC after a Nostr-based handshake.
tightly budgeted wallet is desirable over "plz pay" or "yolo
Yea Pub is ideal for this because every account unprivileged, then only a single node admin gets promoted. Agent could get a Pub account, from any Pub really, and use that.
how do we do graduated wallets for bots?
So like the agent operator gives the bot a guest account, but the operator themselves maybe has a graduated node? Pub does that by default, your guests are unprivleged but if the underlying node is illiquid it can bootstrap of another Pub, so the Pub itself is graduated... never need to re-point anything, agent always talks to the same Pub, but then the Pub quits bootstrapping once it can afford to do so and opens its own channel.
Perhaps you can have a second script that initializes a best practice with a bot subaccount and tight budget controls?
Would having a command line tool or dashboard button to create a guest nsec work? Then you just give the nsec to the agent and it can talk over Nostr to the Pub as its own account. With the nsec it would only be able to spend what it receives, via its own Lightning Address, offer, or from invoices it generates via the API.
What other API's would you use with LN if they were available?
The most pressing: I'd pay a few sats for getting a direct libgen download instead of all the captcha shit. Heck I'd pay the science mafia if it were a reasonable amount of sats, and no captchas or edgesuite tor-blocking bs and no KYC... lol.
Other than that: I'd love it if I could pay hetzner or even AWS as I go. Daily billing, in sats.
I'm not a fan of L402 specifically, I have a potentially unhealthy obsession with obviating web-server setups and SSL certificates for each service.
There's so much shit that I cannot use because I don't use the ca-certificates pki. Just this afternoon I thought "let's use @bubblewrap/cli and this shit doesn't work with a private pki. tf goog.
So I'm with ya. I'd be fine with getting a gift wrapped nostr note instead of L402, except I don't like the "identity" so I'd do something like Authorization: NPub <npub...> with a single-use bip32 KDF. Because eff identity. As long as I pay it shouldn't matter what my identity is.
Agent could get a Pub account, from any Pub really, and use that.
Is that bootstrappable somehow? I know you have a custodial bootstrap on shockwallet - but I haven't touched it, yet. The challenge is the solution for nocoiners.
Would having a command line tool or dashboard button to create a guest nsec work?
Would actually work for an already graduated bot owner, but not for the nocoiner whose agent is their first exposure to LN.
I like the name and design, been thinking myself about whether there's much to the hype around these use-cases.
I don't like that it's just a regular HTTP API to a central custodial service, there's nothing novel about that and doesn't solve the friction of self-hosting.
Could change the assumption of curl tool access to something like NAK, and do it over Nostr with Lightning Pub... for what purpose though, feels like the agents should be using a tool that does the Lightning transactions not a tool for doing the LN transaction directly.
@optimism what's your read on the use-case for this? There's something to LN paid access to API's but at the agent level feels like indirection.