We've added offer conditions to Magma so you can earn Bitcoin from nodes that will always be a good channel peer fit!
If you can't open channels to Tor-only nodes, you can now add a condition for "Sockets contains Clearnet"
This works great for automated Hydro orders!
#m=image%2Fjpeg&dim=1080x1163&blurhash=%7B55Xo.xuITRjR%24M%7BNFjtIkj%5B%25Mt7V%5BayV%5BRj%25XofIVWBoNays%3Bt7rjWBt4ofWTofWAWBx-ofM%7CayjvWUofofNVfks%3Bj%5Baij%5Ba%24WB%24%3BaeRifQbDj%5BfhofkQa%7Cafa%7Bf8j%5Bj%5Bf6I%2BWBogj%5BoMofjvay&x=22ac782d982a8335b13135288f4277fc2e9fd7cc9c7dcdf1f3012731463c6913
Demand for lightning channels has increased significantly and we need magma channel sellers!
We are currently processing 26 BTC of instantaneous liquidity demand through Hydro. For context, our marketplace has processed a total of 157 BTC in the past two years.
Start selling channels today!
A quick question to the nostr:npub19tcpurtt6xulhw0r6sc404j9jraj0h8me2lzs7z2tqewz7l0hpas59nlea folks. What is your stance on nodes that sell channels via Magma and then having their node down for extended periods of time without any info? It’s not like it is a charity and they are dong it for the “love of it”. I know that you are taking a cut from the sellers depending on their tier of subscription, and would want to see some level of protection for the buyer of the channel. So far I’ve lost two purchased channels prematurely due to the other side’s LND bug with reserve dipping, and one is MIA with no info how to contact the owner. NGL, really makes me not too favorable towards the whole Magma thing, seems you pay for nothing in return in many cases. 🐶🐾🤔
These are hard problems to control for, especially with limited information in a P2P network! Feedback is greatly appreciated, as always.
Our primary focus is growing the market and the lightning network. With additional demand for lightning channels, we should see higher quality providers emerge to reap the rewards of high quality service. Without demand growth, we'll focus to breaking down other barriers to participation in lightning. If cheaper, faster, global payments aren't enough of a reward, something else must be holding back participation.
Our core belief is that market forces will drive network improvements and we want our tools to support that to the maximum extent possible.
Where'd you get stuck?
Lightning Yield Opportunity!
We're watching the channel offers get bought up quickly and we need established node operators to create offers on Magma.
You set your price.
Current LINER Yield = 1.50% APY
(take-home rate after fees)
amboss.space/magma
Requires a restart of Thunderhub on occasion, still researching why!
Making a big change to your node?
📢
You can use an Announcement within Amboss to tell all your channel peers about downtime, maintenance, or even share some routing alpha!
The growth of lightning nodes is moderating, transitioning from rapid expansion to a more measured pace. This shift, coinciding with rising transaction fees that raise the cost of new connections, reflects a growing prudence in network expansion. Such cautious behavior underscores the value of our data analytics services in guiding strategic connection decisions in this evolving landscape.
#m=image%2Fjpeg&dim=1702x824&blurhash=Z03u4o_3uM_3%3Fv.7%5E%2Bu3-%3B0K%3D%7CGX%25M-Wx%5D%253%252ozy%3BK0%24%2Coz-C%2C%5BS%7D%24*xa9Z%25M%5E8%253xbxutROqt7&x=bc00c07c9c283029b200319382da26c4f92a5f830088b21059a29ea084cd16fb
Hydro has been automating liquidity for 42 nodes.
The system operates with simple management plans:
1) One Time Purchase
2) Recurring Liquidity (Think DCA)
3) Capacity Goal
4) Inbound Liquidity Goal (full auto)
nostr:npub19tcpurtt6xulhw0r6sc404j9jraj0h8me2lzs7z2tqewz7l0hpas59nlea I think you have conditional issues with Magma offers. 1sats.com will not allow the order claiming socket == tor, while my node socket != tor. FYI
Is it mixing up IPv6 with TOR? 🐶🐾🫡
We'll be adding CONTAINS which should allow much finer grain control!
Here's a bit of the origin story for nostr:npub19tcpurtt6xulhw0r6sc404j9jraj0h8me2lzs7z2tqewz7l0hpas59nlea
We provide payment operations solutions for the Bitcoin Lightning Network!
That's a good reminder!
Hydro ensures you have enough capacity to receive payments automatically. Set up a management plan to get started.
Magma helps you earn yield on your Bitcoin if you already operate a well-connected lightning node without sacrificing custody. Create an offer to start leasing lightning channels.
Happy to help test by sending you some sats for being an early adopter and giving feedback!
Payments made to the ghost address won't show up as a transaction; the balance just increases!
More visibility is coming to help document attempts and payments.
Any additional info you can provide here? This is the first we're hearing of an issue like this.
With custodial lightning wallets withdrawing from the US, lightning users are choosing self-custody and better UX with Ghost Addresses! 👻 ⚡
ghst.to
As I understand it, Amboss is only contacted by my node to get the preimage when it sees that the next hop it is supposed to forward a payment to is not a real node at all. Since all other transactions routed through my node will presumably involve real nodes that I have channels open to, my node will not reach out to Amboss for any other transactions it routes.
Of course, since Thunderhub is open source, you can go audit the ~40 lines of code they added to implement the service on the node's side of things: https://github.com/apotdevin/thunderhub/compare/v0.13.27...v0.13.28
If my understanding is correct, then they will be able to see the payments your node that are routed using your ghost address, but nothing else. Which would mean that it's still a massive improvement over using custodial Lightning, where ALL of your transaction information is exposed to the custodian, and they hold your keys, so they can rug you at any time. By contrast, Amboss only sees those payments I receive through the ghost address, NONE of my outgoing transactions, and most importantly does not hold my keys.
It's even more private and specific than what you described. Thunderhub will only contact Amboss when it sees a specific, hardcoded channel ID as the next hop.
So even though the destination pubkey is different for each ghost invoice, Thunderhub can be surgical about when to request the preimage to intercept a forwarded payment.
Success! 👻 ⚡