Why did you make this?
I find it silly people have projections with difficulty going to 1 trillion or more (I think the highest I have seen is 200 trillion). At a mere 300 billion difficulty all current and proposed mining devices would be operated at a significant loss (assuming $100 exchange rate & $0.10 electrical rate). So at 1 trillion in difficulty even a Cointera rig would be converting $4 in electricity into $1 in Bitcoins. Anyone think that is likely? Significantly higher difficulty is going to require either more efficient hardware, a higher exchange rate, or the average cost of power for the network to decline.
Interesting numbers. We can understand that home / basement / garage based miner's time has come to an end, or will end soon. Considering a data center environment, where hosting / rent is calculated based on 'Rack unit', I am wondering how these numbers would be calculated. Total network hashrate is still a unpredictable. Is it possible to say an investment amount (miner + hosting cost) will break even in 6 months? Not necessarily. Home based miners don't calculate costs for manpower/administration, will often not use AC (which doubles the electricity price) and might more easily mine on a very thin or negative margin. And then there's an army of people with no (self paid) electricity costs at all. But yes, those groups probably won't ever reach a percentage of the total mining power as in CPU or GPU times.. Ente |
|
|
|
if using -S works (it'll be slow) then the below may resolve the issue.
There's at least one combination where -S does not resolve this.. So I won't even start recompiling this for windows. *sigh* Ente |
|
|
|
|
I am as lost here as you are, I didn't get it to work on the Windows machine I have a remote login on.
Maybe someone else can chime in here?
Ente
|
|
|
|
Those "CPU Hash / GPU Hash" combinations mean you found an adress, but the calculation was corrupt. This is pretty common at the moment. Some people got a working system on linux with a distinct version of catalyst. Others speculate it's actual hardware problems with the GPU. Noone is really sure what's going on, I believe. Prohibited in base58 for Bitcoin:  and 1l - thats the only two pairs. o and L are allowed though. Ente |
|
|
|
When the blockchain starts getting into the hundreds of GBs, I suspect that most normal bitcoin users will be using Armory in "lite mode" that doesn't require the blockchain locally at all.
I just bought a 1 Tb disk for 0.5 btc. When the blockchain gets into the hundreds of Gb, we'll be able to buy 1 Pb disks for the same amount of money and I will happily get a disk to store the blockchain and support the network with a full node. I see what you did here! :-) Ente |
|
|
|
|
..ich glaube, auf dem Level betrittst du hier Neuland, vermutlich werden eher wenige Forenleser direkt ähnliches umsetzen.
Um mal für den Laien bei Null anzufangen: Es geht darum, Gewinne aus Tradinggeschäften bei MtGox buchhaltärisch zu erfassen, um sie plausibel und nachweisbar in die Buchhaltung oder STeuererklärung einbinden zu können?
Sehr wertvolle Arbeit, dankeschön!
Ente
|
|
|
|
|
Die Projektpräsentation am Donnerstag war super!
Alles nette Menschen, schön auch von den Organisatoren und Planern "im Hintergrund" etwas erzählt zu bekommen.
Das Projekt ist auch für mich eine Herzensangelegenheit. Cryptowährungen und Afrika gehört einfach zusammen!
Und für alle Skeptischen und Zweifler: Das ist erst der Anfang! Ich sehe das Projekt als Wegbereiter und Katalysator. Cryptocharity bringt alles mit, um sich sehr schnell zu verselbstständigen. Nein, ist sogar darauf ausgelegt, würde ich sagen! :-)
Ente
|
|
|
|
oclvanitygen is also happy to search for all strings in a file specified. doesn't seem to slow it down much. with some work, from the info in this discussion, i was able to get it working on my 7970 at 26m/s reliably.
Interesting! What did you have to do for your 7970 to work? Driver version? You're the first I stumbled upon who got it working, I gave up at this point. Ente i am on SuSE Linux 12.2. using vanitygen-0.21.tar.gz. fiddled with many versions of amd-catalyst 12.10 and below (above failed to install for me). probably landed on 12.10 though i don't recall for sure. ***the real issue*** was that oclvanitygen failed to operate correctly due to loop optimization that needed to be turned off by commenting the following 2 lines out of oclengine.c if (dvn && strstr(dvn, "cl_amd_media_ops")) quirks |= VG_OCL_AMD_BFI_INT; Thank you for the details! I'll give it another try eventually. Ente |
|
|
|
Jason totally stole our show in this article! We have to speed up a bit, eh? ;-) Seriously, this article was pleasant to read, good work! Ente |
|
|
|
TIL there's such a thing as compressed addresses. Is there any good docs on this? I can't find anything that explains it on the bitcoin.it wiki, maybe its called something else. The only mention is on this page https://en.bitcoin.it/wiki/Private_key where it says you can tell if a private key is for a compressed key because it starts with an L or K. From what I've read in random places, compressed are 34 characters (including the 1), right? Every one of my public keys are that long, and I used the normal oclvanitygen to make them, so how much shorter would a compressed public key be? The adress, which we see in our clients, are always the same length and look the same no matter if the underlying key is compressed or uncompressed. I can't go into more detail without writing more false than true statements ;-) (ocl)vanitygen creates only uncompressed keys/adresses, unless you patch it or use a fork from other developers. Ente |
|
|
|
 Thanks guys. You are all amazing. ..made me smile! :-) Ente |
|
|
|
I use salfters. The windows bins are here: https://bitcointalk.org/index.php?topic=25804.msg2296814#msg2296814He gpg signed the md5 and sha1 hashes. I verified the hashes. Haven't checked the sig yet tho. I better do that tomorrow. The GPU version is forked by scintil, but you need to compile it. I don't have a GPU so I never tried it yet. CPU is fast enough for my needs. Thank you for the info! Ente |
|
|
|
Oha! Deutliche Unterschiede.. Ente |
|
|
|
|
..I guess for some people the joke has to slap them right in the face, to be noticed :-P
Ente
|
|
|
|
@Ente, I used almost exclusively compressed keys. Simply because they save transaction size so I pay less fees or none if not needed. If I had used uncompressed keys for some of my transactions, the fee would have been double.
Compressed keys have been the standard since bitcoin-qt version 0.6+. We are at 0.8.5 now.
Oh, good hint, I didn't even think of that yet! I'll start "mining" compressed keys now. /edit: I see samr7s' vanitygen doesn't support compressed keys yet. There seems to be at least two patched versions out there, gmaxwells' and salfters'. Which one are you using, Dabs? Would you be so kind and share the windows bins of this? I have a remote box available for this with 7970 gpu, but no compiling stuff installed there. Oh, is there any gpu vanitygen out there for compressed keys? In case I ever get that 7970 to run.. Thank you! Ente |
|
|
|
Last post of BkkCoins: I'm still here and haven't abandoned the project. I've had some disruptions over the last week as the tile guys that I've been waiting for since March finally arrived and started putting in floors. I've been moving stuff around from room to room, and it's a mess, stuff piled up everywhere. Timing couldn't have been worse, and my time diverted. I'm setting up my workbench and tools again and back working again, though the room I'm in still has no floor and I'll have to move back again in 2 days. If it were just me here I could probably have delayed them but my wife (and other family) presses on me as well. Plus I really need a floor.
I appreciate the kind words above and want to finalize this whole thing so I can move on. I feel like I'm stumbling around not knowing what's actually going to happen regarding Avalon chips, much disheartened by everything, but trying to keep a more positive outlook.
Last post of Satoshi: There's more work to do on DoS, but I'm doing a quick build of what I have so far in case it's needed, before venturing into more complex ideas. The build for this is version 0.3.19. - Added some DoS controls As Gavin and I have said clearly before, the software is not at all resistant to DoS attack. This is one improvement, but there are still more ways to attack than I can count. I'm leaving the -limitfreerelay part as a switch for now and it's there if you need it. - Removed "safe mode" alerts "safe mode" alerts was a temporary measure after the 0.3.9 overflow bug. We can say all we want that users can just run with "-disablesafemode", but it's better just not to have it for the sake of appearances. It was never intended as a long term feature. Safe mode can still be triggered by seeing a longer (greater total PoW) invalid block chain. Builds: http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.19/See the similarities? Okay, I'm the first to speak out what everyone thinks: BkkCoins is in fact a group of anonymous developers! Ente |
|
|
|
Schade, dass man mit ASICs nicht mehr die rohe Rechenleistung in PetaFlops vergleichen kann. Sonst könnten wir mittlerweile der gesamten Top500 der Superrechner, den Clustern der Börsenhäusern und den Rechnern der NSA den nackten Arsch zeigen hihi
Muss man halt nicht die FLOPS nehmen, sondern die MIPS. Guter Plan! Habe auf die Kürze leider nichts zu Mining, Hashes und Mips gefunden. Damit könnte man sinnvoll Network Hashrate Terahashs/s 921.11
Network Hashrate PetaFLOPS 11698.03 auf bitcoinwatch.com ersetzen. Also, hat jemand eine Idee, wie man das umrechnet? Ente |
|
|
|
Von wegen Varianz etc: Schaut doch einfach auf http://bitcoin.sipa.be/, da ist ja alles wunderschön, in verschiedenen Zeitfenstern zu sehen. Sogar schon mit averages. Für so kurzfristige "Kawoom!!1!" Wortmeldungen kommt wohl am ehesten dieser Graph in Frage:  Noch dazu ist es ja nicht nur Varianz, sondern sich tatsächlich ändernde Rechenleistung. Und dann noch die regelmäßigen Tag/Nacht Zyklen, etc pp. Schade, dass man mit ASICs nicht mehr die rohe Rechenleistung in PetaFlops vergleichen kann. Sonst könnten wir mittlerweile der gesamten Top500 der Superrechner, den Clustern der Börsenhäusern und den Rechnern der NSA den nackten Arsch zeigen hihi Ente |
|
|
|
|
Also:
Are you guys creating compressed or uncompressed vanity adresses?
Uncompressed are the original format, but compressed seems to be the standard of the future..
Obviously, at some point all programs will (have to) understand both formats - which isn't the case now.
And then: A firstbit "wasted" on the wrong format can't be used/converted in the other.
Any thoughts on this, or am I seeing problems which aren't there?
Ente
|
|
|
|
oclvanitygen is also happy to search for all strings in a file specified. doesn't seem to slow it down much. with some work, from the info in this discussion, i was able to get it working on my 7970 at 26m/s reliably.
Interesting! What did you have to do for your 7970 to work? Driver version? You're the first I stumbled upon who got it working, I gave up at this point. Ente |
|
|
|
|
Show Posts
