|
I'm wondering if the iOS derivation path was "corrected" to match the Android version, but gear wasn't updated?
If you change the type on the Gear widget to "Android/Electrum/Trezor" etc... Does it show the addresses that match your wallet? I'd test it myself, but I don't have an iOS device to test with.
I have only tested it with Bitcoin TestNet to see if the Gear system is working... Coins were sent/received and I received notification of the payment via Email OK.
I just noticed that the addresses that the widget generates are different for iOS setting... But can't confirm if it matches the wallet on iOS or not.
|
|
|
|
They'll show up after you install and sync Bitcoin Core... As long as a block explorer (like www.blockchain.info) shows that the address has the coins, they're safe. Alternatively, if you need access to the coins in a hurry, you can always export the private key for that address from Armory and import it into a different wallet. |
|
|
|
|
You're sending in the WIF formatted private key to the bitcoin.EC_KEY() function... perhaps it is expecting the actual hexidecimal representation of the private key in a 'bytes' object??
Likely to be something like: b'E705308F9F19BA9292FB0A9F022CC07666AA4D63C14C097F44A674C52599AF2D'
|
|
|
|
The obvious questions are: 1. Is that address definitely part of your wallet? (Check the addresses tab and/or goto the console and type: ismine('1Hefr1NLzABVZhK9Kh7XSB55xRFtK5ex6e')... it should return "true") 2. Is your Electrum connected and synced correctly? Do you have a green dot in the bottom right corner? or red dot? or blue arrows? 3. If you click Tools -> Network -> Overview... does it show the correct number of blocks? Most recent block as of this message is: 487,924... your transaction was in block #487,034... if your Electrum isn't synced up to at least 487,034 then you won't see the transaction. |
|
|
|
Minor oversight I would suspect... there is definitely a 2.9.3 version available for MacOSX... The 2.9.3 .dmg file is in the 2.9.3 folder with all the other installers: https://download.electrum.org/2.9.3/ |
|
|
|
One minor addition to TryNinja's instructions... (assuming you have your 2FA seed phrase written down): When it asks is you want to "Keep or Disable" 2FA... select " Disable"... that way you'll get two master private keys restored to your wallet, and you'll be able to send without using TrustedCoin's 2FA system.  |
|
|
|
Weird... it seems like you've configured everything to look in F:\BTCCore for the blocks folder... but in the debug it keeps outputting: 2017-10-01 15:08:03 (ERROR) -- BDM.pyc:199 - DB error: C:\Users\Admin\AppData\Roaming/Bitcoin/blocks is not a valid path
 ps. if you're having issues finding hidden folders like AppData... refer here: https://support.microsoft.com/en-us/help/14201/windows-show-hidden-files |
|
|
|
Is that address part of your wallet? Either check inside Mycelium... or check using https://iancoleman.github.io/bip39/If you put your BIP32 xpub in as the "BIP32 root key"... click the "BIP32" path... and set your Derivation path to m/0 (make sure "use hardened paths is UNCHECKED) and you should see the addresses that match your wallet. Is that 1EqPgQ address part of your wallet? I suspect maybe selecting the "IOS" derivation path, has resulted in it NOT actually generating the correct addresses for your wallet... Go into your wallet, click receive, make sure the address you see matches one of the addresses in the Gear Widget Summary Table where it lists the pool of addresses generated. If it isn't in the list, that is likely to explain the issue... |
|
|
|
All the 2FA and passwords in the world will not help you if the attackers have your 12 word b.info recovery phrase... those 12 words = all your private keys... and they're not password protected. Put it into https://iancoleman.github.io/bip39/ and "All your Bitcoin belong to us"  Who knows, maybe your info leaked during the HeartBleed thing... or despite your best efforts someone got some malware onto your PC... 410 BTC... that's like over 1.6million USD... and you were keeping them on b.info??!?   you couldn't spare ~0.03 for a hardware wallet? or use offline generated paper wallets? |
|
|
|
Bitcoins "belong" to private keys... Not the other way around. So when you transfer from one Bitcoin address to another, you are effectively reassigning ownership/control of those coins from one private key to another (Bitcoin address and private key have a 1 to 1 relationship). So it doesn't matter that the exchange has a private key, as that key no longer controls those coins. YOUR private key dies. Due to the use of "one way hash functions", there is no way to derive a private key from a Public Bitcoin address. You can only start with a private key and derive a public Bitcoin address. So, once you "withdraw" from the exchange... This transfers the ownership of the Bitcoins from the exchange address to your address (controlled by your private key)... Your private key is safely secured on your hardware wallet and NEVER leaves it... It is NEVER exposed to the outside world... That's the whole point of hardware wallets  Also, your protection against hardware device failure (or USB no longer existing) is your 24 word seed that the device generates during setup and which you wrote down and stored in a nice secure/safe place (you did that right? )... Those 24 words are able to regenerate your whole wallet... They're effectively your private keys stored in an easy to copy format... The algorithms and methods to go from 24 words to private keys are open source and widely known and there are plenty of other sources that will do this, like: https://iancoleman.github.io/bip39/Never give them to anyone and NEVER store them on a computer unless they're strongly encrypted. |
|
|
|
Trezor did have the Raspberry Pi "shield" at one point... An add-on circuit board with Trezor-like OLED screen and two little hardware buttons... It would appear it never caught on and people just bought a Trezor instead  I think the fact that a Pi has some much attack surface would make it difficult to lock down as a hardware wallet... You'd need to remove so much (ethernet, wifi etc) and no doubt have some custom USB drivers or something to prevent data being "leaked" from it... Still, I've seen Pi full nodes with attached HDDs and little screens etc... So maybe useful as an "airgapped" offline wallet? |
|
|
|
|
Until they mine their next block (possibly 2)... Theoretically, a total of around 144 blocks should be mined in total per day... ViaBTC currently have about 5% of the total hash rate...
So you'd expect them to get around 7 blocks per day... 24/7 = ~3.5hrs... So they should find a block on average around once every 3-4 hours...
Of course, it could be that they get lucky and find 20 blocks today and you only have to wait 10 mins... Or they could be super unlucky and find 1 block... And you have to wait 23 hrs...
If it said succeeded, they've accepted your transaction and will mine it eventually... It just might take some time.
NOTE: there is nothing stopping another miner from confirming your transaction in the meantime...
|
|
|
|
Yeah, it looks as though Jaxx may not be scanning your transactions correctly then... I've seen other users around here report similar things before... I don't have any references on hand... But it seems to be a common issue with Jaxx following a restore from seed... I'm wondering if it is a "gap limit" issue where it doesn't scan enough "empty" addresses before deciding there is nothing more to find and stopping... Thereby missing a bunch of non empty addresses?? An easy way to test this would be to try importing you recovery phrase into a desktop version of Electrum... (standard wallet -> I already have a seed -> Click the options button on seed import screen and select BIP39... Derivation path when prompted is m/44'/0'/0' which should be the default setting) See if Electrum comes up with the full amount... |
|
|
|
|
Your problem is that the two applications (MultiBit and bitcoin.com wallet) are creating and trying to import two different file formats.
MultiBit outputs either a plaintext file with your private keys or an OpenSSL encrypted file... Whereas bitcoin.com wallet is wanting an AES encrypted JSON wallet file to import.
The result being that you can't import your MultiBit keys into bitcoin.com. You'll need to use a different wallet like Electrum/ElectronCash that allows you to import private keys in WIF format... Or you'll need to sweep the keys into the wallet you want to use.
I can't find a sweep option on Bitcoin.com wallet... So if you're set on using bitcoin.com wallet you'd need to setup the sweep using another what like Electrum and just change the destination address to your Bitcoin.com wallet address...
Given that you're doing this for BCH, you'd probably need to be using ElectronCash if you're trying to send to a BCH wallet
|
|
|
|
You don't even need the password... You only need the 12 word recover seed phrase. And there isn't really anything "special" about Electrum in that regard. It is simply a "Hierarchically Deterministic" (or HD) wallet... https://en.bitcoin.it/wiki/Deterministic_walletIn other words, all the wallet addresses can be regenerated from the seed. Most modern wallets use this method for backup/recovery. |
|
|
|
If you put those addresses into a block explorer, like www.blockchain.info, do you see your correct transactions and balances? If so, then your coins are fine... And it's probably just Jaxx being retarded. If your balances aren't showing then it's possible you don't have the right seed phrase? |
|
|
|
Despite the fact that they have thousands of happy customers using their product everyday without issue? I don't doubt you're experiencing difficulties, it just sounds like you got a defective unit. It happens. So, if a different cable, different USB port etc didn't help, it's fairly obvious that the unit isn't right. Yes I still have the recovery seeds BUT they are useless unless I get another Trezor...Ridiculous... I can assure you that they're not useless... https://doc.satoshilabs.com/trezor-user/emergency.html#you-have-no-trezor-device-and-recovery-seed-is-availableYou can also use something like: https://iancoleman.github.io/bip39/ To recover your private keys in a real pinch... But importing the seed into something like Electrum is probably your best bet They have not offered me a replacement yet...
Simply request a replacement. Problem solved. |
|
|
|
|
In a word, NO!
MultiBit is a very old, out dated and unsupported wallet... It also has/had no "buy/sell for fiat" capability...
You cannot deposit Canadian dollars into MultiBit.
|
|
|
|
You have three possible states... 1. Base betting, waiting for a streak of losses 2. Betting high after 200 rolls under 99.34 3. Betting low after 200 rolls over 0.66 So you set the flags accordingly... 1. bettingHigh = false, bettingLow = false 2. bettingHigh = true, bettingLow = false 3. bettingLow = true, bettingHigh = false You can then check things like: if lowcount > 200 then
if bettingHigh then
#we're already rolling high, so just keep counting
... Do other stuff? ...
else
#found a streak, and not currently betting, game on!
chance = 0.66
bethigh = false
nextbet = previousbet * 1.00074
bettingLow = true
end
elseif highcount > 200 then
if bettingLow then
#we're already rolling low
... Other stuff? ...
else
#found a streak
chance = 0.66
bethigh = true
... Etc etc etc
end
end
Hopefully that gets you moving in the right direction |
|
|
|
|
Show Posts
