Thanks for response... This is helpful. Pls if anyone knows a simplified way to check address, pls provide a link or instructions as I'd feel better about this confirming the address for output #2 (at least for the first time). Much appreciated.
As Coin-Keeper has suggested... importing your Master PUBLIC Key into Electrum is a relatively painless and safe way to check your addresses... Just download Electrum from here: https://electrum.org/#downloadThen create a "new" wallet -> Standard Wallet -> Use a hardware Device -> Connect the ledger then follow the prompts... After it has created your addresses and opened the wallet, you can view the addresses using "View -> Show Addresses" and then click on the "Addresses" Tab... your Output #2 address should be showing under "Change" (Note: you may need to click the '>' symbol to get the Change section to expand) |
|
|
|
|
Where exactly is it getting stuck? when you try to restore the wallet using your 2FA seed? or when you are trying to send the BCH transaction?
|
|
|
|
You can't import the .key file directly... especially if you put a password on it. You need to export the keys WITHOUT a password, then you need to open the .key file in a text editor... and copy/paste just the private keys into Electrum. They start with a "5", a "K" or an "L"... NOTE: doing this increases the risk of exposure of your private keys... I suggest doing this OFFLINE and doing what you can to ensure the machine is free of malware etc.  |
|
|
|
@HCP. I would like to know how it is possible to transact the bitcoin when the system is offline. If it is offline it cannot be mined with the network blocks! Can give explanation to know about it.
You don't attempt to broadcast the signed transaction from the offline machine... that is why you need 2 machines for this system. One "online" machine that has full copy of the blockchain and only public keys... aka. the "watching wallet"... and then one "offline" machine... airgapped, with no blockchain, but with the private keys etc.. After you have created the transaction on the online machine, you transfer to offline machine via usb, sign it with the private keys... then transfer the "signed" transaction back to online machine via usb and broadcast it. In all honesty, you are just better off getting a hardware wallet... it achieves pretty much the same thing but without the requirement for a second PC and a lot less hassle etc. |
|
|
|
It seems that this is "normal" behaviour since the updates for SegWit were put in... https://www.reddit.com/r/ledgerwallet/comments/6wws8e/comfirm_output_2/Chances are that this Output #2 is in fact a change address in your wallet, so I don't think that you need to worry that your ledger s might have been "hacked"  Checking your addresses is actually pretty easy, so if you need detailed step by step instructions, I'm sure one of us will be able to help out  |
|
|
|
You can try accelerator transactions. I know viabtc, but don't accept tx with fees less 10 sat/B Fee per byte 6.017 sat/B is low.. Don't send with low fees again. Also you can try contact with cissrawk and ask to help you. He is really can do it. You're also missing the point... like several of the others here. OP DOES NOT want his transaction confirmed. OP wants to "rescue" their coins as they have realised that thunderbit is a totally scam ponzi website... it has been online for a total of 12 days  OP is looking for ways to reverse the transaction so they don't lose their $9 worth of bitcoin. As mocacinno and DannyH have already pointed out, the only two options the OP has at this point are: 1. Create a "Double Spend" transaction that uses as least one of the inputs in a transaction with a MUCH higher fee so the new transaction gets confirmed first and invalidates the old one (because one of the inputs is no longer available for spending) or 2. Sit around and wait and hope that the super low fee of 6 sats/byte means the OPs original transaction gets dropped from the mempool and the coins are returned to their wallet. The issue with Option 1 is that it is quite technical and not easily achieved given that the OP is using blockchain.info wallet... not impossible, but certainly not simple. The issue with Option 2 is that it isn't guaranteed to drop and it can take a long time for it to drop... blockchain.info likes to rebroadcast transactions |
|
|
|
If resetstats() keeps crashing your script... you can probably work around it by just tracking the profit yourself using a user created profit variable... as it seems the only "stats" you're using is "profit"... runProfit = 0
startBalance = balance
...
function dobet()
runProfit = balance - startBalance
if win then
...
if (runProfit > 0.000001) then
-- "reset stats"
startBalance = balance
runProfit = 0
end
...
if ((runProfit < -0.0000005) and (runProfit >= -0.0000020)) and (currentstreak == 2) then
...
else
...
end
end
Then you just replace all instances of "profit" with "runProfit" etc... |
|
|
|
|
Like I said... do you have any idea what the password may have been? are you lazy like 99% of computer users and use the same password for everything or just add numbers on the end? ie. myPassword01, myPassword02...
or do you use really difficult passwords for everything? ie. $mYpAs5jaHQ2z#8@!
If you have *some* idea of what the password is... btcrecover is likely to be your best shot... I assume you didn't have any luck with walletrecoveryservices?
|
|
|
|
I have many addresses on my wallet that contain differents amounts: 0.0001, 0.001, 0.002, 0.03 etc ...
But is not a reason to pay higher than my balance !!!! I don't believe this !
That is exactly the reason for paying a fee higher than your balance. Bitcoin transaction fees are calculated on a Satoshi/byte basis... so the larger the data size of your transaction, the more you need to pay in total fee... transaction size is mostly dependent on the number of inputs (each input is at least 148 bytes) and, to a lesser extent, the number of outputs (34 bytes per output)... a "standard" transaction, (1 input, 2 outputs) is around 226 bytes... if you have 10 inputs, your transaction blows out to 1554 bytes... so if you have a bunch of tiny amounts and need several of them to make up to 0.01 btc, your transaction gets big, takes up more space in a space limited block and therefore costs you more... moral of the story: DON'T accept small/dust sized payments... anything less than 0.001 is asking for trouble... |
|
|
|
|
Have you tried restoring as a "standard" wallet? It'll detect it as a 2FA seed after you type it in... And it should then go to the "keep or disable" screen after you click Next...
|
|
|
|
Ok, so looking at the transaction and the addresses involved... 1ExvzdTyFZMigD72eU3aCaPCPm28wcBBna received a total of 0.0477 BTC (47.7 mBTC) prior to the fork... After the fork, you then transferred 0.0477 BCH from that address to 14o6hd7vF9ESktxSbxLdQxunXNsU1SLGKC (I assume this is the Bitfinex address?) in the 0c21121404e6e0416106b60f4aa764044bf983526c7066090b8d072de5311bfc transaction... Receiving 0.04753 after fees. If you only have 0.032 BCH credited to your Bitfinex account, you need to go ask them what happened to the rest of it... So they charge for deposits or something?  It really looks like you've got yourself confused with the "Milli" units that Electrum and ElectronCash both use by default... Granted you may actually have had 47 btc, but you only sent 0.0477 BCH in that transaction. |
|
|
|
|
dropped you a PM... also with some advice for checking why BitcoinABC isn't syncing
|
|
|
|
I rebroadcast the transaction and accelerated it using AntPool and ViaBTC... Hopefully it'll confirm in the next 6-12 hours... I'm wondering if blocktrail are blocking/removed it because of the "dust" output? In any case ViaBTC and AntPool accepted it... So it's in the mempool EDIT: boom! ViaBTC picked it up... You have 1 confirmation... You're welcome Included In Blocks 482196 ( 2017-08-27 11:13:23 + 7,646 minutes )
Relayed By ViaBTC |
|
|
|
Very strange... I just tested this and I had the same issue, New -> 2FA -> "I already have a seed" -> stuck on "please wait" screen... Even tried "standard" -> "I already have a seed" -> enter 2FA seed -> stuck on "please wait" screen... So I shut ElectronCash down, restarted the app and it worked!!?! Shut it down again, restarted the app and tried again and "please wait"... Shutdown/restart again and it worked! So it seems to be a bit of a random error...  All I can suggest is shutting it down and then restarting and trying until it works. |
|
|
|
If you can post the transaction ID of your transfer from ElectronCash to Bitfinex... it'll help clear things up. But I suspect you have transferred 47.7 mBCH (which would have been around 0.0477000 BCH) as by default ElectronCash (and Electrum) are set to "milli" units... quite why that dropped to 0.032 BCH by the time it got to Bitfinex, I can't say... I'd need to see the txid to be able to be sure... but possibly the transaction fee? The only way you would have had 47.7 BCH was if you had 47.7 BTC in your Electrum wallet at the time of the fork For the record, anything you did on BTC network AFTER the fork will have no effect whatsoever on BCH network... so the 2nd wallet and moving to bitshares will have had zero effect on BCH |
|
|
|
As far as I am aware, there used to be a constraint of 72 hours which seems more and more like a weird value as I have had transactions last for weeks before they get confirmed before.
Seems like there is a little bit of confusion here... the "72 hours" was the previous "mempoolexpiry" value... this has been changed to 336 hours (14 days) since Core v0.14: https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_argumentsAs per this stackexchange answer... there are five ways that a transaction is removed from the mempool: As of Bitcoin Core 0.14.0, these are the ways a transaction can leave the mempool: - The transaction was included in a block.
- The transaction or one of its unconfirmed ancestors conflicts with a transaction that was included in a block.
- The transaction was replaced by a newer version (see BIP 125). aka "RBF"
- The transaction was at the bottom of the mempool (when sorted by fee per size), the mempool had reached its size limit (see the -maxmempool option), and a new higher-fee transaction was accepted, evicting the bottom.
- The transaction expired by timeout (by default 14 days after entering).
Some things to note... the 14 day mempoolexpiry value is just a default and can be set by the Node owner... so some pools may be 3 days, some 14 days, some 1 month, some 12 hours etc... Also, if the pool is running on a limited pool size (ie. maxmempool) then it may be pushed out sooner than the mempoolexpiry time... Wallets are able to (and usually do) attempt to rebroadcast transactions... which can "reset" the expiry time for a transaction. I believe this is the main reason that people end up with transactions unconfirmed for weeks. Abandoning a transaction in Core does not remove it from the network... once a transaction has been broadcast, it is there until it drops out of the mempool... all abandoning does it mark it so that your wallet will not rebroadcast it. There is nothing stopping someone else from continuing to rebroadcast or a miner "confirming" that transaction if they wish. |
|
|
|
Is your balance made up of a whole bunch of tiny payments? If so, that will be why the fees are so high... the more inputs you have, the larger your transaction becomes. Fees are calculated on a sats/byte or btc/kB basis... so the larger your transaction size, the larger the fee... Due to the recent spike in the number of transactions and the resulting increase in fees ( https://bitcoinfees.21.co/), you're looking at something like 60-70,000 sats PER INPUT!!?!  Simple math dictates that 10 inputs = a fee of 0.006 to 0.007 BTC |
|
|
|
|
The latest versions of Electrum (from v2.9.0) support custom derivation paths for BIP39 seeds... previously, it was hard coded to using m/44'/0'/0' (ie. the BIP44 spec derivation path used by Hardware Wallets and some software wallets like Mycelium)...
Now, after entering a BIP39 seed (and selecting BIP39 seed from the "options") during the "restore" process... you will be prompted for the Derivation Path you wish to use... so now, it is theoretically possible to import a mnemonic from pretty much any BIP39 compatible wallet.
|
|
|
|
Building databases can take a while depending on your hardware... if it is parsing tx hashes then it is definitely working |
|
|
|
|
Show Posts
