Yes, I'd rather have a refund because the chip cost refund would be more than the unit would make. But I haven't heard back from steamboat  |
|
|
|
I look around in parsePrivateKeyData and figured out what I needed to add to my base58 conversion, thanks.
So what was it? I just did the same thing as you did at first and got a wacky answer. I haven't looked at that in forever, so I'm curious what I forgot. I had to take the substring of the hex instead of the substring of the private key and then it worked. line = "5KJvsngHeMpm884wtkJNzQGaCErckhHJBGFsvd3VyK5qMZXj3hS" binEntry = base58_to_binary(line) print prettyHex(binary_to_hex(binEntry[1:33])) |
|
|
|
|
I look around in parsePrivateKeyData and figured out what I needed to add to my base58 conversion, thanks.
|
|
|
|
Third, they announce a clearance sale on refunded chips.
When did they do this? Link please. It's in the email he quoted. |
|
|
|
|
I'll be in, I had some personal stuff come up last time.
|
|
|
|
|
Success! Thanks
parsePrivateKeyData worked great. I still can't figure out base58_to_binary though (not a big deal). I did try substringing at first using [1:-4], but it never worked for me, I always get too many bytes (and also the wrong answer).
For example:
line = "5JdeQ39z8NUkNVvB37tt74Cu2WSNVj7qb9PdY651UoQnqyCm937"
hardcodedPrivKey = base58_to_binary(line[1:-4])
print prettyHex(binary_to_hex(hardcodedPrivKey))
0x0000: 0d728779 7539eb09 87a0c18f 9e3fac6c 68dbe7f9 1eb106e5 0793d7b9 6e03697f
0x0020: f673
But parsePrivateKeyData works perfect:
line = "5JdeQ39z8NUkNVvB37tt74Cu2WSNVj7qb9PdY651UoQnqyCm937"
pk = (parsePrivateKeyData(line)[0])
print prettyHex(binary_to_hex(pk))
0x0000: 6b88c087 247aa2f0 7ee1c595 6b8e1a9f 4c7f892a 70e324f1 bb3d161e 05ca107b
Ha, and funny enough it just loaded the transactions for this key in armoryqt and there was a small transaction in May. People use the worst brainwallets.
|
|
|
|
|
Thanks, that worked great for a 32-byte hex key. Is it possible to import from WIF? I've tried:
wlt.importExternalAddressData(privKey=SecureBinaryData(base58_to_binary("5KaPWnaXTLUdv5WdbwbiXbjDqUFXEUT1aAgSGrYHtzuGD5mooWv")))
But I get: assert(plainPrivKey.getSize()==32)
Do I have to convert from WIF to 32-byte first? Is there a function in armory? I was snooping in bulkImportAddresses() and found snippets to deal with base-58 private key, but couldn't turn it into anything working.
Edit: It must be in there somewhere because I think you can import WIF from armoryqt. Now I'm on a hunt!
|
|
|
|
It's also possible they could have lied about going to direct shares which means once the exchange goes down it's game over. At least if they are the only ones left holding any shares...
That would mean that they are the only ones buying shares. I wouldn't bet on them holding any shares. |
|
|
|
I haven't seen that loop since I started running bitcoin-qt independent of armory. But I've only open and closed it a few times, so it could just be a coincidence. I know you're busy, but I have (hopefully) a quick question -- I'm trying to add an address to a wallet following the add 500k address in extras, but only adding 1 key (I took out the key reading loop and just used line = private key). I'm not doing it right because armoryqt.py gives me a checksum error on keys that were already in the wallet: line 3245, in unserialize '('+hash160_to_addrStr(self.addrStr20)+')' armoryengine.UnserializeError: Checksum mismatch in PrivateKey (1LMsGerE3FmWmJig6e5DpmjctFar6RVR2L) import os
import sys
sys.path.append('..')
from armoryengine import *
# Could use sys.argv but this script will be used, like, once. Hardcode it!
wltID = 'ydeMUhu' # this was the ID of the wallet I tested with
wltDir = 'ydeMUhu' # this was the ID of the wallet I tested with
wltfile = os.path.join(ARMORY_HOME_DIR, 'armory_%s_.wallet' % wltID)
wltfilebak = os.path.join(ARMORY_HOME_DIR, 'armory_%s_backup.wallet' % wltID)
if not os.path.exists(wltfile):
print 'ERROR: Wallet does not exist:', wltfile
exit(1)
# Remove the backup if it exists
if os.path.exists(wltfilebak):
os.remove(wltfilebak)
# If you don't delete the backup, Armory will think the primary wallet
# is corrupted and restore the backup
exampleEntry = hex_to_binary( \
'0047b8ad 0b1d6803 260ce428 d9e09e2c d99fd3b3 5947b8ad 0b1d6803 260ce428 '
'd9e09e2c d99fd3b3 59fb1670 0860fecd 00030000 00000000 00ffffff ffffffff '
'ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ff71ca50 49feffff '
'ffffffff ffffffff ffffffff ff000000 00000000 00000000 00000000 005df6e0 '
'e2eeeeee eeeeeeee eeeeeeee eeeeeeee eeeeeeee eeeeeeee eeeeeeee eeeeeeee '
'eec93a79 dd04a706 ad8f7311 5f905002 66f273f7 571df942 9a4cfb4b bfbcd825 '
'227202da bad1ba3d 35c73aec 698af852 b327ba1c 24e11758 936bb632 2fe93d74 '
'69b182f6 6631727c 7072ffff ffff0000 00000000 00000000 0000ffff ffff0000 '
'0000 '.replace(' ',''))
wltOut = open(wltfile, 'ab')
rawAddrEntry = exampleEntry[21:]
addr20 = rawAddrEntry[:24]
fixed1 = rawAddrEntry[ 24:108]
prvkey = rawAddrEntry[ 108:144]
pubkey = rawAddrEntry[ 144:213]
fixed2 = rawAddrEntry[ 213:]
addrDataToWrite = []
line = "5KaPWnaXTLUdv5WdbwbiXbjDqUFXEUT1aAgSGrYHtzuGD5mooWv"
privBin = base58_to_binary(line[1:-4])
pubBin = CryptoECDSA().ComputePublicKey(SecureBinaryData(privBin)).toBinStr()
addr20 = hash160(pubBin)
# Pre-PyBtcAddr Entry Header
addrDataToWrite.append('\x00')
addrDataToWrite.append(addr20)
# PyBtcAddr itself
addrDataToWrite.append(addr20)
addrDataToWrite.append(computeChecksum(addr20))
addrDataToWrite.append(fixed1)
addrDataToWrite.append(privBin)
addrDataToWrite.append(computeChecksum(privBin))
addrDataToWrite.append(pubBin)
addrDataToWrite.append(computeChecksum(pubBin))
addrDataToWrite.append(fixed2)
wltOut.write(''.join(addrDataToWrite))
wltOut.close() Any ideas? |
|
|
|
Strange they went through at the EXACT same time and have the exact same confirmations. Last question and I will leave you guys alone for a bit  When backing up Bit QT should I save an extra copy? to a USB? Just thinking if some how mu computer crashed. It just means they were in the same block. The blocks are mined every 5-10 minutes. |
|
|
|
I started accepting them for Biz so I wanted to play with it so I could work out kinks like this before I really got started.
You should use something like bitpay to accept bitcoins -- they'll automatically convert it and send you dollars/euro/etc. Otherwise you take a risk of the BTC value dropping before you can convert it. |
|
|
|
Is there any firmware that lives in the device in NVRAM of some sort, or is everything loaded at runtime?
It's all precompiled and sits in the flash memory on the pic. |
|
|
|
When starting it for the second time, after downloading what blocks it had to, it got stuck scanning on 1%. I found this in the log over and over, for a very long time.
-WARN - 0: (..\BlockUtils.cpp:4865) Marking orphan chain
-WARN - 0: (..\BlockUtils.cpp:4888) Done marking orphan chain
I just added an empty wallet while it was loading and got this loop. I closed and restarted and it's scanning transaction history again, says 20 minutes remaining. |
|
|
|
Finally got around to building it. It worked fine without any makefile changes on Ubuntu 13.04 64-bit. I think it took about 3 hours to build the database, but I wasn't watching very closely. It loads instantly on a wallet with no balance Very nice work. |
|
|
|
OK, well I guess Euclid's Elements was just a load of rubbish then. Which would make Newtonian physics pretty baseless too. Or maybe assuming is equivalent to knowing in a scientific context? Otherwise why bother making assumptions if we have doubts about their soundness? E.g.: assuming that Earth orbits the Sun, we do [ whatever measurements and stuff ]. According to Newtonian physics, the sun should also swivel a little bit due to the mass of the earth pulling on it (like an athlete doing a hammer throw), but we wouldn't know any of that without relying on Euclid's postulates. That's math, not science. |
|
|
|
|
When I ran bitcoind on my raspberry pi it took 100% cpu and made the system unusable. It might have been OK after syncing was over, but I didn't have the patience to wait. Would be interesting to hear of some successes.
|
|
|
|
|
It's silly to lower the max wager because someone gets lucky. The math doesn't change. The max wager should be 0.5% of bankroll for the even money bet. Otherwise you're not maximizing your investors' profits.
|
|
|
|
|
The only thing a malicious server could do would be to lie to you about how many bitcoins you have. It can't steal them or anything. It's a good way to go if you don't want the blockchain hassle.
|
|
|
|
|
Show Posts
