Meanwhile, Bitcoin developers were also thinking about a trick called MAST (Merkelized Abstract Syntax Trees), which would make smart contracts on Bitcoin more compact.
Bitcoin Core contributor Gregory Maxwell then figured out how to combine Schnorr and MAST in a clever way to not only make smart contracts more compact, but in many cases also indistinguishable from regular transactions, benefitting privacy: Taproot.
After years of development, the Taproot code was ready to be activated. This marked the start of a new discussion: how should the upgrade be deployed on the Bitcoin network as safely as possible?
Interestingly, some miners also took the initiative to get Taproot in the Bitcoin protocol, with @officialpoolin's @bitentrepreneur collecting positive feedback from a range of mining pools on taprootactivation.com.
Still, there were roughly to "camps" in the Bitcoin activation debate, that for a while seemed unable to reach consensus on the best method: LOT=false or LOT=true.
Finally, as a neat example of something new that could soon benefit from the Taproot upgrade, several Bitcoin developers have been speculating about a concept known as Payment Pools: bitcoinmagazine.com/culture/buildi…
• • •
Missing some Tweet in this thread? You can try to
force a refresh