The second transaction is stuck as well: ID is 0e2fdfda71845ac00cae2912491c55a310993873cb18c66d688f952ad3dda29d
The previous one received 2 confirmations couple of minutes ago
For the record... your second transaction used a fee of only 11 sats/byte... at a point in time when the number of unconfirmed transactions in the mempool was spiking. That was mostly like the reason for it being stuck. Not sure what wallet you were using to send, but checking things like https://bitcoinfees.21.co/ and https://btc.com/stats/unconfirmed-tx and https://blockchain.info/charts/mempool-count before sending transactions out should give you a good overall picture of the current network load and the sort of fees you should be using for quick confirmations. If someone has any comments about it - write. Some useless shit from 12 y.o. donkey about "i dunno, it happens sometimes, u need too wait" isn`t allowed here
One could almost say the same thing about all the "help my transaction is stuck" threads in the "Technical Support" forum  |
|
|
|
|
Assuming L1, L2 and L3 are all correctly connected to Electrum server(s) on the BTC network... and that those server(s) are not lagging and/or poisoned/malicious etc... then L1, L2 and L3 will all show exactly the same history/transactions.
This is essentially because you're just querying transaction history for a given set of addresses from the blockchain via the Electrum server... and, theoretically, they will all return the same transaction set for a given address as their blockchain datasets should be identical.
What they might not show is the same "labels" for addresses/transactions... as these are kept on your local system (unless you use the LabelSync plugin)... however these can be exported/imported from with Electrum relatively easily if you so desire.
|
|
|
|
Thank you for the recommendations, just a few questions. How many wallets I can create with a single trezor. Can I access it via web and lock it just incase it was stolen.
You can theoretically create as many wallets as you like... either by using different "account" values (m/44'/0'/0', m/44'/0'/1'/, m/44'/0'/2'/... m/44'/0'/n'/)... which is what happens when you click the "add" button inside of the default wallet app... however Trezor has a limitation that you cannot add a new "account" if the last one in the list is "unused". OR you can create multiple wallets by using different passphrases... each passphrase will generate a different wallet (it is part of the "plausible deniability" functionality) ... One minor disadvantage of Nano S is it takes two hands to push buttons...
This really isn't true. You can easily use the Nano S one handed, I do it all the time...  |
|
|
|
hello
i have a probleme i sent all my btc in mycelium wallet (0.025) btc to bittrex account with a fee of 0.0000795 btc 16sat/byte so the transaction is unconfirmed for 24h to this time cause of the low fee
my question is will it be confirmed or forgoten and how much time till it will be forgoten a back to my wallet ?
the txid : 082c79cf4905c44e9f193f23df5412ea44f15534ee8fadce421a7b4ac59bac2a
For some reason, ViaBTC didn't have this transaction in their mempool, so I broadcast it using their tool here: https://pool.viabtc.com/tools/BTC/broadcast/Then I accelerated it using their accelerator here: https://pool.viabtc.com/tools/txaccelerator/ ... They have now mined it and you have 1 confirmation... you're welcome  Included In Blocks 488355 ( 2017-10-05 03:17:44 + 1,022 minutes )
Relayed By ViaBTC |
|
|
|
Open up Bitcoin Core... click: "Help -> Debug Window -> Information"... look for the datadir value... That is the folder containing your wallet.dat and the blocks and chainstate folders  |
|
|
|
You can probably do it easily (but most likely very inefficiently) by using a simple for loop and just moving the items along in the list: myArray = {1,2,3,4,5,6,7,8,9,10}
for i=1,#myArray-1 do
myArray[i] = myArray[i+1]
end
myArray[#myArray] = <INSERT NEW VALUE HERE>
Notes: - It effectively moves every one place to the left and then adds the new value into the last slot... I don't think this would scale well, so I wouldn't try doing this on an Array that had like 100 values in it. - Arrays (technically "Tables") in Lua tend to be indexed from 1 - the #myArray notation is basically just the "length" value of the array... a handy little operator when dealing with dynamically sized arrays - if you need to "read" the value being pushed off the queue, then you need to make sure you use myValue = myArray[1] BEFORE the for loop |
|
|
|
|
When you restored from your seed... did it come up with a "warning" saying that you were restoring a 2FA wallet? Did it ask if you wanted to "keep or disable" Two Factor Authentication?
If it didn't, then the seed you have is NOT for your 2FA wallet that is asking for "One Time Passwords"
|
|
|
|
Go here: https://www.blockchain.infoput the address that you sent the other person into the search box... do you see any transaction information at all?  At the very least you should see 1 transaction with the amount they sent you, and a transactionID. Otherwise, they sent to the wrong address, or they didn't send the coins. Ask the sender for the TransactionID (txid) for the transaction they created. You can also enter that into the website I linked... |
|
|
|
Yeah. I can see that now. However, from what I can gather now, EC_KEY wants a secret not a private key. So if you pass 'BB7529C7834A210374035F50E884C6CA1E42C6DFB43004463AE3BC38A2585E19' as a paremeter, it's not going to work. How would I go about signing messages with that specific private key?.
sign_message_with_wif_privkey also requires the secret.
So let's say I generate a key through bitaddress.org which gives me WIF format, hex format and all that, how would I go about using that?.
Near as I can figure... the "secret" is the 32 bytes of the private key in hex... converted from a string to an Int... from ecdsa.util import string_to_number, number_to_string
...
class EC_KEY(object):
def __init__( self, k ):
secret = string_to_number(k)
...
...
def string_to_number(string):
return int(binascii.hexlify(string), 16)
..
I'll have a mess around tonight... and see if I can come up with some example code to string some of it together.  EDIT: I'm too lazy to hack the code, so I was messing with the Electrum console: >> import binascii
>> binascii.unhexlify("E705308F9F19BA9292FB0A9F022CC07666AA4D63C14C097F44A674C52599AF2D")
'\xe7\x050\x8f\x9f\x19\xba\x92\x92\xfb\n\x9f\x02,\xc0vf\xaaMc\xc1L\t\x7fD\xa6t\xc5%\x99\xaf-'
>> bitcoin.EC_KEY(binascii.unhexlify("E705308F9F19BA9292FB0A9F022CC07666AA4D63C14C097F44A674C52599AF2D"))
<electrum.bitcoin.EC_KEY object at 0x04940DD0>
>> mystuff = bitcoin.EC_KEY(binascii.unhexlify("E705308F9F19BA9292FB0A9F022CC07666AA4D63C14C097F44A674C52599AF2D"))
>> print(mystuff.secret)
104493437413910685574809975339575985857145839109407479576256729153645095530285
>> print(mystuff.get_public_key())
03c8759d2cd3dc2b12f9ce4e539d956986b6fd0d2b38303b141cd8ee09e683be13
>> mystuff.sign_message("this is my message", False)
'\x1cEp\x0f\xc9\xae\xb4\x0f\x89\xf7\x80x\x88%\xa7\xc8\xd4Te\xfcRc\xaa\x0fe\xfa \xf2wP/\xf9\x0b?L@g\x1f\x07J\xba\x0b\x10Bj\xb1\xe6~\xb8\x9f\xc8\xbb|\xd8\xaer\x15\xb8X\x87^\\\xa0\xd9\xa5'
>> mystuff.verify_message(mystuff.sign_message("this is my message", False),"this is my message")
>> mystuff.verify_message(mystuff.sign_message("this is my message", False),"bad message")
Traceback (most recent call last):
File "C:\Users\jared\AppData\Local\Temp\_MEI114882\lib\bitcoin.py", line 642, in verify_message
raise Exception("Bad signature")
Exception: Bad signature
>>
If you check bitaddress.org with your original WIF key... L4xnRyP8ARQHZ1BwVkUVfk8sMkXsyBJxd9zhEMXci6NjHkFd9ewp or the HEX: E705308F9F19BA9292FB0A9F022CC07666AA4D63C14C097F44A674C52599AF2D you'll see the public address listed: 19M16LN1k5Emc8qBuDEYv9Aggpe2ttuABk |
|
|
|
Anyway, Xapo will benefit a little from BCH, because there still will be some users, who will not take their BCH until deadline
The only way that will benefit Xapo is if they screw their customers on the sell rate, as they've stated that at the deadline they will simply sell the BCH "at market rates" and credit the customers BTC... |
|
|
|
Like any "wallet", you can always receive coins to an address without the wallet being open and/or connected to the internet... Otherwise you'd never be able to find paper wallets!  For "withdrawing" (sending coins from an address)... The answer is "it depends"... If no one else has the seed and/or private keys... Then the hardware wallet would need to be connected to a computer for you to sign the sending transaction with the appropriate private key... However, if someone had access to the 24 word seed and/or private keys, they could simply import that into another wallet and send transactions... The idea behind the hardware wallet is that it makes it VERY difficult for someone to get the private keys and/or seed phrase (assuming proper procedures are followed during setup and use) |
|
|
|
|
Just a friendly note... unless you did that on an offline machine, and used a public key to create a watching-only address... you should consider that private key "compromised", as it has been "typed" into an online computer that could contain keyloggers, clipboard scanners, screen grabbers etc.
Having your private keys "exposed" carries risk... so please make sure you take steps to protect your coins going forward.
|
|
|
|
Ok... so it sounds like the address the coins have been sent to is NOT in your wallet... but IS generated by your seed... so that's a bonus! The trick now, is to figure out which "Derivation Path" was used to generate that "incorrect" address from your seed... I did some testing with Mycelium and it seems that when using the iOS setting in conjuction with your xpub, the addresses generated are actually the ones that are generated from m/44'/0'/0' using your recovery phrase: ie. Goto the BIP39 Mnemnoic Code Converter: https://iancoleman.github.io/bip39/ (use offline version etc etc) - Set the "BIP39 Mnemonic" as your 12 word Mycelium seed phrase. - Click "BIP32" tab under "Derivation path" - set "Client" dropdown to "Custom Derivation Path" - set "BIP32 Derivation Path" to: m/44'/0'/0' the "bad" address(es) (from using iOS setting in Gear widget), along with matching private key(s), should be listed at the bottom... NOTE: you NEED to use your seed (and NOT the xpub) so that you can see the private key(s)... once you have the private key(s), you can recover your misplaced coins by simply sweeping the contents of that "bad" address(es) back to the address of your choosing. NOTE2: If you click the "BIP44" tab, you should see your "good" address(es) (from using the Android setting in Gear widget) |
|
|
|
|
In which case I still believe that you have (a valid) but "wrong" seed backup phrase... and your original android wallet with the 1 BTC was running from a different seed phrase... and you've confused the two and put your PC seed onto your android device.
Jaxx "pairing" doesn't literally "pair" your wallets together like a bluetooth device or anything... it just uses the same seed on two (or more) different devices, which generates the same addresses, so when the wallets scan the blockchain, they find the same transactions (and resulting balance).
If your android wallet had a different balance to your pc wallet, then they were most likely running on device seeds.
|
|
|
|
Next stupid question... confirm you are running Electrum... and not ElectronCash? I cannot think how it can not find your coins if the address is definitely in the wallet and you're connected to the Bitcoin network and the Electrum server is synced up past block #487,034. The only thing I can think of is that you're connected to the BitcoinCash network, in which this transaction does not exist. |
|
|
|
You can actually import that seed into Electrum now... They even show you how in this video: https://youtu.be/E-KcY6KUVnYIt will import all the transactions for that wallet, but won't include any labels you may have assigned to the addresses/payments. For the record, the password DOES work, it's the processing of the transactions internally that chokes due to unexpected data causing the error. So, there is a good chance you can use OpenSSL to decrypt the .aes file... But you'll probably have to dig through the MultiBit source code to figure out the iterations/salt settings required etc... |
|
|
|
|
Installer just creates icons etc...
Standalone doesn't...
Both setup and use an Electrum data folder in %AppData%
Portable creates a data directory in the same cost as the portable .exe
Running from sources is an option if you want to... The two options are just different archive formats... .zip or .tar.gz... the contents are (theoretically) the same
|
|
|
|
Ok, then there is something confusing me. To be able to recover an Electrum wallet the user needs the seed phrase only? With 2048 words it's easy to recover the seed of random people? With 2048 how many different seeds can be generated? I tried to install Electrum and set a password, I don't remember if I had the choice to use one. This password is need as well to recover a wallet?
12 words... 2048 possible words in each position... 2048^12 = 5444517870735015415413993718908291383296 possible combinations... In other words... Your chances of finding someone else's seed is slim to none. It should also be noted that not all combinations of words generate valid seeds due to checksum calculations. As I mentioned earlier, password is only required for decrypting a given wallet file (or the private keys stored in that wallet file)... To restore a wallet, you ONLY need the seed phrase. The password that Electrum uses is only for encrypting the contents of the wallet file... It doesn't affect the wallet generation in any way... Ie. It isn't like a BIP38 passphrase |
|
|
|
|
Show Posts
