02d769cb73

bitcoin

There has been a lot of debate about a [recent discussion](https://groups.google.com/g/bitcoindev/c/d6ZO7gXGYbQ) on the mailing list and a [pull request](https://github.com/bitcoin/bitcoin/pull/32359) on the Bitcoin Core repository. The main two points are about whether a [mempool policy](https://bitcoin.stackexchange.com/q/120269/5406) regarding OP_RETURN outputs should be changed, and whether there should be a configuration option for node operators to set their own limit. There has been some controversy about the background and context of these topics and people are looking for more information.
Please ask short (preferably one sentence) questions as top comments in this topic. @Murch, and maybe others, will try to answer them in a couple sentences. @Murch and myself have collected a few questions that we have seen being asked to start us off, but please add more as you see fit.

Quick questions about OP_RETURN? Quick answers here.

tidwell

BooksAndArticles

Why tether moved their HQ to ES right before Trump inauguration?
This is a whole new rabbit hole...

El Salvador's Gulag Cryptopelago

DarthCoin

bitcoin_beginners

If you do not want to read all the rest here is my TLDR answer: because most of them are just noobs (without good knowledge of networking), followers of influencers promoting Tor only nodes and believe that Tor is the magic wand that fix everything. IT IS NOT. Tor is a false illusion of "privacy" for BTC LN nodes and is useless.

---

Ok now let's get into this question. With this post I want to make more noobs to think about and take the right decisions.

### Why most of bitcoiners run a Tor only BTC LN node ?

Because most of them are using bundle nodes boxes (Umbrel, Start9, Raspiblitz, MyNode etc) that mainly are by default Tor connected to the rest of the internet.
Why they use Tor?
Because is damn easier plug'n'play for a noob that doesn't know what is LAN, WAN, ports, IP, domain, FQDN, HTTP(S), packets, encryption etc you name it... Tor is making their life easier, without having to configure routers, ports, IPs etc. And the influencers are "selling" the idea that "run Tor nodes for your privacy" but not explaining what really is privacy.

Let's say it clearly: INTERNET IS A PUBLIC PLACE ! So if you do not want to expose your private activity, then DON'T DO IT ON INTERNET. Anything you do on internet became PUBLIC.

People nowadays cannot make the difference between PRIVATE and PUBLIC but they still demand privacy in a public place LOL. Is like walking naked on the street and you demand to people not to look at you because is private.

### Is it Tor such an ultimate "privacy tool" ?

>The fundamental question becomes: How can conscientious individuals maintain their privacy online? If absolute privacy—complete evasion of government data collection—is the goal, then the internet is simply not suitable. While it may be possible to protect information from hackers and corporations, completely avoiding surveillance by large governments is essentially impossible.

Source - [Tor and the Illusion of Anonymity](https://johnwlittle.com/tor-and-the-illusion-of-anonymity/) - by John Little

As I said before: if you do not want to reveal private parts of your activity, don't do it online! Or at least do it under a pseudonym, another false identity, hide into the crowd that cannot identify or link the REAL you.

Despite its benefits, Tor is not a foolproof solution for online privacy. Here are some reasons why:

1. Exit Node Vulnerability
The data leaving the Tor network through the exit node is decrypted. If the exit node is malicious or monitored, your traffic can be intercepted and analyzed. While your IP address remains hidden, sensitive information like login credentials or personal data could be exposed if the website you’re visiting doesn’t use HTTPS.

2. End-to-End Tracking
While Tor hides your IP address, it doesn’t encrypt the data you send to or receive from websites. If you log into a personal account or share identifiable information, your anonymity could be compromised.

3. Browser Fingerprinting
Tor Browser’s settings are designed to minimize browser fingerprinting, a technique used to identify users based on their browser and device configurations. However, if you modify Tor’s default settings or install additional plugins, you increase your risk of being identified.

4. Correlation Attacks
Advanced attackers, such as nation-states, can use timing correlation attacks to de-anonymize Tor users. By monitoring entry and exit nodes, they can potentially link your activities to your IP address.

5. Malware and Phishing
Tor doesn’t protect you from malware, phishing, or malicious websites. Clicking on harmful links or downloading infected files can still compromise your privacy and security.

6. Adding more time to response
Speed is crucial for BTC LN nodes. Maybe for a BTC only node (not LN) it is OK to sync every 10 min a block, is not a big deal. But for a PUBLIC ROUTING LN node it is crucial to have fastest response. And Tor network is adding huge delays ! That makes your LN node UNRELIABLE FOR ROUTING.

NOTE: we are talking about PUBLIC LN nodes here, not PRIVATE (those that are not doing public routing and are not 24/7 online).

So using a public routing node only behind Tor is totally useless and against the most important thing: routing. You are literally doing more harm than good to the entire Lightning Network because your node will be a bottleneck for all those trying to pass through your shity node a payment.
If you are already a public node, is already known information, so is useless to think you are hiding behind a Tor onion address...

If you really want to not reveal your IP from where your LN ndoe is operating, use a VPN IP, with a Wireguard tunnel towards your LN node machine. That will add a faster route to your node and also full control of the traffic.

You rent a VPS, that is a simple virtual machine in a datacenter. You install your own software OS and Wireguard tunnel. So chances that somebody else is watching your traffic are almost null.
On the other side, using Tor, ask yourself: are you really in full control of the exit nodes? Do you really know who is on the other side of the Tor network that will have to decrypt your traffic in order to forward it to the destination?

---

Another aspect I do not understand from many users: OK they run a Tor only n ode because they run a bundle node software that do not offer a clearnet connection and they are not technically capable to build their own infrastructure with independent software.
The question is: why then use for example to connect over Tor with your own LN node? ARE YOU NOT TRUSTING YOURSELF?
Why do you not use a Tailscale connection, that is a private VPN tunnel, over a private IP (not public IPs).
[I've explained in more details in this guide what is a Tailscale network.](https://darth-coin.github.io/nodes/tailscale-vpn-your-node-en.html). It's damn easy to setup and use, even for not so knowledgeable users and offer enough security and privacy when is about to connect remotely to your Tor boxes. Or even https://holesail.io/

---
If you really want to run a public routing node, then start by learning a lot about networking, security, servers, VPS, VPN, traffic routing etc.

I wrote more guides about these aspects and I invite you all to read them and think more about when is time to run a LN node over Tor:
- https://darth-coin.github.io/nodes/recommendations-ln-node-operators-en.html
- https://darth-coin.github.io/nodes/lightning-node-maintenance-en.html
- https://darth-coin.github.io/nodes/private-ln-nodes-en.html
- https://darth-coin.github.io/nodes/public-private-node-liquidity-scenario-en.html
- https://darth-coin.github.io/merchants/operating-ln-as-merchant-en.html
- https://darth-coin.github.io/wallets/bitcoin-and-privacy-en.html

And here are some very good step-by-step guides about how to run a LN node behind a VPS tunnel, @Hakuna wrote these excellent guides:
- https://github.com/TrezorHannes/Dual-LND-Wireguard-VPS
- https://github.com/TrezorHannes/Dual-LND-Hybrid-VPS

There are even more guides out there about how to configure a wireguard tunnel. Read them all and adapt to your needs. But remember: Tor is not a reliable solution for your LN node !

Why bitcoiners are so "in love" using Tor for their BTC LN nodes?

bitdevs

> Sender can find recipient’s UTXO(s) in payjoin without even broadcasting the final transaction. This attack is described in BIP 77 and 78 however often ignored by privacy advocates.
>
> In a normal bitcoin transaction, the recipient shares their address to receive bitcoin although payjoin requires more information. Recipient needs to share their signed UTXO with the sender to finalize the payjoin transaction. Hence, payjoin cannot be used with untrusted senders.

UTXO probing attack using payjoin

k00b

# Common-input-ownership heuristic  
(An intro to PayJoin)

![](https://m.stacker.news/84818)

---

Meet Alice, a new employee at a **chain analysis** firm


![](https://m.stacker.news/84819)


Her job?  
Track and analyze transactions on the Bitcoin network



Alice’s first onboarding session:   **"common-input heuristic"**

![](https://m.stacker.news/84820)

> All inputs of a given tx are assumed to be owned by the **same owner**

---

To explain it:

Let’s say Bob buys a coffee from Carol with 1 BTC

![](https://m.stacker.news/84821)

Looking at this Tx, it's clear that the outputs are:

- 1 BTC payment to Carol  
- 2 BTC change back to Bob

![](https://m.stacker.news/84822)


---

That’s how input correlation works —  
This is what surveillance companies use to violate your privacy

---

So here’s the question:

![](https://m.stacker.news/84823)

> What if we could break this heuristic…  
> but still make the tx look totally normal?

---

### PayJoin

**PayJoin** is one way to disrupt this heuristic, allowing a tx to be interpreted in various ways

So now, the same tx — but with PayJoin looks like this:

![](https://m.stacker.news/84825)

Can you tell who owns what now?
Yeah... pretty hard.

---



Follow [@Bitcoin_Devs](https://twitter.com/Bitcoin_Devs) for more technical bitcoin posts

![](https://m.stacker.news/84827)

An intro PayJoin: Common-input-ownership heuristic

bitcoin_devs

# CISA (Cross-Input Signature Aggregation) Explained

![CISA Overview](https://m.stacker.news/83885)

---

**CISA**  is a way to combine multiple signature from a transaction into one

![Signature Aggregation](https://m.stacker.news/83886)

This is made possible thanks to the **linearity** property of **Schnorr signatures**, which enables aggregation of multiple signatures into a single one.

Originally, CISA was considered for inclusion in **Taproot**, but the idea was abandoned to keep Taproot simple and manageable.

---

> ⚠️ Don’t confuse **CISA** with protocols like **MuSig** or **FROST**  
> **Signature aggregation ≠ Key aggregation**

---

## CISA vs Key Aggregation

### Difference #1: 

![CISA vs Key Aggregation](https://m.stacker.news/83882)

---

### Difference #2:

- **Key Aggregation**: The verifier only needs the aggregated public key and a single message.  
- **CISA**: The verifier needs all the individual public keys and their corresponding messages.

![Verifier Differences](https://m.stacker.news/83883)

---

### Difference #3:

- **CISA** is used during **transaction signing**  
- **MuSig** is used during **address creation**

---

There are two types of CISA: 

- **Half-Agg**
- **Full-Agg**

🧵 *We’ll explain them in upcoming posts.*

![Half-Agg vs Full-Agg](https://m.stacker.news/83884)


---

## More Resources

- [CISA Research](https://cisaresearch.org)  
- [HRF CISA Research Paper](https://hrf.org/latest/cisa-research-paper)  
- [Blockstream CISA GitHub](https://github.com/BlockstreamResearch/cross-input-aggregation)


CISA (Cross Input Signature Aggregation) explained

ideasfromtheedge

memetic warfare, that's what we are in. it has always been about population mind control. 

one can meme the other political party or a group out of existence, 
or meme it into existence.

they also steal each other's memes, play on words & symbols, make them more or less appealing to the unsuspecting normies, depending on the mission. 

be careful with ur memes, and let the strongest meme win!

The Cult Of Kek and Dark Meme Magic

zapsammy

gaming

On this site you find : PlayStation (Crash Bandicoot, Final Fantasy VII), N64 (Mario 64, Zelda Ocarina of Time), SEGA (Sonic, Streets of Rage), Nintendo (Super Mario Bros, Metroid), Atari, Arcade.....

![](https://m.stacker.news/82499)

![](https://m.stacker.news/82500)

![](https://m.stacker.news/82513)

The site uses WebAssembly based on RetroArch, allowing you to directly choose the machine, then a game that will launch in your browser within seconds. Enough to spend an entire evening chaining levels of Donkey Kong Country 2 and going to bed at 3 AM with hallucinations filled with flying bananas!

This translation describes a website that utilizes WebAssembly technology in conjunction with RetroArch to provide instant access to retro games directly in the browser. It specifically mentions Donkey Kong Country 2, a popular game for the Super Nintendo Entertainment System (SNES) that features Diddy Kong and Dixie Kong on a quest to rescue Donkey Kong from King K. Rool. The text humorously suggests that players might become so engrossed in the game that they play late into the night, experiencing surreal visions of flying bananas - a playful reference to the game's iconic collectible items.

As you will see, the interface is really pleasant, in my opinion, and you can play using the keyboard or, if you have an Xbox controller, simply plug it in and voilà, it will work too. For the more advanced users among you, note that pressing F1 gives you access to RetroArch's advanced options (filters, configurations, etc.). A practical little bonus: the site allows you to save your progress via 'save states,' so there's no need to start over every time you visit.

![](https://m.stacker.news/82512)

The service also works on smartphones via the Android app, with touch controls or the option to connect a Bluetooth controller. The only small drawback is that there are sometimes a few somewhat invasive ads, but well, that's the price to pay for so much free nostalgia.



GAM.ONL - Thousands of free retro games in your browser.

RideandSmile

privacy

I've read, time ago, this news: https://stacker.news/items/899338
But searching some thing more about this new policy I've found this important variation.
The source is here: [GitHub Pages](https://github.com/mozilla/bedrock/commit/d459addab846d8144b61939b7f4310eb80c5470e#diff-a24e74e4595fa85440a2f4e7e5dcfe68aba6e1e593aef05a2d35581a91423847L60)

And on row 62, previously you can read:
>"***We don’t sell access to your data. You’re in control over who sees your search and browsing history***"

but now, the new TOC contain this:
>"***You’re in control over who sees your search and browsing history***"

so, this important part: "***we don’t sell access to your data***" was removed.

For those who use ***librewolf*** it is better to read this discussion on [codeberg](https://codeberg.org/librewolf/issues/issues/2252#issuecomment-2886286)
The team does not agree to fork mozilla given the bad path they are taking, because the librewolf team is small, with little time available and apparently, not very skilled.



Again about Mozilla policy and some word about Librewolf

_Bubble_2009

lightning

### Underrated privacy tools on Lightning

We are seeing many critics about LN not being private, but mostly are coming from people that never dig deep into using LN at its fully potential, they are were just scratching the surface, using just a Phoenix wallet or  maybe another one.

Did you even hear about these terms?
- Wrapped invoice
- LN proxy ([web](https://lnproxy.org/) | [Github](https://github.com/lnproxy/lnproxy-relay))
- [0-conf channels](https://github.com/lightningnetwork/lnd/blob/master/docs/zero_conf_channels.md)
- just in time channels
- trusted channels
- [Zaplocker](https://github.com/supertestnet/zaplocker)
- [Lightning Box](https://github.com/hsjoberg/lightning-box)
- [Dunder LSP channels](https://github.com/hsjoberg/dunder-lsp)

>Glossary:
>*In this guide I will use different acronyms for Lightning Service Provider (LnSP) and Liquidity Service Provider (LiSP), to not have too much confusion between them. A LnSP can be also a LiSP.*

For all those node runners out there, if you want to became a good "uncle Jim" for friends and family or even for local merchants, be their local good LnSP helping them with more tools and services. This could be a real game changer and a good business around your LN node, charging (valuable) fees in sats. In the future not many people will be able to run proper public LN nodes and this is how you can help them. Helping them you help yourself (and not the banksters).

---

## Use case scenario A

Let's consider you are a small node runner, with a public (announced) LN node, for small routing, for your family and few friends. And you want to provide also some additional privacy layers for your own use of LN and for your family/friends.

So you run a public node, well connected, well maintained, with some good routes and good liquidity. Is even possible that you run it for a small shop or not, it doesn't really matter. This node could be just a "front-run node", a "public face decoy", viewed just as any routing node. Can be linked to a real identity or not, as you wish. Can be hosted at home on a Umbrel/Start9/Raspiblitz/MiniBolt/etc node machine or on a VPS with a public IP. It doesn't really matter, in the end is just a decoy node.

What "client wallets" you can use with this node  (I mean connected with some private (unannounced) channels, practically using it your own private LnSP - lightning service provider):
- Zeus LN with embedded LND node
- Blixt Wallet (mobile LND node)
- another simple private LND desktop node, can be a simple PC at home with a LND node in neutrino mode (no need for full BTC node) or a cheap VPS running LND in neutrino mode. This one you can manage it from Zeus as remote node.

These self-custodial nodes are the perfect way to use with multiple LnSP and manage your own liquidity as you wish adding more privacy.

### What "services" you can provide (as a LnSP) with your own public node for these "private clients" ?

#### 1 - Just-in-time channels
Your public node can open private channels towards these "private" mobile nodes, using wrapped invoices and 0-conf channels (not broadcast the onchain tx). Are the perfect way to onboard or start with a new mobile LN node, without requiring any funds in these mobile nodes.

***How does it work?***
- The receiver (mobile LN node) generates an invoices on their lightning node and then sends it to the LnSP (your public node)
- The LnSP creates a wrapped invoice and returns it to the receiver
- The receiver gives the wrapped invoices to sender (can be yourself from another LN wallet or somebody else) for them to pay
- The sender pays the invoice, which goes through the LSP
- The LnSP detects the payment and opens up a 0-conf, just in time, channel to the receiver
- The LnSP then forwards the payment to the receiver using that new channel and the payment is completed

You can see more options for this API in [bLIP-52](https://github.com/lightning/blips/blob/master/blip-0052.md) and [bLIP-51](https://github.com/lightning/blips/blob/master/blip-0051.md), that currently is used in [Zeus calls API](https://docs.zeusln.app/lsp/services/flow#calls).

***How to open JiT channels?***
- In Zeus follow [these instructions](https://docs.zeusln.app/for-users/embedded-node/trusted-funding).
- In Blixt follow [these instructions](https://github.com/blckbx/NodeTools/blob/main/private-trusted-zero-conf-channels.md).

#### 2 - Wrapped invoices
Wrapped invoices are invoices with extra layers around them. In this instance, the LnSP will wrap an invoice generated from your node. The wrapped invoice will appear as if it is generated by the nSP.

In the LSP node must be activated the API call for:
```
{
    "jit_bolt11": "lntb5..."    #Wrapped Bolt11 invoice which can be sent to the sender for payment
}
```

This has two benefits:
- The end user doesn't have to expose their node's public key to senders. The LSP knows the receiver but no one else does. 
- Senders can use routes to the LSP to make a payment instead of having to find a direct path to the end user.

Wrapped invoices uses the same preimage hash as the original invoice. This means that the LSP can't settle the payment without the final receiver completing the payment, so the LSP can't run away with the user's funds.

Be sure to keep ZEUS open when receiving payment as the LSP cannot settle payments on your behalf when you're offline.

#### 3 - Lightning Address Box / Server

This could be used as a decoy LN address, not using your own private domain for a public LN address (donations, zaps, tips, public payments etc). 

>*Sometimes you do not want to use a private domain linked to your real identity and your node in order to receive sats over LN. You can still use those private LN addresses with your own nodes in a more restricted use case (private business, family and friends payments etc) and not being necessary to publish them online. [I explained more about LN address types in this guide](https://darth-coin.github.io/beginner/getting-started-ln-address-en.html).*

Zeus is using Zaplocker method for its @zeuspay.com type of LN Addresses. Read more about it here: https://docs.zeusln.app/lightning-address/intro/. Zeus is using "on-hold invoices" for its LN Address and will forward the sats once your Zeus is online (redeem).

Blixt is using [Lightning Box](https://github.com/hsjoberg/lightning-box) method for its @blixtwallet.com type of LN Address. Blixt is not using "on-hold invoices", is just forwarding the payment to your Blixt mobile node, if is online, is acting only as a trusted LN Address server. If your Blixt node is not online the payment to your LN address will be rejected, so you must keep your Blixt on "persistent mode " in order to be able to receive through your LN address. Here is a demo video how to setup a LN address in Blixt: 

https://blixtwallet.github.io/assets/images/blixt-ln-box-setup.mp4

#### 4 - Private payments / no onchain fingerprint

Yes, you hear it well... NO TRACE on onchain txs. A "0-conf channel" is a not broadcast tx, a channel opened with A TRUSTED PEER that is never confirmed onchain. You can practically keep it like that forever or use *"lncli abandonchannel"* when you want to close it. So you could transact over LN without leaving any trace onchain. If you open a well size of that channel you literally can pass through "almost infinite" sats, back and forth.

These 0-conf channels are known ONLY between your own LSP node and your mobile private node. And by using "wrapped invoices" you are not even revealing the edge nodeID destination to the payer.

#### 5 - Good payment routes through LiSP (liquidity service provider)

Yes, many mobile users are using random public nodes to connect and open shity channels with Tor only nodes, but then they have failed payments to destinations because their peers are not good LSPs.

As a private mobile node, you do not need many channels open with random nodes. If you have only 2 max 3 channels with good LSPs (your own public node + 1 or 2 others as backup) is more than enough for your personal use for payments. 

As your own LSP, with your public "decoy" node you must have good liquidity and public routes to be able to provide successful routes from these private nodes. So keep well maintained your public node.

>Keep in mind:
>With these private mobile nodes, when you create an invoice you have 2 options:
>- you will need to use route hints embedded into the invoice string / QR
>- you will need to use wrapped invoice
>- you can include "blinded paths" but is not working together with wrapped invoice or route hints

---

## Use case scenario B

Let's consider you are a well known public LiSP, selling inbound channels to multiple node runners, public or private. And I am talking to you guys: @rizful_com (Megalith), LNServer, LNbig, Blocktank, @1sats (FlashSats), @Lightning_Lavka and many others out there that are private LSP (and are not well known).

These LSP could offer these services:
- private channels to mobile nodes
- JiT channels for private mobile nodes. Can be a 0-conf channel that later be converted into a full normal channel, once the user reached a certain amount of sats received.
- 0-conf channels between 2 public trusted nodes, where is needed a "shortcut route", adjusting liquidity.
- wrapped invoice for private mobile nodes
- LN proxy for general use
- good liquidity and routes for mobile users
- charging competing fees for opening inbound channels, with fair use and renewal of lease contracts

All these could make an incredible easy onboarding experience for new users onto LN.

I hope this guide will make you think and dig deeper into LN and help you create more solutions for new users. There are so many possibilities to do wonderful things with LN that many people don't even know about them. We are barely scratching the surface now.

***HAPPY LIGHTNING!***

Underrated privacy tools on Lightning

> **About the Book**
>
> The Dictionary of Obscure Sorrows is a compendium of new words for emotions. Its mission is to shine a light on the fundamental strangeness of being a human being—all the aches, demons, vibes, joys, and urges that are humming in the background of everyday life.

There is so much to explore in this book I _finally_ stumbled upon—finally, because I have been thinking about new words for a long time ever since I read 1984, but to expand consciousness, not limit it like in the novel.

Additionally, It's not just a loose collection of words, but it's organized into chapters, concepts, and tags. This is some serious work that we can access for free thanks to the internet.  

Here are some sample words:

---

> **idlewild** _adj._ feeling grateful to be stranded in a place where you can’t do much of anything—sitting for hours at an airport gate, the sleeper car of a train, or the backseat of a van on a long road trip—which temporarily alleviates the burden of being able to do anything at any time and frees up your brain to do whatever it wants to do, even if it’s just to flicker your eyes across the passing landscape.
>
> From _Idlewild_, the original name of John F. Kennedy International Airport in New York City.

---

> **wildred** _adj._ feeling the haunting solitude of extremely remote places—a clearing in the forest, a windswept field of snow, a rest area in the middle of nowhere—which makes you feel like you’ve just intruded on a conversation that had nothing to do with you, where even the gravel beneath your feet and the trees overhead are holding themselves back to a pointed, inhospitable silence.
>
> From _wild_ + dread. Pronounced “_wil_-drid.”

---

> **solysium** _n._ the unhinged delirium of being alone for an extended period of time—feeling the hours stretch into days until a weird little culture begins to form inside your head, with its own superstitions and alternate histories and a half-mumbled dialect all your own—whose freewheeling absurdity feels oddly liberating but makes it that much harder to reacclimate to the strictures and ambiguities of normal social life.
>
> From _solitary_, being by oneself + _asylum_, a sanctuary for the mentally ill + _Elysium_, the Ancient Greek equivalent of heaven. Pronounced “soh-_lee_-zee-uhm.”

---

> **etterath** _n._ the feeling of emptiness after a long and arduous process is finally complete—having finished school, recovered from surgery, or gone home at the end of your wedding—which leaves you relieved that it’s over but missing the stress that organized your life into a mission.
>
> Norwegian _etter_, after + _råtne_, decay. Pronounced “_et_-er-rath.”

---

> **kairosclerosis** _n._ the moment you look around and realize that you’re currently happy—consciously trying to savor the feeling—which prompts your intellect to identify it, pick it apart, and put it in context, where it will slowly dissolve until it’s little more than an aftertaste.
>
> Ancient Greek καιρός (_kairos_), a sublime or opportune moment + σκλήρωσις (_sklḗrōsis_), hardening. Pronounced “kahy-roh-skluh-_roh_-sis.”

---

> **endzoned** _n._ the hollow feeling of having gotten exactly what you thought you wanted, only to learn that it didn’t make you happy.
>
> In sports, the _endzone_ is the final goal, the end of the line—but at a certain point you have to drop the ball.

---

> **enterhood** _n._ the set of living people who have known you all your life, all the way back to your infancy, before you had a clue who you were; a group that slowly shrinks as you get older, until the point when all of your closest confidants have only ever seen an abridged version of you, having joined your story somewhere in the middle of things, just as you did.
>
> From _enter_ + _entire_ + _hood_.

---

> **aulasy** _n._ the sadness that there’s no way to convey a powerful memory to people who weren’t there at the time—driving past your childhood home to show it to a friend, or pointing at a picture of a loved one you lost, only to realize that to them it’s just another house, just another face.
>
> A contraction of _auld lang syne_, which is Scots for “times long past”—fragments of which are still present in _aulasy_, but the meaning has been lost. Pronounced “_awl_-uh-see.”

---

> **cullaways** _n._ the scattering of memories that your brain is actively forgetting at any given moment, erasing them one by one with no input from you and no knowledge that it’s happening at all—which means that when you wake up in the morning, your past will feel imperceptibly altered, with no trace of what you ate last week, a party you attended ten years ago, or the first real conversation you had with your grandfather.
>
> From _cull_, to control the size of a herd by selectively killing some animals + _away_. Pronounced “_kuhl_-uh-weys.”

---

I wonder if there's a word in there for this: the fear of having felt everything one will ever feel, and now it's just going to be more of the same forever.

Which words do you like?

The Dictionary of Obscure Sorrows

Politics_And_Law

Now BlackRock Wants To Control Bitcoin And The Panama Canal

siggy47

First time I'm hearing about this case. 

> If the appellate court upholds that decision, which endorsed database maker Neo4j's right to amend the GNU Affero General Public License, version 3, governing the use of its software with new binding terms, current assumptions about the enforceability of copyleft licenses will no longer apply.

> The GNU AGPLv3 is a free and open source software (FOSS) license largely based on the GNU GPLv3, both of which are published by the Free Software Foundation (FSF). Neo4j provided database software under the AGPLv3, then tweaked the license, leading to legal battles over forks of the software. The AGPLv3 includes language that says any added restrictions or requirements are removable, meaning someone could just file off Neo4j's changes to the usage and distribution license, reverting it back to the standard AGPLv3, which the biz has argued and successfully fought against in that California district court.

Copyleft is well known minefield. Most companies won't let you touch software licensed under them even if you don't intend to modify them. I suspect this case, unrelated as it may be, will only make that situation worse.

Adverse appeals court ruling could kill GPL software license

> Create your bitcoin key without electronics or microchips for unparalleled security.  No operating system means your private key information is safe from hackers and malware.
>
> Randomly assembling 256 bits into the eight slots converts real-world entropy into a number that cannot be duplicated.

You basically insert metal pieces representing 1s and 0s into the cylinder shaped thing's slots. Then they have spreadsheets for generating seeds/public keys:

> Create public keys and receive addresses via any offline and secure tool, including this website's free example spreadsheets, without exposing your key to internet-connected devices.

Definitely a bit whacky but pretty fun.

![](https://m.stacker.news/79938)

256-bit offline and secure physical private key

Our logo is on here, and I don't know why, maybe as a placeholder, but this looks really neat.

TollGate || Bitcoin-powered WiFi Network

Imagine living in a country with the worst internet—not just slow speeds and limited bandwidth, but also exorbitant prices. On top of that, you don’t have 24/7 access. Instead, you’re stuck with a mobile data plan capped at 8 GB per month.  

Yet, you still want to use Bitcoin in your business. You’re new to this, and your business has four employees who are *nocoiners* with no interest in learning about crypto—which is their right, and not a reason to fire them.  

As the business owner, you’re already juggling administrative tasks like pricing, inventory management, supplier contracts, and more. While you trust your employees, you still want to verify that charges are accurate and consistent.  

You’re eager to start using Bitcoin *now*, but there’s no “Uncle Jim” running a node or anything like that. Here’s a solution. IT’S NOT THE BEST IN THE WORLD, but it works in our context.  

We use **Wallet of Satoshi (WoS)** and **Wallet of Satoshi POS (WoS POS)**.  

- **WoS** is installed on the *owner’s phone*. Here, you set up the POS system and add products or services with fixed prices. No need to configure this on every employee’s device. Why? Here’s the beauty:  
- **WoS POS** is installed on each employee’s phone. They log in using *your* Lightning address, so their app displays all the preconfigured products and prices. Employees simply tap the items the customer requests, generating an invoice. This invoice appears in both their WoS POS app *and* your WoS app, showing exactly what was sold.  

**What if the customer wants to tip?** Employees can create a custom invoice for the tip amount (no SAT—taxman—involved here!). You can then reimburse them in fiat, or they can wear a QR code with their own Lightning address on their sweater, hat, etc., so tips go directly to them.  

I think this is a brilliant idea by the WoS developers.  

As the owner, you’ll receive payments instantly, track daily sales, and even monitor which employees are generating the most revenue—all while managing a team that doesn’t need to understand Bitcoin.

**ESPAÑOL**

Wallet of Satoshi y WoS POS. Una solución fácil y rápida.

Imagínate que vives en un país con un internet de lo peor, no solo por su velocidad y ancho de banda sino también por su precio. Además no tienes la oportunidad de tener Internet 24/7. Más bien un plan de datos de máximo 8 GB mensual. 

Aún así quieres usar Bitcoin en tu negocio, pero eres muy nuevo y en tu negocio tienes 4 dependientes, que son nocoiners y no les interesa mucho aprender, es su derecho y no por eso los vamos a despedir. 

Como dueño del negocio debes estar al tanto de funciones administrativas relacionadas con formación del precio, balance del almacén, contratación de proveedores, etcétera. Además, aunque confías en tus dependientes, siempre es bueno verificar y te gustaría que los cobros fueran los establecidos. 

Quieres empezar a usar Bitcoin ya y no hay un tío Jim con nodo ni nada de eso. Traemos una solución. NO ES LA MEJOR DEL MUNDO, pero es una en nuestro entorno.

Utilizamos **Wallet of Satoshi (WoS) y Wallet of Satoshi POS (WoS POS)** 

**WoS** la instalamos en nuestro teléfono, somos los dueños del negocio. En ella configuramos el POS y agregamos los productos o servicios que ofertamos con los precios que entendemos deben ser cobrados. No necesito hacerlo con cada dependiente, ¿por qué? Aquí está lo lindo.

**WoS POS** lo instalamos en el móvil de cada dependiente y la seción se inicia con la Lightning address de nosotros. Entonces en sus WoS POS estarán todos los productos o servicios que hemos configurado con los precios que pusimos. El dependiente solo debe tocar el producto o servicio que oferta tantas veces el consumidor lo solicite, así se forma una factura que cobrará y esa factura se refleja tanto en WoS POS como en la WoS suya, indicando los productos cobrados.

**Y si el consumidor quiere ofrecer propina?** El empleado puede, dijimos que no querían SAT, en el teclado crear una invoice por el monto de la propina, que luego usted le paga en fiat o puede tener un QR de su Lightning address en su pullover o gorra o lo que sea, entonces la propina va para el empleado.

Me parece una idea genial por parte de los desarrolladores de WoS. 

Ustede como dueño va a tener el dinero entrando con cada cobro, sabrá de manera fácil el balance de lo vendido ese día, incluso podrá saber fácilmente cuál de sus empleados, si le fuera necesario, está trabajando o facturando más para su negocio.

Wallet of Satoshi and WoS POS. A quick and easy solution.

BTCLNAT

nostr

Tech team is on fire 🔥



## Firmware info

The *Satcohip v0.14-0.2* with Schnorr support for **Taproot** & **Nostr** is out.

🔊 Compared to v0.12, v0.14 adds the following functionalities:
- Schnorr signature support for Taproot (to be used with @SparrowWallet); 
- Schnorr signature support for Nostr (no key tweaking).

Source: https://github.com/Toporin/SatochipApplet/releases/tag/v0.14-0.2



## Join the beta test

Want to try? Join the beta testers by ordering a DIY compatible smartcard and enjoy a **-25% discount!**

The  smartcard will come with the pre-loaded Satochip v0.14-0.2 applet with Taproot & Nostr support - AND - the default loading keys.

Perfect to build your next Nostr signing device.

![](https://m.stacker.news/79345)


## Info

Order here: https://satochip.io/product/card-for-diy-project/
Coupon code: Nostr-25%

Readme: https://github.com/Toporin/pysatochip/blob/master/README-CLI.md

Some basic commands are:

- Import a private key on slot #0:
```
python3 satochip_cli.py --verbose satochip-import-privkey --keyslot 0 --privkey aabbccddeeff00112233445566778899aabbccddeeff00112233445566778899
```

- Get the corresponding public key:
```
python3 satochip_cli.py --verbose satochip-get-pubkey-from-keyslot --keyslot 0
```

- Sign Nostr event:
```
python3 satochip_cli.py --verbose satochip-sign-nostr-event --keyslot 0 --message "Hello, world" --kind 1 --broadcast
```

Submit your feedbacks on Telegram: https://t.me/Satochip

🙏 Thank you 🙏

Nostr signing device on a smartcard is now a reality 🔥

Satochip_

Yesterday I was asking @Rexdentron about general prices for inbound LSP channels fees here https://stacker.news/items/889542

So I did some investigations, tests and I could gather this table, for those interested, especially for private LN nodes users (not routing!).
I made the pricing only for 1M sats, with the exception of LNServer that is offering min 2M sats. I consider a 1M sats channel well enough to calculate for a regular private LN node to use.

| LSP            | Opening Fee | Chan size | Duration |
| -------------- | ----------- | --------- | -------- |
| Blocktank      | 12,452      | 1,000,000 | 1yr      |
| Olympus        | 52,250      | 1,000,000 | 1yr      |
| Rizful         | 19,878      | 1,000,000 | 1yr      |
| Megalithic     | 20,282      | 1,000,000 | 1yr      |
| FlashSats      | 20,750      | 1,000,000 | 1yr      |
| LQWD           | 8,400       | 1,000,000 | 1yr      |
| LNBig          | 3,600       | 1,000,000 | 1yr      |
| Acinq/Phoenix  | 11,263      | 1,000,000 | 1yr      |
| LNServer       | 7,017       | 2,000,000 | 1yr      |
| Breez          | 4,500       | 1,000,000 | ?        |
| Greenlight     | 4,500       | 1,000,000 | ?        |
| Bitrefill Thor | 25,000      | 1,000,000 | 1yr      |
| Coincept       | 11,300      | 1,000,000 | 1yr      |

If you know more LSPs that are selling inbound channels and they have a clear pricing table, please post here.

LSP Inbound channels fees

econ

> The Bank of England gold discount has emerged due to a surge in demand for Gold shipments to the United States. This rush has led to a rare price discrepancy, with gold stored in the Bank of England’s vaults trading at a discount of over $5 per ounce compared to the London spot price. Typically, Gold in the BOE vault aligns with prices at major commercial vaults like JP Morgan and HSBC, but withdrawal delays—now stretching to several weeks—have made BOE gold less attractive to traders. The tightness in London’s gold market is further exacerbated by soaring leasing rates (up to 4.7%).

> As central banks seek to profit from lending gold. Additionally, a logistical bottleneck exists since the 400-ounce gold bars stored in London must be refined into smaller bars before being shipped to New York, adding costs and delaying deliveries. The mismatch in supply and demand has triggered backwardation—where the spot price of gold exceeds future prices—a rare signal of short-term scarcity. With traders frustrated by delays and shifting to commercial vaults, the BOE’s role as a gold custodian is now under scrutiny, raising concerns about its ability to efficiently manage large-scale gold withdrawals.

Who’s Taking All the Gold? London’s Liquidity Crisis Sparks Panic

south_korea_ln

Nostr Wallet Connect (NWC) is so hot right now. Everybody and their momma adding support for it. My homies love it. So it’s only right I made a PWA for it. 

I wanted a quick and easy way to add, remove, and switch between connections. Send and receive is working albeit very barebones. Will add styling and checks soon™. Just wanted to push this out before I’m no longer embarrassed. 

Check it out here: https://thebullishbitcoiner.github.io/bullishnwc/

![](https://m.stacker.news/77256)

Quickly switch between, add, or delete connections by tapping the hamburger menu. 

![](https://m.stacker.news/77257)

![](https://m.stacker.news/77258)

Tap the info icon to see connection information.

![](https://m.stacker.news/77259)

Oh, did I mention I’m bullish on NWC? 😎