@jedimstr
your comment only gave me an in, I don't specifically remember you being outspoken towards forrestv. although I don't recall you or much anyone else speaking out when he was being mauled either.
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 247. (Read 2591928 times)
December 24, 2014, 11:44:17 AM
December 24, 2014, 10:44:02 AM
jedimstr
I could not agree with you more. IYFTech needs to learn some decorum, or just plain how to be nice. He will flame any one on any form, if he does not think a post is right.
With a attitude like that it is all a big negative and will run Great people from developing and or contributing there time and efforts, and that,s a shame.
One can have a debate and still be human or even nice and still get there point across.
It is just not right!!!!!
Merry Christmas everyone. Enjoy the holidays with your loved ones.
Remember Christmas is all about the celebrating the Birth of Jesus.
Ok let the Flaming Begin.
Not flaming, just pointing out an error. Jedimstr was not asking IYFTech for an apology or accusing him of trolling. He was writing to Carlton Banks for his comment.I could not agree with you more. IYFTech needs to learn some decorum, or just plain how to be nice. He will flame any one on any form, if he does not think a post is right.
With a attitude like that it is all a big negative and will run Great people from developing and or contributing there time and efforts, and that,s a shame.
One can have a debate and still be human or even nice and still get there point across.
It is just not right!!!!!
Merry Christmas everyone. Enjoy the holidays with your loved ones.
Remember Christmas is all about the celebrating the Birth of Jesus.
Ok let the Flaming Begin.
With Bitcoin Core v0.10.0 Release Candidate 1 out for testing, any potential gotcha's for P2Pool RPC interaction. I see in the release notes that there are quite a few RPC and header related changes.
I've gone through the release notes and bug fixes, along with perusing the changes to the core code in the git repo. I don't see anything that would impact the functionality of p2pool. There are a lot of changes to the way the blockchain data is stored locally and some pretty interesting new RPC/API calls that can be made. December 24, 2014, 10:32:13 AM
With Bitcoin Core v0.10.0 Release Candidate 1 out for testing, any potential gotcha's for P2Pool RPC interaction. I see in the release notes that there are quite a few RPC and header related changes.
I was going to wait till rc2 or 3 to instal on my test server, there will most likely be a few release candidates for an upgrade this large, and changes made before the final release may have an impact.
Regardless, I'll give it a try next week and report back.
There is A LOT going on in 0.10.0, so can not say definitively, but it does not look at first glance like it will affect p2pool.
Here are the current release notes (subject to change):
https://github.com/bitcoin/bitcoin/blob/0.10/doc/release-notes.md
December 24, 2014, 10:00:01 AM
jedimstr
I could not agree with you more. IYFTech needs to learn some decorum, or just plain how to be nice. He will flame any one on any form, if he does not think a post is right.
With a attitude like that it is all a big negative and will run Great people from developing and or contributing there time and efforts, and that,s a shame.
One can have a debate and still be human or even nice and still get there point across.
It is just not right!!!!!
Merry Christmas everyone. Enjoy the holidays with your loved ones.
Remember Christmas is all about the celebrating the Birth of Jesus.
Ok let the Flaming Begin.
I could not agree with you more. IYFTech needs to learn some decorum, or just plain how to be nice. He will flame any one on any form, if he does not think a post is right.
With a attitude like that it is all a big negative and will run Great people from developing and or contributing there time and efforts, and that,s a shame.
One can have a debate and still be human or even nice and still get there point across.
It is just not right!!!!!
Merry Christmas everyone. Enjoy the holidays with your loved ones.
Remember Christmas is all about the celebrating the Birth of Jesus.
Ok let the Flaming Begin.
December 24, 2014, 07:33:47 AM
With Bitcoin Core v0.10.0 Release Candidate 1 out for testing, any potential gotcha's for P2Pool RPC interaction. I see in the release notes that there are quite a few RPC and header related changes.
How's it feeling now, after most people in this thread unwisely sat back and watched as the original developer of p2pool was hounded by ignorants who wanted their AntMiner S2/S3 driver fixed? That was well worth driving forrestv away for, wasn't it?
I think you're wasting your venom on the wrong person here. And besides you are way off with your assessment. People wanted forrestv to be more involved instead of just accepting 3 month old Git pull requests from other contributors without any comments for almost a year in the forums. Forrestv said he was busy with his real life and didn't have time. Fair enough if you ask me. Also fair is that some people no longer thought donations that weren't distributed to other developers who've contributed more front end UI and backend fixes in git pulls than forrestv has had time to do himself in the last year should no longer be honored or reduced.
Me, I just want p2pool to grow and have a significant portion of Bitcoin mining going forward which includes keeping the client updated enough so it won't break with newer versions of Bitcoin Core, regardless whichever developer decides to contribute to the cause.
Now if you'd please stop trolling and perhaps even offer an apology for the unwarranted venom... I'd hate to put you on ignore since you've actually contributed some good posts in the past.
December 24, 2014, 06:06:13 AM
With Bitcoin Core v0.10.0 Release Candidate 1 out for testing, any potential gotcha's for P2Pool RPC interaction. I see in the release notes that there are quite a few RPC and header related changes.
How's it feeling now, after most people in this thread unwisely sat back and watched as the original developer of p2pool was hounded by ignorants who wanted their AntMiner S2/S3 driver fixed? That was well worth driving forrestv away for, wasn't it?
What on earth do you mean?
The drivers are not part of p2pool, they are part of the Bitmain fork of cgminer - which ckolivas/kano fixed a long time ago.......Nobody drove anyone away - he just stopped posting. That's his choice.
December 24, 2014, 05:45:58 AM
With Bitcoin Core v0.10.0 Release Candidate 1 out for testing, any potential gotcha's for P2Pool RPC interaction. I see in the release notes that there are quite a few RPC and header related changes.
How's it feeling now, after most people in this thread unwisely sat back and watched as the original developer of p2pool was hounded by ignorants who wanted their AntMiner S2/S3 driver fixed? That was well worth driving forrestv away for, wasn't it?
December 23, 2014, 02:52:09 PM
With Bitcoin Core v0.10.0 Release Candidate 1 out for testing, any potential gotcha's for P2Pool RPC interaction. I see in the release notes that there are quite a few RPC and header related changes.
December 21, 2014, 11:13:56 AM
my pool is still running well, but had to pull some power off it, experimenting with my new pool, much to learn. will be back to p2pool soon. managed to hit couple of shares earlier today. blocks keep em coming.
December 21, 2014, 07:41:40 AM
Frankly I'd advise against anything with Bitmain's name on it.
It's certainly beginning to look that way, looking at their recent failures/cock-ups/mistakes. Sad but true.
December 21, 2014, 07:34:42 AM
I would advise against antpool - their code is terrible & there is zero support:
https://bitcointalk.org/index.php?topic=855548.160
https://bitcointalk.org/index.php?topic=855548.160
Frankly I'd advise against anything with Bitmain's name on it.
As for a S4 friendly pool, ckpool seems to be working well.
M
December 21, 2014, 07:20:17 AM
I would advise against antpool - their code is terrible & there is zero support:
https://bitcointalk.org/index.php?topic=855548.160
https://bitcointalk.org/index.php?topic=855548.160
December 21, 2014, 03:00:59 AM
Umisoo = Ouch!
I feel your pain buddy.....
Edit: Can you ask them to change the settings?
I feel your pain buddy.....
Edit: Can you ask them to change the settings?
Have I done that, ouch. Nothing helps. Engineers from bitmain they tell me that I cant belive my eyes. It doesnt help to send snapshots, they dont understand what is doa share.
No worries, next time I know im not alone here.
Ask them to redirect some port to IP of Your S4 port 22
One thing I love is Elvis, theres no port to be able to change that. Im going to to take a flight nevertheless Elvis is dead or alive. Im going to fly from helsinki to oslo sometime soon.
If my s4 is bad it is. Theres one pool where it behaves like it allmost should, its Ckpool.
December 21, 2014, 02:55:36 AM
Oh great!! Two on two! En plein: yesterday and today.
My shares: 9aeb118c a6c5df0a
Happy mining!
My shares: 9aeb118c a6c5df0a
Happy mining!
December 20, 2014, 05:37:57 PM
Umisoo = Ouch!
I feel your pain buddy.....
Edit: Can you ask them to change the settings?
I feel your pain buddy.....
Edit: Can you ask them to change the settings?
Have I done that, ouch. Nothing helps. Engineers from bitmain they tell me that I cant belive my eyes. It doesnt help to send snapshots, they dont understand what is doa share.
No worries, next time I know im not alone here.
Ask them to redirect some port to IP of Your S4 port 22
One thing I love is Elvis, theres no port to be able to change that. Im going to to take a flight nevertheless Elvis is dead or alive. Im going to fly from helsinki to oslo sometime soon.
If my s4 is bad it is. Theres one pool where it behaves like it allmost should, its Ckpool.
December 20, 2014, 03:50:45 PM
Umisoo = Ouch!
I feel your pain buddy.....
Edit: Can you ask them to change the settings?
I feel your pain buddy.....
Edit: Can you ask them to change the settings?
Have I done that, ouch. Nothing helps. Engineers from bitmain they tell me that I cant belive my eyes. It doesnt help to send snapshots, they dont understand what is doa share.
No worries, next time I know im not alone here.
Ask them to redirect some port to IP of Your S4 port 22
December 20, 2014, 02:28:14 PM
Umisoo = Ouch!
I feel your pain buddy.....
Edit: Can you ask them to change the settings?
I feel your pain buddy.....
Edit: Can you ask them to change the settings?
Have I done that, ouch. Nothing helps. Engineers from bitmain they tell me that I cant belive my eyes. It doesnt help to send snapshots, they dont understand what is doa share.
No worries, next time I know im not alone here.
December 20, 2014, 02:09:21 PM
Thanks very much for sharing Your toughts PatMan, alltough it didnt help me because ive allready bought a s4 to hosted at umisoo. Theres --queue 4096 and a lagging miner now... Nothing I can do to make it better...
Next time I know what not to do.
Next time I know what not to do.
My S4s have the original Bitmain's settings with last firmware. Only address or address + 2048.
In the last 8 blocks, I closed 2. The just closed block (today) has been done by one of my nodes S4
Same settings also for S2 and S3.
I have all my miners set to failover to my local p2pool node, so having custom settings - beyond setting difficulty via the username - isn't doable for me. That said, my S4 managed to sneak in a share in the last brief failover period.
M
December 20, 2014, 02:07:00 PM
Thanks very much for sharing Your toughts PatMan, alltough it didnt help me because ive allready bought a s4 to hosted at umisoo. Theres --queue 4096 and a lagging miner now... Nothing I can do to make it better...
Next time I know what not to do.
Next time I know what not to do.
My S4s have the original Bitmain's settings with last firmware. Only address or address + 2048.
In the last 8 blocks, I closed 2. The just closed block (today) has been done by one of my nodes S4
Same settings also for S2 and S3.
December 20, 2014, 12:08:13 PM
Thanks very much for sharing Your toughts PatMan, alltough it didnt help me because ive allready bought a s4 to hosted at umisoo. Theres --queue 4096 and a lagging miner now... Nothing I can do to make it better...
Next time I know what not to do.
Next time I know what not to do.
imho S4 has --queue set to 8192
Jump to: