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

'gettransaction' returns empty details for some wallet transactions but not others

Bitcoin Knots 29.3, single descriptor wallet managed by Sparrow, four 2-of-3 multisig wallets registered in it.

Three transactions from one multisig don't appear in the Knots GUI transaction list. Ten from another, created the same way a day later, display normally. All are self-transfers between two wallets in the same node wallet.

Comparing gettransaction output for a working and a non-working transaction: every top-level field matches in shape — same fee value, amount: 0, empty walletconflicts and mempoolconflicts, bip125-replaceable: no, correct confirmations. The only difference in the entire object is that details is populated on one (a send and a receive entry) and [] on the other.

The fee is correct on both, which I take to mean input ownership was resolved. That's the part I don't understand — how does the wallet compute a fee and then produce no detail entries?

Other checks on the non-working wallet:

  • getaddressinfo on the destinations: ismine: true, iswatchonly: false, solvable: true, desc and parent_desc both present

  • listdescriptors: correct receive/change pair, matching timestamps, next index matches usage

  • UTXOs present in listunspent with correct amounts

  • rescanblockchain from a height before the transactions — completed, no change balances reconcile; Sparrow displays everything correctly

One unexplained difference: the working wallet has one descriptor with active: true; the non-working wallet has both active: false. Closing and reopening only the non-working wallet in Sparrow didn't change that.

What populates details, and what would leave it empty for a transaction the wallet otherwise fully recognizes?



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