 Show Posts
|
|
Pages: [1] 2 3 4 5 6 »
|
|
Hello,
I'm finding a problem making sure my cold storage wallet is secure.. I find that the only loop hole in cold storage is making sure that the address generated in the offline pc are really random..
I can think of several issues:
1. a ubunto developer change the source code so that all users that create new address in bitcoin will create address from a pool of 200 million address ( so each one will get a different one) but the developer know the keys for all of them
2. downloading a bitcoin-qt client that new address generated from this client is from a pool of 200 million address ( so each one will get a different one) but the bitcoin-qt developer/hacker will have the keys for all address.
What is the best way to be absolutely sure my address is random|?
Has anyone ever thought about this issue?
Thank You.
|
|
|
|
You can create key pairs manually by throwing dice, if you want...
How can I do it? |
|
|
|
but computer can not generate reall random numbers.. Is there a way to create a bitcoin address that is connected to something I add .. like a string that I can add..?
go to http://bitaddress.org/, use the "brainwallet" option. inb4 inevitable "MY BRAIN WALLET WAS HACKED!"using a online website to create an address.. Really? |
|
|
|
|
but computer can not generate reall random numbers.. Is there a way to create a bitcoin address that is connected to something I add .. like a string that I can add..?
|
|
|
|
|
any info about EC_KEY_regenerate_key(..) What is the seed that it gets? from where the random part. the pc is only pseudo random
|
|
|
|
|
How bitcoin-qt generate address and how do I know they are really random?
Thanks.
|
|
|
|
|
Hello I was wondering how multibit is creating new address? Is it possible that multibit author can make it so that all addresss that will be created is known to him? Then he can take all the bit coins..
|
|
|
|
Hello, I followed the bitcoin community for some weeks and have finally set up my mining rig (a 5870 and a flashed 5850, more cards comming). This is my first post here. I use LinuxCoin and have been using the poclbm miner, which went quite well. Now I want to switch to phoenix, but I get the error "FATAL kernel error: Failed to load OpenCL kernel!", both with phatk and poclmb kernels. user@linuxcoin:/opt/miners/phoenix$ export LD_LIBRARY_PATH=/opt/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/
user@linuxcoin:/opt/miners/phoenix$ python phoenix.py -u http://api.bitcoin.cz:8332 -k poclbm DEVICE=0
[22/06/2011 20:28:05] FATAL kernel error: Failed to load OpenCL kernel!
user@linuxcoin:/opt/miners/phoenix$ python phoenix.py -u http://api.bitcoin.cz:8332 -k phatk DEVICE=0
[22/06/2011 20:28:30] FATAL kernel error: Failed to load OpenCL kernel!
I find this strange, since the poclbm miner uses the same OpenCL library and works fine. Can anybody help? Thanks, python ./phoenix.py ...... |
|
|
|
If mining hardware was instead dedicated to generating new addresses; how long do you think would it take till someone stumbled on an existing address that had more BTC stored than what the person would have earned by mining?
Never. Even if the whole generating network was behind it, it would probably never even stumble upon a previously used address, much less one that is worth more than the number of blocks it could have generated instead. Generating blocks is trivial compared to this. Their are 2^160 possible addresses. Lets say 2^32 (4 billion) people use Bitcoin and each generate 2^16 (65 thousand) address. That gives us 2^48 total addresses out of 2^160 possible. The probability of a generated address matching one of these is 1/(2^112). The probably of finding a block at 35 times the current difficulty is around 1/(2^64). Therefore, it would take 2^48 (281 trillion) times longer to find a previously used address. So if it takes you ten minutes to find a block, it will take over five billion years to find a used address. Now keep in mind that we don't have 4 billion users, most users have far less then 65 thousand addresses, and the current difficulty is much lower then I used in these calculations. Mining sounds a lot more profitable. NOTE: I assumed generating an address took equal time as generating a proof-of-work hash. However, I believe generating an address is actually slower since it involves both EC key generation and hashing. Dont you just like probability |
|
|
|
Doesn't Remove the tray icon? Yes it does remove the icon of the autoit script but does not remove the icon of the process started with the autoitscritp |
|
|
|
|
I had 3 5850 got 1.5BTC a day 2 weeks ago.. Now I have 6 5850 again getting 1.5BTC a day...
Very Very sad...
|
|
|
|
|
There should be a change...
I dont exactly know when but there should be...
Maybe when the reward in coins get to 25BTC instead of 50BTC?
Maybe even now.
|
|
|
|
Hey guys,
This seems like great stuff but I seem to be struggling to utilize this and that. I am very newbish to linux but I have used a fair share of command line in windows myself.
Firstly, I saw the persistence guide a few moments ago and followed it up until the point where I am asked to open a root terminal ( I am certain I opened a root term ) and enter sudo su- df. I have tried several variations of this command and have come up with 'unknown user: df' as the most promising and 'unknown command' as the most common. I don't know if anyone else came across this error, if it is some mistake on my part or whatever. Any help would be appreciated, thanks
I am excited about .2b, I wasn't able to get mining going in .2a, I did 'start_mining' but I think I may have been missing what to put into the 'kernel' portion. I tried opencl and something else having to do with phatk or something (words found through searching), but had no success.
Only if you use phoenix miners you need to write what kernel to use... anyway you can wite phatk to use phatk kernal and you can also write poclbm to use poclbm kernal |
|
|
|
|
Some bad luck maybe..
Buy you can see diff is starting to go up again/
|
|
|
|
|
This one is also long...
A bit sad.. But sometimes its long sometimes it fast//
|
|
|
|
I have had a lot of trouble with phoenix. The biggest issue being that it oftens gets stuck on "[0 Khash/sec] blah blah" and never reconnects to the server. This is especially bad when I have torrents running, even when I limit torrent traffic. The only reason I put up with it is because phoenix supports the phatk kernel, which gets me an extra 20MH/s per card. Well, I got tired of it, so I forked poclbm and hacked it to support phatk. Here's my fork: https://github.com/progranism/poclbmSo far so good, poclbm is happily running without any issues whereas my phoenix instances are freezing up  MH/s is about the same. 339 MH/s instead of the 340 MH/s I get on phoenix. Close enough. Lemme know if this helps anyone else.  I never had a problem with phoenix locking up... Every how much time it should happen? |
|
|
|
I haven't got a clue why this hasn't worked for you ? I won't be adding 11.6 to linuxcoin anyway it's very VERY unstable, stick with 11.5 for now. I got it working now and 11.6 does allow you to overclock outside of BIOS limits. The problem is that I was not installing the drivers properly. The driver seems stable in Ubuntu 11.06, but I guess it has different versions of X and other software. hugolp, can you share how you installed catalyst 11.6 on a linuxcoin 0.2a? TIA spiccioli I manged to do it... You need to have a persistent install of linux Then use this manual ... http://wiki.cchtml.com/index.php/DebianBut... One line in there is sudo sh ./ati-driver-installer-11-6-x86.x86_64.run --buildpkg <package> You need to do sudo sh ./ati-driver-installer-11-6-x86.x86_64.run --install instead... It did not let me build a package (what ever it means) I did had evantually 1 problem.. You need to uninstall aticatalyst before you install the new one...\and I think I deleted also opencl... Anyway if you dont want to uninstall the old catalyst you can just do sudo sh ./ati-driver-installer-11-6-x86.x86_64.run --install --push Then it overwrite the files already there... But they say its not good... |
|
|
|
|
