It's a base58 encoded (without the checksum) 32 byte elliptic curve hex private key. It corresponds to the WIF private key 5Jno1aCaRaBWS3DKf5DDB96A5xSTqCJC4GbjQXPBWr8edhWX3Cg
Here's a private key of the same format as the one starting with 9:
4ujvNgAQsPYyGYRes6FCTVXR5zhvotRnZGH2KF8BBov3
See if you can get it. It's for the address 1ErkEFoAQYYNkP9GKk6MW9VyPMXe7EosQs
Thanks, I didn't know that it was common to just convert the secret to base58 like that. I got: 5JFsHfdCqMXmYAoQczHpg1eTCXNRsGjW7tSi3bauUmhTdqUY15z |
|
|
|
|
You're right, better to just give up.
|
|
|
|
|
I'm sure pywallet can import that, but you need the passphrase or some idea of what it might be (# characters, etc) to brute force it.
|
|
|
|
|
Just sign your transaction offline.
|
|
|
|
|
You can monitor transactions as they come in bitcoind. Read the mempool or the blocks as they come in.
|
|
|
|
|
4/1 means it found a difficulty 4 share, but it only need a difficulty 1 share. It counts as a difficulty 1 share still when you submit it.
|
|
|
|
|
When a pool finds a block they need to divide the reward up between all the miners who helped. So they need a way to track who helped and how much they helped. Someone with 1GH/sec shouldn't get as much of a reward as someone with 1TH/sec.
They could have you submit each hash you calculate. The 1GH/sec would then be sending 1 billion hashes to the pool per second, and the 1TH/sec miner would be sending 1 trillion hashes to the pool per second. Each hash is 16 bytes, so this would be 16 terabytes of data per second sending back and forth to the pool. Good luck with that. Even if they only have you send the nonce, that's a crazy amount of traffic.
So instead you could just send "shares", which is a hash that meets the lowest difficulty (1). Of course these aren't valid solutions, because the actual difficulty is much much higher than that, but they represent that you did some work, because it actually takes many hashes to luck out and hit a difficulty 1 solution. So this cuts down on the traffic with the server. If you have a fast miner, even this is too much traffic, so you can only send in difficulty 2 shares, difficulty 100 shares, etc. As long as the pool knows you're only sending in these types of shares they can calculate how much hashing power you have, and what % of the reward you should get.
|
|
|
|
You could use another client and sweep the key. Or use something like sx and do it yourself.
|
|
|
|
so bitcoins are traceable back to you? like if i spend coins to soemone they are always going to be recorded as i sent xx coins to this address?
Yes, unless the blockchain is cut down to save space at some point. |
|
|
|
cp1, Why 51 characters?
Because that's what a private key is. |
|
|
|
|
I'm sure it means there's now two ways you can go to jail.
|
|
|
|
|
Get used to compiling and installing libraries -- it will make your experience with linux much better.
|
|
|
|
hehe, "company"  sorry for the noob-ness but what do you mean greyhawk It's unlikely that someone who steals from online wallets would hold their coins in an online wallet. Did you ever have a backup in any form? You may just have a keylogger. |
|
|
|
|
Just write down 51 characters and use that instead.
|
|
|
|
Thanks for your response. I didn't know that the private key was formatted like a Bitcoin address (version byte plus checksum bytes at the end). Is it possible to import a raw private key (i.e. a 256 bit random number) or is mandatory to format the key in that way?
Unless your wallet has some import raw key mode, you'll have to format in the wallet import format: https://en.bitcoin.it/wiki/Wallet_import_format |
|
|
|
|
I'm pretty good with pywallet and various utilities, but I don't want to use teamviewer either -- I don't even have it installed.
|
|
|
|
|
This is odd -- my bitcoind can't find that transaction, but it can find the block reward transaction.
|
|
|
|
Just want to say I told you so  |
|
|
|
|
The amount is so low that the priority is also very low. Give it some time I guess.
|
|
|
|
|
Show Posts
