@matt_odell@side_swap For app developers, our Bitcoin Stack has a Bitcoin, Liquid, and Lightning BTC & LBTC nodes and more in a convenient setup. https://t.co/Riwmyc81sN
Fat bitcoin stack update:
- now includes the awesome Electrs Electrum server v0.8.7 by @roman_zeyde
- all prebuilt containers updated to Alpine3.12
Scaling Bitcoin is modular.
https://t.co/RiwmycpCkl
Bitcoin Stack containers updated:
- Update bitcoind to v0.21.0
- Update clightning to v0.9.3
- Update elements to v0.18.1.9
There's only one #Bitcoin & #CWIAF
https://t.co/Riwmyc81sN
@sr_gi That's why we denominate in msats internally. Changing to picoSats or whatever should just be a precision change with no side effects. No technical debt.
@sr_gi More precision is easier to handle gracefully than less. Floating points are just an arbitrary representation, that's why all money VOs are based on minimum currency denom. Hence it is sensible to adopt a msat denom at least on a backend system that intends to integrate LN.
@sr_gi You can't integrate with Lightning or layer 2 services unless you account in msats, or sats if only chain. Its pretty dumb to put floating point conversion throughout your backend.
I've built a scalable alternative to BTCPayServer which is aimed at app stack developers. It is a security layer + double entry accounting ledger that abstracts the complete Bitcoin stack into a unified Payment model. I haven't had time for docs yet, but DM if you want a preview.