You can update this now, no need for manual import through the console/command. Bitcoin Core version 23.0 now creates descriptor wallets with Taproot parent descriptors by default. And it's now possible to request Bitcoin taproot " bech32m" address from the GUI's receive tab if the wallet has the parent descriptor:  Reference: Wallet- Descriptor wallets are now the default wallet type. Newly created wallets
will use descriptors unless descriptors=false is set during createwallet, or
the Descriptor wallet checkbox is unchecked in the GUI.
- Newly created descriptor wallets will contain an automatically generated tr()
descriptor which allows for creating single key Taproot receiving addresses.
|
|
|
|
-snip- I know some services online allow us to create transactions, but they could use bitcoin core in the backend for it. And I start this post to see if it was possible without this main software.
Just do not use any transaction generation software at all so you can make sure that Bitcoin Core isn't involved. Except for the signing part since you can't compute the signature by hand. Use your Notepad or any text editor: First, list all the data that you need - input (TXID:VOUT), output's scriptPubKey. Example ( mainnet): input: aaf952cd5604ee02fdcb1c700c8f2f0759af55b8b468adff91ef468540ac336f
vout: 0
value: 100000 satoshi
output: bc1qe55yu3dkw7rc7n8kk2r4r2nq3phagpxnzljtm2
scriptPubKey: 0014cd284e45b677878f4cf6b28751aa60886fd404d3 [22 Bytes in decimal = 16 in HEX]
value: 0.00099720BTC = 99720 satoshi = 0000000000018588 in HEX [8 Bytes] Then construct a transaction by following this structure: learnmeabitcoin.com/technical/transaction-dataFor the fields with " Reverse Byte Order", use this tool: learnmeabitcoin.com/tools/swapendian/ ( or do it manually) Manually constructed transaction from the example above: 01000000016f33ac408546ef91ffad68b4b855af59072f8f0c701ccbfd02ee0456cd52f9aa0000000000ffffffff018885010000000000160014cd284e45b677878f4cf6b28751aa60886fd404d300000000 Broken down into parts: 01000000 (version: 1 in 'reverse byte order')
01 (input count: 1)
6f33ac408546ef91ffad68b4b855af59072f8f0c701ccbfd02ee0456cd52f9aa (input's txid in 'reverse byte order')
00000000 (vout: 0 in 'reverse byte order')
00 (scriptSig size)
[no scriptSig]
ffffffff (sequence in 'reverse byte order')
01 (output count: 1)
8885010000000000 (value in 'reverse byte order')
16 (ScriptPubKey size)
0014cd284e45b677878f4cf6b28751aa60886fd404d3 (ScriptPubKey)
00000000 (locktime in 'reverse byte order') Lastly, sign the raw transaction using your preferred software ( I used Bitcoin Core since it's Taproot). Screenshot that shows it's valid after signing:  ( transaction is not broadcasted) |
|
|
|
Fee Estimation failed . fallback fee is disabled. Wait a few blocks or enable -fallbackfee
i just let it do its thing while watching a movie and now it's cleared.... guess he had to catch up some blocks for good :)
It indeed required to catch-up because the fee estimation algorithm will have to check your mempool and blockchain for the latest transactions' fee rate. Next time if you need to send a transaction right away: you can manually set the fee rate by clicking " Choose..." next to the transaction fee. It will let you set a custom transaction fee at BTC/kvB; e.g.: 0.00001000 for 1sat/vB. |
|
|
|
Here are some quotes of satoshi's posts that support the previously given answers... From this topic: /index.php?topic=571.msg5712#msg5712For " shorter addresses" -snip- To make Bitcoin Addresses short, they are a hash of the public key, not the public key itself. Security of HASH160 -snip-
Bitcoin Addresses are the only place where 160-bit hash is used. Everything else is SHA-256. They're calculated as:
bitcoinaddress = RIPEMD-160(SHA-256(publickey))
Correct me if I'm wrong (please, and I'll gladly eat crow) but I think it would be hard to use an analytical attack on RIPEMD-160 in this case. An analytical attack prescribes a certain range or pattern of inputs to try that will greatly increase your chance of finding a collision. Here, you don't have that kind of control over RIPEMD-160's input, because the input is the output of SHA-256. If an analytical attack helps you find an input to RIPEMD-160 that produces a collision, what are you going to do with it? You still have to get SHA-256 to output that value, so you would still have to break SHA-256 too.
For brute force, RIPEMD-160(SHA-256(x)) is no stronger than RIPEMD-160 alone. But for analytical attack, it seems like you must analytical attack both RIPEMD-160 and SHA-256. If I'm wrong, then the strength is the same as RIPEMD-160 and the SHA-256 only serves as one round of key strengthening.
|
|
|
|
It would be a digital ape fight for the reward and you by depositing on the address will make a number x of apes around the world at maximun excitement.
A fight of whon collect first, are you ready to fight? Are you fast enough?
Most of those " apes" have already set-up a system that can automatically sweep bitcoins sent to famous leaked private keys. It's not about having fast reactions, it about having the fastest node, code, internet, etc. which IMO isn't exciting at all. Creating a group that will watch this specific address could attract donators or even member of the group themselves will donate, yes. But the ones who'll likely win are still the ones who've been collecting the funds, not the ones who are unaware of the info above. |
|
|
|
-snip-
However, if I understand well what I have to do is :
-Choose the option "Create New Wallet"
-When the dialog box asks "What kind of wallet do you want to create ? " --> I have to choose "Import bitcoin addresses or Private keys"
-Enter the private key of the "Cascasius" coin in the dialog box and click on "Next"
-After that, my Electrum wallet (the new one then) should show exactly 1.BTC as balance and I will have the possibility to send the amount on the exchange platform of my choice
You can still create another wallet while another instance is open, use the menu " File->New/Restore" to go to the install wizard, that will enable you to create a new wallet. Just make sure to remember the wallet's name so you wont mix them up with each other if you forgot about the first one. |
|
|
|
Bumping this quite old thread to include a solution involving today's latest Bitcoin Core version ( v23.0). It's now possible to export the parent descriptor with xprv key by using the command: listdescriptors true. You can get your address' prvKey with the help of Iancoleman's BIP39 tool ( or any alternative). Steps: - First use the command: getaddressinfo <address> and take note of the result.
- Export the parent descriptor (private) with the command: listdescriptors true.
- Select the correct parent descriptor based from the address' script type (pkh, wpkh, sh),
also check if it's a descriptor for receiving or change addresses ("internal": false = receiving | true = change); then take note of its xprv key. - Launch BIP39 tool (offline) and paste the xprv key as "BIP32 Root Key".
- Select the correct derivation path as described in the descriptor, the derived addresses and private keys will be listed below the page.
If the address is not in the list: In getaddressinfo's result, look for "hdkeypath":" to see the index ( last digit), since the tool will only show 20 by default; generate more rows if it's 20+. Also check if the path is correct. For Taproot descriptors, the suggested tool doesn't support it yet. |
|
|
|
Not possible to select UTXO in Android version of Electrum! Very bad, I cannot pay anythng because transaction cost is tens of dollars.
Response:
-snip-
The drawback is if the unwanted and preferred UTXO are tied to the same address, you can't select them individually.
This does not work. Addresses are not UTXO. I have old-format address, so the option "Addresses" show only one entry. However, I have tens of UTXO's on that address, so when I set up payment, it is sourced by many UTXO's and fee is multiplied by number of these UTXO's.
Yep, that's the " drawback" that I've described in that response. So your wallet is [imported] and consist of a single private key, Electrum is designed to spend all UTXO that's tied to the same address to consolidate them, that's backfiring for some Electrum users. The only only-Electrum solution that I can suggest is to use a " watching-only" desktop Electrum to create your transaction, then export the unsigned raw transaction ( via QR) to your Android Electrum to be signed and broadcast. Note: Since you'll only import the address and not the prvKey to a desktop Electrum, you can use any PC ( borrow or rent) to set it up. The only issue is privacy which you don't actually have in the first place since Electrum is an SPV wallet. |
|
|
|
Not possible to select UTXO in Android version of Electrum! Very bad, I cannot pay anythng because transaction cost is tens of dollars.
That's unfortunate but there's a workaround. You can still freeze addresses in Android Electrum so its associated UTXO(s) wont be used in your transaction. To get there: - Tap menu (3-dots), select "Addresses".
- Tap the addresses with the UTXO that you don't want to include then tap "Freeze".
- Frozen value will switch from "False" to "True".
- Do the same to the other addresses of your choice.
The drawback is if the unwanted and preferred UTXO are tied to the same address, you can't select them individually. BTW, it's off-topic to this thread. If you have further concerns, please create a new thread. |
|
|
|
There's dumpprivkey <address> command to export an address' private key. Although it will not work in descriptor wallets. For filtering addresses, use listtransactions "*" "100" to list the wallet's transaction together with the associated address(es). Replace " 100" if you think the wallet has more than 100 transaction history. More info about the commands: |
|
|
|
The ERC20 token "BBTC" in the screenshot must be "Binance Wrapped BTC",
its contract address is 0x9BE89D2a4cd102D8Fecc6BF9dA793be995C22541.
It's interesting that I can't find this BBTC shitcoin listed on Binance exchange, but only on Hotbit, Curve and ZKswap, there is almost zero volume, and this could be just one more worthless scam. -snip-It's not meant to be traded that's why it's not listed there. It's only an alternative means to withdraw/deposit/transfer Bitcoin through their so-called " Networks" which are actually Bitcoin-value-equivalent tokens in various blockchains including their Binance Smart Chain; in OP's case, Ethereum ERC20 token. Those tokens are useless outside of the supported exchange. |
|
|
|
I've looked up BBTC some baby Bitcoin shitcoin that is worth exactly $0. So, the question is does this work? I don't think core wallet even allows to send to 0x addresses.
The ERC20 token " BBTC" in the screenshot must be " Binance Wrapped BTC", its contract address is 0x9BE89D2a4cd102D8Fecc6BF9dA793be995C22541. Basically, it's a token with same value as BTC but only for the supported exchange; if sent to Binance, they will credit it as a Bitcoin deposit. However you can't send real bitcoins from a Bitcoin wallet. |
|
|
|
-snip-
if hacker hack from multibit，why wait i change to electrum hacker only hack？hacker can see my private key when i key in electrum？？
The hacker might got access to your MultiBit only in June 2021. The thing is, the funds were sent while Electrum is offline for a long time, the most probable way for the hacker to steal your bitcoins that way is to get access to the address' private key then import it to his own wallet to spend it himself, so it's either one of the two options. The delay may be caused by some hindrance which no one knows, it depends on how you dispose of MultiBit and its backups after you imported the prvKey to Electrum. MultiBit doesn't have to work, he just have to get the wallet file to export the private key from it. Note: The bitcoins wasn't actually moved to Electrum, importing the private key doesn't mean that it's sent to that imported Electrum wallet; Importing the prvKey just granted your Electrum access to the funds, but it's still accessible using the original wallet. |
|
|
|
Try if BTCRecover is faster than that tool: github.com/3rdIteration/btcrecoverThe command should look like this if you already have a list of possible passphrases: btcrecover --brainwallet --addresses 18wASW... --passwordlist dictionary.txt |
|
|
|
Yes, that's the one. So it seems like it's an " [imported wallet]" and not " [imported watching-only]", which you have the key. Together with the other screenshot that you've PM'ed me, the transactions matched with the address from your deleted reply. Now, we can rule out one of the possible cause that's mentioned by others. 2015 i create wallet from multibit ，
2021 march i transfer to electrum，have make some transfer。
2021 april is my last check，after check i never open again and no connect any network
2021 june hacker hack，
2022 april i open check again all gone。
electrum wallet i download from electrum webside version 4.0.9
Judging from the dates and the screenshot's Electrum version, v4.0.9 ( 2020-Dec-18 ~ 2021-Mar-30) matched the latest version at that time. If it's a fake version, the funds would've been stolen a few moments after you unlocked the wallet, but it happened months later. It's highly unlikely that it's a fake Electrum ( but it's much better if you can verify electrum's signature). The other possibilities that I can think of are: - [1] Since it's never opened while it's hacked, the hacker must had access to your private key. Example, from your backup or from [2].
- [2] Your MultiBit wallet may be accessed by the hacker. Since you just imported the private key to Electrum, the fund is still accessible using the key in your MultiBit.
Note that deleted files can still be restored unless the disk was zero filled or physically destroyed.
|
|
|
|
TQ for all reply my msg -snip- i think is electrum wallet have bug,dunno hacker how to use the bug to hack my wallet
If it's a bug in Electrum, every user should have been hacked the same way as you. The problem here is you never tried what's suggested like verifying electrum or providing screenshot, just jumping to conclusions. But since it's really unrecoverable and finding the cause doesn't seem to concern you, we can wrap this thread up. Most of your info doesn't add up anyways. |
|
|
|
here can share photo？
Upload it to imgbb.com or other image hosting site, then paste the link of the image to your reply. You should also verify if your Electrum is not a fake, follow these instructions to verify its signature: https://bitcoinelectrum.com/how-to-verify-your-electrum-download/BTW, if you're looking for a way to find the culprit, only Binance can help you with it. |
|
|
|
-snip- i dunno how the hacker can steal my btc on electrum wallet surface。the last i login check 2021 April，after check i never open the surface ，until 2022.4.24 i open check again my btc already 0 ，my electrum wallet have password and i never give any one my private key also can be hack。
It will be easier to check how if you can provide a screenshot of electrum. or at least the words written at the 'title bar' ( top of Electrum), example: Electrum 4.2.0 - wallet_1 [imported - watching only] Also, did you created the wallet yourself or was it given to your by someone? |
|
|
|
|
Show Posts
