Bitcoin Forum
June 18, 2024, 06:54:31 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 [133] 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 »
2641  Bitcoin / Bitcoin Discussion / Re: MyBitcoin has started spending our stolen coins on: January 12, 2012, 03:40:53 AM
They weren't sent to MtGox. If they were, they would have moved already. I have no idea about that weird consolidation, though. Luckily, it was done so poorly that we can now trace a very large amount of funds. With a script, you could trace each input, as well as the change, to find all spends out of what is known to be mybitcoin from the input and change information. It'd be cool to get a final number, too.

Not necessarily. Coins seem to be swept out of MtGox deposit addresses after 1-4 days, although it was faster months ago.
2642  Bitcoin / Bitcoin Discussion / Re: MyBitcoin has started spending our stolen coins on: January 11, 2012, 09:49:08 PM
The odd thing is the coins are not being sent in the way a normal Bitcoin client would send them, the address balances are being nibbled at and combined with other small payments from other address to new addresses, like here: http://blockexplorer.com/address/12ViYXgordxUkmPhN5PAU9vJRHwc8jftfQ. The coins are sitting in that new address. Now the question is, is that a MtGox address or still the BitThiefs? If MtGox is willing to lock accounts because coins were long before used to scam MMORPG money, they should at least be willing to find, flag, lock, and IP log coins sent directly from mybitcoin users' addresses to the exchange, disclose that those are MtGox addresses if requested, and respond to subpoenas to the identity of the thief (for private action or to be handed over to the prosecution arm of juristictional law enforcement).

Along with the magical re-appearance of "Tom Williams" at the same time, we know it's the site owner, and I have a feeling they are being transferred to the exchange for quick sell, huge sells happening right after these transfers.
2643  Bitcoin / Mining support / Re: How to check AMD Stream SDK version? on: January 11, 2012, 05:19:14 PM
Yes, you seem to be able to mix driver version and OpenCL version to get the best of each without compatibility issues.
2644  Bitcoin / Mining support / Re: AMD update kills Hash rate on: January 11, 2012, 04:58:55 PM
Just ran the AMD update.  Have 3 5850's running clocked at 900/300 1088volts and have been getting 325Mh consistently.  Now....all 3 cards are running under 250Mh. 

WTF?

No need to roll back the whole driver. Run the uninstaller for Opencl only, then extract your old driver and install just the old file.

Only downside  (of it is one) is that further uninstalls and updates may fail to remove the old cl SDK unless you keep the original installation file.

Was 11.12 the introduction of 2.6? So, I would just need to extra the SDK from the 11.11 drivers?


That is what I do, I actually run the ATI installer up to the point where it extracts the files, and then I cancel. On a completely driver-free system. I would then go to the device manager, find the video card, and then install the driver manually using the path C:\ATI\Support\11-12_vista32_win7_32_dd\Packages\Drivers\Display\W7_INF where they were extracted (or whichever version you want). That installs only the video card driver and no other stuff. Then browse your computer to C:\ATI\Support\11-6_vista32_win7_32_dd\Packages\Apps\OpenCL to install that driver's version of OpenCL. That's how you mix and match.

The ATI driver uninstaller leaves behind the newest OpenCL files, even when you choose "uninstall ALL ATI software". Follow these instructions before reinstalling: https://bitcointalk.org/index.php?topic=54693.msg651989#msg651989
2645  Bitcoin / Mining support / Re: How to check AMD Stream SDK version? on: January 11, 2012, 04:52:32 PM
My amdocl.dll is 10.0.831.4, and the OpenCL.dll is 1.2.
Does this mean I am NOT on 2.6?
Then, how comes I am still getting low hash rates? Any ideas?
That indicates a version previous to 2.6. If you want to be sure everything is uninstalled from 2.6 before proceeding, you can follow these instructions: https://bitcointalk.org/index.php?topic=54693.msg651989#msg651989

I would do a complete driver removal, in control panel, programs and features, uninstall ALL ati software with the Catalyst install manager, and restart your computer. Then follow the steps in that post to remove any remaining files. Then download ATI driver 11.6 or 11.11 (mining only, mining + gaming), install and reboot.
2646  Bitcoin / Mining support / Re: How to check AMD Stream SDK version? on: January 11, 2012, 07:36:31 AM
amdocl.dll and OpenCL.dll in the \Windows\System32 directory (on 32 bit windows). Right click on them, choose properties, pick details. 2.6 is version 10.0.851.3 through 10.0.851.6. If you don't like it, delete those files and reinstall OpenCL from an older version (typically put on your system when you installed the drivers in the directory C:\AMD\AMD_Catalyst_12.1_Preview_Windows_Vista_7\Packages\Apps\OpenCL\OpenCL.msi; replace 12.1 with the directory name of the version you want.
2647  Bitcoin / Bitcoin Technical Support / Re: Forced to upgrade to 5.1 - Can someone explain why? on: January 09, 2012, 04:44:45 AM
The bitcoin wallet is stored at ~/Library/Application Support/Bitcoin/. All versions look to the same user directory location for your wallet.
2648  Bitcoin / Mining software (miners) / Re: further improved phatk OpenCL Kernel (> 4% increase) for Phoenix - 2011-12-21 on: January 08, 2012, 08:29:57 PM
If you didn't note it, I profiled the performance of Diapolo's kernel on my 5830 using both SDK 2.5 and the performance-robbing 2.6 here with lots of options and RAM clock speeds. It might give insights of where to go on the kernel for current driver OpenCL performance; the 58xx is a bit different than Diapolo's 5770 in how it responds to worksize.
2649  Bitcoin / Development & Technical Discussion / Re: Outsourcing vanity address generation on: January 08, 2012, 07:51:59 PM
I hate to inject gloom and doom into a fun topic like vanity bitcoin addresses... but y'all should be aware that one of my longer-term goals for the Bitcoin system is to make bitcoin addresses disappear. I hope Bitcoin software 10 years from now tells users "You're about to pay 11 micro-Bitcoins to Amazon.com" and not "2mRwtf8blahblahblah". And I'm not alone, I know Mike Hearn feels strongly about making bitcoin addresses go away for ordinary users.

If you do spent lots of time creating The World's Best system for mining vanity bitcoin addresses, please don't be upset or surprised if you find it is obsolete when "Bitcoin 2017 Turbo++ Enhanced Edition" is released.


The foundations seem napkin-sketched out already from Mike's post; I've started thinking it through, and a self-published alias might be the easiest addition. It would seem best to lift Namecoin's style of address registration with fee. There would certainly be a landrush period, and you would want to discourage squatting, so a significant but diminishing cost would better ensure interested parties might still find their desired alias available (see post #10 above; I paid .55 BTC in fees just for some fun...).

Implementation: You go into your address book, there is an option called "register label on network". You press this, it asks you to create an alias that other clients can see to send money to you. If you are not the first, you get an error that the alias is already taken. The alias is permanently included in the blockchain along with some bitcoins you donate as the fee, and then the address book will list all aliases registered to your address. Other Bitcoin clients would have a searchable database of all these aliases to find you as a recipient.

However, I don't think anything like this should be included in Bitcoin. Although not any more dangerous than "firstbits", it would make it too easy to spoof people into sending money to an "amazon.com" that goes to a malicious squatter instead. It also hinders anonymity and the sender identification that comes with one-time-use addresses.
2650  Bitcoin / Development & Technical Discussion / Re: Vanitygen: Vanity bitcoin address generator [v0.17] on: January 08, 2012, 06:35:26 PM
Interested in a modified version of vanitygen which can produce vanity addresses from minikeys.

A request for software has been posted here:
https://bitcointalk.org/index.php?topic=57040

samr hasn't logged into the forum since August. You might need to get the source yourself, try to set up a compile environment for it, and then modify the software so it searches for proper minikeys (only 1 in 10,000 or so mini-sized keys match the requirements if I recall) and then does the phrase check. Because of this additional difficulty, a normally 1-day phrase might take you 20 years though...
2651  Bitcoin / Development & Technical Discussion / Re: Outsourcing vanity address generation on: January 07, 2012, 05:48:10 PM
..does anyone know of a gpu generator that searches a user supplied dictionary all at once?  I think the one that exists now only does one word at a time.
The answer belongs back on the vanitygen thread, but here's your option:
-f <file>     File containing list of patterns, one per line

oclvanitygen -k -f ListOfWords.txt -o FoundAddresses.txt



---
Steering things back on course:

"filler", as used above, would be a "nonce".

From a glance-through read, it would appear that one would only be able to generate addresses for a single client at a time. Am a wrong, that the hashing and checking will find an address that would work for just one client. Currently, you hash once and see if the public address has any matches from an arbitrary list. Without the benefit of mining vanity addresses for multiple clients while looking for your own too, with minimal performance penalty, it doesn't seem an endeavour worth pursuing.

The second concern would be how to deal with distribution and bounties; now I'm thinking maybe something could be done better than just posting wanted addresses in a forum.
2652  Bitcoin / Development & Technical Discussion / Re: Outsourcing vanity address generation on: January 07, 2012, 04:51:07 PM
I have a new invention: unsolicited outsourced vanity address generation

It kind of works like this:

Address: 1Lukejrwhew7sj4TvWCKksaVo7aLpedHDt
Privkey: 5JB53xyWq9i81tBF2Tud9bpQwk1R2mjQA7gXNDHwp6QyiZC2T7K
2653  Bitcoin / Pools / [20 GH] Ozcoin Pooled Mining Pty Ltd DGM/US EU and AU servers/SSL on: January 07, 2012, 03:38:17 PM
Looks like I am 1% of the pool with a lowly 5770 thrown your way, let's see how it goes!
2654  Alternate cryptocurrencies / Altcoin Discussion / Re: Namecoin - what is going on ? on: January 06, 2012, 08:23:41 AM
Bitcoins can't directly interact with the Namecoin network. You can buy Namecoins on an exchange with your Bitcoins, and then use those Namecoins to buy a domain. It's pretty cheap, about 0.0005 BTC for a domain name right now, less than $0.01 a domain name, and less than GoDaddy by far. That's probably why over 2000 domains were registered in the last 10 days.

The problem is that there are far fewer people using the Namecoin client than there are registered domain names. Of those that actually have a Namecoin wallet, far fewer of those use Namecoin to do DNS lookups - and why should they? You don't know where the names people have created will take you, and there are places it will be impossible to ever use Namecoin's DNS (try going to a Namecoin .bit domain on your iPhone...)

For getting to my own sites myself, it would be easier to use a hosts file. If my site is reallycoolsite.bit, I can't tell people to go to that address, they aren't going to be running a Namecoin DNS. It would be easier to use a DNS redirection service like afraid.org - at least everyone will be able to actually get to reallycoolsite.afraid.org if I say my site is there. Namecoin offers unblockable P2P DNS, but 99.9999% of the Internet is not set up to use these names and won't be, so it's close enough to "blocked" already.

Merged mining has steadied the difficulty and transaction rate of Namecoin; previously it would stagnate for months after a profit-raping mine-fest drove up difficulty. This also means new miners have Namecoins that wouldn't have heard about or used them otherwise, but not much is being done with them.
2655  Alternate cryptocurrencies / Altcoin Discussion / Re: [RELEASED] Coiledcoin - yet another cryptocurrency, but with OP_EVAL! on: January 06, 2012, 08:02:04 AM
this coin is a good one to bet on still

I misread that as "con" and thought it was a surprisingly honest post. Wink

The vitriol should go down a notch here. As far as I can tell no actual transactions have been reversed. Just orphaning (er, which is what you should expect with blocks coming every 10 seconds, unfriendly funnybusiness or not .  And even still, not orphaning deep enough to have invalidated any spendable coins— which is what the maturity limit is for after all.


There is no limit to how far back coins can get zapped. At the launch of i0coin, I had 300-confirmation generates go pooof.
2656  Other / CPU/GPU Bitcoin mining hardware / Re: AMD Catalyst 12.x Drivers on: January 06, 2012, 07:35:48 AM
AMD appeared to already be silently updating the previous preview release, the version of it that I downloaded two days ago had Stream SDK 10.0.851.4 instead of 10.0.851.3. This release has 10.0.851.6. The Stream SDK/OpenCL version is what makes a difference in mining, and I doubt there will be many changes in the new 2.6 architecture (not like the huge changes from 2.5 to 2.6) now since it is not a preview, it is the current developer SDK.

Tested: Identical mining performance to previous preview.
2657  Alternate cryptocurrencies / Altcoin Discussion / Re: [RELEASED] Coiledcoin - yet another cryptocurrency, but with OP_EVAL! on: January 06, 2012, 06:53:59 AM
One thing that wasn't changed: longest chain wins. If attacker can start at block 0 and get ahead of all that has been mined by the rest, poof, your generated coins are gone.
2658  Bitcoin / Bitcoin Technical Support / Re: catalyst 12.1 Great gaming, Bad mining on: January 06, 2012, 06:42:12 AM
Has anyone found a way to have new drivers installed, To fix the cpu bug and play games, Without losing mh/s performance?
Why yes, all you had to do was look: AMD Stream SDK 2.6 (Catalyst 11.12/12.1) - Get your performance back! (Phoenix)
2659  Bitcoin / Bitcoin Technical Support / Re: Is it safe to login MtGox on a compromised computer using YubiKey? on: January 06, 2012, 06:40:45 AM
Go ahead and type in your password; compromised can mean key logger and screen shots, your wallet file sent to another computer, along with your bookmarks and address book. Hope you didn't use your password anywhere else, or have any btc in your wallet. Yubikey protects against a stolen Mtgox user/pass being able to log into MtGox without the physical fob code, but it doesn't prevent anything else a hacker might want to do.
2660  Economy / Economics / Re: History repeats itself, another bubble on: January 05, 2012, 12:03:43 PM
Look out, another bubble?! What's old is new again!



.08 was, if not a bubble, a spike, since it is down to .05 now.  I'm betting on it going down a bit more before it starts climbing again.

(of course, I'm only planning on buying like 10 dollars worth of bitcoins anyways, so it's not a real momentous decision)
I wonder if he sold those 200 coins for $6000 at the top of the last bubble... or doubled his money at .10
Pages: « 1 ... 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 [133] 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!