Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner. Last I checked, DiabloMiner had bugs in its rollntime implementation, and Diablo-D3 stubbornly denied they existed (thus refusing to fix them), so I blacklisted it from using it. Specifically, with rollntime enabled, DiabloMiner is somehow confusing its work and when it expires, and sending shares against work older than 2 minutes, even after it has received new work. If Diablo-D3 has fixed this, and someone is willing to do some real-time testing to confirm it (on IRC), I'd be glad to remove it from the blacklist... |
|
|
|
Good idea.
The developers listed on bitcoin.org are the people who have 'push' rights to the github source tree, but I like the git approach.
Who wants to volunteer to make it happen?
If you mean a PHP file that parses Git repository and produces a list of developers, categorized and sorted - I can do it. Tell me what you need. There's a lot of git repositories to include in that... http://luke.dashjr.org/programs/bitcoin/ has a list |
|
|
|
|
When the value of Bitcoin shot up to $30/BTC, we dropped the minimum payout from 1 BTC to the current ~0.34 BTC (200 TBC). The marker price has changed quite a bit since then, so should the minimum payout be raised? Keep in mind, the whole purpose of the minimum payout is to made a happy medium size to minimize the miners' transaction sizes (and therefore minimize transaction fees as well), so the minimum payout is ideally the average size of a transfer/purchase.
I expect to leave this poll open only for a day or two, and implement the result as-is.
|
|
|
|
Confirmed that's at least one of the User-Agents I'm getting. Now on a connection rate limit... |
|
|
|
|
I'm seeing a couple of absurd (1000+) connection counts from single IPs to Eligius.
What user-agent does bitHopper send?
|
|
|
|
|
I have blocked the two mining proxies using address 1DeVdPQ18o5oRAuBq49hD5K8tNtwdBwhc2. There is no reason you should need over 2000 connections for a mere 60 MH/s, and it's degrading the pool's performance. Contact me when you fix it, and I'll unblock you.
|
|
|
|
I'm sorry, I must have missed the copyright notices. Copyright law does not require notices. Everything is copyrighted by default. |
|
|
|
It should be noted that publicly posting logs of private* IRC channels is arguably illegal (copyright and/or wiretapping) and explicitly against Freenode's policies. If you're considering publishing channel logs, think it through. The freenode network is an interactive environment. Even on public channels, most users don't weigh their comments with the idea that they'll be enshrined in perpetuity. For that reason, few participants publish logs.
If you're publishing logs on an ongoing basis, your channel topic should reflect that fact. Be sure to provide a way for users to make comments without logging, and get permission from the channel owners before you start. If you're thinking of "anonymizing" your logs (removing information that identifies the specific users), be aware that it's difficult to do it well—replies and general context often provide identifying information which is hard to filter.
If you just want to publish a single conversation, be careful to get permission from each participant. Provide as much context as you can. Avoid the temptation to publish or distribute logs without permission in order to portray someone in a bad light. The reputation you save will most likely be your own. * As stated above, "private" is the default for channels, unless they are known to be publicly logged usually by a mention in the topic. Interesting he says ArtForz is the attacker. He was obstinately accusing me yesterday. |
|
|
|
Can't close an open source thing without removing all open source code from it. What CH/RS did was put up an illegal and illegitimate message in a readme file, which not only can safely be ignored but should be ignored. This is not correct. Bitcoin is under the MIT/X11 license which allows people to restrict or close it up as they like. Also, even if Bitcoin was GPL'd and they tried to pull this, their infringement does not automatically mean you can infringe on their code. Anyhow, Solidcoin was flawed from the start. It didn't fix much, if any, of the known issues in Bitcoin, and only worked-around the "pump and dump" issue other similar scams have seen. Over the past few days, I've explained to various people on IRC how a new cryptocurrency could be done to really fix these problems and significantly restructure things, so hopefully some of them will get together a team to actually try implementing something new (it falls outside the scope of my interest in Bitcoin to do so myself). |
|
|
|
|
Finally got around to it... Eligius now has IPv6 support again.
|
|
|
|
Payout queue manual send hereFor some reason, my own local client got stuck and I had to restart it. If you don't see your payout, but it's on the link above, you might want to try the same. If that still doesn't work, try -rescan.
|
|
|
|
|
We already have B⃦ in every popular Bitcoin logo.
|
|
|
|
I'm using Windows. How to clear current settings? I think it's in the registry on Windows. It shouldn't lock up through... Is the project still alive? Yes, but I haven't seen a need to change much lately, and there's been no activity as far as other developers submitting merge requests either. It would REALLY help the security if the passwords would be stored in a hashed form rather than plaintext in the address string in the settings.
Could it be fixed please? No, it's not possible due to the HTTP protocol being used (which also sends it cleartext). I think if you leave the password out, it will prompt you. |
|
|
|
Block Explorer too. yes but that is not true data because sometimes some payments get split between multiple addresses for example the block chain show 0,91 less BTC that the total amount received by the adress That doesn't make sense... the block chain is the authority as to what was received. you did not understand me well i have one address for each pool so i did check the address for your pool and i saw for the last transaction i get +0,18xxxxx (data from blockexplorer.com) i was like wtf i dit get payed that from eligius, so i did check around and i did find that the extra 0,18 come from a mred payment, even if on mtred i use a totally different address, after manually checking all payments versus blockexplorer.com data acording to blockexplorer i did earn 0,91 less BTC Still doesn't make sense. Maybe run bitcoin with the -rescan option? |
|
|
|
Block Explorer too. yes but that is not true data because sometimes some payments get split between multiple addresses for example the block chain show 0,91 less BTC that the total amount received by the adress That doesn't make sense... the block chain is the authority as to what was received. |
|
|
|
Luke is there any way to check the total payed BTC for a certain address ? It's in the JSON data as "everpaid", and there's obviously Block Explorer too. If someone wants to make a branch for the stats, I'd be glad to merge it. Update on the payout bottleneck: I put together a patch to allow me to make manual sends for payouts. Two guys in the channel are helping me with the test, which should be confirmed working with the next block. Assuming all goes well, I plan to do a sendmany to take out a large chunk of the payout queue. Due to the size of the sendmany, I expect it will not be relayed (and therefore not visible in your clients) until Eligius finds another block-- but it will be reflected in the payout queue page and stats immediately. In short, your unpaid balance will disappear after the next block, and that portion missing will be paid by a regular transaction in the block following that one. |
|
|
|
Anyone else get an "Unknown Address!" page when trying to check their stats? My address is gone from the payout queue page too.
BTW, is this still a problem? Can you PM me your address/link? |
|
|
|
|
Show Posts
