Bitcoin Forum
May 07, 2024, 04:46:27 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 [59] 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 »
1161  Bitcoin / Project Development / LBC Stats on: February 10, 2017, 03:19:26 PM
I modified the stats slightly:

  • The pool performance shown is a 24 average and as such is equivalent to the last point (0 on x-axis) shown in the pool performance graph.
  • For #51 you can now see a "from to" estimate. The previous value was just the (pessimistic) "max" value assuming #51 would be a private key 251-1

Based on the 2nd you can see the time - at most - it will take to hit #50. (currently 51 days)
Estimate for #49 is left as an exercise to the reader.


Rico
1162  Bitcoin / Project Development / On Rewards on: February 10, 2017, 02:55:46 PM
When showing the help via ./LBC -h the 1st option you saw was

Code:
     --address <BTC P2PK address>
      Give a BTC address for rewards to this client. NYI

The NYI (not yet implemented) will be gone with the next version of the LBC client and also the type of the BTC address is not constrained anymore (you can give a P2SH as well). I intend to release the next LBC client this weekend and yours will most probably auto-update - so leave the download section alone for now  Smiley.

Code:
$ ./LBC -h

         LBC - Large Bitcoin Collider v. 1.005
    client fingerprint: 8eb48dd9fd0a77b8b4110be83baf04c2

 Usage:
    LBC [options]

 Options:
    --address <BTC address>
      Give a BTC address for rewards to this client.

(remark: The to-be-released-client will probably have a bigger version number than 1.005)

So how does setting a BTC address look like and what will it do?

You can set a BTC address for the id you own any time/as often as you want, but only the last value is valid. You can check the BTC address set via query (-q). And you can do both in one step:

Code:
$ LBC -q -a 1DoofusZqKv2wDhUAvKRjUPVQsyZw3NKCw
Server answer to 'query' is:
{
"done" : 18075470,
"btcadr" : "1DoofusZqKv2wDhUAvKRjUPVQsyZw3NKCw",
"ips" : {
...
},
"lastsee" : ...
}
'done' means we have delivered  18953.504 valid Gkeys.

From then on, the given BTC address is attached to your id and whatever reward - relevant to your client - the pool will issue, will be paid to this BTC address (or whichever is active at time of payout - as you can change them as often as you want).

Wait - what reward?!

 Smiley

When the pool started, i planted some small bounties in the search space for any client to find. Some may remember 1AKKm1J8hZ9HjNqjknSCAfkLR4GgvCAPjq and 1TinnSyfYkFG8KC3gZ72KpYxBXsxSadD8.

While this is some fun and I plan doing so again, it's more of a "the winner takes it all" game and that's not what pools are about - is it?
So there will be another incentive, but this time - with a BTC address attached to an id - the pool can reward clients proportionately.

Let's say - and this is just a thought experiment / example - I put out a 1 BTC reward to be distributed among all ids in the top30 (except __rico666__ - of course) proportionately to their delivered GKeys, with this in place I can do so.

Or let's say the pool does find something and no one claims ownership - we can use this for distribution of the find.

Or let's say the pool does find something, the rightful owner does claim (and prove) ownership and we can distribute a finders fee among the clients... or ... or ...



Some time ago, I promised to make sure people who supported the pool early on will have favors. The 1st such favor will be, that any id in the top30 will get a GPU client for free (i.e. as many GPU client instances as you want/need - for your id), everyone else wanting the GPU client will fork out 0.1 BTC  Tongue
I reserve the right to give out GPU freebies to special supporters - like arulbero - should they be interested. Also, the price for becoin is 0.5 BTC.

The 0.1BTC for any GPU client will not be paid to yours truly (aka me), but - see above - proportionately to all pool members except myself. Specs of the GPU client will follow soon.

So maybe it is time to have a look at the cost-benefit evaluation of being in the top30 of the LBC:

The cheapest price/performance AWS compute nodes will allow you to compute/check 65 Gkeys for 40 us cent. If I look at some examples of the current top 30:

Code:
Rank	Client Id           #GKeys	Activity
1 Unknownhostname                        101313 3m 6s
2 a01f54a6df31b6d9075a99507b7c4a27 48206 5m 25s
3 Brother_of_Castor                 44736 3m 54s
4 HeavenlyCreatures                 37771 1m 16s
...
7 JudeAustin                         17611 4m 15s
...
13 John_Snow                          6238 2h 15m 12s
...
30 a14f027942e6f0507083a3d4f2ae376f 1866 13d 21h 14m 56s

based on the AWS price, #30 is worth some $11, John_Snow delivered keys worth about $38, Unknownhostname about $623(!) etc.
So right now, if you are not in the top30 and want a GPU client, it's way cheaper to deliver some Gkeys than 0.1BTC
Once you are in top30 and you have a GPU client, you will be part of the LBC establishment for quite some time to come.

If you are not in the top30, but have delivered quite some Gkeys under different ids (different computers, hardware changed, etc.), I repeat my offer to merge your contributions to one id.

Right now, the vast majority of the pool performance comes from Unknownhostname and HeavenlyCreatures. That is two guys (or groups - but I believe guys), delivering over 80% of the pool performance. Most of the ids in the top30 are dormant as you can see. The entry barrier is f*ing low, so carpe diem.


Rico
1163  Bitcoin / Project Development / alive and kicking on: February 09, 2017, 04:59:38 PM
I'm back.

How is this luxury trip being financed?  Perhaps a sudden windfall of BTC?  Whose BTC?  How obtained?  

No BTC involved whatsoever. I just made a deal with a European top model to be at her service and she
promised to pay for the trip. Life's hard.



~160 Mkeys/s while I was away. Wow! Seems #49 has not been found yet, at least I have no info about it.
But I see quite some janitoring has to be done (promised undelivered blocks) - please people end your sessions
with "e" + return (and wait), instead of Ctrl-C

It'd be quite some irony if #49 was in one of the blocks to be re-issued.



I managed to hack some things after fulfilling my duties with aforementioned model, so expect some news
and releases this weekend. Spoiler alert: You may want to make sure OpenCL is installed correctly on your
machine.  Wink


Rico
1164  Bitcoin / Project Development / AFK on: February 02, 2017, 07:02:12 PM
For the next week, I'll be having fun in the Alps and will be trying to not break my legs - or neck.
I leave you with the LBC ... unattended, so I hope the pool will not be completely dead when I return.  Wink


Managed to push out a stats update with a graph showing the 24h pool speed average
(if you look at the X-axis right to left, thats like 0 = [now, -24h] -1 = [-24h, -48h] etc.)

So if you will not hear anything from me for the next 168hours, do not worry, I probably haven't been murdered yet.  Wink


Rico
1165  Bitcoin / Bitcoin Discussion / Re: As it turns out, Craig Wright actually is Satoshi! on: February 02, 2017, 06:45:31 PM
That never made sense so either Wright is crazy or he is Satoshi and is devilishly shrewd to have fooled everyone that he is not Satoshi when in fact he is.

Muhahaha ... YMMD! Cheesy

Wait until I find his keys, then I will prove that I am Satoshi. But not before. Before that event I am not Satoshi.
This is where quantum theory meets Bitcoin.


Rico

1166  Bitcoin / Project Development / Re: Advice for a Javascript Graph package? on: February 02, 2017, 04:22:54 PM
Hey Rico,it really depends on how detailed you want your graph to be.As well fancy I might add.To start with,it actually depends on your js coding skills.There are a lot of liblaries ranging from newbie friendly graphs to organizational charts.I have used the following and they are mostly used around.

1.Jquery based easy API :  http://www.flotcharts.org/
2.D3.Js ,cool stuff here : https://d3js.org/
3.Velocity Js : http://velocityjs.org/

If you just want it to be functional without much UI details,go with the first option.

Thanks for the pointers, but I went with Graph.js in the end. It's really simple what I need:

http://imgur.com/2Prnnuql.png

Rico
1167  Bitcoin / Project Development / Re: Large Bitcoin Collider (Collision Finders Pool) on: February 02, 2017, 01:33:32 PM
Why client wrote
Quote
Server doesn't like us. Answer: wrong secret

Look at #371 - #374
https://bitcointalk.org/index.php?topic=1573035.msg17644236#msg17644236


Rico
1168  Bitcoin / Project Development / Advice for a Javascript Graph package? on: February 02, 2017, 01:31:58 PM
Hi,

I'd like to provide some nice graphs on the LBC stats page - for starters a graph with the pool performance for the past ... say month.
Ideally I'd like to use some nifty ready-made JS package and give it a set of numbers and it would display some nice visually appealing graph.
I am aware of 1-2 JS packages doing this, but wanted to hear your suggestions/input.


Rico
1169  Economy / Service Announcements / Re: upgrade Directory.io program on: February 02, 2017, 12:43:39 PM
WARNING: DO NOT SEARCH FOR AN ACTUAL PRIVATE KEY AT THIS SITE. TELLING THE SITE YOUR PRIVATE KEY WILL ALLOW IT TO TAKE YOUR BITCOINS.

Thanks Cpt. Obvious. Why not put the font size to 72pt or something like that?
Never enter private keys to any site anywhere. Ever. So it applies also to the aforementioned site. No news there.

@privatenode:

You may want to take the search WIF key functionality out of the page, so people do not shit their pants. I think the value-add in your site is the range warning for potentially leaked addresses. And I could think about an API you could query for the current search front of the LBC pool (with recently over 1 mio pages on directory.io per second it's moving quite fast) basically the directory.io link at https://lbc.cryptoguru.org/stats

The balance does not seem to work, http://block.okcoin.cn/address/1EoXPE6MzT4EnHvk2Ldj64M2ks2EAcZyH4 has zero contrary to the claimed  15068  (Satoshi?)

Also your page offset starts at 2

http://washen.me/1 is nirvana


Rico
1170  Bitcoin / Bitcoin Discussion / Re: As it turns out, Craig Wright actually is Satoshi! on: February 02, 2017, 12:28:51 PM
I was expecting a much nicer guy to be Satoshi I must admit.

At least as nice as you egghead - I guess.
Thanks for the pointer to your video. Now every time I need an adrenaline rush I know where to go.

Even if I assume Wright is a wanker far worse than I could imagine ... I'd still prefer listening to him for hours than to have listen to you moron for 5 minutes.

Pro advice: get a new head with more space in it.


Rico
1171  Other / Off-topic / Re: Favorite OS and reasons on: February 02, 2017, 11:27:57 AM
I certainly do prefer Linux over Ubuntu.


Rico
1172  Local / Projektentwicklung / Re: Large Bitcoin Collider (Collision Finder Pool) - Deutscher Thread on: February 02, 2017, 10:07:28 AM
Wenn das auch unter Windows laufen würde, würde ich das auch mal probieren wollen aber Linux ist ein Buch mit sieben Siegel --> zumindest für mich :-)

Die LBC Appliance (virtuelle maschine unter Windows) sollte doch easy genug sein. Das haben nun wirklich schon ganz andere "Experten" ans Laufen gebracht.


Rico
1173  Bitcoin / Project Development / Re: Large Bitcoin Collider (Collision Finders Pool) on: February 02, 2017, 09:09:55 AM
Thanks for your insight -  it's a benefaction for me to see someone who understands.

How do you propose this "stopping" be demonstrated, or enforced?  My understanding is there are now several people who have the functional software. (Am I wrong?  Can only thread OP actually test-for-success the work submitted by pool participants?)

All of the checking is being done with the clients and they are out there. So if today/tomorrow the LBC pool ceased to exist, all the clients could continue to work with manual address spaces.

Code:
./LBC -c cpus -p from-to

They could agree on distributing the search space among them via email, carrier pigeon or smoke signals. Probably sooner or later someone came up with some neat IT solution that replaced the smoke signals, put some stats on some webpage...


Quote
Also, while at least three people have expressed dismay at this public exercise, and urged, implicitly or otherwise, it's cessation - does anyone have the responsibility for seeking out persons (if any) engaged in an identical non-public effort?  

becoin said he'd spend the rest of his life on this holy crusade. Yes, that's what he said.


Rico
1174  Bitcoin / Project Development / 128 Mkeys/s on: February 02, 2017, 08:16:15 AM
wow HeavenlyCreatures use gpu maybe  Cheesy

Unlikely - looks more like 200 140 CPUs, but the pool key generation rate is rising hard.
We just broke the magical 128 Mkeys/s - which is equivalent of searching 1 million pages on directory.io per second!

The pool performance shown is a 48h median, current (fluctuating) speed is above 200 Mkeys/s, with that rate, we will hit #49 of the puzzle transaction in less than a week.


Rico
1175  Local / Projektentwicklung / 108+ Mkeys on: February 02, 2017, 07:36:36 AM
Der Pool zischt momentan ganz schön was weg. Tendenz steigend. Vermutlich knacken wir heute Es ist soweit: die magische Grenze von 128 Mkeys/s (entspricht 1 Million Seiten auf directory.io pro Sekunde)  und dann ist der Pool eine Million mal schneller (vermutlich noch mehr) als willis wget-Projekt von damals.

Naja und im englischen Thread wird schon gemutmaßt wie böse Bitcoin-Kriminelle kommen und mich und meine Familie ermorden. Also unterhaltet euch noch mit mir, so lange ihr Gelegenheit dazu habt.  Smiley

Rico
1176  Bitcoin / Project Development / 100+ Mkeys/s on: February 02, 2017, 07:13:41 AM
The pool just cracked it's all time high (98 Mkeys/s) and rising...


becoin ... oh becoin

The point is it's not a collision that is found. The privkey is guessed because 1) it was generated with some crappy RNG, 2) very weak brain wallet pass was used, or 3) address simply belongs to same people that "found" it. In short, the cryptoguru doesn't know what does collision mean.

Quoted for future reference.

Everybody (including me) knows that a collision is found when two different private keys to the same address are found. You are most welcome to set up a project to find a collision as you think it should be done. Teach us more becoin - how would you do it?

...


Rico
1177  Bitcoin / Project Development / Re: Large Bitcoin Collider (Collision Finders Pool) on: February 02, 2017, 07:06:23 AM
1. The "About" section claims that the reason "why" is because somebody said it wasn't possible. That certainly makes sense but once the first "collision" was found the point was proven and there is nothing to prove anymore so why keep going?

A collision is found as soon as you have two different private keys that evaluate to the same Address.
We found two addresses with funds, the keys are weird (either broken RNG or real collisions of a "regular private key") but up to now no one came with an alternate key - so we cannot be sure it's a collision.

Quote
2. If a "collision" is found the amount (if any) is "misplaced" (i.e. stolen) into so-called custodial address. The reason for that is because when the discovery is announced somebody else could quickly find the same and steal it. And the reason why the discovery is announced in the first place is.. to prove the point that has already been proven? Again, why this whole thing still keeps going? To prove the point was a valid and perfectly understandable reason. What valid reason is there now?

If we simply announce the private key and the funds stay where they are - they are gone and no one knows who drained them (simply the person who was quickest). By the process of transferring them to a custodial address and announcing we can "protect them". Now I believe that let alone the announcing of having found something and stating the custodial addresses should make it dead clear that this is not some stealing. If anybody wanted to steal - why make it public? I really get tired of having to explain this.


Quote
3. The webpages are full of "rightful owner" this, "rightful ownership" that, but how is this rightful owner supposed to find out about what really happened, i.e. that they in fact weren't robbed, they were just "robbed"?

How about you look at: https://blockchain.info/address/1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg

Quote
Assuming that every owner of bitcoins in the whole world will somehow magically become aware of some random thread at some random Internet forum and from now on will be anxiously reading it every day for the rest of their lives is just insane.

Have you read https://blockchain.info/address/1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg already?

As for checking a "random thread" somewhere: I believe when LBC finds some more addresses, it will not be a "random thread" somewhere, but a quite well known thread. Also the development is not finished yet. I may set up a RSS feed for https://lbc.cryptoguru.org/trophies.

Quote
4. So far only empty or almost empty addresses have been found but what will happen when some reasonable amount (hundreds or thousands BTC) is found? Will the "announcing" and "misplacing" happen again?

As far as I am concerned - yes.

Quote
If somebody has such an amount in one address they are either stupid or they have many similarly loaded addresses. If the latter is the case then aren't you afraid what may happen to you and your dear ones if you piss off the wrong people? I don't see it entirely unrealistic if some angry criminals tracked you down and murdered you and your whole family, and they will most certainly not care one single bit about your "proving the point", "custodial address" etc. bullshit.

Ok - I think we can stop it here, because your choice of words proves you are not here to have questions, you have some opinion already. You also watch movies too much.

But just for the fun of it, to entertain your "army of hitmen coming after me and my friends": If anything like that was to happen. And it's a big IF because the pool would have to find something, actually my client would have to, so I would do the custodial transfer, they would have to find out who I am (which is the easiest part), they would have to be totally dumb (but criminals often are) to not simply get their funds back by providing their alternate private key....

I certainly hope they would not be as dumb as to killing me immediately, but torture me 1st for the private key of the custodial address.  Wink
Because else - you know - they would need LBC to find that.  Cheesy


Rico
1178  Bitcoin / Project Development / Updates on: February 01, 2017, 06:58:41 PM
So:

1)

164kvbiwxEq3wfeUWLSdxBuQeAyMhyFe4N funds are on their way to custody at 1CTota4HeLLEgg5x5jv5xxp3Rw2SqTdKiW
see - https://blockchain.info/tx/2f00dc3f462f406ec8e96f402dbc0c342f36b69425c28e6ab0472fe0b62119a6

2)

There is a new BLF file (170201) on the FTP server, upon restart, your LBC clients should patch your blf files.

3)

Pool at 70+ Mkeys/s  (edit: 64Mkeys/s = 500 000 pages on directory.io per second, we are now at 74 Mkeys/s)

4)

Oh yes - and the private key to 164kvbiwxEq3wfeUWLSdxBuQeAyMhyFe4N is 0xe09c93a2ec81


Rico
1179  Bitcoin / Bitcoin Technical Support / Bitcoin Core still tad pole to user friendliness on: February 01, 2017, 06:40:23 PM
I have my Bitcoin Core on my home server and start it remotely, but thanks to the X protocol I work with it on my notebook.

Despite local network things go tenaciously, but for now I'm willing to attribute that to X and not to bitcoin core.

What I really must attribute to the Bitcoin core is:

The use of modal dialogues when it's completely unnecessary
and
amnesia when it comes to UI settings

in combination these two are killing me every time. I have therefore some questions, which in fact are rhetoric and really just comments:


  • Why is the coin selection dialogue (when coin control features are on) modal?
  • Why can't bitcoin core remember a single friggin changed UI?

As for the 2nd point: If we take this coin selection dialogue and the table in there, well the table is pretty fucked up - which applies visually for every table in bitcoin core - but hey, we can change the widths of the columns etc. So we do it. After lots of beautifying work, the visualization is usable, but - oh no - we need to look up something else, and because that dialog is not modal, we have to close it. Aaaaaand...

When we return all is again fucked up as it was before!!!

Now imagine doing this over a remote connection. Over and over again ... and again... Bad developers. No soup today.


Rico
1180  Economy / Digital goods / Re: Cheapest AWS EDU 150$ Code! 11$ per code + promo code on: February 01, 2017, 03:45:06 PM
bought all remaining 3 codes, all work.  Smiley


Rico
Pages: « 1 ... 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 [59] 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!