yeah, it sucks that hardware is just so extremely hard.
I admire them for doing it and always feel like I need to support them and such projects more in those efforts by buying the products. - so high5 that you did it!
did you try other similar projects?
whatever you are comfortable with using.
here the goal was to use the coinos wallet with the alby account.
you can also check the alby extension that would work the, too
It didn't connect to nostr:nprofile1qqst4qyeqenw7zm0fwjsty68h6cnys5jre2xd8ngqpjv5a2j26s78fspzdmhxue69uhhqatjwpkx2urpvuhx2ue0fjzwm2 either
nostr:npub1h2qfjpnxau9k7ja9qkf50043xfpfy8j5v60xsqryef64y44puwnq28w8ch do you plan to implement the other NWC functions, too?
no, nothing is required. it's a standalone app that has everything it needs. resource usage is also very limited (it loads the blockchain data through a block explorer API)
True. hmm, that spec needs to be updated there. because if more than one is provided then it should be an array imo relay[]=xxx&relay[]=yyy
otherwise different parsers interpret it differently.
At the same time multiple relays add some complexity for apps and wallets. so far all NWCs used one relay afaik.
I personally doubt that relays for NWC are the weak link in the chain and need redundancy that the event is published to multiple ones.
Also considering privacy and that those are no "normal" events.
Do you know why nostr.mom seems to not work for NWC events?
nostr:npub1h2qfjpnxau9k7ja9qkf50043xfpfy8j5v60xsqryef64y44puwnq28w8ch does not support all NWC functions, yet. So far only sending and loading the balance I think.
Is open hardware becoming more important?
like https://mntre.com
I'm waiting for nostr:nprofile1qqsrxra3gv0lnkxz2pcxh0xuq9k4f9dr7azwq3aypqtnay4w0mjzmtqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzamhxue69uhkzarvv9ejumn0wd68ytnvv9hxgtcpzfmhxue69uhhqatjwpkx2urpvuhx2ucunm6wg to debug the code so I can connect my nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcprdmhxue69uhkummnw3ez6vfwde3x7tnpdenkzmnf9e3k75xqss4 account to an NWC compatible wallet like nostr:nprofile1qqst4qyeqenw7zm0fwjsty68h6cnys5jre2xd8ngqpjv5a2j26s78fspzdmhxue69uhhqatjwpkx2urpvuhx2ue0fjzwm2
I've debugged this and there seems to be an issue with the nostr:npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv NWC URL.
Minibits adds multiple relays (e.g. relay=wss://relay.minibits.cash&relay=wss://relay.primal.net&relay=wss://relay.damus.io&relay=wss://nostr.mom ) This is not as the spec describes it and I think also different client implementation interpret this differently.
Our implementation here uses the last relay and this one seems to not respond to a NWC request.
nostr:npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv I recommend to only use one relay now.
(We as Alby also operate a NWC optimized relay that we offer.)
why did I not know about it? hmmm.
should we get better at non-digital far distance, mass-communication somehow? or what can we learn?
do you want to help and try Alby Hub there?
Not exactly. Phoenix Wallet app on mobile, can be restored with only your seed phrase. ACINQ keeps a copy of your channel state for you and this is how you can go back as usual even if you delete your app or lose your phone.
For "Alby with Phoenixd" on the other hand you can't have your seed easily shown to back it up some reason. So you have to command line into the Phoenixd files of the Ulbrel to find the .dat seed file.
I did it, and then tried to restore from seed in the "Albyhub with Phoenixd" app, to see if like for Phoenix Wallet , my funds will magically be back thanks to ACINQ backend.
But not only did I lose my 14 SATs left and my channel, but the node which was set up was a different one, with another pubkey so it's kind of shady how it works for me...
If nostr:nprofile1qqsrxra3gv0lnkxz2pcxh0xuq9k4f9dr7azwq3aypqtnay4w0mjzmtqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzamhxue69uhkzarvv9ejumn0wd68ytnvv9hxgtcpzfmhxue69uhhqatjwpkx2urpvuhx2ucunm6wg can once again enlighten me it would be nice 🙂
when you use phoenixd then you need to refer to how phoenixd works: https://phoenix.acinq.co/
phoenixd writes some data that contains the seed and channel data.
Alby Hub is just using the phoneixd API - it can not know anything about the seed or similar. That's the same when you use LND.
In those cases Alby Hub just does API calls to those services.
I think Phoenixd is a bit different to the phoneix mobile app but I don't know the details. You best need to talk to ACINQ and their support for more clarity.
We have some scripts to install phoneixd but for support and details about phoenixd one has to talk to acinq.
please let us know how you like the experience.
I opened a channel and added my wife on friends & family then we both installed Alby Go. I see our combined sats on my Alby Go, I only want to see my sats on Go not ours combined. On hub combined is fine, but not in my personal wallet. — This is a comment on: https://yakihonne.com/flash-news/nevent1qqsfm8nzuf9hj4jpstuyg8fasd09jgjmrnaph3yqt6zruhnwnluh2fqzyqeslv2rrlua3sjswp4mehqpd42ftglhgnsy0fqgzulf9tn7usk6cqcyqqqqqqgtgxhv6
then use also an isolated connection for you in your Alby Go.
Anyone using CasaOS here?
what kind of issues? it should happen automatically
great, thanks.
we open up further soon and we are constantly sending out waitlist invites.
if you have an account you can also invite your friends directly.
nostr:nprofile1qqsrxra3gv0lnkxz2pcxh0xuq9k4f9dr7azwq3aypqtnay4w0mjzmtqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzamhxue69uhkzarvv9ejumn0wd68ytnvv9hxgtcpzfmhxue69uhhqatjwpkx2urpvuhx2ucunm6wg does Alby accept Tor connections in the NWC service? Do you offer a .onion address? We could have a setting for NWC after this.
I am not sure how Tor comes in here. The relay accepts Tor connections. The Hub itself does not have any Tor built in. So we can’t connect to other Tor only lightning nodes currently and if somebody wants to run the hub interface behind Tor then it would need to be separately configured as a hidden service.
But I think only the relay is typically relevant, isn’t it?
where? in the extension? maybe just change the names there in the settings?
I side loaded it onto my nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll and I have had to restart it 3 times now
did start9 stop the app? did start9 restart?
I have absolutely no idea.
Usually this file is made available easily in these kind of apps for noobs (that I am btw) directly in the settings with some kinds of warning or something.
Here I have nothing, this is why I try to understand how it works before using it more extensively.
I asked nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x in an other note to explain it, hope he will see it.
this is up to phoenixd and phoenixd only writes that files to disk. the user needs to backup those files.
we can also not make those available in the albyhub UI as phoenixd does not expose it. (same as it is in LND)
if you want a more simple setup then use only albyhub with the embedded node.