Hannah

This is a wake up reminder that you shouldn’t have an internet connected privileged binary running on your production systems. What was a bad update could have easily been a massive adversary backdoor. A third party vendor will always be the weakest link. Isolate critical systems

As we prepare to launch the testnet of our Bitcoin data availability layer, we see a potential predicament in the explosive growth of Bitcoin Layer 2s. While the collaborative effort in the Ethereum community has set the gold standard for Layer 2s, those rules can't simply be reapplied to Bitcoin, which doesn't possess the same sophisticated smart contract functionality as Ethereum. Despite Bitcoin Virtual Machine (BitVM) being fairly new and still in the theoretical stage, developers have raced to build use cases on top of it. But rushing to build Bitcoin Layer 2s without fully fleshing out their appropriate design puts the security of user assets at significant risk. At MultiAdaptive, we believe the goal of data availability is to protect user assets above all else. That's why we are building truly native DA solutions that inherit the security of the main chains, including Bitcoin. Rather than building our own consensus layer, we use an Avalanche subnet and leverage Bitcoin protocols like Ordinals to publish data commitments. That way, Bitcoin is approving what data should be stored, not just what data has been stored. This is just one aspect of what we are developing. If you are working on a Bitcoin Layer 2 where the security of user assets is your absolute priority, come build with us! 🚀

on rollups, L1s, interop, safety, censorship resistance: rollups scale better than fast L1s because they can have a smaller replication factor than L1s. less redundancy = more room to go faster due to less communication overhead between block producing nodes. verifying nodes can always up by leveraging the block producers to assist them with verification (e.g. verifiers can do low cost stateless & parallel execution using verkle trees witnesses on L2 and keep up even tho there may only be a few large sequencer machine that can produce blocks) so it's easy to expect that there will be a few extremely fast rollups, where x-rollup interop won't be the main issue, and then there's a long-tail of rollups where interop might be harder yet not matter as much. if you want to interoperate with assets on the L1 (hint, you do) then your system has a bridge where the bridged assets are secured as if they were in the L1. also -- despite the less redundancy, you achieve censorship resistance same as the L1, using it as a slow path if the fast path fails. this is done by making the L1 contain a summary of the L2 state, and enabling the L1 verify claims about the L2 state (e.g. "privileged entity tried to censor my transaction/steal my money, L1 please punish them") interactively w/ the fault proof or non-interactively w/ the ZKP, both techniques which are taking an execution trace, committing to it, and making a bunch of statements against it. then the L1 gets convinced about them by sampling i.e. checking here and there to see if you did the work correctly and punishing you if you didn't. non-surprisingly, Ethereum L1 data availability sharding also works by sampling. this hopefully gives you an intuition on how you can stack a few techniques together to achieve fast systems which are censorship resistant, safe, and do not require a large set of operators coming into consensus, using the L1 as a ground truth court.