pull down to refresh
@ek
5,367,009 sats stacked
stacking since: #57444longest cowboy streak: 233 verified stacker.news contributornpub16x07c...2j2s96s89dekzyis
0 sats \ 0 replies \ @ek 5h \ parent \ on: Stacker Saloon
Did you accidentally select ~AI in the dropdown?
This the global recent feed:
The node: prefix is more than just a convention—it’s a clear signal to both developers and tools that you’re importing Node.js built-ins rather than npm packages.
the "... more than just a convention—it's ..." sounds like AI ...
No clear warning: There was zero indication that enabling this option would make your content publicly searchable on Google.
Wrong
But, if you don't have proofs that match the amount, you would need to go online and swap for the needed proofs at the mint.
This also applies to offline receives.
The sender needs to not only know the recipient in advance, but also what denominations they will use. The recipient can’t give you change back.
Still useful, but that’s another important limitation.
Did you configure
--auto-liquidity?The default requested liquidity amount is 2m sat, configurable with--auto-liquidity. The higher the amount, the higher the upfront cost, but the lower the mining fees in relative terms.
If you did not, this means it will open a channel with 2m sats inbound liquidity once you have enough fee credits to pay 1% + mining fees (around 21k sats).
I think
estimateliquidityfees is giving you the fee if you would configure --auto-liquidity with that amount. But not sure why it's giving you a service fee of ~1k sats for 5k sats, it should be 1%. Maybe I'm wrong.Thanks, looks just like you said
Will check if I find anything interesting in your wallet debug logs