|
It is saying it is not certified by a trusted signature. This is fairly normal... it just means that none of your Trusted signatures has vouched for Thomas' signature.
PGP signatures work on a "web of trust"... for instance: Person A trusts you... You vouch for Person B... therefore Person A will trust Person B because you vouched for them. At the moment, no-one you trust (including yourself) has vouched for Thomas' signature, so you get the warning that the key is not certified... even though it is definitely the one used to sign the file (The "Good Signature" message)
|
|
|
|
the exact procedure I am following for creating the text file is copying the entire contents of it from electrum.org and then pasting it onto textedit and saving it. then I have to rename it because it automatically puts an rtf ending.
Can you not just right click the link for the .asc file and select "save link as..."? You should be able to just save the file directly from the browser rather than copy/pasting... it is possible that you are either missing data while copy/pasting or it is screwing up the newline/carriage return characters etc... How does the thomasv@electrum.org PUB key I downloaded from the key server play into this, if in anyway? Did you import the thomasv PUB key into your keychain? You need to make sure that you've created your own GPG keypair... and then imported his pubkey so that it can verify the file using it. |
|
|
|
He appears to be using https://www.bitaddress.org/ (or some clone of it)... it is opensource and free to download (they have a link at the bottom of the page). Simply click the "wallet details" tab at the top, input the private key and click "view details" it'll show all the info... NOTE: DO NOT put your private key into an online version of this website... download it and run it on an offline computer! Also, check out some of TP's Bitcoin tools: http://gobittest.appspot.com/ The "Bitcoin Address" and "Private Key" tests illustrate how you convert from one thing to another, step by step |
|
|
|
Seems to be working fine from here... I just tried it (Windows 10 + Chrome)... https://shop.trezor.ioClicked on the black circle, clicked "Add to cart"... selected shipping country and DHL shipping option and click "proceed to checkout"... it asks for the delivery address and payment type. |
|
|
|
|
Sounds like Electrum is having trouble syncing the block headers... Do you have a green dot in the bottom right corner of the Electrum window or blue arrows or a red dot?
Regardless of which one you have, when you click it, it should bring up the network settings, what is the "blocks" value? it should be 484,000+
|
|
|
|
This implies that you have to trust that the manufacturer doesn't have any rogue employees.
Much like you have to trust your OS maker doesn't have any rogue employees... or Intel/AMD... or the hard drive manufacturer... or the USB manufacturer... or the WiFi chipset manufacturer... or the RAM manufacturer... or the Ethernet manufacturer... or the Router/Modem manufacturer... or the <insert every other link in the chain> Trezor do their best, and you can verify the publicly viewable code is the one on your device...: https://github.com/trezor/trezor-mcu/blob/master/README.md#how-to-get-fingerprint-of-firmware-signed-and-distributed-by-satoshilabsWith Electrum, you run it on an offline computer or bootable USB and you sign the transaction there. Then you take the transaction to the online computer and broadcast the transaction. The private key never leaves your offline computer.
And what makes you think that a rogue version of Electrum wouldn't encode your private key in the OP_RETURN section of your transaction prior to signing it? What guarantee do you have that the version of Electrum you downloaded is the same as the code on Github? You'll NEVER find a 100% secure solution... there are ALWAYS attack vectors... especially when humans are involved. |
|
|
|
I just purchased a trezor and set it up. My plans for this are ultra safe storage of a decent sum of BTC for a long period and not using it on a day to day basis.
I have read through how it works and watched a half dozen you tube videos but I am not sure how to securely verify my seed words should I ever need to use them. It seems you can do a restore but that involves typing them in on your computer which doesnt seem safe if your computer is compromised.
Then again using the device without testing the seed restore process doesn't seem to safe either.
Any recommendations?
Restoring the Trezor has 2 options for helping to protect your seed... 1. The words are entered into the computer in a shuffled order... along with "bogus" words. So you end up entering more than 24 words in random order... in an effort to confuse/defeat keyloggers. 2. As of firmware 1.5.2, they have an "Advanced" recovery system. It works like the PIN entry, with randomised "letters" displayed on the device screen, and you click the box on the PC. It is a LONG process entering 24 words this way, but it is nice and secure  Read here: https://doc.satoshilabs.com/trezor-user/advancedrecovery.html |
|
|
|
Or it could be that some people don't want to attract attention to their paper wallets... plastering Bitcoin logos all over it confirms exactly what it is and may just catch the eye of someone leafing through a stack of papers on your desk. Whereas, a "plain" sheet of paper might go unnoticed. There are a couple of nice ones here: https://bitcoinpaperwallet.com/bitcoinpaperwallet/generate-wallet.html#And they have a template... Personally, I quite like the "Hobbitcoin" one |
|
|
|
i sent some bitcoins over a month ago now but made a mistake with the fee being too low, its still unconfirmed and i have tried to start bitcoin core using the -zapwallettxes command but it doesn't make any difference.
You need to right click the transaction and select "Abandon Transaction". Then shut down Bitcoin Core and restart with the -zapwallettxes command. |
|
|
|
And if someone steals your Nano they cannot read the Seed because they haven't the PIN.
But they may disassemble the Nano and directly read the flash memory in it, and copy directly your private key.
You make it sounds like they just need to crack open the case and read some data from the "flash memory" to be able to get the private key... The Ledger Nano S Hardware Wallets use a "secure element" (aka smartcard) that makes it extremely difficult for anyone but very well resourced attackers with very high levels of technical expertise and specialised equipment to be able to perform the private key extraction attack. Ref: https://www.ledger.fr/2015/01/17/bitcoin-security-why-smart-cards-matter/Granted, this is an article written by the manufacturer, but the theory is sound... |
|
|
|
I'm the only one who can't manage to get the last update? the wallet didn't auto update and when I check for new update through the menu, It says that I'm 2.9.2 and It's up to date while there is clearly a new version out.
I think their "in app" 'check for updates' system is broken... Mine says "you're up to date"... I'm on 2.8.12... and Play Store has 2.9.3 and the "update" button  |
|
|
|
[code]It's not so much the "text" size (ie. the number of characters or spaces etc) of the script... it is what the script is actually doing.
Basically, it is like the difference between a person counting to 10 and then clicking bet... versus counting to 1,000,000 and then clicking bet. Obviously, the second option will take longer.
Having a LOT of commands (10,000 vs. 150) is like basically the same thing... it is like you're asking the bot to count to 1,000,000 which takes time (even for a bot)... so the betting speed is reduced.
Tips:
- Try to avoid "loops" if possible. These are BIG cpu cycle killers
- Try and arrange long if-elseif blocks, so the most likely/regularly occurring situations are tested at the beginning of the block. That way you don't waste CPU cycles doing comparisons for situations that hardly ever happen.
for example:
[code]
if thingThatHappensEverySecondBet == true then
..
elseif thingThatHappensEveryFifthBet == true then
..
elseif thingThatHappensEvery20Bets == true then
..
elseif thingThatNeverHappens == true then
..
else
..
end
- Try not to include pointless "if" statements... don't do something like this, it needs to evaluate three If statements EVERY time through the code: if color == red then
..
end
if color == blue then
..
end
if color == green then
..
end
Do something like this instead: if color == red then
..
elseif color == blue then
..
elseif color == green then
..
end
This code may will only need to evaluate one if statement if the color == red, two if the color == blue and worse case scenario, three "ifs" if the color == green.[/code][/code] |
|
|
|
You're welcome. Note that you might find that the exchange decides to charge you a fee for recovering your BTC... a lot of the exchanges charge fees for fixing what they call "cross chain" transactions.  Anyway, good luck with the BTC recovery... hope the exchange helps out! |
|
|
|
It would appear you've sent BTC to a BCH address You were not supposed to send your BTC from Electrum to a BCH address. You were supposed to import your seed into Electron Cash and then send your BCH from Electron Cash to the BCH address at the exchange. You will need to contact QuadrigaCX and ask them nicely to recover your BTC using the private key that they have for the address: 16ckC8g6BkUDoJPXi1VxvfC41ift4LwQ1Z They are the only people that can recover your BTC. Your BCH is still in your original address as you can see here: https://www.blocktrail.com/BCC/address/3HicmPMRmFLZHPu8zstsQdAegNQ2s2f4ptAlso, I note your original BTC address is a "3" address... was it a 2FA wallet perchance? or was it just a standard multisig? Either way, you are probably going to have some issues getting your BCH out... it's not as simple as importing your seed into ElectronCash |
|
|
|
... the generation of the transaction is handled onboard the wallet. the only information exposed to memory, to the best of my knowledge, No, the transaction is created in your software wallet (Ledger app or Electrum etc). It is the SIGNING of the transaction with the appropriate private keys that happens on the hardware wallet. Anyone of you that has a Nano and can confirm that it displays transaction info upon PIN request ?
And to answer the OPs question... yes, it displays the address and amount and you have to confirm it before the transaction is signed and returned to the software wallet for broadcasting. |
|
|
|
|
Sounds like the seed you have, is not for the wallet you're currently using! If you can use the "Wallet - Seed" menu option in Electrum, I suggest you use it and double check what the seed for your wallet actually is!
Also, double check the addresses that the seed generates in ElectronCash, if they're not the same addresses as from Electrum, you definitely don't have the right seed.
|
|
|
|
|
You will only have BCC if you had Bitcoins in that Electrum wallet at the time of the fork on Aug 1st.
If you moved BTC prior to Aug 1st = no BCC
If you put BTC in that wallet after Aug 1st = no BCC
if you had BTC when fork happened on Aug 1st = BCC amount equal to BTC balance on Aug 1st
BCC will only show in a BCC wallet (like ElectronCash or BitcoinABC)
|
|
|
|
Hi, thanks for your inform but I a little bit confused. can I save my all BTC in electrumwallet in this method. I dont want to loss it.
Yes, your seed will restore your old Electrum wallet.. with all the addresses and transactions etc. To test, in Electrum goto: "File -> New\Restore -> Standard Wallet -> I already have a seed", then enter your seed and click next... add a password if you want (DOES NOT have to be the same as your old one) It should recreate your old wallet with the same addresses and transactions. In Electrum passwords are only used for encrypting the private keys in the wallet file and encrypting the wallet file as a whole... they don't impact on the seed at all. They are NOT BIP39 Passphrases. Note that you don't even need to remove your old wallet first, you can just create a new wallet file (different name to old wallet) and restore your seed... so you can test it to make sure you know how to make it work  |
|
|
|
|
If a transaction already had 4 confirmations... then those BTC are effectively gone from your wallet. The chances of the network shifting and being able to "undo" 4 blocks is pretty low. Do you have any transaction IDs so we can see exactly what is happening?
|
|
|
|
|
Show Posts
