Firstly, you might like to investigate the "Edit" button as well... Multi posting like that is frowned upon. Secondly, the developers totally understand. It is you that doesn't get it. A lot of people like the "Be your own bank" idea... but dislike the implied "you are now responsible for your own security"... they're "lazy" and just want everything served up on a plate... so they use online (centralised) services where they don't control their private keys... then they moan and whinge like crazy when it all goes wrong and all their coins disappear due to a server hack... or the service changes their terms and conditions and jacks the fees up... or starts demanding AML/KYC identification and blocks their accounts. It happens time and time again... and still people seek the "safety" of online crypto services For some reason, people these days seem to shun responsibility... it's always "someone elses fault" in today's "class action lawsuit" world... If you want to use an online service, no one is stopping you... but it carries risk as well... you need to decide what level of risk you're willing to carry... and how you want security and convenience to balance out. My suggestion if you truly want to embrace crypto: Read, Learn, Be Happy
|
|
|
If I have 5 BTC in my electrum Wallet, how can I test with just a little bit?
For example, in my electrum Wallet I have: address 1: .002 BTC address 2: 2 BTC address 3 3 BTC
Total BTC: 5.002
How can I just test with the .002 BTC ?
Just export the private key for "address 1" from Electrum and import into a BCC wallet... Step 1. Goto the addresses tab... if you don't see it: "Wallet -> Addresses" Step 2. Right click "Address 1" (the one that has 0.002 BTC) and select "Private Key" Step 3. Input your password when prompted and copy the private key. Step 4. In ElectronCash, create a new wallet ("File -> New/Restore -> Standard wallet -> Use private/public keys") Step 5. Paste in the private key and you should see 0.002 BCC in your wallet. NOTE: you may need to alter the network settings as per this post to get ElectronCash working right: https://www.reddit.com/r/btc/comments/6qyn18/electroncash_notice_how_to_select_bitcoincash/
|
|
|
You don't... at least not with Electron Cash for the moment: https://github.com/fyookball/electrum/issues/6As I suspected, MultiSig (and therefore 2FA) is broken in Electron Cash. I suspect 2FA won't be fixed in a hurry as I don't think TrustedCoin are going to implement BCC support any time soon... However, the Electron Cash devs might fix MultiSig which means you could restore using 2FA seed and disable 2FA which will make your wallet a 'normal' MultiSig... So, the short answer is: Wait for Electron Cash Dev to fix MultiSig
|
|
|
OP isn't using a multisig though? I think that's just a plain wallet.
2FA IS a MultiSig... it's a 2-of-3, where you have 1 keys... and TrustedCoin has 1... and the 3rd is "hidden" in your seed. Even if you restore a 2FA from seed and disable the 2FA functionality... it is STILL a 2-of-3 wallet... it's just the restore process puts 2 keys into your wallet, so you can provide 2 signatures and don't need TrustedCoin anymore... @hcp, did you use electron cash to get yours and have you managed to sign a transaction from it yet (or are you also on a 2FA/multisig wallet?
No, I used BitcoinABC...
|
|
|
i get "transaction rejected by network rules" 16 mandatory script verify flag failed - signature must be zero for failed check-(multi)sig operation after imported an electrum btc wallet with 2fa into electron cash wallet and sending bitcoincash coins to another electron cash address. the bitcoin cash coins are correctly seen but im unable to send them
Is this something to do with the fact there isn't actually a block on the network?
Probably more likely that Electron Cash is not able to support 2FA properly. BCC transactions are signed in a different way to BTC transactions due to the replay protection. When you use 2FA, it's effectively a multisig that you send to TrustedCoin to sign. They only know BTC so will be signing it as a BTC transaction... so the transaction will be "invalid" on the BCC network, and it will be rejected, hence the error. If the OP restored using a 2FA seed and disabled the 2FA, I suspect it might be that MultiSig in Electron Cash is broken... EDIT: Yep... MultiSig in Electron Cash is broken: https://github.com/fyookball/electrum/issues/6
|
|
|
The ledger peeps wrote up all you need to know here: http://support.ledgerwallet.com/knowledge_base/topics/bitcoin-cashAt the moment, Bitcoin, UASF and SegWit2x are all on the same chain... they will only be split later (if at all) according to the rules of UASF and SegWit2x. If in doubt, just pick Bitcoin chain for now. So, send from "Old" wallet Bitcoin Chain to "New" wallet Bitcoin Chain. Then use the "old" wallet to do whatever you want with BCC. If you do nothing... then your BTC and BCC will just sit on the private keys that they're on now. The only risk is that BCC might dump to zero and become worthless
|
|
|
At the moment (and I suspect for the forseeable future): No, Armory is not compatible with BCC. You can't get BCC with Armory. You'll need to use a BCC wallet. Check here: https://www.bitcoincash.org/ - The choices are a bit limited at the moment... To get your BCC, you need your private keys. Suggest you create a new Armory wallet, move all your BTC to new wallet... then use old keys to "claim" your BCC using the BCC wallet of your choice. This method should protect your BTC as the BCC wallet won't have access to the new keys.
|
|
|
Yeah... I'm not sure about some of his claims either... It would seem that the OP must trust the RAR devs more than Crypto-wallet devs... Is RAR opensource? ummm NO. OP, do you know for sure that RAR has no: "bugs, glitches, backdoors, ... etc that either allows them to be hacked or they screws up on their own, or both." I'll go ahead and guess no... "maximum security (free of 3rd-party trust)/maximum trustless" Are you sure about that? All you are doing is switching your trust from one software/hardware provider to another (with closed sources)... But hey, you found a system that works for you...
|
|
|
Have you tried following the information released by the Ledger dev's here: http://support.ledgerwallet.com/knowledge_base/topics/bitcoin-cashSeems you need to update to latest Ledger Nano S firmware, install a "BCH" (aka BCC) app on your device, and update the chrome extension. You should then be able to choose between Bitcoin and Bitcoin Cash when you go to use the chrome extension.
|
|
|
"Safest" and "Online" are pretty much mutually exclusive... if you value "safety" for your crypto currencies... don't use online/web wallets. You only need to look at history to see why (Mt. Gox, Bitfinex etc). For Bitcoin, a good place to start for a wallet is here: https://bitcoin.org/en/choose-your-walletPersonally, I'd recommend Bitcoin Core (yes the initial sync takes a while, but it's worth it. Plus, you can run in pruned mode if hard drive space is an issue)... or Electrum (Lightweight, SPV wallet with an activity developer and active community).
|
|
|
You're confusing wallets and addresses... and it sounds like you're not familiar with change addresses: https://en.bitcoin.it/wiki/ChangeI'd also recommend this: https://en.bitcoin.it/wiki/Coin_analogy - It helps explain why change is created and why inputs are used the way they are... and how outputs are created. As for your transaction, if you can post the Transaction ID, it would be easier to tell exactly what has happened, but I'm guessing you have simply sent the amount you wanted to the Exchange and the "change" has been returned to a change address in your wallet. If you look on the "Addresses" tab, you should be able to see the 2nd "unknown" address... (you may need to expand the "Used" and/or "Change" sections)
|
|
|
You have nowhere to turn... those coins are gone. Honestly, I'm sorry for your loss, but you are just wasting time by attempting to get them back. There is no link between IP addresses and BTC addresses...
|
|
|
my concern is that you send 1theycehFHdnsxxx pre AUG 1 address to a new 3BTC address, and inadvertently send your BCC to the same address, but don't to have the privkey as this 3xxxx simply does not exist, but your some how cleared out your old address and sent it to a key in BCC.
That can't happen because BCC has two-way replay protection... BTC transactions are not valid on BCC network... and BCC transactions are not valid on BTC network. You cannot accidentally clear out "BCC" by sending BTC transactions (and vice versa). Or you send BTC to older 1address but some how it does not got through and goes to and 3xmcnc mapped address, becuase the new protocol block hash or whatever acts that way.
And again, no... if you send to a 1bitcoinAddress, the only place those coins are going is to a 1bitcoinAddress unless your wallet software is broken and doing stupid things.
|
|
|
Fair enough...
If you have Bitcoin Core, you can download and install the BitcoinABC software (it uses the same wallet.dat format at the present time), rather than exporting (and potentially exposing) private keys. There are some necessary precautions that you will want to use tho, as by default it attempts to use the Bitcoin Core datadir's so it could "corrupt" your Bitcoin Core install, by messing with the block files...
Prior to the fork, I simply copied my entire Bitcoin Core datadir folder... and called it "BitcoinABC"... I start the BitcoinABC client with the -datadir="E:\BitcoinABC" argument and (after it actually found some ABC nodes to connect to) it is syncing nicely with the ABC chain... with it's own copy of wallet.dat.
Unfortunately, I'm not sure if creating a copy of the datadir and blocks will work post-fork, as there are blocks that are "invalid" on the BCC chain... which may cause ABC to choke? It's possible that a reindex will just remove the "invalid" blocks after Block #478558... and then it will resync from there... but I can't guarantee that.
Also, it is recommended that you actually create a new wallet for Core, send all your BTC there... then use a copy of the OLD pre-fork wallet.dat with ABC... that way, should the ABC software leak your wallet file and/or keys, only your BCC is at risk, because all your BTC are already in a different wallet/addresses.
|
|
|
Have you tried simply going into Bitcoin Core debug window and using the "dumpprivkey" command? I see no reason why it wouldn't work... it is part of Bitcoin Core which is fairly standard across all the OS platforms...
|
|
|
maybe You can say, why this kind of stuff dsnt works?
if (losecount > 0) then nextbet = previousbet+0.00000010
If first bet was 0.00000100, then he will make second one 0.00000254 and third 0.00000408, 0.00000562, 0.00000716, 0.00000870, with this command lines, why?!
maybe there is another simplies method, to do/make, that bot's add 0.000000xx amount for every 10 losed bets in row?! like first 10bets he add 1, next 10bets he add 1.1, next 10bets he add 1.2?!
Without seeing your whole script, it is impossible to say why that code is not working... but I'd guess that either it is not being executed due to conditional checks not resolving to what you think they should be (ie. you have an IF-ELSE statement that is not resolving correctly)... or you code somewhere else that is overriding your nextbet and increasing by 0.00000154 sats every bet instead of 0.00000010 Do you have settings from the basic/advanced tab set causing issues? another issue is that bot making "fast doublebets" when amounts are bigger, and are night internet connection is better and dice site servers are less people.
sample:he need to stop when win and make basebet, but it can;t assimilate information or what, and make another big bet with last increasement... allmoust cant play if dont run two bots in same site...
The bot works in a sequential manner... it doesn't (can't) make a bet until it has processed the previous one. If the bot is not stopping/resetting when you think it should, it is most likely because your stop/reset conditions are wrong. Again, perhaps your basic/advanced tab settings are causing problems...
|
|
|
|