@shads: Do you thing it would be possible to have a pure java implementation of getWork() without the need of calling the bitcoin daemon, using for example the bitcoinj library? Could this speed up things?
|
|
|
On the way down to where? Someone able to answer this would be probably rich enough to not bother checking threads like this one ;-)
|
|
|
hey whats the status on the site upgrade? Going well? BTW: please, pretty please implement the "coming soon" feature to add notes to the workers because I've made a mess with mines and it would be soooo useful :-)
|
|
|
no, non è lui l'autore (è scritto in fondo all'articolo che poi è anche vecchiotto). Avevo visto il nome in fondo all'articolo, pensavo semplicemente fosse il suo vero nome. In ogni modo grazie per l'informazione. Rimane però la domanda: perchè accostare SCEC a Bitcoin visto che non hanno nulla in comune?
|
|
|
e l'autore pare essere molto competente L'autore che poi saresti tu..? Se posso approfittare per chiederti non ho capito bene che c'azzecca lo SCEC con Bitcoin? (Il fatto che il tutto sia in un sito che si chiama chemtrail non semplifica le cose)
|
|
|
A mozilla developer, Brian Warner, does a technical introduction of bitcoin. Video and slides.
|
|
|
Not knowing if there is a thread dedicated on gather information about new merchants accepting bitcoins I write here just to let others know, I hope this is not a problem otherwise please point me to the correct thread. JonDo, a site selling proxy and anonimizer tools, started accepting bitcoins.
|
|
|
btw: I can't find any documentation about the extraNonce: where is it recorded? why I can't see it on blockexplorer and such?
|
|
|
http://Uploaded.to now accepts bitcoins: Besides additional, useful changes such as the newly designed Download Page with a Facebook-like button, we have taken the decision, as the first file hosting service worldwide, to accept bitcoins. You will receive more information on this in the next few weeks.
|
|
|
Hello BitMole, I live in Italy, and our bitcoin community is really small, for now. General people is very conservative and most of them if very suspicious about bitcoin. Still, they trust the Euro and governments, go figure :-)
Anyway, I can try to organize a group, we have a forum, we have a facebook page and we know almost all of the italian bloggers, so we can try.
My goal with my previous post was to suggest a thread to coordinate activities toward some goal, as to make a site accept bitcoins. I suppose that the first major site that accepts them will pave the road for the others.
If we move in a coordinate way some lobbying should be effective, I guess.
|
|
|
In the linked method, what is really interesting to me is: xhost + chmod uog+rw /dev/dri/card* I've never seen the dir /dev/dri on any of my ubuntu or debian systems: do you have it?
|
|
|
I think that it's completely ineffective to try to "convince" a site to accept payments in btc. The only effective way would be to coordinate everybody to ask them to do so, and then buying something. For example I'm sure that a chinese shop like http://www.dealextreme.com/ or http://www.tinydeal.com/ would be interested in bitcoins if some hundred of customers ask to support it. But how many of us is ready to do so? (I would be one of them, btw)
|
|
|
Awesome, thanks for all the infos.
But I would like to know more about the extensions used for the VGAs: what are they and where they could be bought?
Thanks!
|
|
|
[Awesome -- registering to this thread for updates]
|
|
|
Next step for botnet operator: write a small script to generate 100000 worker names and set the worker name in your trojan payload to random(100000) You can simply avoid such a behavior with a captcha (both for account creation and new worker. Anyway, the more work a bot owner has to do, the more it looks for simpler alternatives, i.e.: less managed pools.
|
|
|
And if anyone have suggestions on what we should do to avoid this in the future, please feel free to help out. I'm starting to get out of ideas. Jack's idea seems to me the most interesting one: instead of just restricting number of getWorks (or, more in general, web access) to an IP you should use the worker name as a discriminator. In other words there must be a minimum ratio between number of web requests and number of valid shares per unit time. This way a large (and productive) user behind a proxy is not penalized while a bot network issuing requests from all over the world (and using the same worker name) can be correctly detected and shutted down. I don't know php but I would handle this kind of policy using a filter under tomcat (a java app server), this way it's not handled by the application but it's simply an access layer.
|
|
|
I want to simply thank Jine for his dedication on this (difficult) task. Thanks! And long live bitcoins.lc
|
|
|
I admit I'm not grasping your aim but I'm interested in knowing more. Anyway, I just think my version is just more "pure", and that it can allow to get rid of the 6 block per hour limit, for instance. For what I understand the 6 block limit x hour is not a limitation but a design choice, done to balance the number of blocks with the time needed to broadcast them over a global network: the more blocks per unit time, the higher the probability of chain splits and needed reorganizations.
|
|
|
|