nostr:nprofile1qyg8wumn8ghj7vf5xqhxvdm69e5k7qgnwaehxw309askcem09e6hg7r09ehkuegqyz5ql398sc6wuf42hjkf2x6vl4a4dtsch27n83d0mnmta4kusr4azxeg5ka nostr:nprofile1qyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99uq3zamnwvaz7tmwdaehgu3wwa5kuef0qqsvfa085adgecmg84ffelcxx6zrn3ffu5jrc6cjtwng0zge3ptv43ckq3nc4 nostr:nprofile1qyxhwumn8ghj7e3h0ghxjme0qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qpql2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqta478g nostr:nprofile1qykhwumn8ghj7mrwv35hxcmn9ej82cmtv3h8xtn0wfnj7mn0wd68yun9d3shjtm22ejkv5tcdadqzxrhwden5te0wpexjanpw3jjuun9vshxwc3wdejhgqpqvvwdc3edn4e22062dcryft4eaxlpd0nmgmh8adacp5afzvvc40yqp4kua3 nostr:nprofile1qyw8wumn8ghj7cn4vd4k2apwvdhhyctrd3jjuum0vd5kzmp0qyv8wumn8ghj7emjda6hquewxpuxx6rpwshxxmmd9uqzqc3uxj2swdhkggvpz3afhn7kzxy4c84ddec6hy6nt922mrf4jecf0q3mad nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcprdmhxue69uhkummnw3ezuumpw3ehgunpd35kztnrdakj7qpqv3tgrwwsv7c6xckyhm5dmluc05jxd4yeqhpxew87chn0kua0tjzqvzw3k0 nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcprdmhxue69uhkummnw3ezuumpw3ehgunpd35kztnrdakj7qpq7t2g2h0nnf7mvxtxvm5ydxs85ycumhqgmj48gj35gdplln655yxqwly073 nostr:nprofile1qydhwumn8ghj7mn0wd68ytnnv968xarjv9kxjcfwvdhk6tcqyqsmz28p4er0rkrnuuyedld3gkf0w00lh70jcfhjxvk7wz07rfwv7fpk0z8
I’m truly sorry to hear about that 😓. , it is quite depressing to work hard for Robosats, and then hear about users losing money.
We have a couple of Github issue that are aimed at increasing safety for sellers.
https://github.com/RoboSats/robosats/issues/2113
https://github.com/RoboSats/robosats/issues/2138
One of them is about introducing a Nostr-based reputation system without losing privacy (with some caveats).
Koala is already doing a great job integrating NOSTR in many aspect of the platform (the orderbook, the coordinator rating and soon the whole chat are on NOSTR).
Ideally we can leverage NOSTR also to improve safety, even though the implementation would not be simple and straightforward.
If you have thoughts, questions, or suggestions or feedback on the issues we’d love to hear them!
Let’s work together to make this better. 💪
Having some trouble accessing RoboSats via Tor. Is there an updated link? Using this currently:
http://robosatsy56bwqn56qyadmcxkx767hnabg4mihxlmgyt6if5gnuxvzad.onion/
#asknostr nostr:npub1wsqpvgpfwq6a4fs5whqxn7gtd9gqsll2p5qnfdu4ltr43s6wwxgsgk4xtl
Yes, it seems that main frontend is down. The good news is that you can use any link listed here (and also any self hosted version including android app) isrobosatsdown.templeofsats.org/
Temple Of Sats coordinator is now running on Bitcoin Knots.

I was on the fence about this, but seeing the announcement of a fellow node operator brings me closer to make the decision.
Sure, I just answered you 🙂
Routing budget is covered by buyer. Invoice amount already account for it. Keep in mind that 1000 ppm is 0.1 %
If you use something like Alby hub, it will not accept it at default settings, because their routing hint with megalithic node take more than the default 1000 ppm routing budget.
Other self custodial wallets have similar issues.
In such cases, you can simply press advanced and increase the routing budget from 1000 to 2000+ ppm .
Try to go into settings , and select API instead of NOSTR
Click on advanced and set a higher ppm.
It fails on defaults because Alby with megalithic node as LSP "sucks" more than the default Robosats routing budget of 1000 ppm.
https://isrobosatsdown.templeofsats.org
You can connect at any onion link, main frontend is down
Main frontend is down, but you can keep using any of the onion link here : https://isrobosatsdown.templeofsats.org
... Or any self hosted frontend!
Main frontend is down, but you can keep using any of the onion link here : https://isrobosatsdown.templeofsats.org

We crossed 100 coins of volume 🙌
Which areas of the interface you think should be improved?
Sorry nostr:nprofile1qqsxg45ph8gx0vdrvtzta6xal7v86frx6jvstsnvhrlvtehmwwh4epqpzamhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0v4jx2m3wdehhxarj9ekxzmny9ua2vh28, I was not clear. The issue is not payment failure. When the client waits for buyer invoice, it does not accept the invoice when it gets pasted from alby. So the channel capacity should not matter.
nostr:nprofile1qqsg900w2ph8d84ujnhz7d3dqlqevrwwgzavv5xcy6jzlrsvqxwre9spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qghwaehxw309a3xjarrda5kuetj9eek7cmfv9kz7c0wfau do you remember if there was a particular error popping up?
nostr:npub1v3tgrwwsv7c6xckyhm5dmluc05jxd4yeqhpxew87chn0kua0tjzqc6yvjh
regarding this post, several user reported issues on posting alby hub invoice as payout method in robosats.
I guess alby changed the stucture of their invoice and it does not play well with robosats now.
if needed , i can share a sample of alby hub invoice!
Thanks!! Should nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpypmhxue69uhkummnw3ez6un9d3shjtnvdekkzuntv468xtnrdakj7qpqwsqpvgpfwq6a4fs5whqxn7gtd9gqsll2p5qnfdu4ltr43s6wwxgsgymdaz updates the "Robosats Federation status web page" ??: https://isrobosatsdown.templeofsats.org/status/robodex
Yes! Will do by tomorrow 😉
they do! Koala made an impressive job on that. Make sure to upgrade to the latest version of the app 😉
For SimpleX I have created this one:
https://github.com/lft3t8bx/Robosats-Orderbook-Alert-Bot-for-SimpleX-Chat
But it is not for trade notifications.
I think nostr:npub1v3tgrwwsv7c6xckyhm5dmluc05jxd4yeqhpxew87chn0kua0tjzqc6yvjh is working for NOSTR notifications.
Right now If you use the android app, there are inbuilt notifications over tor, this is probably the safest approach we have right now.
To avoid the issue above, one can activate telegram notifications so that you are informed at all time about the status of the order without stressing too much with tor browser 😉
Thanks for your message 😉
Oh yeah, I did an hardware migration yesterday, and totally forgot to start the bot!
Now it is up, thanks!

