Watched a few of their tutorial videos. They do a really nice job with those

Is there one page somewhere that links to all of the official guides for wallet linking? It would be great to share that single resource with people.

I got it working. I was hesitant to stop the AlbyHub LDK node as I wanted to avoid downtime there, but I decided to bite the bullet and do that.

After that, Lightning.Pub installed fine.

Afterwards, I couldn't start AlbyHub again as I got the following error: {"error":"listen tcp :8080: bind: address already in use","level":"error","msg":"echo server failed to start"}

My guess is this is the conflict which was preventing Lightning.Pub from starting properly when AlbyHub was already running.

If I again start AlbyHub first, and try the fresh Lightning.Pub install, I get the same result. "Can't retrieve wallet status". Screenshot at bottom. It did have the "Port 9735 is in use. Checking next port..." line, but, that must not have been the only issue.

Heading back to AlbyHub for now as I have other family members using it, but, I'll get another machine going at some point to test out Lightning.Pub. Or, if you have other ideas how to make them both work without wasting too much of your time, we could take that offline as well. Thanks for your help!

Seems to still be having an issue with the previous install even after the steps above (up to and including $ rm -rf ~/lightning_pub ~/.lnd ~/lnd ). Seems it is still finding migration files somewhere. I should just try this on a separate machine at some point

Thanks for your efforts here. This is what I got:

Have to head back out. Will try again later. I went from Lightning.Pub to Alby Hub, so previous Lightning.Pub files were still around. Seems like the install may have worked? I'll have to figure out how to get the nprofile to pop up again. I have the nprofile saved from the last time I was running Lightning.Pub but that isn't working as a source in Shockwallet. I get a "Cannot connect to source. error enrolling admin token. Nostr connection timeout" error in Shockwallet . Maybe wiping Lightning.Pub and starting from scratch with a fresh nprofile is the way to go. LND is also hanging around from the previous Shockwallet install. Wiping that and reinstalling might also help.

That’d be great

Alby hub is using LDK. Would there still be a conflict with LND then?

I meant to circle back and try Lightning.Pub to see how it was progressing, but the easiest device to do that on is an Ubuntu machine that is already running Alby Hub. With the one line install there are port conflicts. Since running Alby Hub is fairly common, is there any way to get a one line install that uses alternate ports and doesn’t interfere with Alby Hub?

Who did these users sell the "No" shares to? Wouldn't whoever bought the "no" shares still have them, and be shown in the "losers" section? Or does it mean User X bought them, and User X also had "yes" shares, so they offset, and it reduced the number of "yes" shares user X was holding?

If so, would it be possible to show the amount of sats "lost" by users selling "no" shares at a loss (i.e. less than they bought them for). It feels like that is a missing piece of the closing metric.

For the Auburn Oklahoma game, how was there 5.09k sats paid out to winners, but only one loser of 39 sats? Still trying to figure out the user interface, but shouldn’t the amount won equal the amount lost (minus fees)?

So the initial liquidity is essentially just the market creator placing an initial bet, on both sides (or all options for a multiple outcome market) at the initial odds they are setting for each outcome. So for a binary market, lets assume the creator sets the odds at 80% for yes and 20% for no. The maximum loss would be if someone bought up all of the "no" shares and won (the outcome was "no"), and nobody bought any of the "yes" shares, the creator would would effectively have just lost their "yes" bet, and be out ~80% of the initial liquidity. Is that correct?

So when the creator of the market is setting the fees (sell fee, buy fee, win fee) those go to the creator of the market and no fees on top go to Predyx? So Predyx's cut comes from the initial liquidity depending on the outcome? Is Predyx getting the losing side of the market's initial liquidity, and my hope would be I make that back in the fees I set? Or am I misunderstanding? Thanks

What are Predyx’s fees on the user created markets?

Are there any plans to add a pay per use model that would let me just top up tokens with lightning rather than a monthly subscription? It could even have a cost of X tokens per day for data storage. Perhaps I would prune previous conversations more diligently to control storage costs there if that was a factor beyond actual computation.

I looked into the bridge but didn’t want to deal with configuring a reverse proxy. Would be great for everything to just work over nostr. I guess you’re saying use the bridge you’re already hosting, which as you pointed out isn’t any different than the trusted getalby addresses. The NWC credentials are nice for the family and friends to be able to plug into stacker news and other nostr apps for the funding source. A CLINK wrapper for that would be nice.

I would love to see more wallets adopt CLINK offers. The self hosted Alby wallet lets me share my node with family in a way that gives them each a unique lightning address that works in almost all lightning apps. The fact that all the addresses are @getalby.com lightning addresses is more centralized than I’d prefer, and it seems CLINK would fix that. However, at this point in the adoption cycle it makes sense to keep using Alby Hub for the more widely accepted lightning address and NWC support. I’ll keep checking in from time to time though and hope for more CLINK adoption. Keep up the awesome work.

First time seeing this. Thanks for sharing.

It feels more to me like it breaks the glass ceiling for those who have app ideas they wish existed so they could use, but not necessarily for those who want to make apps for the masses. If you want something for you and your friends to have access to, current tools are great for that. Once you want more than that, you’re still going to have an app full of issues that is challenging to scale. Not to mention a host of other issues. Depending on your jurisdiction, you may want some legal insulation to protect yourself personally from any proprietary code that may have gotten incorporated into your vibe coded app; something that would be less of an issue for a free app you share but more of an issue if you’re charging for it and it becomes popular.

Mullvad was the only service I had ever used bitcoin cash for since it allowed me to buy a few hours of a vpn at a time, especially when on chain bitcoin fees were high. I was hoping when mullvad’s lightning payments came out of beta they’d also allow for smaller time intervals, but it seems the minimum is still a month. Lnvpn.net used to have less than a day as well I believe. Seems altcoins through Mullvad is still the only way to get a vpn for an hour if needed. Missed opportunity.

Honorable mention for http://shakespeare.diy/ which has been very impressive so far for quickly generating simple web apps