Gotcha. So he made the changes on git I presume - can you ask him to post a link to it? Thanks  No. I don't believe any changes were made or are planned to be made on git. It is a separate payout system developed for NastyPool that is written in a different computer language (C vs Python). Are there plans to open source that code and allow others to use it on their nodes? |
|
|
|
|
Hey Matt, Aussie node is playing up.
|
|
|
|
Once the pool gets bigger I will of course automate more of those checks, however, they don't take very long, and there will always be a final manual check of the information to help ensure it's correct - for security reasons also.
thumbs up! That is very comforting to know, and I wonder if other larger pools that I won't mention by name practice this as part of their protocol...I really appreciate all the effort and time that you and ck have put into developing this wonderful pool. I know your time is valuable. I just want you guys to know it doesn't go unappreciated. yeah ditto, I've always found that transparency is the key to helping your customers understand. It's usually when you try to lie and keep them in the dark that they start to become impatient and unreasonable. |
|
|
|
|
The node is running the latest code from github. It also sits right next to Matt's Aussie relay server. Unfortunately due to network latency and lack of good peers nearby there will be dead or orphan shares. I've done everything possible to reduce them including going to an ssd based vm.
1Th/s these days is so small and with the share diff at over 18M on p2pool these days its just not viable for small miners.
I am watching the antpool news closely and if they release code that fixes the variance then I'll update my node and move my miners back.
Until that happens, it is what it is and nothing more can be magically plucked from thin air.
Where you mine is totally up to you, I've never once hit a namecoin block yet I keep it there and anyone in the know will tell you it not worth merge mining anything else.
Personally I have to roi on my s3's and kano's pool has given me 60% of that. Once I've satisfied my roi and/or someone releases a fix for p2pool variance for small miners I'll put my hashing back into p2pool.
Until then the node will stay up and available for free for anyone wanting to mine to it.
|
|
|
|
Pool's broken......Kano, please fix your crappy code  Yes, its a joke. Last time I asked for a block though we got one, so here it goes. How about another block please? Edit: oh, one legit question, how do i get rid of old workers? Do they drop off after x days non use? There's an item down my todo list to add an option to have it not show workers that haven't had shares for ... I guess a week or something like that. I've not decided the time frame control(s) yet - but yeah it's on the todo list. I don't give time frames for non-critical changes coz I'll usually disappoint people who take too much notice of the time frame But rest assured, it is something that's been requested already so it's definitely on the todo list. Cool, thanks. Yeah purely cosmetic so no rush. |
|
|
|
Pool's broken......Kano, please fix your crappy code Yes, its a joke. Last time I asked for a block though we got one, so here it goes. How about another block please? Edit: oh, one legit question, how do i get rid of old workers? Do they drop off after x days non use? |
|
|
|
Why is ur site not showing the last block?
Its been paid to my wallet....
P2pool sometimes does that. It'll show eventually |
|
|
|
He runs one of the relay nodes My bad Yeah it has stabilized quite a bit now with >98% efficiency. |
|
|
|
Don't forget that even if they end up being just one node in any p2pool network - be it the existing one or a new one, they will be far more than 51% of that network meaning it's as good as a centralised pool.
Like I said, they're paying homage to the idea of decentralisation because clients are demanding it so it makes for good marketing on their part. While them contributing to p2pool is most welcome, I see no sign of any of the alleged decentralisation.
I think they intend on open sourcing the code so that existing nodes can then provide a "team" hashing effort while giving the node operator a way of paying out miners in that "team". Problem there of course is we then have a burden of trust back on the miners towards the node operator. I think its a step in the right direction though and a compromise between single central pools and the P2pool model. That way you wouldn't have all miners on one node, you could still have local nodes to reduce latency. You would of course loose the freedom of moving between nodes without loosing your shares unless somehow the shares can be communicated to another node, a bit hard when the sharechain is tracking shares for the nodes wallet and not the miner itself. |
|
|
|
Silly question, but inquiring minds want to know. How do we get a 594M diff solution if the network is requiring 38B?
Luck 😉 |
|
|
|
|
They aren't providing a charity as they are pocketing the transaction fees. What they appear to be doing is providing an agent as such. A mechanism whereby you mine on their node to the default address that then appears as a larger miner. Since its larger there is less variance. They are then calculating the shares to miners on the node and paying them from that nodes wallet.
It is centralizing the smaller miners but still hashing on p2pool's sharechain.
It's a novel approach to trying to solve variance and similar to having a secondary sharechain. It will be interesting to see the code and how it works out the subchain payments.
I must say it does sound like what Kano and ck have been doing, like a ckpool instance connecting to a p2pool backend.
|
|
|
|
dodo dood dood dood another one bites the dust, and another one down and another one down, another one bites the dust...... |
|
|
|
|
Yeah baby! When will this end? Never I hope.
|
|
|
|
You know what, I just realized I said IE 10 when I meant Windows 10.
That's all Win 10 is right now, a developer preview.
M
haha all good, lets not clog up the most awesome pools thread with windows debates  Bring on the next block I say There you go mate, all you had to do was ask. Block 329482 WOOHOO!!! haha sweet! (that should have been pool's not pools) |
|
|
|
You know what, I just realized I said IE 10 when I meant Windows 10.
That's all Win 10 is right now, a developer preview.
M
haha all good, lets not clog up the most awesome pools thread with windows debates Bring on the next block I say |
|
|
|
ah yeah, you are talking about the tech preview specifically? yes, it is a tech preview, Microsoft pay a lot of attention to their beta programs these days which is why their products as so much more stable when they are released. It's all good info that just helps them deliver a better product to you. It's not a good idea to run a tech preview for your every day work anyway and the final version will not do this as they are not actively trying to find bugs and develop the final product. anyway.. you always have the choice right? |
|
|
|
|
quick restart to add more peers.
|
|
|
|
I hereby from this day forth proclaim this pool.....ROCKIN!  |
|
|
|
Payout 329310 sent hmm I didn't see this payout come through. I'm sure I had shares on that block. block chain is slow right now Yup, strike that, reverse it, thank you. I.e. Just came through 😁 |
|
|
|
|
Show Posts
