What about if transaction isn't confirmed yet (was broadcasted BEFORE fork at 12:20 UTC)? When does replay protection kicks in?
Given that the fork actually occurs at 12:20 MTP (Mean Time Past)... which is theoretically about 6 blocks AFTER 1220 UTC... it gets a bit tricky The criterion for activation of the Bitcoin Cash hard fork activation is based on "Median Time Past", or MTP. This means that the chain split will not occur at exactly 12:20 UTC on Aug. 1st, but some time after.
MTP is a statistic calculated over 11 blocks, and trails behind wall clock time by about 6 blocks. This means that the last common block will be approximately the 6th block with a timestamp after 12:20pm. The block after that will be different on either chain.
If you broadcast the transaction, and it doesn't confirm before the fork actually occurs... (ie. the last common block or earlier) then it should NOT be included in the BCC network, as their miners/nodes should refuse the transaction as it does not conform to their rules... and should be regarded as invalid. Just be aware that because the fork doesn't occur until some time AFTER 12:20 UTC... that if you broadcast a transaction at 12:19 UTC, there is a chance it will still confirm BEFORE the fork actually takes place and thus be present in both chains AFTER the fork. |
|
|
|
Is it possible to use mycelium seed in electrum wallet to get BCC?
Only if you use the " Electron cash" wallet... as Electrum DOES NOT support BCC and Electrum dev does not support nor endorse ElectronCash wallet When you create the wallet in "Electron", you will need to click the "Options" button when you enter your seed and specify that it is a BIP39 seed. |
|
|
|
You'll want to include a paused "flag" and a loss counter... so, if there is a "win", you reset the lossCount back to 0... if a "loss" AND chance == 33.33 then you increment it by 1. When the counter gets to 5, you set the flag to true and use that condition to specify the betsize = 0.00000001 I assume when you say that "it resumes from the previous level" that you want it to store the old bet amount from where it paused... and then use that once it starts betting again? NOTE: this code is UNTESTED chance = 81.12
bethigh = true
basebet = 0.00000031
nextbet = basebet
losscount = 0
oldbet = 0
paused = false
function dobet()
if win then
if paused then
losscount = 0
paused = false
nextbet = oldbet * 1.59738 -- resume betting at previous level
else
chance = 81.12
nextbet = basebet
end
else
if chance == 33.33 then
losscount = losscount + 1
if losscount == 5 then
paused = true
nextbet = 0.00000001
oldbet = previousbet -- save the current bet for resuming later
elseif losscount > 5 then
paused = true
nextbet = 0.00000001
else
nextbet = previousbet * 1.59738
end
else
chance = 33.33
nextbet = basebet/3.3
end
end
end
|
|
|
|
Ah, thanks HCP. I assumed they'd both work of the same software (although bip91 has been implemented to make both networks replay-proof).
It's probably a good idea to try to empty private keys before putting them into another software (especially if the developer isn't known - if ThomasV is not the producer of electrum cash).
Yes, definitely... it is even recommended by ThomasV in his post about Electrum and BCC: BCC wallets will require you to import your seed or your private keys, which can be exported from Electrum. Doing so will expose all your Bitcoin funds associated with that seed to the BCC wallet you decide to use.
Therefore, *after* the BCC fork, but *before* you enter a seed or private key in a BCC wallet, you should move all your funds to a new Electrum wallet, with a new seed. You will still be able to use the old seed or private key with BCC, because BCC has replay protection. Wait until your funds are confirmed in your new Bitcoin wallet, before you enter the old private key in a BCC wallet. This will protect your BTC funds from rogue/untrusted software.
|
|
|
|
|
Correct, that is the point of 12 word backup seeds... your entire HD wallet and all the keys/addresses in that HD wallet can be recreated from the 12 word seed.
The note about needing to do backups, only applies to the "Singe Address Accounts" created by importing a private key
|
|
|
|
No, the only reason to create a new wallet/seed/private keys and send your coins, is so you can safely use your old seed/private keys on a BCC wallet without fear that you're exposing the keys that your BTC's are stored on. It is just a safety measure. So, even if the BCC wallet you choose is "bad" and it leaks your seed/keys, your BTC will still be safely stored elsewhere. If you don't care about BCC and don't want to use it... you can continue to use your old wallet and just ignore the bitcoin world as it goes a bit crazy for a couple of days sorting out all this hardfork mess  |
|
|
|
- Would just keeping the current Electrum wallet that contains BTC without doing anything until situation clears in the next few days, weeks or months be a sure way not to lose any BTC ?
Assuming that your computer isn't compromised by malware etc, then yes, that would work... If you have no interest in BCC, then you don't need to do anything out of the ordinary. Your BTC will remain safe in Electrum. And, in the, highly unlikely, event that something happens to the Electrum network, you have easy access to your private keys and can move your keys to another BTC wallet. |
|
|
|
It is possible from the GUI... but the catch is that the total value that you want to send PLUS the fee, must be stored in the address that you want to send from. It cannot be spread across multiple receiving addresses. If you look at the "Addresses" tab (if you cannot see "Addresses", then use the menu item "Wallet -> Addresses")... you can right click on the address you want to send from and select "Spend From"...  As you can see in this example, while I have a balance of over 11.106 BTC, if I wanted to send from mnsp6mr6P42A3CfmEhNc35h1LwgQ5X7Hsj, I can only send around 9.9 BTC. You can then enter multiple lines in the "Pay To" box:  Remember: You will only be able to send up to the amount of UTXOs (minus the required fee) in the chosen address. So in my example, I would need to have at least 0.039 + fee in my selected address to be able to send to the three addresses. If you don't have enough coins in the address you want to use, you'll need to consolidate enough coins into the address you want to use first. |
|
|
|
|
You don't send from an address. You create a transaction that transfers control of a certain value of coins from one set of private keys to another set of private keys.
You can't really influence which UTXOs controlled by your wallet are used in any given transaction using Mycelium. It has no coin control features. If you try to send the exact amount contained in one address it won't work, as it will then need to use other UTXOs to pay the fee... at which point, Mycelium's algorithm may detect a better combination of UTXOs to use to minimise transaction size etc.
|
|
|
|
...as for transaction in the case as you said (@HCP),
then creating signed raw tx with BTC wallet and pushing it to BCC network wouldn't work? am I right?
I was hoping by pushing raw tx would at least reduce the exposure of my priv key
That's correct... you cannot create a signed transaction for BTC and then broadcast it on BCC network. That is exactly what the replay protection is designed to achieve. You WILL need a BCC compatible wallet to be able to create BCC transactions after the fork. |
|
|
|
As informed 13 days ago, due to Aug 1 hardfork, ChipMixer will be closed from July 31 till situation get stable.
I'm glad I have the next 3 days off work so I can keep an eye on things... It sure is going to be an interesting couple of days  I honestly think that BCC is going to dump hard as everyone trades it out to try and make some extra BTC... I honestly don't see it surviving as viable cryptocurrency |
|
|
|
 no worries for the late reply. I was away from my office also. Ran the new script http://imgur.com/a/3ZBo1added a # to line 222, ran the script and it competed with out errors.  Doh... had an empty "else:" clause... that would explain the indentation error Glad you managed to figure it out tho. So I use the info in the parsed_wallet.txt then ?
No the parsed_wallet.txt is just a plaintext dump of your wallet file... the private keys and seeds and stuff will still be encrypted in that txt file... or they should be You should have had some addresses/private keys displayed on screen when you ran the script... It purposely doesn't write anything to a file to try and prevent data leakage... it only displays on screen (and will be in memory)... If you run with: python find_unspent_multibitHD_txes.py mbhd.wallet.aes > output.txt It will save all the output into a text file... I don't recommend this unless you're get hundreds of output lines and it is exceeding the scrollbuffer of the terminal window and you can't just scroll back up to see the addresses/private keys... |
|
|
|
|
Just make a new wallet with a new seed... The idea is to have a new seed (and therefore new private keys) and move all your BTC coins to it (AFTER the fork of course) before you use that seed (private keys) in a BCC wallet. This is so any BCC wallet you choose to use with your old seed has no knowledge of this new seed (and new private keys).
It is just an extra layer of protection should the BCC turn out to be rouge/malware... ie. You import your old seed (private keys) to "BadBCCWallet"™, and it sends your old seed/private keys off to a thief, but they can't steal your BTC as they are all now safely in a wallet with a different seed (private keys).
|
|
|
|
I'm not sure which BCC wallet I'll try to use yet, it looks like Electron Cash is still Coming Soon.
They have their github up: https://github.com/fyookball/electrumPersonally, I just copied my Bitcoin Core blockchain folder and installed a copy of BitcoinABC and set it up to use the copy of the blockchain folder. I'll probably end up pruning it to save some harddrive space |
|
|
|
You do not need to access your secret keys (private keys) to get your bcc.
You just need to do a different configuration of electrum in order to connect to a BCC node instead of a BTC node in order to get access to your BCC wallet.
This is no longer the case since BCC implemented two-way replay protection. BTC transactions will not be valid on BCC network... and BCC transactions will not be valid on BTC network. ThomasV is not implementing BCC support in Electrum at this time ( https://electrum.org/bcc.txt) If you want to transact BCC, you WILL need to export your private keys into a BCC specific wallet (ref: https://www.bitcoincash.org/ and look at "wallets"). I've seen references to an "Electrum Cash" (possibly renamed to " Electron Cash") wallet which looks to be a fork of Electrum that is intended to work with Bitcoin Cash... |
|
|
|
It really isn't that hard... If you have access to your private keys... you will be able to access BTC and BCC. How you go about doing that is entirely up to you. You will be able to access your BCC at any point in time AFTER the fork if you have access to the private keys which have coins when the fork occurs. Given that BCC has implemented Replay Protection, and that BTC transactions will not be valid on BCC network... and given ThomasV's stance on BCC ( https://electrum.org/bcc.txt), you will need to export your private keys and import them into a BCC specific wallet to be able to broadcast BCC transactions as the transactions that Electrum generates will not be compatible with the BCC network. |
|
|
|
|
No... it isn't possible.
Mainly because when the fork happens, they still use the existing history of the current BTC blockchain as the base for the BCC blockchain. So the entire history (including the fact that your transactions don't exist and all the inputs have been used in other transactions) is exactly the same at the moment of the fork.
Secondly, you wouldn't be able to rebroadcast the transactions anyway, as the BCC guys have implemented "Two-way Replay Attack Protection" to prevent exactly this sort of thing. BTC transactions will NOT be valid on BCC network... and BCC transactions will NOT be valid on BTC network.
|
|
|
|
Norton said "it only has 5 customers using it so it is unsafe." what is wrong with me being #6?
Nothing, IF you downloaded Electrum from here: https://electrum.org/#downloadBecause Electrum contains some functions involving encryption... (which is something a lot of viruses and trojans do to try and prevent detection/removal) it is quite common for antivirus software to generate a "false positive"... Antivirus software isn't always 100% accurate (and Norton certainly isn't close to being the best either.  ) There are a lot more than 5 people using Electrum... there are thousands if not hundreds of thousands... if there was a problem, we'd all know about it! |
|
|
|
Just out of curiosity, how are you checking for the addresses? Did you create a new wallet in Electrum (standard wallet, "Use a hardware device"?) and then look at the addresses generated or are you checking some other way? Also, in your original message, you said: ... So I pressed receive on my Nano S Ledger, scanned the QR code through the coinbase app and transferred them
Where did this QR code come from exactly... were you using the Ledger Chrome extension? Also, it seems like the coins are still in that address, so i wouldn't give up home just yet |
|
|
|
|
Show Posts
