t4es5ter5's avatar
t4es5ter5
t4es5ter5@bitbubblex.com
npub1rxdg...na9d
Maximalist to the bone
t4es5ter5's avatar
t4es5ter5 2 years ago
Unfortunately this video format can current only played with @Amethyst . Wonder when other clients ever will support this? @Iris image Example: On most client only audio can be played. This format is the default format of the Pixel 8 video recorder. Not found out how to change this.
t4es5ter5's avatar
t4es5ter5 2 years ago
Need to tweak a bit with audio. Somehow it is not recorded well.
t4es5ter5's avatar
t4es5ter5 2 years ago
Ordinary evening at Cafe Babel in Valletta
t4es5ter5's avatar
t4es5ter5 2 years ago
I have decide to stop with my lightning node. Too risky. Also got another force close of WalletOfSatoshi I think this new class of replacement cycling attacks puts lightning in a very perilous position, where only a sustainable fix can happen at the base-layer, e.g adding a memory-intensive history of all-seen transactions or some consensus upgrade. Deployed mitigations are worth something in face of simple attacks, though I don't think they're stopping advanced attackers as said in the first full disclosure mail. Those types of changes are the ones necessitating the utmost transparency and buy-in of the community as a whole, as we're altering the full-nodes processing requirements or the security architecture of the decentralized bitcoin ecosystem in its integrality. On the other hand fully explaining why such changes would be warranted for the sake of lightning and for designing them well, we might need to lay out in complete state practical and critical attacks on a ~5 355 public BTC ecosystem. Hard dilemma. There might be a lesson in terms of bitcoin protocol deployment, we might have to get them right at first try. Little second chance to fix them in flight. I'll be silent on those issues on public mailing lists until the week of the 30 oct. Enough material has been published and other experts are available. Then I'll be back focusing more on bitcoin core. Best, Antoine