His GPUs are burning, his VRMs frying most likely. His cards need some cleaning from all the dust that they've probably accumulated.
|
|
|
My monthly traffic is usually 2.5-3TB. 10GB in 20 days, Nowhere near enough for me.
|
|
|
To be honest, I already had thought of a Vanity pool concept last year around this time, trouble was that I had no idea how it would work. Back then I was not familiar with public-key cryptography much less that you can add them or multiply them. 1. provide instructions for generating EDCSA key pairs.
Sure, I`ll try doing that with the next update. 2. realistic bounties based on difficulty.
Yeah, I`ll probably have to do something about it. So far "pay what you want" has turned out to be "pay minimum amount" ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif) . Question: Have you received enough interest in your project to warrant a move from a bounty system to a true pool system where everyone in the pool is working to generate a vanity address and then shares in the profit? The bounty method seems incredibly wasteful.
Not yet. So far the interest has been slim. But yeah, once the site gets popular I`ll probably have to move into the traditional pool system. For now, I`m just keeping it simple. I like your project enough that I've sent you a very small donation. I hope this develops into something the community can use as a viable income resource in the future.
Thank you for your donation. I also hope more people become interested in the project. Perhaps some hybrid between a vanity address and a Bitcoin debit card would do the trick... ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Perhaps calculate the difficulty of the pattern like in VanityGen and using some formula to calculate the fee for finding it.
|
|
|
Interesting discussion. Valid points, too.
|
|
|
Windows will be tough, some C applications usually require little to no modification to compile under GCC(Windows) whereas some may be much harder to do. It really depends on how much OS specific APIs you use.
|
|
|
Well, there are 115,792,089,237,316,195,423,570,985,008,687,907,852,837,564,279,074,904,382,605,163,141,518,161,494,337 private keys according to the wiki article(not full 2^256 because of secp256k1). And this number is pronounced as one hundred fifteen quattuorvigintillion, seven hundred ninety-two trevigintillion, eighty-nine duovigintillion, two hundred thirty-seven unvigintillion, three hundred sixteen vigintillion, one hundred ninety-five novemdecillion, four hundred twenty-three octodecillion, five hundred seventy septendecillion, nine hundred eighty-five sexdecillion, eight quindecillion, six hundred eighty-seven quattuordecillion, nine hundred seven tredecillion, eight hundred fifty-two duodecillion, eight hundred thirty-seven undecillion, five hundred sixty-four decillion, two hundred seventy-nine nonillion, seventy-four octillion, nine hundred four septillion, three hundred eighty-two sextillion, six hundred five quintillion, one hundred sixty-three quadrillion, one hundred forty-one trillion, five hundred eighteen billion, one hundred sixty-one million, four hundred ninety-four thousand, three hundred thirty-seven
|
|
|
If this library will be libevent dependant, it's already not portable, since libevent is hardly found for Windows. And I also found this bit of code void CBSecureRandomSeed(uint64_t gen){ FILE * f = fopen("/dev/urandom", "r"); // Using urandom for speed. fread((void *)gen, 32, 1, f); } There is no /dev/urandom on Windows. Though I suppose, since it's still early in development, Windows support could wait, but then again when you add more dependencies which are for Unix machines(I have not seen a port of libevent for Windows, for instance), it will be tough to add Windows support.
|
|
|
I see that Abe is still under development, when can we expect 0.7?
|
|
|
Somehow I doubt that. I am more inclined to believe that a planet has a billion times more atoms than that number, considering a human body has a similar value, according to this article: http://education.jlab.org/qa/mathatom_04.htmlBut I am no physicist.
|
|
|
I CANT WAIT TO UNCOVER ONE OF PIRATE'S ADDYS HERE WE GO
I bet if someone does find an address it will be .000001 bitcoins or something lol
Not unless you have a list with address to look for. The ones I suggest trying to look for are Satoshi's addresses since it's unlikely they will be spent anytime soon, if ever.
|
|
|
just a warning.... don't run random executables linked on this forum... ![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif) Sure, sound advice! I do guarantee that this app does no malicious things, but I agree that to be on the safe side in general, either run executables in a secure virtual machine or sandbox (such as Sandboxie) or compile them from the source. The (quite short, exactly 75 lines!) source code for this app will be released soon. I need to clean it up a little and make it more readable - it's still a little messy right now. Very cool Project, even though of course it's a bit 'pointless'. What happens when (as in before the sun dies out) you find a non-zero balance? Also- does it support GPU's? :-) Also- can you export all these Bitcoin addresses and Private keys? IE: can it double as a key pair generator? Sure, all addresses along with their private keys are automatically exported to a file on the desktop (the location will be changed to something more sensible in the next release) From my experience, there were different ways to get the current user's home directory under XP and W7. You'd need to handle that properly.
|
|
|
Your goal may not be to do that to blockchain.info, but it is still exactly what you are doing.
Ive actually written a similar cmd-line app, but it uses a file with exported addresses that have more than 50btc in them. ABE is very useful here, albeit slow to import the chain.
|
|
|
Does this mean if either part is lost, you lose access to any coins in there?
|
|
|
Alright, achieved an almost 200-300%(varies a lot) increase in key generation by moving code a bit. UI elements will now correspond to the correct API Level. Added an About OpenSSL dialog which will tell you the OpenSSL version used, should be the one that comes with the phone, or if it is an older device, then use the static libraries in the Compatability version. Added Elapsed time and planning to add Estimated time.
Update September 1st, 2012.Ok, I have added a new feature. I have added the ability to select between 3 chains, Bitcoin,Namecoin and Litecoin as well as two themes, Dark Holo and Light Holo which were introduced in Honeycomb 3.0. This is why this time I am providing 4(four) different versions: - Compatability version <- For Android platforms <3.0 as well as statically linked OpenSSL 1.0.0a.
- Normal version <- Uses UI elements that are standard for the platform(noticeable difference from first version if ran on a >3.0 device), comes with shared libraries, but they are never actually used, since the phone uses the more recent ones that come with Android, on ICS 4.0.3 that would be OpenSSL 1.0.0e.
- Holo Light version <- same as Normal version, except that the theme is Holo Light.
- Holo Dark <- same as Normal version, except that it is a darker theme.
But, with new features come new bugs. The new bugs are: Navigating away from the application while it is looking for a Regex match will not continue to search for a vanity address thus resuming the application you will find out it had stopped and was reset. Same thing happens when screen goes off or the user locks the phone. Should be resolved in v0.2bFor the same reason, if you try to copy either the private key or bitcoin address and navigate away to paste it into another app, after resuming a new address will be generated thus you will not have the ability to copy the private key or bitcoin address associated with the address/private key you had previously copied. There is a workaround though. Android has a clipboard, so just copy the private key, then the bitcoin address and use the clipboard to fetch the data. I think this is only available in ICS. Fixed in v0.2b- The dialog that appears when clicking 'About OpenSSL' has a button which at the moment does not do anything.
- Elapsed time is only shown when a match is found
The reason I have not fixed these bugs, is that I only found out about them last night, and I don't have time to fix them since I will probably be away for a week or two, if not more. I know this sounds like more of a regression due to all the bugs, but it is Alpha, a stage where new features and bugs that come with them are expected. Normal -> http://www34.zippyshare.com/v/31630959/file.htmlCompatability version -> http://www34.zippyshare.com/v/86928096/file.htmlDark Holo -> http://www34.zippyshare.com/v/87173194/file.htmlLight Holo -> http://www34.zippyshare.com/v/53924730/file.htmlFile size is larger due to added support for SpongyCastle crypto functions. They are not used, but will be. For Technical users: Bitcoin: address type: 0, privkey type 128. Litecoin: address type 48, privkey 128 + 48; Namecoin: address type 52, privkey 180(starts with 7??). And remember, while in Alpha stage, I do not recommend using the addresses untill I implement a verification feature to ensure Privkey matches the Address displayed.[/list]
|
|
|
I was actually going to suggest using a traffic monitor to check the app, but I suppose that works as well.
Anyway, I went in and applied a few optimisations I thought would work, but somehow the JVM deattaches the thread now, so I scrapped it all and I am going to redo it.
(while at the same time trying to cross-compile a toolchain for android)
|
|
|
I think I have a plan on how to squeeze more keys on the C side. Right now the biggest bottleneck is function call overhead. In order for one address to be generated, I must call the jni wrapper which allocates memory for the private key and bitcoin address and then call the actual function where the address is generated which in turn allocates memory for the bignum variables and frees them when it is finished. Obviously allocating and freeing memory is expensive so what I plan to do is setup an event handler in the aformentioned function and if a key is requested at least a few allocations will be avoided.
And after that I will try to optimize in assembly, while ironically, I do not know any.
Also, noted on the case-insensitive search. But you also must remember that enabling such an option would disable regex.
|
|
|
Not sure if any similar apps exist, but I made one anyway. Realistically you'd never want to generate a vanity address on a phone since it is slow, considering phones are not fast as PCs, but now at least if someone asks if there is a vanity address generator for Android, we can say yes. I suppose now you are wondering if this app is safe. I can say it is, but just to assure you guys, most of you Litecoin miners used to use my binaries of pooler's litecoin miner and I could've put malicious code anytime I wanted, but did not(there was once a false positive warning of a trojan in the libcurl library, precompiled, which I had downloaded from a website I found in the official links on the curl website, but that was it). In case you are still paranoid, use a traffic minitor to see that it does not make any outgoing connections OR simply do not use the app ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) . Also, while the app does not require any permissions some are forced on the apk by default. The application is still Alpha but is in a working state, however I do not encourage you to use the addresses untill I am sure that the OpenSSL library I am using does not have any security flaws. Speaking of OpenSSL I am providing my own, but the phone might use the ones that come with Android by default, hence why it might not work on 2.3 and lower. I can confirm it works on my Samsung Galaxy SII running Ice Cream Sandwich 4.0.3. Post on which it does not. Update September 1st, 2012.Ok, I have added a new feature. I have added the ability to select between 3 chains, Bitcoin,Namecoin and Litecoin as well as two themes, Dark Holo and Light Holo which were introduced in Honeycomb 3.0. This is why this time I am providing 4(four) different versions: - Compatability version <- For Android platforms <3.0 as well as statically linked OpenSSL 1.0.0a.
- Normal version <- Uses UI elements that are standard for the platform(noticeable difference from first version if ran on a >3.0 device), comes with shared libraries, but they are never actually used, since the phone uses the more recent ones that come with Android, on ICS 4.0.3 that would be OpenSSL 1.0.0e.
- Holo Light version <- same as Normal version, except that the theme is Holo Light.
- Holo Dark <- same as Normal version, except that it is a darker theme.
But, with new features come new bugs. The new bugs are: - Navigating away from the application while it is looking for a Regex match will not continue to search for a vanity address thus resuming the application you will find out it had stopped and was reset. Same thing happens when screen goes off or the user locks the phone.
- For the same reason, if you try to copy either the private key or bitcoin address and navigate away to paste it into another app, after resuming a new address will be generated thus you will not have the ability to copy the private key or bitcoin address associated with the address/private key you had previously copied. There is a workaround though. Android has a clipboard, so just copy the private key, then the bitcoin address and use the clipboard to fetch the data. I think this is only available in ICS.
- The dialog that appears when clicking 'About OpenSSL' has a button which at the moment does not do anything.
- Elapsed time is only shown when a match is found
The reason I have not fixed these bugs, is that I only found out about them last night, and I don't have time to fix them since I will probably be away for a week or two, if not more. I know this sounds like more of a regression due to all the bugs, but it is Alpha, a stage where new features and bugs that come with them are expected. Normal -> http://www34.zippyshare.com/v/31630959/file.htmlCompatability version -> http://www34.zippyshare.com/v/86928096/file.htmlDark Holo -> http://www34.zippyshare.com/v/87173194/file.htmlLight Holo -> http://www34.zippyshare.com/v/53924730/file.htmlFor Technical users: Bitcoin: address type: 0, privkey type 128. Litecoin: address type 48, privkey 128 + 48; Namecoin: address type 52, privkey 180(starts with 7??). And remember, while in Alpha stage, I do not recommend using the addresses untill I implement a verification feature to ensure Privkey matches the Address displayed.![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FAujeG.png&t=663&c=oi5l6d0wi8USVw) Planned features: *Support for alt-chain addresses.[Semi-complete, more to be added] *Creating wallet with X keys. *Show elapsed time as well as estimated remaining time.[Semi-complete, more to be added] *Built-in check to verify addresses [Semi-complete; Addresses are generated on the native side, but will be verified on the Java side] *Support for Mini private key format [Done, but a more secure entropy for random strings must be added] *Display address/private key as QR code *Display public/private key in other ways, such as Hex instead of Base58. If possible, please post your speeds(keys per second) as well as phone models and firmware version. SGS2: 140 keys on avg going from 140 to 145 using v0.2. Wrong calculation, so the numbers were wrong. Oh, and if you like this app you can also donate to 12jujMxZodCde2o4LvLRpsXK5tF1WQ9YC9
|
|
|
Wow...replacing fans without opening the card? Can life get easier?
|
|
|
|