5 days of downtime and counting: https://status.iota.org/
631 karma · joined February 1, 2013
In fact, you won't even find "invest" word on the website.
There is zero promise, nor even implied, about future value.
It is not expensive. Currently fees are in cents per on-chain transaction. And basically 0 for Lightning Network payments.
It is traceable though and that is indeed a big issue going forward. Again, Lightning Network helps to some extent but much more is needed.
I would definitely pick Coldcard over Ledger though.
Coldcard is open source and open hardware to a much greater extent, while still using secure element for secret storage and PIN counter. It also offers advanced security features like proper multisig support, airgaped operation, roll-your-dice entropy input, etc.
For very large value transfers exchanges are expected to wait for 100 confirmations (~17 hours) until they credit balance.
It's all probabilistic.
Finally, Bitcoin PoW is not security theatre, it is just one piece of the complex security system.
Regarding the supply chain, there is very little that can be done, and yubikey-like solutions certainly do not excel here. Trezor T at least comes with no firmware (to be installed by the user) and holographic sticker. Basic, but better than Yubikey et al.
This is already the case with Mazda's touch-disabled-while-driving screens.
Not sure at all about the net effect on safety.
As for the architecture, in DigitalOcean the external block storage is the only way to separate function from state. We need this to be able to rebuild VPS-es regularly. This is to avoid configuration drift and to prove/enforce reproducibility.
We run 26 services in production on DigitalOcean. Every single VPS in our setup uses block storage feature as a persistence layer (system logs, app logs, databases, etc).
Thanks to this architecture we can rebuild machines at will. The _function_ and _state_ are nicely separated.
The downside is that we are now fucked.
To be precise, small feature branches are perfectly fine. They are meant to be reviewed and squashed into master ("trunk") in a few hours to a few days maximum.
Squashing instead of merging has a big advantage of being able to quickly revert the changes if things go awry despite all best practices in place.
PS Avoid gitflow and similar workflows as they introduce leaps and thus risk. As everything in software engineering, you want your workflow to be as incremental as possible.