LBANK INFO CRYPTOCURRENCY

I’m helping a friend recover access to a Bitcoin wallet that was originally set up around 2018 using someone else’s first-generation Coldcard (presumably Mk1). My friend is not technically knowledgeable and doesn’t remember the exact setup or backup procedure. What we currently have: A USB flash drive that he believes was used to store or back up the wallet. A handwritten sequence of 12 words. A handwritten 6-digit PIN. A Bitcoin receiving address previously used to check the balance around 2020. We are not certain whether the original Coldcard device is still available. What I’m trying to understand: From the Coldcard documentation I’ve found, encrypted wallet backups can be protected by a separate 12-word password, which is different from the wallet’s BIP39 seed phrase. I’m therefore unsure whether the handwritten 12 words represent: The actual BIP39 recovery phrase for the wallet; or A password used to decrypt a Coldcard backup file. I’m also unsure wha...

I am trying to identify a Bitcoin-related service or wallet that I remember using around 2009. I understand that modern mnemonic recovery seeds (such as BIP39) did not exist in 2009, and I am not claiming that this was a modern seed phrase. My recollection is the following: I was introduced to Bitcoin by a friend. I created a new email account specifically for this. I registered on a website with an email address and password. I bought Bitcoin for a small amount of euros. My recollection is that payment was made by bank transfer from a German bank account. Afterward I could see a Bitcoin balance associated with my account on the website. I was advised to move the bitcoins to a wallet so that I would still have access to them if the website disappeared. I did not install wallet software. I remember doing this in the browser. During this process, the system generated a number of apparently random words for me. I understood these words at the time as a password/passphrase and...

ok using in regtest with my bitcoin core, i am trying to import the below descriptor and its corresponding arguments for the importdescriptors command but i am unsuccessful. i've tried a few different variations and still the same issue. bitcoin-cli-rt -rpcwallet="my-descriptor-wallet" importdescriptors << 'EOF' [ { "desc": "tr([9a3ad634/86'/1'/0']tpubDCAqxEgJB2o9ZL4gozDZ5xmRGYFzV7oJB1hC1hSDYqXyoFYNEvbHh7smPmhDPsozfusb4czadKiC5HQ4e231rY9o9Q6tN34nrruJcF6rPYB/0/*,{multi_a(2,[8e7dc54e/86'/1'/0']tpubDDGyiLE11EYR9sNLNqExhwASubctpctXt5S5kfHepuL4UtihdkvKuHvakCR6od6yusSCruZ3HnejrgEvechahX3PjNQr87WPwMrUHM1J7CM/0/*,[32bbb15e/86'/1'/0']tpubDCwvzUy66wLsmQ7GzB1Tzem7xL9JWCtAYj3z2ubqFyRebgvbwtSXNxyzSHNs2zCNWuUHe8QpnMqNsvQcXYRyaxYZaNtNQLX4MgohApjsTs3/0/*,[c556a9ec/86'/1'/0']tpubDCJTFn83QPCEVG8i7ZpChtYsykvU6U2g8QJTHhJQ3xQbLwDiEg1DSFtRV25FaJkpwxLbCA91iB8AZrxJmh13XBbpPuk64bcYWVsm4xLBnZL/0/*),an...

Today I was back at trying to sign a transaction spending a musig UTXO in Bitcoin Core. Last time around, Pieter W. gave me two pieces of advice. Use PSBTs, as they're more likely to work on modern stuff like Musig than raw transactions. He asked how I was generating my private/public keys, which made me realize I'd probably calculated my pubkey incorrectly. So today I took a new swing, using the same methodology I use for signing regular multisigs in Bitcoin Core, but now I can't get the PSBT to process correctly. I. Capturing the Individual Keys I used the simplest method possible to generate a musig address: grab addresses from two different wallets and capture their pubkeys. (The private keys should then be sitting in those wallets.) Here's the address & pubkey capture: musigaddress1=$(bitcoin-cli -rpcwallet=musig1 getnewaddress) musigaddress2=$(bitcoin-cli -rpcwallet=musig2 getnewaddress) musigpubkey1=$(bitcoin-cli -rpcwallet=musig1 -name...

hello i am building lightphon.com a dapp where you can buy and sell compute power. What i really need is a place where you can get the 66 hex characters usdt group key (taproot assets) from Recent Questions - Bitcoin Stack Exchange https://ift.tt/kJWBOhE via IFTTT

I recently installed Bitcoin Core 32.0rc2 on one of my nodes and noticed that the reported P2P protocol version changed from 70016 to 70017. I remember 70016 being used for quite a long time, so I was curious what exactly triggered the protocol version bump. What changed in protocol version 70017 compared to 70016? Also, how does a 70017 node behave when connected to a peer that only supports 70016? from Recent Questions - Bitcoin Stack Exchange https://ift.tt/Pz5vkwX via IFTTT