In case you're wondering why no news: Heavy development and testing. Next release will be a big one, so despite RERO, it may take another week or even two. Meanwhile pool runs und churns. As the image is too big for bitcointalk, click on this to view. Rico edit: Pool performance 24h average pretty steady at 23.5 MKeys/s, short term fluctuations between 21 MKeys/s and 29 MKeys/s |
|
|
|
sich bei einer Privaten "Bank" niederzulassen.
Das die gut sind, ist unbestritten. Aber was das kostet! Rico |
|
|
|
Also mal kurz zur Schweiz und den 1000er Scheinen. Es gibt Sie tatsächlich und die sind gar nicht mal so selten.
Allerdings bringt dir ein 1000er Schein so ziemlich nix in der Schweiz. ... Du bist also gezwungen, diese zuerst in einer Bank und hier macht das auch nicht jede Filiale, den 1000er in kleinere Scheine zu wechseln.
Wenn jetzt noch jemand dem Bergvolk sagt, dass es da so ein Wertaufbewahrungsmittel gibt, das noch weniger Platz wegnimmt als ein 1000er Schein und das man in 100 Millionen kleine Teile schnippeln kann und das vermutlich mehr Akzeptanzstellen in der Schweiz (weltweit sowieso) hat als der 1000er Schein. Ja dann ist aber Polen offen - ooderrrr? Rico PS: Ich fordere bedingungsloses Grundverständnis für die Schweiz. |
|
|
|
Naja - ich bin nicht hier um Dir die Illusion zu nehmen. Ich werde einer der Letzten sein, die es trifft.
Aber so ist es richtiger.  Rico |
|
|
|
Ich höre das schon seit 40 Jahren. Damals war Oetker-Entführung mit 21 Millionen. Wegen dem Lösegeld in 1000er hatten einige sich lautstark dazu geäussert 1000er abzuschaffen. Es gab diese 1000er weiterhin bis 2002.
Jetzt mal Anke (sind ja in der Schweiz) bei die Fisch'! Das stimmt ja alles, dennoch gab es nach 2002 eben den 500€ Fetzen und da haben sich mittlerweile die Genossen aber nicht nur geäussert, sondern beschlossen: http://www.deutsche-handwerks-zeitung.de/500-euro-schein-abschaffen-kosten-in-milliardenhoehe/150/3093/326993Deswegen sehe ich überhaupt in einen Schweiz-Thread rein, weil das Erste was aufkam war dann Wert/Volumen: https://www.heise.de/newsticker/meldung/Die-Schweiz-haelt-an-ihrem-1000-Franken-Schein-fest-3211123.htmlUnd das ist ja auch schon wieder Mai 2016. Also lange lange her. Du kannst heutzutage nicht einfach mit den 80ern kommen. Die Entwicklung beschleunigt sich, die Aktionen der Geldhüter werden ganz offensichtlich (dafür muss man kein VT-Spinner sein) immer hektischer, immer panischer und das in immer schnellerem Rythmus. 300 Millionen Menschen in der EU nutzen Euro-Bargeld. Du musst für 300 Millionen Menschen die Infrastruktur aufbauen.
Das geht heute schneller als in den 80ern. Economy of Scale sagt Dir was? Kreditkarten sind DAS Musterbeispiel für eine solche. Es ist schon heute nämlich genau andersherum: Wenn Du als Händler keine KK akzeptierst, bist Du gelackmeiert. Nur ganz wenige, mit einem ganz ganz besonderen USP können sich so einen Boykott überhaupt erlauben. Wenn heute wirklich jemand das ernsthaft fordert und es aussieht als könnte was draus werden, hat man immer noch 10 Jahre Zeit es zu boykottieren. Um bei der Wand zu bleiben: ich fahre so langsam gegen die Wand, das ich sie 2x aufbauen und wieder abreisen kann, bevor ich mir die Schnauze dran verbeule.
Ich kannte mal einen, der hat im Winter das Wochenende mit heruntergelassener Hose am Fensterbrett verbracht (glücklicherweise war die Heizung an). Als wir vom Skifahren zurück kamen (wo er eigentlich mit sollte) und bei ihm die Tür aufbrachen meinte er nach ein paar Ohrfeigen, Heiß und Kaltbädern: "Ich wollte mir vor der Abfahrt noch Zeug reinziehen und dann hat's zweimal geblitzt und jetzt seid ihr da." Für den war ein Tag wie ein "Blitz". Chefin ... Ich wusste nun nicht, dass es auch Drogen gibt, die das genaue Gegenteil bewirken. Rico PS: *der gerade darüber nachdenkt wie lustig es wäre Boykot mit nur einem t zu schreiben* |
|
|
|
I also want to invest into the project.
I have 1 BTC that I can throw into this.
Thank you for the nice/generous offer. When I started this, I made the decision to stem the cost for pool operation myself. I intend to keep it that way, both for idealistic as well as for legal reasons. This is a hobby/geek project and I shall never make money out of this, because I'm pretty sure somewhere some legal a**orifice would then like to construe this as "commercial interest". Therefore, no banners, no "begging" for pool support and - not even taking unsolicited grants like this. You still can support the pool with your 1 BTC another way: https://bitcointalk.org/index.php?topic=25804.msg16267353#msg16267353https://bitcointalk.org/index.php?topic=25804.msg16273114#msg16273114I am willing to pay also an incentive for a GPU-based LBC miner. If we can make a formal "pot" with the incentive, I'm pretty sure there is now more than enough monetary incentive to either hack oclvanitygen to our bidding or do something LBC specific. I'm already in the process of writing up a formal requirements specification. If the more generic question "What can I do to help?" comes up, here's a few things: HackIf you are a good hacker and know OpenCL and/or CUDA ... see above! Help to spread the newsWhile I can maintain this English thread - and to a certain degree also the German one (as we don't have a Czech one, I can't be of any help there) - I would certainly welcome if someone could maintain HQ information about the project in other languages that are inaccessible to me. Don't underestimate the language barrier. Think of a situation when this becomes well aware in the Chinese boards and some day some manufacturer would approach us with some ASICs  Also, while bitcointalk.org certainly is a good megaphone for this project, it certainly isn't the only one and I'm not even sure it's the biggest. I would like to see some /r/bitcoin information maintenance of this project, but I am afraid I don't find the time to do so myself. I'm also very old school so I do own neither a Facebook, nor a Twitter account... Help with the documentationI'm trying to document as good as I can, but in a rapidly changing project like this, there will inevitably be some outdated information. Also, I may already be getting a little bit project-blind and assuming the user-in-spe knows things he simply can't know. Both making it harder for newbies to participate. Actually IF you are a newbie, exactly this situation is valuable. Of course you are expected "to read it all", but if you then see inconsistencies, outdated information, missing information... assemble and report that (I prefer bulk processing). If you can do a small How-To in some other language, then by any means do it! Rico |
|
|
|
Ich mache mir also erst den Kopf wenn Aldi und Lidl das Bargeld im Laden abschaffen wollen.
Also zu spät. Vorher ist es ein Pups der stinkt, mehr nicht.
Ich mache mir auch immer erst Gedanken nachdem ich mit meinem Auto volle Kanne gegen die Wand gefahren bin. Vorher ist die sich nähernde Wand ja nur eine hypothetische Gefahr, mehr nicht. Rico |
|
|
|
Die Nationalbank hat deshalb Banken auch schon empfohlen, mit Bargeldnachfragen (…) restriktiv umzugehen. Die Nationalbank hat deshalb Banken auch schon empfohlen, mit Bargeldnachfragen (…) restriktiv umzugehen. Die Nationalbank hat deshalb Banken auch schon empfohlen, mit Bargeldnachfragen (…) restriktiv umzugehen.  Rico |
|
|
|
I bet most of you - if you are not Satoshi Nakamoto - have asked themself "Why oh why didn't I mine for da precious BTC back in 2009?" The answer is actually trivial: It's either because you didn't see its value (as at that time it had none) or you were unaware (because others also didn't see its value therefore the news "have you checked out this new cool cryptocurrency..." didn't spread). If you do not participate in the LBC yet, you will ask yourself the same question in a year or so. Deja Vu at its finest. 2016-07-10 0.0000000000000000000000000000000000000000000000000000000000% 2016-09-17 0.0000000000000000004524764939984744324231018884855317923702% 2016-09-21 0.0000000000000001253458951869845883453371545658596111253200% 2016-09-24 0.0000000000000043042164539298425445359190647758710199397875% 2016-09-26 0.0000000000000073909029565816723002553643394779850994024627%2016-09-26 0.0000000000000094983619014185236171698521342910676276368576% If you participate in the LBC, you know that number. If you don't - find out. Very soon, the (yes - still small) probability to find an address with funds will be 16384 times higher than it was (then) 10 days ago.Done.The math behind this is simple, the pool has searched an additional 14bits of search space since then. Now contrary to BTC mining this seems to be inverse. You do not need to participate now. The later you get in, the better probability you start with. Right. Except... you know this, I know this. The pool knows this. The pool is aware of when a client started and how many blocks it contributed since then. Since we all want to serve up justice (right?), the pool will take that information into account in the future. How? What? You may ask. I could say "Wait and see". I could say "I don't know yet". I could explain how, but I won't now. Suffice to say, the possibilities how to steer justice are many. Early adopters can get "better blocks" a.k.a more promising search space, there can (and will) be bounties for all where exactly these parameters will be taken into account for an aliquot share. You know - the old school aliquot... "pro-rata". "Proportionately" for the younger among us. Some are probably already aware of the new options that have popped up in the LBC help ...
Options:
--address <BTC P2PK address>
Give a BTC address for rewards to this client. NYI
...
--secret <[oldpassword:]password>
Set or change password for enhanced security (changing BTC address).
They are there for a reason and the NYI will vanish soon. Rico - serving justice since 1970 |
|
|
|
I would prefer a flag, to start at a specific block, instead of a range(which is limited to one day work). So i don't need to start over again, once it has done the work of one day.
Like in a loop, ./LBC -c 4 <start-block> and just go on with the work like forever
I know what you mean and LBC will have in the next (or one of the next) version a very sophisticated way of defining search space. Additionally to auto <from>-<to> it will offer also janitor <from> and you will be able to enter the numbers in various formats 12121 (normal - old - 1M block) #2382392832 (concrete key number) #b10101010101 (same, but binary) #xffa100d (guess... Oh - 'janitor' will explicitely ask the server for leftovers no one had a look at so far (or didn't deliver PoW). etc. Rico |
|
|
|
I'm not crystal on what you want me to help you with. I'm more of a web developer, honestly have no idea what h160 are, nor a LBC. Please elaborate, this is quite interesting to me.
Never mind, I had to do the implementation today morning after breakfast anyway. Rico |
|
|
|
 Testing mode. Using page 0, turning off looping. Benchmark info not found - benchmarking... done. Benchmarked factor 1.7527004375 oTest check failed! Expected 4 hits and got 28! ... Simply ignore it. "Someone" (not me) planted a surprise in block 1. Surprise surprise, test broken because - see https://bitcointalk.org/index.php?topic=1573035.msg16295924#msg16295924When checking the Windows client via LBC -x, I realized, that there was no way, a user could determine if the check ran successful if there were only some hits. So now the check checks itself and will bail out if there are not exactly X hits.
And "someone else" (me) ... didn't make LBC -x with the new blf before releasing. edit:Behold! The incremental updater/purifier! If and only if (iff) you experience the problem above (28 hits instead of 4 when running LBC -x) and you do not want to download again a blob of 512 MB bloom filter, you do this: * Install xdelta3 ( http://xdelta.org/) - your distribution should have it * download http://62.146.128.45/download/unpollute.bindiff <--- a fabulous only 10 Kb * in LBC-client dir do: xdelta3 -d -s funds_h160.blf unpollute.bindiff funds_h160_clean.blf
mv funds_h160_clean.blf funds_h160.blf
done. LBC -x should work as documented. I will incorporate this into LBC, so I can finally establish a quick and seamless update of addresses with funds on them with minimum network traffic for the clients. Very truly yours, Rico
|
|
|
|
HRD-core steht nun zum Download für Alle bereit: http://62.146.128.45/download/LBChrd-0.837_l64.tbz2Anleitung zur Installation siehe README.txt, bzw. https://bitcointalk.org/index.php?topic=1573035.msg16338052#msg16338052Auch Early Adopter sollten updaten, im Paket is ein neues .blf und ich habe mir sagen lassen da sind einige Überraschungen drin. edit: Eine Überraschung ist, dass der Test LBC -x fehlschlägt, weil er 28 Treffer statt 4 findet. Das kommt daher, weil tatsächlich jemand - will ja keine Namen nennen - 24 Überraschungseier in Block 1 gepflanzt hat. Sind natürlich alle längst weg. Wenn man das nun loswerden will (also NUR in dem Fall, dass man obigen Fehler hat) ohne wieder 512MB an bloom filter file downloaden zu wollen, macht man Folgendes: * Man installiere xdelta3 ( http://xdelta.org/) - sollte auf jeder linux Distribution drauf sein * dann download von http://62.146.128.45/download/unpollute.bindiff <--- lediglich magere 10 Kb * im Verzeichnis LBC-client gibt man folgendes ein: xdelta3 -d -s funds_h160.blf unpollute.bindiff funds_h160_clean.blf
mv funds_h160_clean.blf funds_h160.blf
fertig. LBC -x sollte wieder so tun wie gewohnt. Ich werde die Funktionalität in LBC einbauen, damit wir endlich eine Updatemöglichkeit haben ohne wegen ein paar Adressänderungen immer ein halbes Gigabyte über die Leitung schaufeln zu müssen. Rico |
|
|
|
Ist es auch möglich mehrere Computer bzw. Server über den gleichen Fingerprint laufen zu lassen?  (Ich denke an eine vollständige Kopie meines Linux Betriebssystems, das ich dann auf mehreren USB laufen lassen kann unter dem selben Fingerprint) Ich denke derzeit über eine Aggregatorfunktion nach, bei der ein LBC nur die HRD-cores auf definierten/erreichbaren Servern via SSH ausführt und deren Output einsammelt. Rico |
|
|
|
Hey guys, it's nearing that time of year when I have nothing to do. I'm looking to code.
Are there any ideas that you would like to see come to life? Just any interesting project. I don't want anything to do with holding funds, like a wallet or the like. I want to find a simple project to work on as a hobby, something like Preev, a great service to the community.
I'm out of ideas.
For the LBC, I would need: A better/more efficient way to distribute current h160 with funds on them.At the moment, from time to time a blockparser run parses the then-current blockchain, extracts the h160 of interest. Then a perl storable ~360MB is built and also a bloom filter ~512MB is built. Depending on the client, the users have to download one or the other. Ideally, the server would be aware of new addresses with funds appearing and addresses being drained of funds, then it could offer the clients more frequently small "diffs" for the data they have. I'd have no objection to offer this as an open API as service to the community outside the scope of LBC. I know how to do it, but lack the time atm. Rico |
|
|
|
I'm surprised how - from pool operation and development - I still get new insight every day. This also affects my motivation. When I started this project, I simply wanted to test how far an individual can go. To get some practical feeling for the task at hand that has been discussed so often in theory. In theory only. I also wanted to be able to make some estimate about the capabilities some clandestine group doing such a thing might have. When what seemed to be limits kept being pushed more and more to what seemed to be new limits, there was also some motivation to disprove common beliefs and mantras about the infeasibility of such an endeavor. Or - at least - to correct the numbers. When I read about Ryans lower bound estimate of capabilities of "someone" already having been searching the PK-space @ 28 MKeys/s here, I suddenly felt the need to get this pool up to speed, so a public community project could at least outperform such clandestine Muffugahz. So that is currently my motivation: to amass a keyrate that will draw level with aforementioned capabilites and eventually pull ahead. ------ Currently the pool operates the HRD-core on the equivalent of roughly 22 Skylake cores. I will make a polished version of it available today evening (CEST) for everyone interested to download. The pool has seen - so far - 59 individual clients of which alone the top5 are responsible for 80% of it's performance. I am quite confident, that my current goal of surpassing ~ 28 MKeys/s will be reached within a week. And then let's just pick another goal - together. Rico |
|
|
|
Are you approaching the batches in a linear fashion versus maybe dividing up the keyspace so that you are "attacking" different lengths with different batch pools?
Not sure if I understand correctly, but currently there is only one pool: The PK space 1 ... almost 2 256. Of this, we will preferably look at the 1st 160 bits, because IF both SHA256 and RIPEMD160 are behaving as they should, they have uniform distribution. Therefore the output of RIPEMD160 should have also a source in the 1st 160bits of the SHA256 keyspace (and the next 160bit, and the next, ...) (That's why there are - in theory - 2 96 valid private keys per address) Because we are watching something around 9 million addresses, the effective search space is around 136.75 bits until something is found. Of this, something over 41 bits were already searched. Clients are basically free to decide which search space interval they want to cover (if they give it manually). If they simply let the server decide where to search, it will assign them search intervals depending on their speed and time commit within the 1st 160bit. Uh. That's heavy cuisine. Bookmarked for later study. Thanks. Rico |
|
|
|
Ich werde einer der letzten sein, den es trifft.
Jeder hat so seine persönliche Verdrängungsstrategie. Rico |
|
|
|
|
Show Posts
