AbiTxGroup
|
|
June 04, 2013, 04:54:49 AM |
|
With the discussion of the p2pools, the one thing that I like a lot is that with pools working together, you can designate one of the other pools as a backup if the current pool you are connected to goes down or has any connection problems. When you move to the backup server, you do not lose any of the past work that your miner(s) have done, you continue as though you were still connected to the first server.
|
|
|
|
CartmanSPC
Legendary
Offline
Activity: 1270
Merit: 1000
|
|
June 04, 2013, 04:57:56 AM |
|
With the discussion of the p2pools, the one thing that I like a lot is that with pools working together, you can designate one of the other pools as a backup if the current pool you are connected to goes down or has any connection problems. When you move to the backup server, you do not lose any of the past work that your miner(s) have done, you continue as though you were still connected to the first server.
Wow, didn't know that. Since PPLNS can take up to 24 hour to reach your full payout amount that is a powerful feature.
|
|
|
|
ofeefee
Legendary
Offline
Activity: 1023
Merit: 1001
Tokenize Fantasy Sports
|
|
June 04, 2013, 06:16:14 AM |
|
What does the .0025 do on this?
YOURDGCADDRESS+0.0025
This requests that the P2Pool send you work to solve at a difficulty of .0025. Optional. Can reduce the number of stales and orphans for your local submissions .0025 is good for a 7970 may want to reduce that to .00125 or lower for a lesser GPU I have 3 7950s on one and a single 7950 on another, what value to optimize it them. I tried letting pool do not but it was disastrous output. I used cart mans numbers and looks like .0029### was good for 1800, and .0007 I think was close for 7950. Can someone let me know what they use?
|
|
|
|
ssshhh
|
|
June 04, 2013, 08:13:56 AM |
|
p2pool\networks.py SPREAD=90, # blocks IDENTIFIER='7696CFD6441FB537'.decode('hex'), PREFIX='4C2530B5ED0E1EB5'.decode('hex'), P2P_PORT=23396, WORKER_PORT=8810
I can see that the published P2Pool code in post #1 has alternate values for the following :- p2pool/network.py SPREAD=72, # blocks IDENTIFIER='a5aed03050126d6d'.decode('hex'), PREFIX='b6c0601991aa19a3'.decode('hex'), P2P_PORT=25396, WORKER_PORT=25397,
Would you be able to let us know why you chose those values? At least that way we can all come to a consensus P2Pool. I chose SPREAD=90 since from research on the forum I found that this is suppose to be based on the block target time of the altcoin. bitcoin SPREAD=3 block every 600 seconds Baseline litecoin SPREAD=12 block every 150 seconds 600/150=4 4x3=12 bbqcoin SPREAD=30 block every 60 seconds 600/60=10 10x3=30 digitalcoin SPREAD=90 block every 20 seconds 600/20=30 30x3=90 Please correct me if this is wrong! IDENTIFIER, PREFIX and P2P_PORT are random but have to match from pool to pool to successfully connect. Again, got this from researching on the forum so please let me know if you find something to the contrary. Also, not sure if my values are valid since I just used random 19 digit numbers and converted them to hex. WORKER_PORT is the port miners will connect to. This can be unique for each pool. Excellent. The question now arises as to how we get all P2Pool ops to use consensus code. I will send a PM to akabane (who has has a P2Pool github link in post #1) to see if he has any additional info on P2Pool configuration requirements. I hope we can all pull this off.
|
|
|
|
CartmanSPC
Legendary
Offline
Activity: 1270
Merit: 1000
|
|
June 04, 2013, 08:20:12 AM |
|
Almost every time I look at the digitalcoin wallet it is stuck re-syncing. Is that a problem? Since I run it 24/7 on a dedicated server it's not easy to know when it's in the re-syncing mode. I have added the nodes listed in the first post but that did not help.
This wallet is used by the pool so if it is causing any delays then that is a concern. Don't actually see that it's causing any problems. Have lost some found blocks to others in the network but don't know if the wallet sync issue is the cause.
Only happening on the DGC wallet.
|
|
|
|
Pointeh
Newbie
Offline
Activity: 50
Merit: 0
|
|
June 04, 2013, 08:28:14 AM |
|
Is it just me or is this coin greatly undervalued?
It seems the market believes it's not just you. check your e-mail please Hey, You can post any issue here or PM me it. That way others can help you too. ok I've been going crazy can anyone help me with the difficulty trying to figure out when the next change will be and what it will be The pool I use had current dif, projected dif and change time on the sidebar - http://dgc.epools.org/
|
|
|
|
ssshhh
|
|
June 04, 2013, 09:06:54 AM |
|
one more quick one, concerning all of the talk about networking the P2Pools... would that help cut down on the amount of "requested work restart"s that i'm getting? cause that seems like it would be good? sounds like having them all talk to each other would up everyone's efficiency? would that result in less orphans or rejects, and result in better overall hashing power? would that change how much rewards people are receiving? or if everyone's efficiency gets upgraded at the same time, would it just mean that the network will be more robust but the rewards would still pretty much remain the same?
I found when I changed the setting on the pool to SPREAD=90 it significantly cut down on Stratum request for work restart. Try dgc.xpool.net:8810 to see if that is the case for you there. Connecting the pools will have them using their hash rates collectively for finding blocks. You will get your portion regardless of the p2pool your on when a block is found. More blocks will be found but your portion of the share will be smaller because of the increased number of miners on various p2pools working together. An example can be seen at ltc.xpool.net:9327 Even though there is only one miner at that "node" with 250 Kh/s he will still get a portion of a found block. The entire pool (collective?) is over 620 Mh/s so he is participating with that hashing power even though the local node is only providing 250 Kh/s of it. If it was not connected the miner would rarely if ever be paid with only 250 Kh/s. Since ltc.xpool.net:9327 is participating with the other p2pools he will get paid regularly. Don't know if that makes sense...it is my understanding of it anyhow Yes. The litecoin P2Pool is a great example. There are plenty of miners out there who would like to participate but due to the lower hash rates they sit on the sidelines and only mine at the inception of a coin. If all P2Pool ops came to a consensus, Digitalcoin P2Pool could expand towards the depth of the Litecoin P2Pool where even the miners with lower hash rate can have a piece of the Digitalcoin future!
|
|
|
|
ssshhh
|
|
June 04, 2013, 09:10:12 AM |
|
To expand on the example of the one miner at the ltc.xpool.net:9327 node you can lookup his payment address in the charts. Then go to the payout section and search for his address. You will see his expected share of the next payout along with everyone else's in the entire 620 Mh/s pool...kinda neat if you think about it.
When you select a p2pool you will want one that is obviously participating with other p2pool to increase the frequency of payments. Selecting a p2pool comes down to finding the one that is "closest" to your miner. By closest I mean has the lowest latency. Also look for a p2pool that has a low number of orphaned shares. I hear that dead shares don't matter much. You want to be on a p2pool that is reliable (don't go with the hours in node up time section as that resets if the node has to be momentarily restarted..check the graphs for big lapses in data).
I dont want to come off as an authority on any of this stuff though..it is just my understanding from researching the board.
Your input has great value. I consider myself a newbie to P2Pool but I can see the potential of Digitalcoin and I can see what a great help a consensus P2Pool would be for Digitalcoin. I will step back into the background if we can pull it off. I am here to learn from the experience of others.
|
|
|
|
Sondey10mg
|
|
June 04, 2013, 09:17:22 AM |
|
With a concensus p2p I would mine this coin 24/7
|
*Image Removed* *Image Removed*
|
|
|
karsy
|
|
June 04, 2013, 10:33:54 AM |
|
Anyone know someone who could make a pokergame for this coin?
|
|
|
|
|
r32godzilla
|
|
June 04, 2013, 10:41:48 AM |
|
Yep dgc is performing quite nicely. Steady climb in value on Cryptsy rather than a regular pump and dump like some other alts. Looking forward to Baritus bringing online the dgc advertising platform and his other excellent ideas for dgc. Dgc is really starting to gather some good momentum now.
|
|
|
|
techbytes
Legendary
Offline
Activity: 1694
Merit: 1054
Point. Click. Blockchain
|
|
June 04, 2013, 10:50:54 AM |
|
Yep dgc is performing quite nicely. Steady climb in value on Cryptsy rather than a regular pump and dump like some other alts. Looking forward to Baritus bringing online the dgc advertising platform and his other excellent ideas for dgc. Dgc is really starting to gather some good momentum now.
Yeah, I don't know where they go to discuss but they are cranking out services for the DGC community. This is what I called development. WDC? That's another story. -tb-
|
|
|
|
ssshhh
|
|
June 04, 2013, 11:07:16 AM |
|
I just found another github source for P2Pool which includes a Digitalcoin configuration. https://github.com/novaspirit/p2poolThis one also has alternate values. p2pool/networks.py digital=math.Object( PARENT=networks.nets['digital'], SHARE_PERIOD=30, # seconds target spacing CHAIN_LENGTH=24*60*60//10, # shares REAL_CHAIN_LENGTH=24*60*60//10, # shares TARGET_LOOKBEHIND=200, # shares coinbase maturity SPREAD=30, # blocks IDENTIFIER='be43F6b8c6927210'.decode('hex'), PREFIX='b587193ba6d4749a'.decode('hex'), P2P_PORT=25477, MIN_TARGET=0, MAX_TARGET=2**256//2**20 - 1, PERSIST=True, WORKER_PORT=24397, BOOTSTRAP_ADDRS='p2pool.dsync.net'.split(' '), ANNOUNCE_CHANNEL='#p2pool-alt', VERSION_CHECK=lambda v: True, ),
The SPREAD value of 90 was a result of the research of "CartmanSPC" I chose SPREAD=90 since from research on the forum I found that this is suppose to be based on the block target time of the altcoin.
bitcoin SPREAD=3 block every 600 seconds Baseline litecoin SPREAD=12 block every 150 seconds 600/150=4 4x3=12 bbqcoin SPREAD=30 block every 60 seconds 600/60=10 10x3=30 digitalcoin SPREAD=90 block every 20 seconds 600/20=30 30x3=90
Can all P2Pool ops use this? Or are there any suggestions for alternate values? The IDENTIFER and PREFIX values differ. I will contact the author of P2Pool "forrestv" to see if there is a method for choosing those values. Please help create a consensus P2Pool for Digitalcoin.
|
|
|
|
baritus (OP)
Legendary
Offline
Activity: 966
Merit: 1052
|
|
June 04, 2013, 11:53:42 AM |
|
We need to reach a consensus on the P2pool settings so that we can make a standard.
|
Digitalcoin - Sha256, Scrypt, x11 Mining - Multi-algorithm & One Click Masternodes - Founded in 2013
|
|
|
djslick
Legendary
Offline
Activity: 980
Merit: 1000
|
|
June 04, 2013, 12:15:00 PM |
|
Cartman, you're a champion. totally explained the concept of networked p2Pools, and i agree that it would be beneficial to the average miner and DGC as a whole. I'll definitely check out that pool you linked once i get home to my miner tomarrow. speaking of pool talk, i noticed that http://www.digicoinpool.com/ seems to be well over half of the total network hashrate? as of this posting, the site's header reads: Pool Hashrate: 310.19 MH/s Network Hashrate: 448.26 Mh/s Difficulty: 2.24897441 Pool Miners: 114 Pool Workers: 246 isn't this a bad thing? again i don't know much about this stuff, but i've heard word that 51% of the network can start making like false results or something, and they have enough hashing power to verify the false results so they look real? or something? is DGC less prone to this type of attack? I really don't know why people don't just stick to the p2pools, as i've already enjoyed the regular and fast payouts ticking away on my taskbar, get a warm feeling everytime i see a deposit, like: "i'm working too hard, i gotta sit back and let my cryptocoins work FOR me" heh *edit, the only thing i can think of is that the "h" in Mh or MH mean something different? one's capitalized and the other isn't... i would have thought just the big or small "m" is what would matter with that format.
|
|
|
|
baritus (OP)
Legendary
Offline
Activity: 966
Merit: 1052
|
|
June 04, 2013, 12:21:48 PM Last edit: June 04, 2013, 12:38:26 PM by baritus |
|
There's no concern about a pool having more than half. I have a full explanation in an earlier post answering a similar question.
P2Pool Announcement
To speed things up deliberations, anyone who is interested in joining the P2pool settings decision making process can contact me within the next 2 days to join the panel. The panel will eliminate alternatives until a consensus is reached. At which point, a new fork will be created on Git with the accepted settings that everyone can update to.
P2pool owners: Your success depends on your community. Build it.
|
Digitalcoin - Sha256, Scrypt, x11 Mining - Multi-algorithm & One Click Masternodes - Founded in 2013
|
|
|
mm8000
Newbie
Offline
Activity: 42
Merit: 0
|
|
June 04, 2013, 12:36:49 PM |
|
Cartman, you're a champion. totally explained the concept of networked p2Pools, and i agree that it would be beneficial to the average miner and DGC as a whole. I'll definitely check out that pool you linked once i get home to my miner tomarrow. speaking of pool talk, i noticed that http://www.digicoinpool.com/ seems to be well over half of the total network hashrate? as of this posting, the site's header reads: Pool Hashrate: 310.19 MH/s Network Hashrate: 448.26 Mh/s Difficulty: 2.24897441 Pool Miners: 114 Pool Workers: 246 isn't this a bad thing? again i don't know much about this stuff, but i've heard word that 51% of the network can start making like false results or something, and they have enough hashing power to verify the false results so they look real? or something? is DGC less prone to this type of attack? I really don't know why people don't just stick to the p2pools, as i've already enjoyed the regular and fast payouts ticking away on my taskbar, get a warm feeling everytime i see a deposit, like: "i'm working too hard, i gotta sit back and let my cryptocoins work FOR me" heh *edit, the only thing i can think of is that the "h" in Mh or MH mean something different? one's capitalized and the other isn't... i would have thought just the big or small "m" is what would matter with that format. Yes, it's bad for many reasons. The owner needs to close the signup form. Just think if his pool got attacked or hd crashed..
|
|
|
|
QueenB
Member
Offline
Activity: 70
Merit: 10
|
|
June 04, 2013, 12:38:19 PM |
|
Anyone know someone who could make a pokergame for this coin?
Am working on it....get ready for some demos soon... got a server today, loading the files...
|
|
|
|
fenican
|
|
June 04, 2013, 12:51:49 PM |
|
Changed SPREAD=30 to SPREAD=90 for my pool
Note that this actually created a lot more, not less, Stratum "work restart" requests.
I think what is happening is that the P2Pool targets blocks for about 1/10'th the time as the main network. Hence, if the main network has 20 second block targets the pool now has 2 second block targets
I think we're in uncharted territory with the 20 second blocks not sure anyone has thought through optimal pool settings for a coin that fast. For now I'll stick with the SPREAD 90 and see how well it works
|
|
|
|
|