EDIT: I MADE IT!!! I just had to add that line in the end: sudo make install DESTDIR=/mnt/c/workspace/bitcoin Yeah... it seems like a simple permissions error... no doubt because Windows 10 has made "C:" somewhat protected to try and prevent malware and viruses and the like... In Linux, "sudo" == "SuperUser do", so it's basically like running things as "administrator" in Windows. Just one of the many "gotcha's" of trying to cross-compile things... made slightly more complicated by running Linux through Windows!  Glad you managed to finally get it sorted... good luck with the altcoin experimentation  |
|
|
|
|
Couple of questions that might help eliminate some possibilities for what is wrong...
- Does the address show in the Electrum "addresses" tab? (might need to use View -> Show Addresses)
- At the top of your wallet in Electrum, does it say: [Standard], [imported] and does it say [watching only]?
- When you are signing the message, I assume you are putting the address in the box labelled "address" and not just in the "message" part?
- Does the address start with a "1", a "3" or "bc1"?
|
|
|
|
Ok... one last thing... did you happen to generate and send to a "native Segwit" address (aka bech32 aka "bc1") address in Mycelium?  The wallet.trezor.io wallet only supports the Nested SegWit addresses from memory... and Mycelium (and Electrum) will work with either, so you if you generated a "bc1" address in Mycelium... and sent to that, the Trezor wallet won't be able to see it |
|
|
|
What I don't understand is why someone, having discovered that a game is broken, continues to play the broken game? Were you expecting it to magically start working again? Surely, if you discovered an issue, would you not just contact support and say "Hey, I think GameX is broken, FunctionalityY doesn't seem to be working correctly"? Who knows, they might offer you a bug bounty... But to continue playing it... and on top of that also to deposit money five more times and continue to play the game just seems ridiculous.  They say the definition of insanity is doing the same thing over and over expecting a different result  |
|
|
|
Does anyone know the legal possibilities of those whose complete data has been stolen in case something bad happens to them? Is there a legal basis for a claim for damages, or perhaps on some other basis? Without having actually looked... I'd be very surprised if there wasn't the standard "We are not liable for any losses incurred by using our website, devices, systems etc" disclaimer buried in their Terms of Service somewhere. Indeed... (after I actually went and looked it up) from the website Terms of Use: ...
Crypto assets are volatile. You should be fully aware of the level of risk involved before engaging in crypto-related activities. Any loss of data, crypto assets or profit is your sole responsibility.
...
And then the Ledger Live Terms of Use: Limitation of liability
YOU EXPRESSLY UNDERSTAND AND AGREE THAT LEDGER AND ITS DIRECTORS AND EMPLOYEES SHALL NOT BE LIABLE TO YOU FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES, INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS, GOODWILL, USE, DATA, COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, OR OTHER INTANGIBLE LOSSES, RESULTING FROM: (I) THE USE OR INABILITY TO USE THE SERVICES (II) ANY CHANGES MADE TO THE SERVICE OR ANY SUSPENSION OR CESSATION OF THE SERVICES OR ANY PART THEREOF; (III) THE UNAUTHORIZED ACCESS TO OR ALTERATION OF YOUR TRANSMISSIONS OR DATA; (IV) THE DELETION OF, CORRUPTION OF, OR FAILURE TO STORE AND/OR SEND OR RECEIVE YOUR TRANSMISSIONS OR DATA ON OR THROUGH THE SERVICE; AND (V) ANY OTHER MATTER RELATING TO THE SERVICE.
THE ABOVE LIMITATIONS DO NOT APPLY IN RESPECT OF LOSS RESULTING FROM (A) LEDGER’S FRAUD, WILFUL MISCONDUCT OR GROSS NEGLIGENCE, WILFUL MISCONDUCT OR FRAUD; OR (B) DEATH OR PERSONAL INJURY.
And then the Sales Terms: ARTICLE 8 – LEDGER’S LIABILITY
TO THE FULLEST EXTENT PERMITTED BY LAW, LEDGER DISCLAIMS ANY AND ALL LIABILITY FOR LOSS OF PROFITS, INCOME, VALUE OR DATA, OR INDIRECT, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES.
YOU ARE SOLELY RESPONSIBLE FOR THE COMPLIANCE WITH THE TERMS OF USE AND THE INSTRUCTIONS PROVIDED IN THE USER MANUALS.
TO THE FULLEST EXTENT PERMITTED BY LAW, LEDGER’S TOTAL LIABILITY FOR ANY CLAIM ARISING FROM THESE TC’s, INCLUDING ANY IMPLIED WARRANTIES, IS LIMITED TO THE AMOUNT YOU PAID TO PURCHASE THE PRODUCT.
....
Basically, they refuse to accept any liability for anything... but that's fairly standard "boilerplate" stuff for pretty much any company Although, the "Gross negligence" part could possibly be argued, but that depends on the exact details of the flaw/breach that led to the data being leaked and whether it could be considered gross negligence I guess... |
|
|
|
... wallet.trezor.com
Firstly, I hope that's just a typo... it should be wallet.trezor. io Not sure if it's just because I haven't had my morning coffee... but to clarify: - Funds sent to Mycelium watching-only wallet that monitors Trezor accounts - Funds not showing when viewing wallet on wallet.trezor. ioIs that correct? If so, I haven't had any issues with wallet.trezor.io recently... I assume you're running the latest firmware and Trezor bridge etc? It could just be a slight network issue with the Trezor backend not having synced properly? |
|
|
|
Yeah, I wanted a completely different seed, but it sounds like that isn't going to be very convenient to do. Ah well, I suppose if I ever end up buying a laptop I'll install LL on that and fire up the Nano X. No rush. It's not impossible... you just need to use a decent naming convention when you are adding the accounts to Ledger Live so that you don't get them mixed up. The downside being that it basically just lumps all the accounts together in the "portfolio" and "Accounts" section... you don't have any option to segregate them by device or even passphrase etc, so depending on your reasons for wanting "independent" devices, this could be a nuisance Alternatively, as already mentioned, Electrum probably makes it easier to segregate your devices while using "one app", as you simply create a new wallet file within Electrum dedicated to the Nano "X"... and call it "NanoX_wallet" or something similar... and if you choose to encrypt the wallet, it won't even open without the device connected. The downside of using Electrum being that you will only have access to BTC. In any case, you need LL to be able to install/remove/update the coin apps and any firmware updates etc. |
|
|
|
I see you were smart and marked it "RBF = False" I noticed your transaction was still unconfirmed and thought it might be interesting to see if it could be "sniped", given that it is an "anyone can spend" address... txn-mempool-conflict (code -26)
Sadly, I don't know any miners... so no "double-spend" options available... but it is somewhat reassuring to know the system is working as intended Finally, it is interesting that the brainwallet-and-the-like-prying-bots obviously haven't tuned into this (yet?).
I think it is mostly because the general use of brainwallets really died out years ago after a lot of coin loss... well before SegWit was a thing. The only SegWit compatible brainwallet I know is https://segwitaddress.org/Sure, people keep sending coins to well known brainwallet addresses for shits and giggles or "testing" like your BTCLeak friends (abc123 anyone? )... but generally speaking, there really isn't much to be gained from monitoring/sweeping these addresses except the odd bit of dust. |
|
|
|
I suspect that the way I created the transaction is just simply incorrect. Unfortunately, I'm pretty much out of ideas at this point... and I don't have the time to go and download the Bitcoin Diamond Core client and sync it up and start messing around with it. I would suggest you try and contact the Bitcoin Diamond devs directly and see if they are able to assist. |
|
|
|
Not sure why you were not able to use the WSL with Windows 10... But I think it might have all gone wrong initially when you attempted to modify the "PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g') # strip out problematic Windows %PATH% imported var" command Modifying that PATH might have screwed up a lot of stuff as the system wouldn't be able to "find" various things while attempting to build. Also, make sure that your WSL Ubuntu is Ubuntu 18.04. Execute the following command in WSL Ubuntu and make sure it says 18.04: Should show something similar to:  Using WSL Ubuntu 18.04, I simply followed each step here: https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md, and I did not have any issues... you have to copy/paste each command one at time... and you need to let each command finish before you enter the next one. Note that some of the commands can take a LONG time to finish (like 10-20+ minutes etc)... so you need to wait until you are back at the "$" prompt before you do the next command! Anyway, after doing all the steps... and then doing: make install DEST=/mnt/c/workspace/bitcoin
It copied all the .exe files to my C:\workspsace\bitcoin\bin directory:  
Note: The /mnt/[DRIVE LETTER]/ notation is just the way that the Windows Subsystem for Linux (WSL) is able to interact with your Windows drives/file system... Windows and Linux use very different setups... so when using the WSL system, you have to use Linux notation. Basically, your Windows drive letters C:, D: etc are available in /mnt/c and /mnt/d etc...So: C:\workspace\bitcoin\bin == /mnt/c/workspace/bitcoin/bin Also, I see you're wanting to build your "altcoin"... do note the important warning here: Note that for WSL the Bitcoin Core source path MUST be somewhere in the default mount file system, for example /usr/src/bitcoin, AND not under /mnt/d/. If this is not the case the dependency autoconf scripts will fail. This means you cannot use a directory that is located directly on the host Windows file system to perform the build.
If your altcoin source code is in C:\coin, you WILL NOT be able to compile it from this location... you'll need to copy it to somewhere within in the WSL Ubuntu file system first! For instance, if your altcoin source code is in C:\coin, you can use the following to copy it to the "mycoin" directory in your home dir in WSL Ubuntu filesystem: cp -r /mnt/c/coin ~/mycoin
Then instead of doing the following commands: git clone https://github.com/bitcoin/bitcoin.git
cd bitcoin
You can just do: And then continue following the rest of the instructions... EXACTLY as they are shown on that page... just copy/paste them, one line at a time. |
|
|
|
Basically, Electrum generates the " extended key" at m/84'/0'/0' and then uses that extended key as the root key... it then starts generating addresses as m/0/0, m/0/1, m/0/2 etc. (which are actually equivalent to: m/84'/0'/0'/0/0 etc) You can test this using Ian Coleman's BIP39 mnemonic converter: humble shoe steel champion good fall manual okay carbon eye bamboo minimum
zprvAWgYBBk7JR8GjBZDbo7MdVF9joK6GY581EeVAFTuPrqnDimH8bCqnSr7UNCr9Xo2YV8637rAAUNtGqqBNNF14NY37fu4B6WmV3wUxHmoMAB
Select BIP84 tab... gives us these account extended keys:  and this address:  So wee get an Account extended private key of: zprvAe4w8ERG69nfgjYSwkzaRokCDBrnaXPQykiBv6fDpFTkDiWDjBHJhQkeXJAKFAGdruUzict2rq5FfKPZRfv4qmvBrYzTLVXwoF2qXXjpHWy
and the matching account extended public key: zpub6s4HXjx9vXLxuDcv3nXanwgvmDhGyz7GLydniV4qNazj6WqNGibZFD58NYQBKk7yLcx3jTo87vxqG86CjpqFpXdUeSXQRTubZaxehpSvnEY
Which matches the one displayed by Electrum:  And these are the keys that Electrum stores in a BIP39 keystore/wallet file: 
If we use this account extended private key as the BIP32 root key at the top:  Select BIP141 and use "m/0":  We can see we derive the same addresses, with the path m/0/0:  And because it's not hardened, you are able to derive all the addresses from the the matching "account extended pubkey"... you can also test this by putting the account extended pubkey in as the BIP32 root key, selecting BIP141 tab and setting derivation to m/0... you'll get the same bc1qs702fa457e4qyqwz7e0pcwlp2cz0400h8lfu6h address I suspect this is "by design", so you can actually use the "pubkey" to create watching-only wallets for cold storage setups etc. |
|
|
|
...
One more member of this Ledger cultIt would appear that you didn't read anything I wrote except for the "I like it" part... so therefore I am part of this so-called "Ledger Cult"  Instead of deciding what you think I think of Ledger, lets try reading what I actually wrote: ...
And I'm not sure why you seem to think that everyone here "worships" the Ledger... I like it, but as someone else mentioned, it's far from perfect
...
Yep, obviously I'm the Ledger Cult Leader Can anything bad be said about Ledger hardware wallet or not?
Obviously, there are lots of "bad things"™ that can be said about it... the buttons feel flimsy... entering PINs/Passphrases is problematic... the screen can't display all the data at once... their native software has a ton of issues... and some of their UI/UX decisions are just terribad, imo... adding all these shitcoins and shittokens instead of providing some "proper" features etc. Having said that, I can understand why they chose that path. Does everything happening with Ledger needs to be justified? I'm not even sure what you mean by this? Justified by whom? Ledger? The "cult members"? Their detractors? |
|
|
|
I guess that depends on if you're going to use them with the same seed or set them up as "independent" devices with different seeds etc... If they're "identical" (ie. both devices with same seed), you basically just plug and play with either device... and you can control the accounts with either device connected. if you want them to be independent, it gets a bit trickier, as you have to add all the accounts from both devices and Ledger advise you to name the accounts so you know which account belongs to which device. It's the same for access any "hidden" accounts using the 2nd pin (different passphrases etc)... when you "add account" you just connect and unlock the device using the other PIN/Passphrase and it'll find the "hidden" accounts etc. Refer: https://support.ledger.com/hc/en-us/articles/360007646053-Use-multiple-Ledger-devices |
|
|
|
|
I possibly broke something... from the error output in ElectrumBCD, it seems to have an issue parsing the "sequence" number of the inputs.
What error do you get in Bitcoin Diamond Core?
|
|
|
|
In Electrum, following those steps:
Tools > Preferences > Use Replace-by-Fees
@tranthidung, just so you know, you might want to ease up on the "highlighting"... it doesn't play nicely with Dark Mode scripts  |
|
|
|
Ok... so I have been experimenting with coinb.in... and I think this unsigned raw transaction should do what you want... 0c00000005ced76461a72202df3012dc24e57c6753a6785fc5ddbb99c5b6222eac0dc59fbe010000004a042053005fb1754104ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85acfdffffff32956964f917f762e21f28cb91bb193d0dc6dbfc8d57ca7620060f378dc1ee34000000004a042053005fb1754104ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85acfdffffffcd960fbe24ad5466a1c314fb295666f27d0cd8f4b4f6fc5c3b722bb2035ee338010000004a042053005fb1754104ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85acfdffffffee0e52a3ede1df1b97e4d54d33df60864c9033786db298ed5e5cc8984d8808b9010000004a042053005fb1754104ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85acfdffffff6e9e9b9213dda29a98971ca748147e6f7f61bf6a212d8cea25993ac79dbe4b7f000000004a042053005fb1754104ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85acfdffffff0190966d54030000001976a914e074383cfb31e11c236d284960437d515b6970d688ac2053005f
decoded raw unsigned transaction: {
"txid": "39bc5bb4adc2cb5ba16a3f9c1b0831acff33e73d19952a1d7838a28a5940b074",
"hash": "39bc5bb4adc2cb5ba16a3f9c1b0831acff33e73d19952a1d7838a28a5940b074",
"version": 12,
"size": 619,
"vsize": 619,
"weight": 2476,
"locktime": 1593856800,
"vin": [
{
"txid": "be9fc50dac2e22b6c599bbddc55f78a653677ce524dc1230df0222a76164d7ce",
"vout": 1,
"scriptSig": {
"asm": "1593856800 OP_CHECKLOCKTIMEVERIFY OP_DROP 04ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85 OP_CHECKSIG",
"hex": "042053005fb1754104ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85ac"
},
"sequence": 4294967293
},
{
"txid": "34eec18d370f062076ca578dfcdbc60d3d19bb91cb281fe262f717f964699532",
"vout": 0,
"scriptSig": {
"asm": "1593856800 OP_CHECKLOCKTIMEVERIFY OP_DROP 04ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85 OP_CHECKSIG",
"hex": "042053005fb1754104ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85ac"
},
"sequence": 4294967293
},
{
"txid": "38e35e03b22b723b5cfcf6b4f4d80c7df2665629fb14c3a16654ad24be0f96cd",
"vout": 1,
"scriptSig": {
"asm": "1593856800 OP_CHECKLOCKTIMEVERIFY OP_DROP 04ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85 OP_CHECKSIG",
"hex": "042053005fb1754104ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85ac"
},
"sequence": 4294967293
},
{
"txid": "b908884d98c85c5eed98b26d7833904c8660df334dd5e4971bdfe1eda3520eee",
"vout": 1,
"scriptSig": {
"asm": "1593856800 OP_CHECKLOCKTIMEVERIFY OP_DROP 04ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85 OP_CHECKSIG",
"hex": "042053005fb1754104ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85ac"
},
"sequence": 4294967293
},
{
"txid": "7f4bbe9dc73a9925ea8c2d216abf617f6f7e1448a71c97989aa2dd13929b9e6e",
"vout": 0,
"scriptSig": {
"asm": "1593856800 OP_CHECKLOCKTIMEVERIFY OP_DROP 04ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85 OP_CHECKSIG",
"hex": "042053005fb1754104ac3cf2516879f0fdb61d237f99dcfb48f38c850e7d2df17b503c013673e734b8dc2c51331319b2e9e5d3d1067ad6d3378f9b719de5b0eaa8723d62a8ab39fa85ac"
},
"sequence": 4294967293
}
],
"vout": [
{
"value": 143.01370000,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 e074383cfb31e11c236d284960437d515b6970d6 OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a914e074383cfb31e11c236d284960437d515b6970d688ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"1MTob4BxRmv7FvcQaa2VLwniafMxYE2X32"
]
}
}
]
}
Essentially it takes the BCD UTXOs from: http://explorer.btcd.io/#/tx?tx=be9fc50dac2e22b6c599bbddc55f78a653677ce524dc1230df0222a76164d7cehttp://explorer.btcd.io/#/tx?tx=34eec18d370f062076ca578dfcdbc60d3d19bb91cb281fe262f717f964699532http://explorer.btcd.io/#/tx?tx=38e35e03b22b723b5cfcf6b4f4d80c7df2665629fb14c3a16654ad24be0f96cdhttp://explorer.btcd.io/#/tx?tx=b908884d98c85c5eed98b26d7833904c8660df334dd5e4971bdfe1eda3520eeeand http://explorer.btcd.io/#/tx?tx=7f4bbe9dc73a9925ea8c2d216abf617f6f7e1448a71c97989aa2dd13929b9e6eand sends them to BCD Address: 1MTob4BxRmv7FvcQaa2VLwniafMxYE2X32 (which was the address that I got from your first raw transaction) using a fee of 7000 BCD sats. NOTE: I have no idea of what a "good" BCD fee actually is, but I figured that 7000 BCDsats is ~USD$0.00006 so it shouldn't be a problem . I had to manually input the UTXOs into coinb.in and adjust the values so they match the actual BCD values (rather than the BTC values) and then I manually modified the first bytes so that it sets the "version" to 12. IF, 1MTob4BxRmv7FvcQaa2VLwniafMxYE2X32 is indeed the BCD address you are trying to send to, then theoretically should be able to put this into Bitcoin Diamond Core and then signrawtransaction using the privkey that matches the pubkey you used to create the 3KMMUTT5794GBtscY78Z6Dn5MQNkwTR8bJ address... and then broadcast it. However, if it isn't, then let me know what address you do want to send to, and I'll recreate the unsigned raw transaction with the correct address. I would strongly suggest that you use decoderawtransaction in Bitcoin Diamond Core first, and double check that everything looks correct before you broadcast this. It's quite possible I've made a horrendous mistake somewhere and you could lose all your BCD. |
|
|
|
And for the record, I don't think the Bitcoin wiki (linked before) should read "Bech32 pubkey hash or script hash", since we have determined that a script hash won't produce a usable address.
But it will... just not the "script hash" that you are thinking of... refer: https://bitcoincore.org/en/segwit_wallet_dev/#native-pay-to-witness-script-hash-p2wshNative Pay-to-Witness-Script-Hash (P2WSH)- Native P2WSH is a scriptPubKey of 34 bytes. It starts with a OP_0, followed by a canonical push of the scripthash (i.e. 0x0020{32-byte scripthash})
- Same as P2SH-P2WSH, scripthash is SHA256 of the witnessScript.
- When spending a native P2WSH, the scriptSig MUST be empty, and the witness stack format and signature generating rules are same as P2SH-P2WSH (including the requirement of using compressed public key)
NOTE: emphasis added As per the P2SH-P2WSH docs on that page, the "scripthash" is the SHA256( witnessScript)... it is not double SHA256 nor RIPEMD160(SHA256) etc. |
|
|
|
U right ive point this out in an wrong way i dont mean the keys import or sweeping i mean after the import of the keys.
for ex. when i need it on an other wallet to gather funds, then should i sweep or to just send the keys to the other wallet
just the option which gains more privacy preferentially in relation to funded coins which comes from chipmixer.
If you have already imported the keys into an Electrum wallet and you want to move the funds to another wallet... just send them in a transaction as you normally would any other transaction. Although, you might want to consider using the "spend from" option in Electrum, so that you avoid accidentally linking UTXOs back together by including them all as inputs to the same transaction. Also, it would be a go idea to avoid sending all the funds to the same address... as again, that creates a link between them all. This is effectively the same thing as "sweeping"... all sweeping does is "simplify" the process for you and means you don't need to import any keys. Instead, it will take a private key (or keys) and then create a transaction that sends all available UTXOs controlled by those keys to an address of your choosing. Probably not ideal, as you can only specify ONE destination address when sweeping, and that will relink all the UTXOs back together again (unless you sweep each key individually). So, your options are: 1. Import ChipMixer keys, then create transaction to send coins to other wallet (new keys) or 2. Sweep ChipMixer keys directly into other wallet (new keys) or 3. Do neither and leave the coins on the ChipMixer keys until you need to spend them Neither importing nor sweeping is any more "private" than the other if you need to move the coins to another one of your wallets... they will both end up creating transactions that take coins from the ChipMixer addresses and send them to your addresses... and in both situations you need to take steps to prevent them all being relinked. Leaving the coins on the ChipMixer keys until you wish to send them to someone else is probably better for privacy... but security wise is not great because ChipMixer have knowledge of the private keys and you have to trust them not to steal them (or leak the keys). So, in this case, it's a trade-off between privacy and security. Which option is better for your particular use-case is only really something that you can determine. |
|
|
|
0c0000006fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d619000000000006ced76 461a72202df3012dc24e57c6753a6785fc5ddbb99c5b6222eac0dc59fbe0100000000ffffffff32 956964f917f762e21f28cb91bb193d0dc6dbfc8d57ca7620060f378dc1ee340000000000fffffff fcd960fbe24ad5466a1c314fb295666f27d0cd8f4b4f6fc5c3b722bb2035ee3380100000000ffff ffffee0e52a3ede1df1b97e4d54d33df60864c9033786db298ed5e5cc8984d8808b90100000000f fffffff6e9e9b9213dda29a98971ca748147e6f7f61bf6a212d8cea25993ac79dbe4b7f00000000 00ffffffff44acf3e12307b616ccf089bee698d761a536d624a2911717fa48599db5f5789900000 00000ffffffff01f2678908000000001976a91452c73e9034e81ab1180a27119f44edab85dda860 88ac00000000
That one returns "missing inputs" error... You might have to do some investigating in BCDExplorer... find the addresses that you're spending coins from and make sure that the UTXOs you're trying to spend actually exist and are unspent on BCD blockchain. I suspect the issue comes from the fact that BCD's "replay protection" partly involved making the BTC:BCD ratio 1:10... (but mostly the version "12" change I believe) so you can't just take a BTC transaction and rebroadcast it on BCD as all the values will be incorrect and the UTXOs will be invalid. Hopefully, you don't have too many UTXOs/addresses to check, otherwise it could be a very labour intensive task... |
|
|
|
BitcoinTALK-PROTECT
You owe me a new keyboard... and a beer!   gets my vote for Post of the week! |
|
|
|
|
Show Posts
