facebook page for recent updates and news? i hate facebook. i would rather get updates and news here pls
I'm planning to add some facebook widget instead of current news bar on the left side, so even people without a FB profile will see major news. I agree that it's necessary to see important updates directly on the website. I picked FB, because almost everybody have or can have an account, and it is probably to easiest way for the people to give me the feedback. Many people also have problems writing here because of rules for newcomers. Generally I think FB is pretty good tool for building a community, but of course you don't need to register on FB to use the pool :-). |
|
|
|
I would like to know if you could pass a signed transaction onto another party (say, from the payer to the payee) too. This would be very useful for areas with limited data connectivity, as it would only require the receiver to 'upload' the transaction.
Yes, this is possible with signed transaction. You could also have situations where both parties had no Internet access and such transactions could be treated like cheques, which could be cashed when the payee is next online.
But you need to be really careful here. The fact that transaction is signed doesn't mean that it is valid. If you cannot fully trust payind side, you shouldn't receive such transaction offline... |
|
|
|
Is anyone else having high reject rates after you get a longpoll?
What does "high" mean? Is you miner connected to LP port? What miner do you use? Please post me a PM. Edit: I re-checked LP mechanism and everything seems fine. Also all my rigs connected on the pool have pretty low stale ratio (~0.15%). |
|
|
|
I needed some break from work on backends, so today I launched multilanguage support for website. Not all texts are currently translated, especially some emails, but I'll fix it during the time. Currently English, German, Russian and Czech translations are available. If you want pool site in your language and you want help me with it, let me know :-). I'm especially looking for some French or Spanish native speaker... 1: Can a date/time localization be added?
Yes, it's already on my list. However it will come after DGM. 2: In the statistics page, can an additional field be populated showing the number of shares submitted for past blocks?
Yes, this is part of DGM update which is planned in next days. |
|
|
|
has the pool been suffering alot of down time? my end seems ok
As far as I remember, there were two noticable downtimes in last week, both because database maintenance. First was around 30 minutes, second exactly 10 minutes (crunchyferrett :-P). I don't think those two outages can affect overall hashrate in some significant way. |
|
|
|
The hash rate shown on the account page has been consistently 20-25% below what my miner tells me it is, I never really gave it much thought. One or the other, or both, are wrong.
Well, that hashrate on the profile page is just an estimation; hashrate given by your miner will be much more exact. Actually as far as you don't see any connection issues in the miner, don't worry. Pool indicates accepted or rejected shares directly in getwork response, so all possible issues should be catched by your miner. |
|
|
|
|
My appologies for recent downtime, it was database maintenance (second and final part). Downtime was less than 10 minutes.
|
|
|
|
|
OK, BTC payouts working again (I just sent batch of all pending payouts), I'm working on NMC now.
Edit: NMC payouts works as well.
|
|
|
|
|
Payouts are still disabled, I came at home too late and it's always better to be fresh while handling with coins. I'm working on fix right now and payouts should be enabled very soon.
|
|
|
|
|
splitt, invalid ratio is slightly under 1% in long term average. Yes, in recent days there were some extra invalids, but as you can trace on blockchain.info, it was really just bad luck, there isn't any obvious mistake. Pool is also directly connected to some well propagated nodes and also to few other pools to minimize latency.
|
|
|
|
|
Writing from mobile connection; i was fixing one issue on the server, sorry for short outage. Connection from here was incredibly laggy. I also stopped payouts, they'll be back on the evening UTC.
|
|
|
|
|
Ok, it's back up, downtime was 35 minutes.
|
|
|
|
|
I'll start linux kernel & database update in following 30 minutes. Unfortunately I need to stop application, expected downtime will be 20-30 minutes.
|
|
|
|
Would moving to PPLNS temporarily be a possibility? Or would you be changing one difficult to solve problem for another?
At this moment is simplier to finish DGM than do all coding and testing for PPLNS and then DGM again... |
|
|
|
As Inaba said the number and order of fields in JSON is immaterial
To be exact, this is true only for keys of an array. Lists (and history of blocks should be definitely stored in list) are ordered. But I see your point. Actually I'm for defining JSON API as an standard, because it's usually easier to handle in applications, and provide alternate CSV API with block history only (from pool side it's just an iteration over original JSON and columns with expected order). |
|
|
|
...so it can't be too much harder than PPLNS to implement here - especially when Slush has more experience than anyone at running a pool using exponential scoring).
The main difference between current score implementation is that score equation needs only time as an input, but proper implementation of DGM need to know also count of already submitted shares (across all backends). Pool core is designed quite scalable, there's no online synchronization between backends necessary, but it goes against DGM requirements. And it's the pain and the reason why it takes so much time. Originally I expect that it won't be so hard, but I felt into solving strange threading issues (cause framework which I'm currently using doesn't natively support user's threads). |
|
|
|
Have you guys seen Luke's BIP?
Yes and I see it overcomplicated, especially that "collab" construction. Better to have more APIs than one huge monster, isn't it? I even think that current API should be split into more calls like account state (balances, address, etc) and worker states. |
|
|
|
I did that specifically so you could add nmc_balance, nmc_unconfirmed, and nmc_paid. Although I suppose we could make them a sub array of BTC: or NMC: (or whatever other currency) and then just use balance, unconfirmed, paid.
Having currency name in variable doesn't look smart. Then I prefer - separate calls completely (and have an api for every currency) or have separate section for every currency, like ...'balance': {'BTC': {'unconfirmed': 0, 'confirmed': 0, 'paid': 0}, 'NMC': {...}} ... |
|
|
|
The only (<market>.scid) files available are the ones I specified in the command line above. There are no other .scid files. You are saying other markets should be available to choose, I'm not sure what's wrong?
Are you using latest version, 0.5? Edit: I see you're using 0.5. Then if you don't specify any market, feed will use "-s mtgoxUSD,*" by default. It means: Download mtgoxUSD history on startup, then start feed and store all other streams as well (and download market history on first update). If you're using -s parameter without "*", it will stream only markets which you defined. |
|
|
|
Do I have to start a fresh terminal for each exchange I want to monitor?
No, feed is downloading *all* quotes by default,storing them in separate files (<market>.scid). Default behaviour is that markets are lazy-loaded,that means feed will dowload market history once there's some move. If you specify market in -s parameter, market history will be downloaded actively after startup... |
|
|
|
|
Show Posts
