Any ideas? Yes, install Catalyst v11.11. BTW, a yearly repost?...: If you are just trying to use vanitygen, here's a Windows binary HOWTO: Installation:- If GPU acceleration is desired, install ATI Drivers v11.10-v11.11 (with SDK 2.5) or latest Nvidia driver, test that OpenCL is working with GPU miner software. If drivers with SDK >2.5 have been installed, files may need to be manually removed.
- Download and unzip vanitygen-0.22-win.zip to it's own directory.
- To interact with the program, you need to open a terminal/shell/command prompt in the program's directory. In Windows Vista/Win7 Explorer, hold down the shift key on the keyboard while right-clicking the folder where vanitygen was extracted, and choose Open command window here.
- Test CPU operation. This command line will generate a Bitcoin addresses beginning with 1ABCD in around a minute or less:
>vanitygen 1ABCD - Test GPU operation. This command line will generate a Bitcoin addresses beginning with 1ABCDE in around a minute, using the first OpenCL device in your system:
>oclvanitygen -d 0 1ABCDE
OpenCL GPU device configuration:OpenCL is the language used for talking to a GPU, and is installed with the video card driver. If the above GPU command didn't run correctly, generating over 1Mkey/s, then you should examine your OpenCL configuration. Remove the -d 0 option ("use device #0") from the command line above and run it again, which will list available OpenCL devices. Here's mine: >oclvanitygen 1ABCD
Available OpenCL platforms:
0: [Advanced Micro Devices, Inc.] AMD Accelerated Parallel Processing
0: [Advanced Micro Devices, Inc.] Juniper
1: [GenuineIntel] Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHzBoth a GPU and the system CPU are available in my system; on yours, the GPU may not be the first listed. "Juniper" is this AMD GPU's code name. The first line is the platform number, the second two lines are the available devices under that platform. Change the -d 0 line in the example above to the GPU desired. If no GPU is shown, the video card driver or OpenCL is not installed properly. If you have multiple OpenCL SDKs or implementations installed, more than one platform may be shown, specify the correct one (e.g. -p 1 for the second platform if shown.) Example command lines (oclvanitygen, device 0, default platform):- Search for exact prefix 1ABCDE, keep searching after first match is found (-k):
>oclvanitygen -d 0 -k 1ABCDE - Search for prefix 1ABCDE in any combination of upper or lower case (-i):
>oclvanitygen -d 0 -i 1ABCDE - Search for ABCD anywhere in address (only supported on CPU vanitygen) (-r):
>vanitygen -r ABCD - Search for prefix 1ABCDE, use a seed file to make address generation more secure and random (-s):
>oclvanitygen -d 0 -s RandomSeedFile.txt 1ABCDE - Search for prefix 1ABCDE, keep searching after first match is found, and save all found address to a file:
>oclvanitygen -d 0 -k -o GeneratedAddresses.txt 1ABCDE - Search for many prefixes at once using a text file listing them (newline after each prefix including last):
>oclvanitygen -d 0 -k -f PrefixList.txt - Use all options above including case-insensitive search, and turn on verbose mode for more information:
>oclvanitygen -d 0 -v -i -k -f PrefixList.txt -o GeneratedAddresses.txt -s RandomSeedFile.txt
When specifying a case-sensitive address prefix on the command line or in a text file list, you must only use valid Base58 characters. This means you must only use lower-case i or o, and only upper-case L, or you will get an error. - Bad: 1celeron, 1CELERON
- Good: 1ceLeron, 1CELERoN
I found an address, now what?Vanitygen finds an address that matches your search parameters, and provides the private key for that address. The private key is never shown to you in the Bitcoin client; it is used behind the scenes, and is the secret part of your address that you should never give to anyone. The mainline Bitcoin client does not have the ability to use private keys directly, but you can do other things to use bitcoins sent to your new address: - In Bitcoin-qt: Help -> Debug window -> Console. Type importprivkey 5Jxxxxxxxxxxx "my vanity addr"
- Use the "redeem private key" option on MtGox, and input the private key you found. Any Bitcoins sent to the address will now be automatically withdrawn to your MtGox account. This is permanent, there is no option to remove or cancel a private key once it is added to your MtGox account,
- Use an alternate Bitcoin client, such as Armory, that has an "import private key" feature,
|
|
|
|
|
The first response already identified the IP address as a Tor exit node. Further attempts to identify will be fruitless. You should focus on re-securing your funds, ideally sending all funds to a new blockchain wallet account with a new email address.
Secondly, the email may be a phishing attempt, do not click on any links in the email as they may go to a hacker's site that impersonates blockchain.info and attempts to trick you into putting in your credentials.
|
|
|
|
ive been reading about bitcoin escrow?
is that a good option?
Unless the escrow holds the BTC for 180 days and releases to the buyer only if the buyer doesn't chargeback in that time... Or longer, credit cards can be charged back far after that: http://www.webhostingtalk.com/showthread.php?t=296411Also ..Typically, the card issuer then has up to 190 days from this day to successfully dispute and recover the payment on behalf of the cardholder.
Any guarantee, membership or subscription period purchased as part of the transaction may be added to the 190 day period. For example, it is possible to fully or partially chargeback goods with a 12 month guarantee within 545 days of the "purchase date". |
|
|
|
CPU mining is ludicrous, it would take you a year mining 24/7 on a new i5 CPU to even make enough Bitcoin to meet the minimum withdraw amount on pools, while costing ten times more in electricity than your earnings. Anyone else care to take a stab at this explanation? I don't think I did it justice.
http://we.lovebitco.in/mining/ |
|
|
|
You are not allowed to sell items (preorders) on eBay that cannot be delivered in 30 days. http://pages.ebay.com/help/policies/pre-sale.htmlIf you want to sell presale items, be sure to meet all of the following criteria:
Guarantee that the item will be available for shipping within 30 days from the purchase date. Be sure to clearly state this information in your listing.
Clearly indicate in the listing that the item is a presale item.
The handling time specified in your listing should reflect the time from the end of the listing until the item is shipped to the buyer—not the time the item is in your possession. Be sure to specify the correct handling time in your listing.
In the listing form, you need to use the default font size of 3 so people can easily see these sale terms.
Make sure your listing follows these guidelines. If it doesn't, it may be removed, and you may be subject to a range of other actions, including limits of your buying and selling privileges and suspension of your account. This is from preorder sellers often stringing buyers along trying to get them to wait past the time that eBay disputes can be opened, and selling items that they don't have and might not get. |
|
|
|
I've tried both but it's all the same..
Does it matter?
In Bitcoin-Qt options, set your optional transaction fee per kB to 0.0006, then you will beat everyone else that is only paying 0.0005 (the minimum that is automatically included). blockchain.info doesn't consistently use a fee that will get you fast confirmation, the advice is to go into the options and change the fee setting to "generous" -> 0.001 per transaction (which still is not a minimum fee that is calculated using the formula Bitcoin miners look for, but usually sufficient). |
|
|
|
Warning, the link has binaries and no source. The file dates were not changed so this is likely virused up, not recompiled.
Actually, the vanitygen binaries are verbatim from official zip, plus just opencl dlls stitched in the archive. Naturally you should test on untrusted machine, as every binary code posted on forums. For paranoid users, i'd recommend to use the linux version. Then why does the github https://github.com/wyuzhe/vanitygen/commit/6f7fd04adc609b19520cdab4cc12d648e364adbe show that "the fix" is modified calc_addrs.cl, oclengine.c, oclvanitygen, etc which would indicate new binaries? |
|
|
|
Hello, I've created workaround for buggy 13.x catalyst driver, needs some testing though (especially the miner and win32). For the impatient: linux: $ git clone https://github.com/wyuzhe/vanitygen.git
$ cd vanitygen
$ make oclvanitygen
$ ./oclvanitygen -vv -D x:y 1Blah
In case you get odd output like: Match idx: 0
CPU hash: 0ecfec41290a506e784a4521597213398abf9a98
GPU hash: 08e030855f47c3141a5808d8767a89562ec5c655
Found delta: 497669 Start delta: 1
It means the compiler backend is still outputting broken code (although it compiles). To fix that try: ./catalystwrap ./oclvanitygen -vv -D 0:0 1ov
win32 binaries are available at: https://www.dropbox.com/s/lddvyiyl58uhgio/vanitygen-0.22-catalystmod.zipHowever received little to no testing, so comments are welcome. The gory details: https://github.com/wyuzhe/vanitygen/commit/6f7fd04adc609b19520cdab4cc12d648e364adbeIn short, ATI LLVM-IR backend miscompiles stuff like: uint x, b, c;
uint x += (a < b)
The boolean result of (a < b) is expressed as byte (u8 in crash report), but VLIW architectures know no such thing. Workaround is using artificially complex expressions which cannot be readily expressed as setcc in llvm ir (but will be optimized away during R600 lowering anyway). Warning, the link has binaries and no source. The file dates were not changed so this is likely virused up, not recompiled. |
|
|
|
 sorry, i don't know how to post an image here yet.. Quote this and you will see how I modified your post. The first thing is to use the "links to share this image" code on imageshack, the URL you used is not embeddable. |
|
|
|
|
vanitygen will make an address and private key that is only printed to the console.
|
|
|
|
The house edge is there. You might not notice it, but it has an effect on each and every roll you make. To make it more understandable, every time you send 1.00 BTC to Satoshidice, they send you back 0.981 BTC. If you send the 0.981 BTC to them again, you now have 0.9624 BTC. They have just added variance to this process to keep you entertained for a while. The more you bet, the more you reduce the variance and approach the above scenario. The more you bet, the more you compound your loss. The only winning move is not to play. |
|
|
|
The default minimum per-kB fee has been reduced in Bitcoin from 0.0005 to 0.0001, with a pull called "Make MIN_TX_FEE match MIN_RELAY_TX_FEE" being committed to the master branch, on track for the next release. You didn't hear about it? Probably because of the obfuscated name. Testing binaries are available here (do not run these unless you truly want to test bleeding edge software). This can be used now, the only technical impediment is that some pools may disallow minimum fees smaller than the current default and will skip your transaction due to this. This means that Bitcoin will create fees 1/5 the size of previous versions by default. Users of the newest version will be in competition for blockchain space with those paying the current fees, with no warning that including a higher optional/additional fee will be required for fast processing they've been used to. This will also make blockchain spam cheaper (and those services who's business model involves blockchain spam more profitable) if this becomes the new standard fee everyone is paying. How long will it take for your transactions to confirm? Have fun. |
|
|
|
Currently the greatest $ volume day yet.
Closing UTC day volume is around $21M USD, or considering MtGox takes 0.3-0.6% from each side of the trade, somewhere between $120K-$240 K of revenue in 24 hrs. Still just 0.1% of the $154 M/day revenue of JPMorgan Chase. |
|
|
|
I note that the osx wallet for name coins trys to reach irc.
Is that normal ?
Yes, namecoin is based on Bitcoin 0.3.24, which is before IRC was removed or a config file option was added to enable or disable it. |
|
|
|
DC wasn't taking the piss. Some of us have spent years trying to explain the dangers of mining at a proportional pool, the pool failing at 0.43 * D shares solved being chief amongst them. Bitlc failing shouldn't come as a surprise. Yup, you can see in this quote I knew about pool hopping (and was trying to get proportional fixed on the pool). For the longest time Jim couldn't be made to understand that pool hoppers profit at the expense of others: ...Stats are also randomly delayed, so that having good stats available can't be used against the pool. If you are mining and sending in accepted shares, then you get paid accurately for your work.
If miners hoppers didn't withdraw their actual balance, kinda sucks, you are owed that money. I'm just making the same clarification that I have previously, in response to "we mined for two months": if everyone moved all the mining power they have over and get this block killed it has to be almost dead we are almost at 2.2 mil shares
...(paraphrase: that's not how bitcoin works, dumb pool op)... Also, there is no reason to feel guilt shutting down a pool mid round - nobody found a block, so nobody gets paid. That's as simple as it gets. |
|
|
|
oh same! The last block was being worked on for like 1.5 months before hearing this crazy story. I think it's nonsense. I think we got hosed by someone we trusted and I don't think we'll ever get out btc out. It'd be nice but I think Jine and Erick are the same person. Karma's a bitch.
Your legal advice is that a block wasn't found, there is no reward. Wah wah wah. It is a proportional pool, you get a proportion of the reward when a block is found. |
|
|
|
|
(removed my 2nd guess of galaxyabstractor w/ info & leaked password etc per his request...). My first conclusion is probably right, but it could be another sock puppet of the "primary user"; language use was enough to win the other "ID Me" thread. - DC
I added galaxyabstractor because of Sweden IP and membership in pirate party, previous Bitcoin development, language use of "IP-address".
|
|
|
|
37.123.170.220 IP
Congrats, he hit my PM webbug also, it's a TOR exit node.2013-04-06 12:42:22: 37.123.170.220 |
|
|
|
|
Did you do the version handshake first?
version:
When a node creates an outgoing connection, it will immediately advertise its version. The remote node will respond with its version. No futher communication is possible until both peers have exchanged their version.
When you get bitcoin to ack the version, you know you are making checksums right, and you've also opened up further communication.
There's dumps of hex transactions on the common structures wiki link above.
BTW, I've never done what you're trying to do, I'm just good at reading(?)
|
|
|
|
|
Show Posts
