How to use quote tag: 1. Put the message you want to quote between [ quote] and [/quote]. You should have that: [ quote]blahblahblah[/quote] 2. Write your comment AFTER [/quote]: [ quote]blahblahblah[/quote]lulz 3.  4. Profit |
|
|
|
This is a great possible addition to secure bitcoins 'offline', problem is, it's very user-unfriendly.
These functions should be in the normal client, using a nice interface, instead of the need for 2 or more different command-line tools.
For your post, the message of iamzill does apply If it's integrated in the client, the functions will be known by attackers and bruteforce will be far more easy So either the client integrates thousands of different functions of the passphrases and user must learn which one he used, or that great idea will be reserved for people willing to study a little bit Also, no need for command line: http://www.miraclesalad.com/webtools/md5.php |
|
|
|
Instead you can create yourself your privkey (at least the hex one, 64 characters long, I don't know if all base59 ones are valid they are not because of the checksum) using your own pattern that you know by heart, thus no need to write it
E.g. 1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef for 19ffB4HttNCHfY1t3YuErEytCspyHyVMwv
just for fun i sent you 0.02 btc to that imaginary address  ...you'll have to now import it quick before someone else does  I nearly lost them, just figured out my wallets seem broken  I had to pay fees for not being stolen but thanks  Really smart, I love it Just one thing: the priv key has been written somewhere Instead you can create yourself your privkey (at least the hex one, 64 characters long, I don't know if all base59 ones are valid they are not because of the checksum) using your own pattern that you know by heart, thus no need to write it E.g. 1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef for 19ffB4HttNCHfY1t3YuErEytCspyHyVMwv Or if you prefer learn sentences: md5('I love bitcoin').md5('Paypal suxxx') for 1G1b4mbjaCYNxsZJyaWV9qyE5cFVhZxBcy Or even substr(md5('I love bitcoin'), 0, 14).md5('Paypal suxxx').substr(md5('I love bitcoin'), 14, 18) This is very dangerous and very stupid, and I'm talking about sending BTC to an anonyomus Nevis LLC level stupid here. The current bitcoin market cap is $90 million USD. Even if just 1% of bitcoiners take your advice, that's still $900,000 USD free money for anyone capable of setting up a GPU farm (a rare talent, I might add ). Human chosen passwords only have 1.0 to 1.5 bits of entropy per letter. Your examples contain less than 30 bits of entropy, and that's not taking into account the hacker will populate their dictionary with frequently appearing words from this forum. Compared to the ~256 bits of entropy in real Bitcoin keys, your method would generate private keys that are 2^226 ~= 1.07839787 × 10^68 times easier to brute-force. That's why I added the substr trick... If people are stupid enough to just use md5.md5 that's their problem... Everyone who is savvy enough to know how to concatenate two md5's know they MUST use salts and tricks like that too... 1KJvYREkZxEgDczTKoEtvrhfkALsFsWKRa: my two passphrases are 'jackjack' and 'iamzill', come at me bro |
|
|
|
Really smart, I love it Just one thing: the priv key has been written somewhere [NSFNewbies]Instead you can create yourself your privkey (at least the hex one, 64 characters long, I don't know if all base59 ones are valid they are not because of the checksum) using your own pattern that you know by heart, thus no need to write it E.g. 1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef for 19ffB4HttNCHfY1t3YuErEytCspyHyVMwv Or if you prefer learn sentences: md5('I love bitcoin').md5('Paypal suxxx') for 1G1b4mbjaCYNxsZJyaWV9qyE5cFVhZxBcy Or even substr(md5('I love bitcoin'), 0, 14).md5('Paypal suxxx').substr(md5('I love bitcoin'), 14, 18) |
|
|
|
Avoir 2 raccourcis bitcoin pointant sur 2 datadir différents est tout à fait faisable, mais je ne sais pas si l'on peut lancer le client bitcoin 2 fois en même temps (je ne pense pas, mais à confirmer).
S'ils ont des datadir différents et des ports différents, si si * Je crois que la création d'un virement sans être connecté au réseau fonctionne, mais à confirmer ! Sinon, toute la méthodologie s'effondre ^^
Pas encore mais c'est prévu je crois avoir lu |
|
|
|
|
Look at curl, it should help
|
|
|
|
+1 for joespie91 AND +1 for John Smith. I feel that they both make some good points.
I think there are a whole lot of possible tests that each one of us would fail and there is a realistic possibility of any number of them coming to pass.
+1 |
|
|
|
|
Just to let you know, the error was on Ubuntu, not Windows
I don't have access to my laptop right now, i'll test asap
Also I made a mini script to compile when make doesn't find cl.h
I didn't make a pull request because it's rather dirty but it might be useful for some
It's useful for me because I can compile without modifying oclvanitygen.c: the script modifies oclvanitygen.c, runs make, then modifies oclvanitygen.c back
|
|
|
|
I just saw the -o flag, I will make pywallet read the output files On my laptop oclvanitygen crashes (actually it worked once and crashes since then): Difficulty: 4553521
clBuildProgram: CL_BUILD_PROGRAM_FAILURE
Build log:
Internal error: Link failed.
Make sure the system setup is correct.
Device: ATI RV730
Vendor: Advanced Micro Devices, Inc.
Driver: CAL 1.4.1385
Profile: FULL_PROFILE
Version: OpenCL 1.0 ATI-Stream-v2.1 (145)
Max compute units: 8
Max workgroup size: 128
Global memory: 268435456
Max allocation: 268435456 I made a commit adding the addrtype flag and sent it I used it to make the address of both Namecoin Faucet and Testnet Namecoin Faucet: FaucetFbyx6bCZX84Va8YxAxUNMxJfJhRD |
|
|
|
Maybe she deleted wallet.dat |
|
|
|
Too many people in one pool very bad for Bitcoin.
I think you a word in this sentence. |
|
|
|
ok... I'm sorry if I am still being a little dense, but what exactly do you
mean "write the address of your new empty wallet"
I was meaning "write down somewhere the bitcoin address of the new wallet", to know where to send your coins How do I make a new empty wallet? By just naming any plain old file emptywallet.dat and saving it with notepad or something? Or do I have to run and install a bitcoin client on a separate machine?
Or are you saying.... once I rename my wallet.dat to walletsavings.dat - the bitcoin client will automatically create a new wallet.dat and then a new adress to it, and THAT is the file I rename to emptywallet.dat and then rename
walletsavings.dat back to wallet.dat and poof, my coins are there again when I retstart the client... then I send to that address... close the client and do the renaming thing again and take start the client.... wait to receieve the coins... repeat process with multiple names and store multiple walletsavings1.dat walletsavings2.dat around in various secure locations?
Then you just close bitcoint client, move the wallet back in and rename it as wallet.dat when you want to use the coins from that particular wallet and start up the client again.
Yes exactly, sorry for my poor english  What would happen if you did this while the client was running?
I don't know, but it's not a good idea |
|
|
|
|
Le dossier Bitcoin existe bien ?
Si oui, vide le pour voir (garde peut-être le wallet au cas où)
|
|
|
|
you guys know what we say about Poland in Germany? "That was a mistake?"  no I mean the jokes (sorry to the Polish ppl here ) You know where you find your car after it got stolen? (you can replace car with any good you want ) Oh I know another one: Why do Russians always steal 2 cars in Germany? - Because on the way home, they have to pass through Poland! Anyways: Maybe it still can somehow be recovered? Pay the hoster to rip out the HDD asap and run some undelete programs... I don't know which infrastructure they used though, so it might or might not help. Edit: Ok, read the statement... where exactly does it state how many BTC were lost? It only says, bitomat.pl is for sale for 17 000 BTC, not that 17k have been "flushed". They try to sell bitomat.pl for 17 000 BTC to give back people their money |
|
|
|
|
As far as you don't delete your wallet.dat, the coins aren't lost
There are many threads about that error, you should find them and resolve the problem
|
|
|
|
The Registration Pin is only for bots, really, so it's not a security risk as far as I know. Is that what you are getting at?
It's not a security risk but they are far too simple, bots can read them easily Why not using recaptcha? |
|
|
|
|
This is relevant to my interests
Too bad Python3 is needed
|
|
|
|
|
I like where this thread is going
|
|
|
|
You can't imagine how hard I want to see that kind of sites succeed in the future Btw, please, add a favicon Edit: your 'Registration PIN' can be OCR'd immediately, you should change it |
|
|
|
|
Show Posts
