Thread

Holy shit it's working! Paid a 100k sats Lightning invoice from two different Cashu mints at the same time. Enter atomic multinut payments. All Cashu wallets let you use multiple mints. To reduce rug risk, we encourage users to leave only small amounts on each mint. This introduces a big UX challenge which forces users to distribute funds on different mints in a smart way. It's particularly problematic when you're trying to pay a bigger Lightning invoice from your small balances. Who has time for that? The Lightning protocol allows nodes to split a single payment HTLC into multiple parts to increase the chance of reaching the destination, called Multi-Path Payments (MPP). Typically, that's done from one sender to one receiver. What if... you can just break the rules? A multinut payment originates from multiple Lightning nodes to pay a single invoice, atomically. Even if none of your mint balances can cover an invoice, as long as your total balance is large enough, you can pay the invoice. I don't think anyone was crazy enough to do this before. Pretty sure what you see here is the first invoice being paid using a CLN and an LND node at the same time. Amazing work by the team, special thanks to @x.

Replies (68)

Spicing it up:
calle's avatar calle
Holy shit it's working! Paid a 100k sats Lightning invoice from two different Cashu mints at the same time. Enter atomic multinut payments. All Cashu wallets let you use multiple mints. To reduce rug risk, we encourage users to leave only small amounts on each mint. This introduces a big UX challenge which forces users to distribute funds on different mints in a smart way. It's particularly problematic when you're trying to pay a bigger Lightning invoice from your small balances. Who has time for that? The Lightning protocol allows nodes to split a single payment HTLC into multiple parts to increase the chance of reaching the destination, called Multi-Path Payments (MPP). Typically, that's done from one sender to one receiver. What if... you can just break the rules? A multinut payment originates from multiple Lightning nodes to pay a single invoice, atomically. Even if none of your mint balances can cover an invoice, as long as your total balance is large enough, you can pay the invoice. I don't think anyone was crazy enough to do this before. Pretty sure what you see here is the first invoice being paid using a CLN and an LND node at the same time. Amazing work by the team, special thanks to @x.
View quoted note →
This is huge and completely redefines the landscape on Cashu v fedimint All your eggs spread across many baskets that can be used in concert, or all your eggs in one big basket protected by multiple entities? In Cash, one mint rugging means you lose all that is on this mint, but only that. On Fedimint you lose nothing until a majority of guardians rug, in which case in you lose everything. Now that both approaches achieve the same level of practicality, the determing factor is your threat model. And that's great πŸ”₯
calle's avatar calle
Holy shit it's working! Paid a 100k sats Lightning invoice from two different Cashu mints at the same time. Enter atomic multinut payments. All Cashu wallets let you use multiple mints. To reduce rug risk, we encourage users to leave only small amounts on each mint. This introduces a big UX challenge which forces users to distribute funds on different mints in a smart way. It's particularly problematic when you're trying to pay a bigger Lightning invoice from your small balances. Who has time for that? The Lightning protocol allows nodes to split a single payment HTLC into multiple parts to increase the chance of reaching the destination, called Multi-Path Payments (MPP). Typically, that's done from one sender to one receiver. What if... you can just break the rules? A multinut payment originates from multiple Lightning nodes to pay a single invoice, atomically. Even if none of your mint balances can cover an invoice, as long as your total balance is large enough, you can pay the invoice. I don't think anyone was crazy enough to do this before. Pretty sure what you see here is the first invoice being paid using a CLN and an LND node at the same time. Amazing work by the team, special thanks to @x.
View quoted note →
Earlier this year, I fell victim to a devastating cryptocurrency scam that cost me $79,000 worth of Dogecoin (DOGE). I met a scammer through a Telegram investment groupβ€”a woman named β€œClara” who posed as an experienced crypto broker. She shared impressive-looking client testimonials and promised a 35% return in just seven days. Her website looked professional, and despite my initial doubts, I eventually transferred 500,000 DOGE, worth about $79,000 at the time. For the first week, everything looked fineβ€”the trading platform showed my balance growing steadily. But when I tried to withdraw my funds, I was told I needed to pay a $12,000 β€œwithdrawal fee.” Clara reassured me this was standard and fully refundable, so I paid it. Unfortunately, that was just the beginning. More unexpected charges followed: a tax clearance fee, a network fee, a security deposit. Before I knew it, I had lost an additional $8,000. I was crushedβ€”emotionally and financially. My savings were gone, and I blamed myself for ignoring the red flags. A friend eventually suggested I reach out to JBEE SPY TEAM RECOVERY, a company known for helping scam victims recover stolen cryptocurrency. Although I was skeptical, I was also desperate. I contacted them and provided every detail I could: wallet addresses, transaction history, chat logsβ€”everything. Their team got to work right away. Using advanced blockchain tracking techniques, they traced the stolen DOGE, identified the scammer’s wallet, and worked with relevant authorities to freeze the funds before they were moved any further. Throughout the process, they kept me informed and reassured. After days of relentles s effort, JBEE SYP TEAM RECOVERY successfully recovered the majority of my stolen Dogecoin. Their professionalism, expertise, and transparency turned what felt like a hopeless situation into a story of redemption. If you’ve been a victim of crypto fraud, I highly recommend contacting them: Email conleyjbeespy606@gmail.com Telegram +44 7456 058620 you can also contact on instagram
↩ replying to npub1h5e0...f2e2
Sure, ecash was meant to be used in small payments or for small amounts usually to be used without fees at the sacrifice of you needing a custodial for your balance (the mint) thus it is recommended to have small balances on these mints. Lighting on itself was meant to be non-custodial therefore incentivizing a higher capacity for sats on it, it has small fees, but comes with the headache of managing and rebalancing channels. So what its shown here is that if you have balance split among multiple mints, you can use this balance from them to pay a single invoice in lightning, thus reducing the risk of being rugged by the total amount by a single mint custodian, and not having to manage a lighting node to make big and fast payments.
THIS IS AWESOME. THINK I'LL DUMP NO MORE (OR LESS) THAN 58,000 SATS INTO ANY GIVEN MINT.
calle's avatar calle
Holy shit it's working! Paid a 100k sats Lightning invoice from two different Cashu mints at the same time. Enter atomic multinut payments. All Cashu wallets let you use multiple mints. To reduce rug risk, we encourage users to leave only small amounts on each mint. This introduces a big UX challenge which forces users to distribute funds on different mints in a smart way. It's particularly problematic when you're trying to pay a bigger Lightning invoice from your small balances. Who has time for that? The Lightning protocol allows nodes to split a single payment HTLC into multiple parts to increase the chance of reaching the destination, called Multi-Path Payments (MPP). Typically, that's done from one sender to one receiver. What if... you can just break the rules? A multinut payment originates from multiple Lightning nodes to pay a single invoice, atomically. Even if none of your mint balances can cover an invoice, as long as your total balance is large enough, you can pay the invoice. I don't think anyone was crazy enough to do this before. Pretty sure what you see here is the first invoice being paid using a CLN and an LND node at the same time. Amazing work by the team, special thanks to @x.
View quoted note →
=============================== #7 ⚑ Most Zapped Last Week =============================== Nostr’s Value4Value (V4V) model is all about plebs directly rewarding creators for the value they receive, no middlemen fees, no ads, just pure community-driven support using sats via the Bitcoin Lightning Network. Thanks to
ZAPLIFE.LOL
A decentralized Craigslist running on Nostr
 by @PABLOF7z for providing this data. Here are the top zapped posts from last week, showcasing creators who received the most engagement: πŸ”₯ Top 3: Most Zaps 1. Zaps Received: 132 Sats Earned: 51k View quoted note β†’ 2. Zaps Received: 100 Sats Earned: 13k View quoted note β†’ 3. Zaps Received: 49 Sats Earned: 7k View quoted note β†’ πŸ’° Top 3: Most Sats 1. Sats Earned: 441k Zaps Received: 192 View quoted note β†’ 2. Sats Earned: 200k Zaps Received: 12 View quoted note β†’ 3. Sats Earned: 51k Zaps Received: 132 View quoted note β†’ #most-zapped_nostr_recap
This is the most popular post on Nostr this past week. Bullish.
calle's avatar calle
Holy shit it's working! Paid a 100k sats Lightning invoice from two different Cashu mints at the same time. Enter atomic multinut payments. All Cashu wallets let you use multiple mints. To reduce rug risk, we encourage users to leave only small amounts on each mint. This introduces a big UX challenge which forces users to distribute funds on different mints in a smart way. It's particularly problematic when you're trying to pay a bigger Lightning invoice from your small balances. Who has time for that? The Lightning protocol allows nodes to split a single payment HTLC into multiple parts to increase the chance of reaching the destination, called Multi-Path Payments (MPP). Typically, that's done from one sender to one receiver. What if... you can just break the rules? A multinut payment originates from multiple Lightning nodes to pay a single invoice, atomically. Even if none of your mint balances can cover an invoice, as long as your total balance is large enough, you can pay the invoice. I don't think anyone was crazy enough to do this before. Pretty sure what you see here is the first invoice being paid using a CLN and an LND node at the same time. Amazing work by the team, special thanks to @x.
View quoted note →