OP_CAT•Boxes😺📦

🐾 Earn 2x @VaultLayer LASER Points with OP_CAT•Boxes 🚀 We’re always working to bring more utility to our holders! 🎉 Get 2x LASER points when you stake Test BTC with an OP_CAT•Boxes😺📦! 🔗 Start here 👉 app.vaultlayer.xyz Login with your UniSat wallet holding OP_CAT•Boxes CAT721 NFTs.

👀

@JakeBlockchain vaulterbtc.ai

You have $10k to invest in a Bitcoin startup today. Which one are you choosing?

Don't sleep on this change to win real Bitcoin ⏰ only 48 hours left! 👀

@100_Layer @ProtocolCAT 👀

#CAT20 @ProtocolCAT is coming to #Bitcoin network! #CAT20 protocol is now live on #Bitcoin Signet, powered by #100Layer 1⃣ #CAT20 on #Bitcoin 2⃣ Real #OP_CAT Application 3⃣ Not just proof of concept, Not just demo 4⃣ Bitcoin Miner validated 5⃣ No indexer needed 6⃣ OP_CAT smart contracts 7⃣ Decentralized and Trustless Now experience #CAT20: deploy, mint and transfer, based on #OP_CAT, on #Bitcoin Signet, on #100Layer, 100layer.io/signet/cat20 More about #CAT20: catprotocol.org

Cool way to show your support for the Bitcoin OP_CAT softfork!

$1M in BTC in support of #OPCAT @xverse

“Imagine Bitcoin as a giant calculator, input Hong, then Kong, press OP_CAT, and u get Hong Kong” Probably the most easy-to-understand analogy of OP_CAT ever. 🤓 Amazing job @scryptplatform🔥

👀

Despite the survey’s bias towards a covenant-only proposal, #OPCAT still ranks as the #1 choice.

Permissionless vs permissioned: the biggest philosophical difference between miner-enforced token like CAT protocol and indexer-enforced token like Rune is that the former is decentralized and permissionless: to add a new customized feature such as AMM on CAT, you just program a smart contract. You do NOT need to ask permission from anyone, not even the protocol developer. While in indexer-based metaprotocols, you have to beg the centralized developer(s) to add the feature.

#CAT721 fixes this with on-chain provenance

@Dan7dkt_Btc Bring OP_CAT back!

New Page Live: OP_CAT Showdown! opcat4btc.xyz/opcat-showdown OP_CTV, OP_VAULT, and OP_TXHASH all bring improvements, but OP_CAT does everything they do and more. OP_CTV improves security, scalability, and Layer 2 efficiency, but OP_CAT enables broader smart contract capabilities and more flexible covenants without being limited to predefined templates. OP_VAULT enhances Bitcoin security with predefined vault transactions, but OP_CAT allows for custom, advanced vault structures with greater flexibility and spending conditions. OP_TXHASH focuses on transaction verification, but OP_CAT offers a more versatile approach, supporting custom validation methods and complex scripting. Instead of multiple limited opcodes, Bitcoin needs one powerful, flexible upgrade. OP_CAT delivers security, scalability, and smart contract innovation all in one. Special thanks to @TaprootWizards @quantumcats, @udiWertheimer @rot13maxi @RomanCCLVI @Dr_DAO_ for my bitcoin education See why OP_CAT is the clear choice: 👉 opcat4btc.xyz/opcat-showdown

@aixbt_agent Study OP_CAT!

taproot wizards lands $30m series A to expand bitcoin's programmability through OP_CAT. 10 lines of code that could enable eth-like protocols on btc

@ercwl Bring OP_CAT back!

I want to take the opportunity here to clear up some confusion around OP_CAT and the extent to which it enables "ETH-like" protocols on Bitcoin. If you're reading this, and you're wondering "Why Would We Want To Make Bitcoin _Anything At All_ More Like The Garbage Shitshow That is ETH?" and for that reason feel that OP_CAT is unnecessary, l understand that emotion and want to clarify some things. What does OP_CAT do and why do we actually need it? So, everyone who knows anything about Bitcoin knows that the longest dispute/challenge we've had with the protocol is how to make it scale. How do we enable more transactions on Bitcoin, more users, to transact on the chain in a non-custodial fashion? In 2015-2016, we were at a crossroads and basically had to choose between: 1) Increasing the blocksize, making blockchain validation harder to do for the average user at home 2) Attempt to scale using complex "Layer 2" technologies, trying to aggregate as many transactions offchain as possible and settle to the mainnet only when necessary At the time, the downsides of (1) were clear and understood. Many people in Bitcoin felt that it was unwise to go for this option before we had explored (2), myself included. So we explored the Lightning Network, the channel-based, only "real L2" system that was possible to build on Bitcoin at the time (leveraging the OP_CLTV and OP_CSV opcodes that had been recently softforked into the protocol, and later, also SegWit—the latter two softforks activated specifically to enable LN). But Lightning has proven to be lackluster. While it is possible to route around BTC offchain in this manner, in a decentralized way, many, if not most LN-engineers are deeply frustrated with the complexity of the protocol. While marginal improvements have been made, we're still stuck with a channel-based, liquidity-management-based scaling system that drives most people to use custodial solutions, undermining the core premise of Bitcoin (self-sovereingty, privacy, censorship resistance). So, unless we want to surrender and actually make the blocks larger, we have to make Layer 2 protocols easier to use. The main roadblock to make Layer 2 protocols that are channel-free and easy to use is the lack of ability to in code specify how a Bitcoin transaction output (UTXO) can be spent. This technical detail is what's known as "covenants". There are many proposals for how to enable covenants and a lot of politicking involved in how to choose the right one. We've been observing the covenants debate deadlock for years. One of the leading proposals, called OP_CTV, has failed to win sufficient community consensus, and has often been bikeshedded by leaders in the industry with arguments such as "Why don't we just re-enable OP_CAT which exists today on sidechains like Liquid and altcoins like Bitcoin Cash?" If the primary holdup to activate covenants are questions like "Why don't we just activate OP_CAT instead?" then I think it's worthwhile to force the conversation and say, "Yeah, how about it? Why don't we just activate OP_CAT?" In May last year in Austin, at the most high-density Bitcoin developer conference of the year, @btcplusplus, developer consensus that are in some flavor in support of adding the functionality of OP_CAT was gauged and the overwhelming sentiment was that OP_CAT is actually something that we want in Bitcoin. Again, the introduction of OP_CAT is a way to introduce covenants into Bitcoin, with the core purpose being to break Bitcoin free from the lack of functionality that prevents it from being able to host good Layer 2 protocols (that don't require channels, trust, or inbound liquidity). Yes, it is true that these Layer 2 protocols will also be able to run Ethereum-like computation ontop, instead of just being scaling mechanisms, but OP_CAT overall is not an "Ethereumification" of Bitcoin. Bitcoin Core won't be any costlier to run at your home computer with OP_CAT, Bitcoin Script won't be running complex Turing complete computation, Bitcoin won't be managing more data onchain than the current 4MB block limit allows, it won't have rich statefulness, it will still be using the same old rudimentary UTXO-model at the baselayer. The only difference being that that rudimentary UTXO-model can now concatenate elements and verify if a hash belongs in a particular Merkle tree, and carry state from one UTXO to another, enabling every UTXO to operate as a tiny "state machine" in and of itself. This allows more powerful, user-friendly Layer 2 protocols, such that users can actually use them non-custodially and not keep their funds in custodial wallets, as we see with most leading Lightning efforts today, defeating the purpose of using Layer 2 protocols in the first place. So, would OP_CAT allow more "ETH-like" protocols to run ontop Bitcoin? Yes! It allows for channel-free, permissionless, user-friendly L2s to be built. Does OP_CAT make the Bitcoin Layer 1 "ETH-like"? Not by a longshot.

💡 OP_CAT: Should It Be Enabled? Let’s Vote! 🔐 OP_CAT has the potential to unlock dynamic Bitcoin functionalities like covenants, cross-chain compatibility, and Layer 2 scalability. 🚀 But should it be activated? Your vote matters! 🗳️👇

].@TaprootWizards has raised $30 million with which it plans to build an ecosystem of applications using the OP_CAT Bitcoin improvement proposal. By @JamieCrawleyCD trib.al/EEOWBub

@CoinDesk @TaprootWizards @JamieCrawleyCD Bring OP_CAT back!

👀

Happy Lunar New Year!🐍🌕 LFmeow!

@unisat_wallet Thanks for supporting CAT721!

UniSat Wallet Extension v1.5.3 now supports CAT721! You can now send, receive, and manage your CAT721 assets seamlessly in the UniSat Wallet! ✨ 🔗Update your wallet: unisat.io/download 📖 Learn more about CAT721: catprotocol.org/cat721 Stay tuned as we continue to roll out new features and improvements! 💪 2/2

A new way to buy FB is here! 🔥 UniSat Wallet v1.5.3 Now Supports FB purchase with @AlchemyPay✨ Upgrade to the latest version of the UniSat extension wallet and easily purchase FB using Alchemy Pay. Simply click the "Buy" button on the homepage to get started. 📲 Download UniSat Wallet: unisat.io/download We’re always improving your experience and will continue to provide more convenient FB trading options in the future. Stay tuned for more updates! 1/2