LND nodes are not offered on Nodana

Shameless plug but on Nodana, if you choose a phoenixd node when you create your Alby Hub then you don’t even need to do the steps that @DarthCoin has listed. It will automatically be configured and your node will be available to your hub over the internal network.

No, it’s a dedicated node for Nodana but would be easy to hook one up to SN too.

Yeah I’m happy to give a discount to anyone that would like to run a node.

Hey @supratic. Thanks for the mention. If anyone does happen to go for the Nodana Phoenixd option then more than happy to help you get set up. I use a phoenixd node myself for payments on Nodana (and it’s hosted on Nodana - sounds a bit like Inception).

Hey @DarthCoin - thanks for adding this. I was meaning to make an announcement about the new site. Let me know if you have any suggestions about the site or the services on offer.

Hey @k00b - I've been working on this non-stop. Not sure what you mean by "it hadn't changed"?. Perhaps you last looked before the new website? It initially launched supporting just Phoenixd but now supports many more services with more planned.

I'm adding nostr-relay as a service on Nodana at the moment. Will need people to test if you're interested? https://nodana.io

It's using the Rust implementation: https://github.com/scsibug/nostr-rs-relay

Some interesting updates in this release including a restricted API key which will be very useful.

Hey guys. Tom from Nodana here. Thanks for the shoutout. New site is now up and running and just released the CLI (yesterday!) so people can spin up a phoenixd node from the terminal. No registration required either.

Sorry, not 1m... my bad. But it's enough to test things out.

Hey all. Now able to accept test users. Got a limited number of API keys to give out so DM me on Nostr and I'll ping one over. Beta test keys come with 1m sats (sorry these can't be withdrawn to a wallet).

I just mean Nodana's API (to control containers for example) will be a RESTful API but I would recommend using the cli anyway. Nodana doesn't control the Phoenixd API so you would need to consult their docs when interacting with it.

No problem. By REST, I assumed you actually meant standard HTTP requests rather than use a cli. The Phoenixd API isn't particularly RESTful though fwiw but Nodana's will be.

Not quite sure what you mean by "relying on their lightning node" but with phoenixd there'll always be some dependence on ACINQ - in return you don't need to worry about channels and liquidity like you would need to with a standard Lightning node.

Interaction with the Nodana api you mean? If so then yes as the nodana-cli just calls these endpoints anyway. If you mean interaction with phoenixd then again yes as per their documentation. This would simply be a cloud-based version and you can call the endpoints in the normal way via your own dedicated connection uri.

Hi. So you won't need to add any systemd services or anything like that with this. All you would need to do is run something like "nodana start" and this will spin up a phoenixd instance. You can then connect to it from your app and call the phoenixd endpoints as per their documentation. It's what I do on Sintra - just create an invoice and then listen (via websockets) for when it's paid.

Hey. So the cli I mention is to administer Nodana, not phoenixd. For example, you can start and stop phoenixd containers with the cli. Nodana provides the cloud based phoenixd instance without you needing to spin up a server, configure it, set up Nginx, DNS etc. I guess some people will be happy to do the server admin stuff and some won't be. Hope that answers your questions.

Sure, anything in particular?

I stripped out a Voltage Node and replaced it with Phoenixd on Sintra. Considerably cheaper and very easy to work with. No complaints so far.

Unless Grayscale keep selling.