Tangem Wallet Pack of 2 - Secure Crypto Wallet - Trusted Cold Storage for Bitcoin, Ethereum, NFT's &

Tangem Wallet Pack of 2 - Secure Crypto Wallet - Trusted Cold Storage for Bitcoin, Ethereum, NFT's &
Key item features Ultimate Security: Generates a private key that remains on the card, safeguarding crypto and NFTs from hackers with EAL6+ certification and audited firmware. Versatile Compatibility: Manages over 13,000 tokens across 70+ blockchains, supporting DeFi, NFTs, and DeEx without wires, Bluetooth, or USB. Effortless Operation: Utilizes NFC for secure transactions via a mobile device and the Tangem app, enabling buying and selling crypto with various payment methods. Smart Backup: Features a second Tangem Wallet as a backup, eliminating the need for paper, pictures, or seed phrases for recovery. Durable Design: Boasts IP68 protection against environmental conditions, ensuring longevity and robust physical security. Comprehensive Support: Compatible with Bitcoin, Ethereum, Solana, XRP, USDT, and over 6,000 cryptocurrencies, integrating with dApps and WalletConnect.

LBANK

Why is `SIGHASH_ALL` allowed in taproot when `SIGHASH_DEFAULT` is more efficient?

The existence of SIGHASH_DEFAULT makes SIGHASH_ALL redundant for Taproot, since both produce the same behavior — except SIGHASH_DEFAULT saves a byte by being implicit.

Given Bitcoin’s usual focus on minimizing blockspace usage (e.g. x-only pubkeys, minimal ScriptSig rules), why isn’t there a consensus or policy rule to disallow or discourage SIGHASH_ALL in Taproot signatures?

I’m not suggesting it’s a bad design choice — I just want to understand the rationale behind allowing the redundant form.



from Recent Questions - Bitcoin Stack Exchange https://ift.tt/3HkUf0R
via IFTTT

Popular posts from this blog

Crypto Exec Warns Tokenization Is Moving Faster Than Expected

Bitcoin Mining Could Be Strengthening The Ruble, Russian Central Bank Says

Nigerian SEC Partners With Police To Tackle Crypto Ponzi Schemes – Details