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

Can all consensus valid 64 byte transactions be (third party) malleated to change their size?

The Great Consensus Cleanup proposes to make 64 byte transactions consensus invalid, for various reasons. They have been non-standard for years and appear to serve no useful purpose.

It appears that any such transaction can be malleated into a different size, so that in practice there is no confiscation risk even if such a transaction were useful. I'm trying to understand this aspect better.

Given a UTXO A, which either already exists or is freshly mined under the current consensus rules (e.g. through a non-standard transaction).

Given a 64 byte transaction T that spends it (non-standard by definition).

Without access to the secrets (if any) that were used to generate T (private key, hash pre-image, etc.)

Is it always possible to change T into a consensus valid transaction T' that spends A?

Additionally, if I understand correctly, it's not possible for any 64 byte transaction T to send coins to a destination B that is a secure (i.e. >= 20 byte) public key (hash).

Regardless, for every B, is there a malleated T' that preserves B (at least still spendable by the private key b)?

If the latter is too hard to prove, could one could show that any T can be malleated by an attacker to divert coins away from B.



from Recent Questions - Bitcoin Stack Exchange https://ift.tt/NA5BXIJ
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