Phone: Amethyst
PC:
- articles: habla.news / yonnle
- rest: coracle / primal / nostrudel
You don't have the enough memory to remember the Linux commands
Public-Pool now has a Windows desktop application for self hosting!
If you'd like to help me test this, download the installer and check out the README.
https://github.com/benjamin-wilson/public-pool-app/releases/tag/1.0.0
All you need is your own bitcoin node.
MacOS and Linux distributions will come later.
**mempoolfullrbf=1** is a mining optimization? 🤨
For Linux 🐧 lovers 👇
PD: Ride With GPS allows to you an easy-to-trace the route automatically following the OSM Bicycle map version only pointing the start-finish points on the map
Tip:
1. Design your new track using Ride With GPS web version
2. Export .gpx file and import it to Wikiloc using web version
3. Follow the route with a lot of features using Wikiloc app version
All using the free plans
Enjoy it!
Congrats! Sometimes it is difficult to find a way out of traffic depending on the location, I recommend to you to use **Ride With GPS** app to create a new route, It give yoy the percentage of paved and unpaved terrain that you will find. Good luck!
It's a bit difficult, I think each client uses a different NIP/kind events... 😕
i.e satellite.earth and Amethyst uses the same, but habla.news and Coracle uses another different for communities... 🤷
For the moment, try searching MiniBolt on "Groups" section using coracle.social
On satellite.earth and Amethyst (communities) it appears don't detect the posts, very confused.. The newly Nostr protocol 😅
Dear followers, sorry for the spam 🙏, I included the previous posts related to MiniBolt in the MiniBolt Nostr community and they will appear to you as new bulk posts 🫣
Do you plan to include Bisq v2.x?
Ok, I think that I found it:
⚡We've added Lightning invoice decoder to Amboss Space!
Invoice decoders deliver insights about payment requests that can come in the form of an invoice, an LNURL, or a Lightning Address.
To demonstrate the insights you can derive, we've prepared a thread of wallet invoices!
Starting simple, here an invoice from BitcoinJungleCR, a custodial lightning wallet:
Similar setups include: zbd, walletofsatoshi , and Strike
This is a BOLT11 invoice where it pays to a single node destination. Routing Node Operators will use the Payee Pubkey information to discover new nodes to connect to so that the network can have a variety of routes to pay BTC Jungle CR reliably.
https://amboss.space/node/03797da684da0b6de8a813f9d7ebb0412c5d7504619b3fa5255861b991a7f86960
Next up in complexity, a BOLT11 invoice from @Breez_Tech, a self-custodial lightning wallet:
If you check the Payee Pubkey of the Breez invoice, you'll reach a page that says "Unable to find this node". This isn't a error; this reveals that @Breez_Tech is using "private" node destinations.
To help the lightning payment reach the destination, it will require Route Hints!
In the Routing Info is a Pubkey, revealing a well-connected 28 BTC capacity node that will convey the payment to the "private" node destination.
Services with similar setups include: MuunWallet (uses a swap service), ElectrumWallet (yes they do lightning!)
"Private node" here only means unannounced to the network (like not listed in the phone book), not a guarantee of privacy.
There are many reasons to use private nodes in practice and most of them are operational: load balancing, payment reliability, failover protection, etc.
Even more complex, we have @CashApp invoices, which include 2 separate paths to reach a private node destination. https://amboss.space/lightning-decoder?request=lnbc1pnxrdk6dqdgdshx6pqg9c8qpp59d8cvaf5209myfkn9wk67ywa5exyt230gjpkjs7dh0yxzczaqk4ssp5e8e6wehwurw4zdfs6lkj5s9my702vpxjs26zfyv3vmrw00x64k0q9qrsgqcqpcxqy8ayqrzjqv06k0m23t593pngl0jt7n9wznp64fqngvctz7vts8nq4tukvtljqz3rvvqq88sqqsqqqqqqqqqqqqqq9grzjqtsjy9p55gdceevp36fvdmrkxqvzfhy8ak2tgc5zgtjtra9xlaz97pmylyqqt0gqquqqqqqqqqqqqqqq9gwmef3kht3jvnnft2yqagtdr6qsp0mw00mcs334wmjakjxf7m0suy3dm0cjcr9vd03c500225tf4suxu9ufrsqrl2p3k748ctvlygm3cpcr888n
Instead of only one potential path to pay, there are now two which can be attempted. This allows one of the public nodes to undergo maintenance while the other remains online to ensure higher payment reliability.
Makes sense when you have 50 million potential users!
Okay now it gets crazy complex: @fedibtc Bravo includes not only two separate routing paths, but there are multiple hops in the second path!
Look how long the invoice string is! That is a lot of data to pack into an invoice, which can also make the invoices more difficult to scan as QR codes or be unable to fit into a tweet!
Setups like this one are fascinating, but each decision is a tradeoff.
In the 2-hop path, the first stop is @LQWDTech followed by "Henwen 🐷", which was also used in the 1-hop path.
This must make Henwen one of the "Gateways" into the ecash Federation.
https://amboss.space/node/0364913d18a19c671bb36dd04d6ad5be0fe8f2894314c36a9db3f03c2d414907e1
https://amboss.space/node/02f0c7b731ca40a285d7c12aa1c5c7c7caa4598d3d6d34904c3714cd0d47852640
Mind blower time. Let's talk about @AquaBitcoin invoices.
Aqua invoices only include a single route hint, but the route hint is to a private node!
The payee pubkey is a public node, @Boltzhq, which swaps between the @lightning network and @Liquid_BTC.
Boltz is using "magic routing hints" allowing Liquid to Liquid payments within LN.
https://docs.boltz.exchange/v/api/magic-routing-hints
We hope you learned a lot from this thread!
What else would you like to know about invoices?
What other insights can you gain from this tool?
Very useful, thanks, but I think this should be in a separate and dedicated tool section and be able to link it and save on browser bookmarks
Ubuntu server o Ubuntu desktop? misma pregunta para Debian, con interfaz o sin interfaz gráfica?
De que se trata exactamente?
One more time...
I don't know if it could be the cause, but please, add the POW defense to your Tor hidden service conf ASAP
👇
HiddenServicePoWDefensesEnabled 1
Is not they apply the POW defense maybe?