Posts

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.

What is the exact process for importing bitcoincore descriptor wallet to Sparrow Wallet

I recently converted a legacy wallet to a bitcoincore descriptor wallet. Now I'd like to create a new Sparrow wallet and import (not sweep!) the transaction history and balances to it. The Sparrow client is already configured to connect to a Raspiblitz full node over Tor. I'm finding difficulty specifically with how to import the descriptors fully and correctly (with included transaction history). I'm willing to entertain interim steps as long as the at the end I end up with a functional (non-watch) wallet in sparrow that is a duplicate of the bitcoincore wallet. from Recent Questions - Bitcoin Stack Exchange https://ift.tt/vLalSCd via IFTTT
Read more

LBANK

LBANK

Where are inner null bytes valid in p2p messages

P2P messages use null bytes as padding when the field size is larger than the content. For example, a command field is interpreted as 12 byte ASCII, so the version command is typically as follows: version\0\0\0\0\0 My question is, is it also valid to have inner null bytes? eg: ver\0sion\0\0\0\0 Some protocol applications I notice treat inner null bytes as valid, which seems mistaken. from Recent Questions - Bitcoin Stack Exchange https://ift.tt/oMqS6sa via IFTTT
Read more

I have 9 words out of 12 words from the 2048 list I pay 5 K for help

Someone can help me to login my wallet if I’m missing three last words out of 12 from Recent Questions - Bitcoin Stack Exchange https://ift.tt/u4itZNh via IFTTT
Read more

CRYPTO RECOVERY

For anyone dealing with lost crypto, investment scams, or frozen funds, I highly recommend reaching out to the recovery team on their website at https://fundsrecoveryagent.com . They’ve already helped several people in this group as well as many others across different communities recover their funds successfully. Their team is well known worldwide for handling recovery cases professionally and efficiently. If you need assistance, don’t hesitate to contact them directly. from Recent Questions - Bitcoin Stack Exchange https://ift.tt/7Cb5FgH via IFTTT
Read more

bitcoin core quickest method legacy -> descriptor wallet migration

I had a power outage recently and realized my current setup needs to change. The old ass laptop that I use for just bitcoin core needs to be retired. I've been running a pruned node on it forever. it's been OS updated recently and the blockchain is catching up once again. I'm thinking to move to Sparrow wallet synced to a Raspiblitz instance (over tor) and the have a method for importing the bitcoin core wallet via output descriptors. However the few times I've tried to migrate the legacy wallet bitcoin core (v31 now) have complained about the process and demanded a blockchain re-index. ex: [error] Prune: last wallet synchronisation goes beyond pruned data. You need to -reindex (download the whole blockchain again in case of a pruned node) That's not really feasible even if I wanted to since this old machine is struggling even to catch up to the last week of being offline, nor do I even have the space on it anymore for a full blockchain. So the que...
Read more

What's the current situation with Bitcoin testnets?

On mempool.space, testnet3 is marked as deprecated and encourages users to use testnet4. is testnet4 now the canonical testnet for Bitcoin? why not just call testnet4 just testnet now? it's all confusing from Recent Questions - Bitcoin Stack Exchange https://ift.tt/KJlIvn8 via IFTTT
Read more

What kind of wallet or protocol would sign a Taproot keypath spend with SIGHASH_NONE?

Browsing early Taproot transactions, I came across this one (block 709,911, ~280 blocks after Taproot activation): https://mempool.space/tx/ef72502f5d2509f519be33304e385bdf9d1bed5e4cd19f7a254700299db2ba91 What caught my eye: It's a P2TR keypath spend, single input, single output, dust-level amount (1943 → 1803 sats) The witness signature is 65 bytes ending in 0x02 — i.e., SIGHASH_NONE (not SIGHASH_NONE|ANYONECANPAY which is 0x82) nSequence is 0x9f (= 159), which under BIP68 would imply a relative timelock of 159 blocks Plain SIGHASH_NONE (without ANYONECANPAY) on a 1-input-1-output transaction seems strange to me — the signer is essentially saying "I authorize spending this UTXO regardless of where the output goes," but there's only one output. Anyone seeing this in mempool could in principle replace the output and rebroadcast. Questions: Is there a known wallet or protocol that signs P2TR keypath with plain SIGHASH_NONE (0x02)? I'd expect 0x82 (NONE|AN...
Read more