#JoininBox v0.8.0 is released with an improved ability to start a pruned full node within minutes with the help of Ketominer of https://host4coins.net.
There is a startup and menu option to download the pruned chain and chainstate from https://pruned.host4coins.net/blocks (similar to the now seemingly abandoned https://prunednode.today )
There are other updates for the prebuilt images for RPi, amd64 and now running the latest Bitcoin Core v25.0.
I use ZFS on my servers - TrueNAS and a simple Debian one. It works great. Can expand the pool if needed. The easiest config is a mirrored VDEV with 4 disks. Can make automated snapshots of everything if needed and have separate mounts for any folder.
Docs are plenty and all well tested.
Nope, should I? Do you have some relevant experience? Tell me a little more.
Also check the lighting typo in the readme header.
I am dreaming of @lnproxy built in to my zaps.
The workflow is not designed that way, but if you know your ways around linux it is possible.
The menu option will just start fresh every time.
When Nostr - Twitter crossposter?
#crossposter
Using https://liquid.boltz.exchange you can balance your channels with a swap to LBTC for 1000ppm
or pay LN invoices up to 5million sats from your Liquid stash.
With Confidential Transactions (even cross-asset) batching achieves the same as coinjoins, glad to see the usage come.
To reliably break the transaction graph would need some peers to batch with maybe like in the JoinMarket Maker-Taker model.
With the amounts hidden the coinjoin soduko becomes impossible and the Taker inputs can not be identified even when there are only a few participants.
I have seen this. Oh shit.
Moved to ZFS pools now, often testing failing disks before sending to RMA. At least they die encrypted.
A reminder for RPi lightning node runners:
the cost of the force closure of 10 channels now can buy you a decent used laptop, PC or even a server.
Disable all services causing high load and increasing memory usage.
Don't let the hardware fail on you, prepare in advance, check here for some advice:
https://www.lightningnode.info/hardware-deployment/recommendations
The next batch of the metal cases for the #LNPos (https://github.com/lnbits/LNPos) is now available on the https://diynodes.com shop.
The design is updated with easy access to the reset button.
There are a good few so batch orders are welcome to save on postage (they are heavy!).
Agree that the two way peg in Liquid is not permissionless. That is what it does not make it a real layer 2 according to the thinking above vs lightning, but this is only difference in semantics.
Re the practical differences between the Elements sidechain and an ecash system it is interesting to thinking that the outcome is quite similar, but there are fundamental differences due to the tech used - blockchain vs ecash.
On Liquid
- the supply can be audited (however more complicated than on bitcoin due to CT)
- need to wait for blocks (1 minute only)
- IBD requirement
- UTXO model (CT hides the amounts)
- and most importantly it is almost prohibitively difficult to start a new Elements sidechain
Ecash mint:
- proof of reserves is not figured out yet (interactive, maybe with key rotations etc)
- fast as only depends on the mint
- better privacy with tokens of fixed denominations which are not connected in any way
- easier to deploy
I am sure there are many other nuances.
My subjective perception is that I would be more comfortable with Liquid for higher amounts or longer time, but for the transactional use ecash seems to be very promising (just like custodial LN wallets have the best UX currently - but without privacy from the custodian).
No, it is a sidechain. Different rules apply and can't get out without permission or trading.
Yes, a custodial system doesn't feel like a layer to me as none of the base layer rules apply.
that escalated quickly from play computer to data center
In short: a custodial system is more like an alternative rather than a layer on top.
Lightning is layer two as can be settled onchain directly.
Custodial ledgers and ecash mints are equivalent in the sense that there is no direct (meaning trustles) settlement to chain or LN.
They can be viewed as an alternative closed system or maybe as layer 3 (for the trusted conversion) depending on the definition.
By this view a mint or custodial LN wallet supports the base layer or LN only on the level of the custodian. The users transact intraledger and can swap out in a trusted fashion.
That's good, but yes, the last hop pretty much still gives the node away.
Also needs to have LNaddress and zaps plugged in which is not that straightforward when it is only on cli.
There could an solution which generates the virtual hop through the LND/CLN GRPC or REST, but that is very implementation specific.
#[2] works for any BOLT11 invoice, more private and has a pretty simple API to work with.