Topic: Bringing ByteCoin Back to Life!( Update! Possible Fork) (Read 1691 times)
thanks for the information!
I tried a lot of different values last night. I went as high as /600000+4
What I am seeing is a very strong difference in behavior on the eligius stratum pool for bitcoin, and your p2pool for bytecoin.
I was pointing about 80 GH/s to your pool, and the statistics showed a trivial bump from 10 GH/s.
I got a payout of about 0.7 bytecoin. In the same time I would have gotten about 0.5 BTC.
It is not ready for ASICs at this time. When you run the calculations on how long it will take to mine to the 20160 block boundary at the current rate, the coin is not really useful for payments. The choices I see are to go back to a block in may and fork the blockchain, and remove the blocks by the dude who raised the difficulty, or to make the miners ASIC friendly.
P2Pool does not have a good reputation among the Avalon owners. Eliopool does. I do have a virtual machine installation of eloipool that does work with bitcoin. It gives some sort of error with the original bytecoin client and does not mine. I was not able to track it down when I had an Avalon to point at it. That is unfortunate.
I plan to package the virtual machine with eloipool so that anyone may download it and start it up.
Firstly thank you very much for your testing and report. I am very sorry it is currently not able to handle the load applied by Avalons.
I spent some time reading up on Eliopool last night, and I believe instead of furthering development on my p2pool I will begin work on a fresh BTE pool with that configuration. Likely this will take me some time, but rest assured I will update here and perhaps also PM you prior to going public for some further testing if you are interested.
Thank you again for your time ProfMac, I very much appreciate your feedback.
if you do that feel free to email me a link ill work on modifying it for bytecoin and once work it send it back around and also open up a public pool
anywhere from 20 GH/s to 80 GH/s.
I just restarted with the /50 suffix. How is that number defined?
I don't have a clear answer to that just yet.. I'm reviewing the discussion here:
Edit - top post of that page explains it, and I've actually made a mistake here again.. Let's start you off at /1000+1
https://bitcointalksearch.org/topic/m.816322
I tried a lot of different values last night. I went as high as /600000+4
What I am seeing is a very strong difference in behavior on the eligius stratum pool for bitcoin, and your p2pool for bytecoin.
I was pointing about 80 GH/s to your pool, and the statistics showed a trivial bump from 10 GH/s.
I got a payout of about 0.7 bytecoin. In the same time I would have gotten about 0.5 BTC.
It is not ready for ASICs at this time. When you run the calculations on how long it will take to mine to the 20160 block boundary at the current rate, the coin is not really useful for payments. The choices I see are to go back to a block in may and fork the blockchain, and remove the blocks by the dude who raised the difficulty, or to make the miners ASIC friendly.
P2Pool does not have a good reputation among the Avalon owners. Eliopool does. I do have a virtual machine installation of eloipool that does work with bitcoin. It gives some sort of error with the original bytecoin client and does not mine. I was not able to track it down when I had an Avalon to point at it. That is unfortunate.
I plan to package the virtual machine with eloipool so that anyone may download it and start it up.
anywhere from 20 GH/s to 80 GH/s.
I just restarted with the /50 suffix. How is that number defined?
I don't have a clear answer to that just yet.. I'm reviewing the discussion here:
Edit - top post of that page explains it, and I've actually made a mistake here again.. Let's start you off at /1000+1
https://bitcointalksearch.org/topic/m.816322
Even when I slow it down to 256 MHz instead of 350, and I split the work into three accounts, the Avalon times out every few minutes. The reject ratio is maybe 10,000 times too high.
Can you try this for me?
Configure your username with "/50" following your BTE address? This will assign a higher share value, and should improve the rejects. We may have to try a few different values to see what works best for your hardware.. How many GH are you pointing to the pool?
anywhere from 20 GH/s to 80 GH/s.
I just restarted with the /50 suffix. How is that number defined?
Even when I slow it down to 256 MHz instead of 350, and I split the work into three accounts, the Avalon times out every few minutes. The reject ratio is maybe 10,000 times too high.
Can you try this for me?
Configure your username with "/50" following your BTE address? This will assign a higher share value, and should improve the rejects. We may have to try a few different values to see what works best for your hardware.. How many GH are you pointing to the pool?
Anyone out there able to test my pool with an Avalon?
Pool's been up and stable, averaging around 7-8GH/sec lately. I've run it with GPU's and Asicminer USB's but no full on ASIC's that I am aware of.
Stratum is supported to deal with high hash rates.
Pool site is now available at http://digipool.no-ip.org
Point your miners to 75.156.208.65:6327 with your BTE payout address as username, and password is ignored.
Please let me know if there are any issues with Avalon compatibility.
Pool's been up and stable, averaging around 7-8GH/sec lately. I've run it with GPU's and Asicminer USB's but no full on ASIC's that I am aware of.
Stratum is supported to deal with high hash rates.
Pool site is now available at http://digipool.no-ip.org
Point your miners to 75.156.208.65:6327 with your BTE payout address as username, and password is ignored.
Please let me know if there are any issues with Avalon compatibility.
I am pointing an Avalon there, it reports as alive.
my web browser doesn't see 'http://digipool.no-ip.com'
Are there any real-time statistics
Hey sorry, I put .com instead of .org in that post.. Correcting it now. Try here:
http://digipool.no-ip.org
And yes, there is currently a simple set of real time stats on the pools website.
Even when I slow it down to 256 MHz instead of 350, and I split the work into three accounts, the Avalon times out every few minutes. The reject ratio is maybe 10,000 times too high.
Anyone out there able to test my pool with an Avalon?
Pool's been up and stable, averaging around 7-8GH/sec lately. I've run it with GPU's and Asicminer USB's but no full on ASIC's that I am aware of.
Stratum is supported to deal with high hash rates.
Pool site is now available at http://digipool.no-ip.org
Point your miners to 75.156.208.65:6327 with your BTE payout address as username, and password is ignored.
Please let me know if there are any issues with Avalon compatibility.
Pool's been up and stable, averaging around 7-8GH/sec lately. I've run it with GPU's and Asicminer USB's but no full on ASIC's that I am aware of.
Stratum is supported to deal with high hash rates.
Pool site is now available at http://digipool.no-ip.org
Point your miners to 75.156.208.65:6327 with your BTE payout address as username, and password is ignored.
Please let me know if there are any issues with Avalon compatibility.
I am pointing an Avalon there, it reports as alive.
my web browser doesn't see 'http://digipool.no-ip.com'
Are there any real-time statistics
Hey sorry, I put .com instead of .org in that post.. Correcting it now. Try here:
http://digipool.no-ip.org
And yes, there is currently a simple set of real time stats on the pools website.
I have about 1 reject for every 300 accepts in bitcoin with an Avalon.
I have about 100 rejects for every 1 accept with your pool. The avalon restarts frequently. I slowed the clock from 350 MHz to 282 MHz to try for a better accept ratio. It did not help. Next, I am trying to send to 3 different accounts, instead of only 1.
Ok, I'll keep a close eye on it here for the next little while.. not too sure what's causing your high rejected rate at this point.
Anyone out there able to test my pool with an Avalon?
Pool's been up and stable, averaging around 7-8GH/sec lately. I've run it with GPU's and Asicminer USB's but no full on ASIC's that I am aware of.
Stratum is supported to deal with high hash rates.
Pool site is now available at http://digipool.no-ip.com
Point your miners to 75.156.208.65:6327 with your BTE payout address as username, and password is ignored.
Please let me know if there are any issues with Avalon compatibility.
Pool's been up and stable, averaging around 7-8GH/sec lately. I've run it with GPU's and Asicminer USB's but no full on ASIC's that I am aware of.
Stratum is supported to deal with high hash rates.
Pool site is now available at http://digipool.no-ip.com
Point your miners to 75.156.208.65:6327 with your BTE payout address as username, and password is ignored.
Please let me know if there are any issues with Avalon compatibility.
I am pointing an Avalon there, it reports as alive.
my web browser doesn't see 'http://digipool.no-ip.com'
Are there any real-time statistics
I have about 1 reject for every 300 accepts in bitcoin with an Avalon.
I have about 100 rejects for every 1 accept with your pool. The avalon restarts frequently. I slowed the clock from 350 MHz to 282 MHz to try for a better accept ratio. It did not help. Next, I am trying to send to 3 different accounts, instead of only 1.
Anyone out there able to test my pool with an Avalon?
Pool's been up and stable for nearly 4 days, averaging around 7-8GH/sec lately. I've run it with GPU's and Asicminer USB's but no full on ASIC's that I am aware of.
Stratum is supported to deal with high hash rates. PPLNS payout system. Running the non merged-mining Bytecoin 0.8.1 daemon for now.
Pool site is now available at http://digipool.no-ip.org
Point your miners to 75.156.208.65:6327 with your BTE payout address as username, and password is ignored.
Please let me know if there are any issues with Avalon compatibility.
Pool's been up and stable for nearly 4 days, averaging around 7-8GH/sec lately. I've run it with GPU's and Asicminer USB's but no full on ASIC's that I am aware of.
Stratum is supported to deal with high hash rates. PPLNS payout system. Running the non merged-mining Bytecoin 0.8.1 daemon for now.
Pool site is now available at http://digipool.no-ip.org
Point your miners to 75.156.208.65:6327 with your BTE payout address as username, and password is ignored.
Please let me know if there are any issues with Avalon compatibility.
I have eloipool working on my server. It is configured for bitcoin, and works with an Avalon.
I am having some trouble having it connect to bytecoin-qt. It connects, but complains. There are probably some constants that are not correct, such as the network id.
I am having some trouble having it connect to bytecoin-qt. It connects, but complains. There are probably some constants that are not correct, such as the network id.
dont make one yet, ill make it when we get the mandator update out. Im also buying a domain for the site
KK, ill make an official relaunch thread here now with your pool as the first. Ill link it up here when its done.
ill chip in when ive got this one done. I had a pool up for days profmac there was 1 miner from what i could tell. Anyways if all goes well and i manage to get the merged mining patch applied then we might be able to have a pushpool/stratum based pool
I want to use your pool, but I cant connect to it 
ill chip in when ive got this one done. I had a pool up for days profmac there was 1 miner from what i could tell. Anyways if all goes well and i manage to get the merged mining patch applied then we might be able to have a pushpool/stratum based pool
I do have a suggestion, you need to think of more features and usability for eg like that of namecoin or devcoin if you are to succeed in SHA-256 dominated by Bitcoin nearly totally.
Working on a coin right now that is sha based, and will need a merge mine patch from the start in order to succeed IMO. Anybody wants to chip in let me know.
The Avalon community is still having trouble with P2Pool.
Not much, we've added new checkpoints to the client it seems to have been a false alarm. We will be pushing out a mandatoru update in an hour or so
Jump to: