You're assuming DB uses the same bitcoind as the bitcoind that [Tycho] issues payments. I highly doubt they are the same and if it is, that's a huge security risk as far as setting up pools and issuing payments to pool members. [Tycho] has already confirmed that he only keeps a 'minimal' amount of BTC's on-hand for payments so I'm sure he's running at least a few different wallets/bitcoind's. I never thought about it that way But it's still strange, he could use a modified bitcoind that accepts all tx's from his node processing payments There's a reason he doesn't do that, I must forget something For the OP, it won't show up in Blockexplorer yet. OP verified it's still an unconfirmed transaction (TX) via http://bitcoincharts.com/bitcoin/ (which is down right now). He has all the blocks on his client I believe. Sorry I didn't read post#8 carefully |
|
|
|
All these immediate accusations of SCAMMER! just hurt bitcoin as a whole.
He's not getting or asking for any money from anyone. How can he be a scammer?
This I just don't get it  |
|
|
|
A payment FROM Deepbit is unconfirmed?
As they put payments in the blocks they find, it's kinda weird...
https://en.bitcoin.it/wiki/Transaction_feesOn the other hand, nobody mining new bitcoins necessarily needs to accept the transactions and include them in the new block being created. The transaction fee is therefore an incentive on the part of the bitcoin user to make sure that a particular transaction will get included into the next block which is generated.Basically, it's up to the people/pools in determining which TX's are accepted and put into the new blocks as they are found. As you've noticed, those people/pools have been ignoring the low-priority/no-fee ones lately. http://blockexplorer.com/Check the 'Transactions' column. Cheers, Kermee Deepbit is a pool. Is it really smart to refuse its own tx's? A payment FROM Deepbit is unconfirmed?
As they put payments in the blocks they find, it's kinda weird...
Yup, and still unconfirmed. Going on 6 1/2 hours now. Guess I'll have to wait until tomorrow (as per post above). Did you check your transaction in blockexplorer? The link is the date column in the Deepbit payments page You have all the 139497 blocks? If so, you should contact them |
|
|
|
|
A payment FROM Deepbit is unconfirmed?
As they put payments in the blocks they find, it's kinda weird...
|
|
|
|
|
Anyway, what is dwolla???
|
|
|
|
Any one else get this from MTGOX? Thank you for your support and for using MtGox. We appreciate your presence and would like today to give you a free Yubikey. Considering recent problems with hacked accounts, hacked computers and more, we see the Yubikey as a good step toward better security. You can read more on the Yubikey from the Yubico website: http://www.yubico.com/ - note that the yubikey we sell is only usable on MtGox. To receive your free yubikey, you just need to login on mtgox.com, click "Order a Yubikey" in the menu, choose if you want either a yubikey with our logo or not, and on the next page enter the following code: And the "following code" is ? It might help if you read the rest of the email... (note: this code will expire end of december.) Once done, you can fill your address, and confirm your order on the following page. Please remember that the code can be used only once (after confirming your address, the code will not be usable anymore). You can also give this code to someone else and let them get a free Yubikey. Thank you again for your continued support. From all the MtGox team info@mtgox.comhttps://mtgox.com/ BTW, I got one too |
|
|
|
|
I just added the warning, thanks for pointing that out
I'll search if I can see when bitcoin is running
Auto-filling with default wallet location ok
|
|
|
|
Nice!
If the capitalization was intentional (and it looks like it was), that's one of the most complex prefixes that anyone has found to date.
it was, though I'm looking for another one that stands out a bit more ... but I'm fairly happy with that one  I found Jackjack7eYNdGkbgUUrtKBraSWBUV5DJP too With such speeds I think an address with 8 fixed characters can be found Maybe more with vanitygen pools  That might interest some people here: I just finished a web interface for pywalletDownload the last version, run ./pywallet --web and go to localhost:8989 |
|
|
|
News: August 2014My boring professional life made me stay away from bitcoin for far too long but I'm now back in business Pywallet won't be fixed anymore except for critical bugs Instead I'll finish its successor (that still has no name) News: September 2013I'm rebuilding pywallet from scratch: This threadFirst of all, I'd like to thank Joric for the first version of pywallet he made, this thread is about my fork. Pywallet is a python script that deals with wallet.dat. It allows you to do plenty of things inside it. You can post here whatever you want about pywallet: critics, asking for improvements/changes, telling me it helped you, pointing out errors/bugs, etc. Pywallet 2: 22nd March 2013Pywallet has been discontinued for around a year but is now actively developed again. Look at the end of the 7th page for updates: encrypted wallet support, exporting/importing to/from files, merging wallets, etc. Instructions (see also here) Currently you can: - Dump your wallet, see your pubkeys, privkeys, their labels, etc
- Under "Dump your wallet:"
- Fill version with 0 for bitcoin, 52 for namecoin, 111 for testnets
- Dump your transactions to a json file
- Under "Dump your transactions to a file:"
- Fill Output file with the full path to the file where you want the transactions to be written, this file must not exist
- Import a key/address into your wallet, with a label, or as a reserve key
- Under "Import a key into your wallet:"
- Key is the private key to import, in base58 or in hexadecimal chars
- Label is the name you want to see in the Address Book of the client
- Check Reserve if you want your address NOT to show in the Address Book
- Version = 0 for bitcoin, 52 for namecoin, 111 for testnets
- Format of the private key: Hexadecimal if you see only digits, a, b, c, d, e and f, otherwise chose Regular
- Import a transaction into your wallet
- Under "Import a transaction into your wallet:"
- Txk is the tx_k value you see in the wallet dump
- Txv is the tx_v value you see in the wallet dump
- Import transactions from a json file
- Under "Import a transaction into your wallet:"
- Txk = "file" (without quotes)
- Txv = full path to the transactions dump file
- Delete addresses from your wallet
- Under "Delete a key from your wallet:"
- Key is a Bitcoin address, not a priv key
- Type: Bitcoin Address
- Delete transactions from your wallet
- Under "Delete a key from your wallet:"
- Key is the hash of the transaction you want to delete (type "all" to delete them all)
- Type: Transaction
- Get info about a privkey, i.e. see address, base58 privkey, hexprivkey, pubkey and hash160, using the network you want
- Under "Get some info about one key[and sign/verify messages]:"
- Key is a private key
- Leave Msg, Sig and Pubkey empty
- Version = 0 for bitcoin, 52 for namecoin, 111 for testnets
- Format of the private key: Hexadecimal if you see only digits, a, b, c, d, e and f, otherwise chose Regular
- Sign and verify string, files, and binary string
- Under "Get some info about one key and sign/verify messages:"
- Key is the private key you want to sign the message/file with (only for signing)
- Message is the message you want to sign/verify
- If it is a string, just type it
- If it is a binary string, type "Hex:" just before its hexadecimal representation
- If it is a file, type "File:" just before its full path
- Signature is the signature of your message (only for verifying)
- Pubkey is the pubkey used to sign the message (only for verifying)
- Read a device to find deleted keys (CLI only)
- Assuming that:
- The device you want to read is /dev/sda3
- The size of /dev/sda3 is 30.1Gio
- You want pywallet to write the new wallet containing the found keys in /home/jackjack/recovered_wallets
- Run "sudo ./pywallet.py --recover --recov_device /dev/sda3 --recov_size 30.1Gio --recov_outputdir /home/jackjack/recovered_wallets"
- Then replace your wallet (back it up before) with the recovered wallet and run "bitcoin -rescan"
- Print the balance of a bitcoin address, read from blockexplorer
Installation:
- Linux/OSX: See README file
- Windows:
How to run it: Download it there: https://github.com/jackjack-jj/pywallet Run './pywallet.py --web' then open ' http://localhost:8989' in your brower Requirements: Python 2.5-2.7, with bsddb package  twisted package is necessary if you want to use the web interface  ecdsa package is necessary if you want to sign and verify messages Confirmed to work on: Ubuntu 32bit(me) Windows 32bit(me), 64bit(ctoon6) OSX(defxor) Pywallet can be used to: Import Vanitygen keys Delete 0/unconfirmed transactions Recover Namecoins (and testnetcoins) sent to Bitcoin addresses Create a deterministic wallet (using a passphrase) Create a deterministic wallet (using a file) Broadcast offline transactions Create a Bitcoin/*coin address from scratch Recover a wallet/deleted keys
|
|
|
|
Yeah everything is a scam I always knew MtGox was a scam  Tradehill too bitmarket too coinedbits too bitomat too OH SHIIII- |
|
|
|
le 2è a été trouvé 7 minutes après le 1er, avec 218 shares, pour un hashrate moyen de 2.23 Ghash/s ! C'est donc 50 bitcoins supplémentaires que ce sont partagés les quelques (fidèles  ) mineurs qui minaient entre 9h47 et 9h54 ! Vous venez d'épuiser votre chance pour les 10 années à venir, changez tous de pool |
|
|
|
|
Go on everybody, sell, sell, SELL!
|
|
|
|
Same |
|
|
|
this is btc from mybitcoin
Quite possible |
|
|
|
I'm sure someone will quote Matthew, with his post...
I sure hope not. I was laughing so much while writing it I don't even know what I said.  You should read it again then, it's just hilarious, you should post in more threads |
|
|
|
I'm sorry but that trick only adds a negligible amount of entropy, which is negligible. It doesn't matter what kind of tricks you use, whether you end up with 20 bits of entropy or 200 bits of entropy, you're still greatly weaking the system. Suppose by using lots of passwords, lots of substr, repeated hashes, and salts and you end up with 250 bits of entropy, that's still only 1.5% of the entropy of a real key. Is it worth it to go through all that custom code and memorization just to end up with a private key that's 64 times weaker? Isn't it much safer just printing out the key pair like OP suggested or burning the wallet.dat on a CD?
As for your challenge, you missed my point about mentioning the $900,000 USD reward money. I'm not saying it's possible for an attacker to target your specific password. In fact, I can almost gurantee your address 1KJvYREkZxEgDczTKoEtvrhfkALsFsWKRa won't be brute-forced. I was claiming that if enough people saw your post and adopted your method, the attacker can steal from those people collectively, since they all share the same tiny keyspace.
Sorry if I come off as too critical, but I'm just trying to make sure bitcoin stays secure. If lots of people spoke out critically against mybitcoin in the first place then it wouldn't have ended up the way it did. I believe the only to way to ensure the collective security of the bitcoin eco-system is to harshly criticize any non-secure algorithm, organizational structure, and business practice that gets suggested. Every security compromise and every fraud devalues everyone's bitcoins, and more importantly threaten the future of this cryptographic currency.
I'll stress it again, it's almost perfectly for safe for jackjack to use his method for himself. But if somehow this method ends up being implemented in the official client and thousands of people start using it, then the bruteforcing will begin and people will lose money and see it as a bitcoin security hole when it clearly isn't. I'm only criticizing it so that this worst case scenario doesn't happen. You're more than welcome to use it on your own.
Sure it's less secure but at least people using that won't lose/delete/formatc:/etc their wallets definitely and cry "I deleted my wallet.dat, I can't recover my coins, it's Bitcoin's fault" anymore I think that if each person choses his own function and knows they are weakening his safety, it's remains mostly ok The problem is indeed if people use it without understanding what they do or if the functions are in implemented in the client I didn't understand your first post like that I'll add a NSFNewbies tag in my post  |
|
|
|
|
I'm sure someone will quote Matthew, with his post...
|
|
|
|
ats@ats-desktop:~/poclbm$ ./poclbm.py -v -d1 http://l_0:p@deepbit.net:8332
01/08/2011 16:02:22, Setting server (l_0 @ deepbit.net:8332)
deepbit.net:8332 01/08/2011 16:02:23, Unexpected error:
Traceback (most recent call last):
File "/home/ats/poclbm/HttpTransport.py", line 45, in loop
self.queue_work(work)
File "/home/ats/poclbm/Transport.py", line 115, in queue_work
self.process(work)
File "/home/ats/poclbm/Transport.py", line 74, in process
self.set_difficulty(work.difficulty)
File "/home/ats/poclbm/Transport.py", line 67, in set_difficulty
true_target = '%064x' % (int(bits[2:], 16) * 2 ** (8 * (int(bits[:2], 16) - 3)),)
ValueError: invalid literal for int() with base 16: 'eefa1-1'
deepbit.net:8332 01/08/2011 16:02:23, LP connected to deepbit.net:8332
deepbit.net:8332 [268.906 MH/s (~0 MH/s)] [Rej: 0/0 (0.00%)]^C mining works but no share submitted. repost from russian newbie thread https://bitcointalk.org/index.php?topic=33432.0Same here |
|
|
|
|
Show Posts
