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.

How to Sign a Musig with Bitcoin Core

I created a musig descriptor with Bitcoin Core: My addresses: tpubDCWbaTx1wFG3JHpT5sK7HD2yBDLdoonfz7SN5Jnk3UGXf3EAMNECcDrGQQXP6jccdgcczRnSDTBAXauK19EAbf3KvnHmRCsKk2gGdWP3Xke tpubDCis6zc7jL21KnV9Rz7zRz2AsFartHsdQx9uVdnd2kVuNpCNX5mhHaMwYrR7YvdT3GKqKVKNDRSz966Z9DjXqUvyz7gHkfh751GBJ68CYab The keys were master keys from other wallets. Here was my descriptor: tr(musig(tpubDCWbaTx1wFG3JHpT5sK7HD2yBDLdoonfz7SN5Jnk3UGXf3EAMNECcDrGQQXP6jccdgcczRnSDTBAXauK19EAbf3KvnHmRCsKk2gGdWP3Xke,tpubDCis6zc7jL21KnV9Rz7zRz2AsFartHsdQx9uVdnd2kVuNpCNX5mhHaMwYrR7YvdT3GKqKVKNDRSz966Z9DjXqUvyz7gHkfh751GBJ68CYab)/<0;1>/*) No problem with importing or deriving addresses: $ bitcoin-cli -rpcwallet=musig importdescriptors '''[{ "desc": "'$DESC_WITH_CS'", "timestamp": "now" }]''' [ { "success": true, "warnings": [ "Range not given, using default keypool range" ] } ] $ bit...
Read more

LBANK

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...
Read more

If a BIP39 hardware wallet is lost, what exactly is recovered from the seed phrase?

I’m trying to better understand the relationship between a hardware wallet, a BIP39 seed phrase, and the actual Bitcoin keys. Suppose a user initializes a hardware wallet, receives a 12- or 24-word recovery phrase, and later completely loses or destroys the physical device. If the recovery phrase is imported into another compatible wallet: What exactly is being reconstructed from those words? Are the same Bitcoin private keys and addresses deterministically regenerated? What additional information might still be required, such as a passphrase, derivation path, or wallet type? Are there situations where having the correct seed phrase alone would still not be enough to recover the expected Bitcoin wallet? I’m specifically interested in the Bitcoin/BIP32/BIP39/BIP44 side of this rather than device-specific recovery instructions. from Recent Questions - Bitcoin Stack Exchange https://ift.tt/i7GAKkm via IFTTT
Read more

How to make your own crypto coin or token?

I'm absolute new to this. Can someone help, how I can make my own coin or token and sell it on the crypto market? I don't mind it being a long-term project like 6 months to 1 year. Is this the right community for building this? If no, can you suggest better spaces, please. from Recent Questions - Bitcoin Stack Exchange https://ift.tt/B5P3h2c via IFTTT
Read more

Does Margin Trading Affect the Crypto Order Book?

I’m trying to understand how margin trading affects the crypto market. If a trader uses margin to open a large long or short position, does the executed trade directly affect the underlying crypto order book, similar to a regular spot trade? Or does margin trading operate through a separate order book, depending on the trading product? For example, how would this work on an exchange such as Nezobank ? Does the impact on the order book depend on whether the position is spot margin or a derivative? I’d appreciate a simple explanation with an example if possible. from Recent Questions - Bitcoin Stack Exchange https://ift.tt/oX1Fb5M via IFTTT
Read more

Take custody of your bitcoin

Bitcoin is an independent decentralized financial system. It does not need any exchanges or the clarity act. It needs us to hold our own keys when we buy it and never sell. Only buy with self, collab, or multi-sig custody. Only use as collateral and borrow any crypto. Why would anyone sell bitcoin? from Recent Questions - Bitcoin Stack Exchange https://ift.tt/2aM4Bi3 via IFTTT
Read more

Should a watch-only Bitcoin wallet descriptor be treated as a secret backup?

I'm setting up a Bitcoin wallet where the signing keys remain offline, while an online machine only has a watch-only output descriptor. For example, the online wallet may contain an account xpub together with the master fingerprint, derivation path and address type, but it has no seed or private keys. I understand that someone who obtains the descriptor cannot directly sign transactions, but they may be able to derive the wallet's addresses and monitor its transaction history. I'm trying to understand the exact security boundary here: What information can an attacker learn from a watch-only descriptor alone? Does leaking the descriptor create any direct risk of losing funds, or is it only a privacy risk as long as no private key is exposed? If one non-hardened child private key were later compromised, could the account xpub contained in the descriptor then be used to recover the corresponding account private key? Does the hardened account boundary protect t...
Read more