Question for the devs: Why stick with libdb4.8 when most others are using libdb5.1? Had to compile with the --disable-wallet option since I could not get libdb4.8 to work  |
|
|
|
On a different note: I have noticed that people are still using and mining the old version  Where/how are you tracking this? Would be interesting to see... |
|
|
|
In regard to merge mining (and I apologize if I've missed it in this thread)...how do you pay found merge mined blocks back to your nodes miners? I see that some people manually convert merge mined coins to BTC and then do a "send many" back to p2pool but has anyone figure out something better? Someone forked proxy pool to accept a second coins payment address in the password field but every public site using it has since shut down. I am concerned that it may not be a viable solution. You haven't missed it. There's absolutely no support for it, and in the current state of the code, there's no way to even do it. For example, let's say that I mine on node 1 for some time and find 3 shares. I move onto node 2. I find 5 more shares. I move back to node 1 again, and I find a share that solves a merged coin block. How does the node pay me? What about paying other miners who had previously been on the node, but for whatever reason have since moved off? Besides this, how do you know to which addresses to pay out the coins? There are a lot of changes that would be required to ever be able to handle paying out merged coins to miners in any way. Thanks jonnybravo0311. I had the thought of supporting merge mined coins by having p2pool use additional sharechains (auxShareChain). It would handle payments and combine the hashing power just like the main sharechain. Not a trivial task and beyond my time and skill level. |
|
|
|
|
Going with a multi-algo implementation seems like an overly complicated way to go about attempting to secure the blockchain. I'm not versed in the technical details of how a multi-algo coin functions but if the goal is to secure the blockchain then implementing auxPOW should be considered as an alternative.
DOGE went from having 60 Gh/s to 800 Gh/s after implementing auxPOW. Just realize that any dramatic increase in hashrate will have a similar dramatic increase in difficulty. Also, if miners start to receive DGC essentially for "free" it could cause downward pressure on the price from them dumping a coin (DGC) they don't care about.
|
|
|
|
In regard to merge mining (and I apologize if I've missed it in this thread)...how do you pay found merge mined blocks back to your nodes miners? I see that some people manually convert merge mined coins to BTC and then do a "send many" back to p2pool but has anyone figure out something better? Someone forked proxy pool to accept a second coins payment address in the password field but every public site using it has since shut down. I am concerned that it may not be a viable solution. |
|
|
|
I suspect this merged mining will hurt both Litecoin and Doge. Diff has been driven through the roof on both and profitability seems to be in the toilet.
You're missing the whole point and reason for the merge mining. To make both coins ultra secure so they can push them mainstream starting in a few months. The merged mining will only add more hashrate to LTC from miners who decide to mine LTC and also get DOGE. They (LTC) did not change their coin to support auxPOW so any additional hashrate they get is just former DOGE miners moving over. Miners don't necessarily need to mine LTC to get DOGE though as any POW scrypt coin can be used to get DOGE now. |
|
|
|
Because with AuxPoW, a Doge is tapped into all scrypt hash power.
ALL? Incorrect. Doge is tapped into (sharing) Litecoin's hash network. Just like all the sha256 merged coins are sharing the network with Bitcoin. I believe the AuxPoW fork code allows the sharing of any script coin with a hashrate higher than that of Doge, which at this time is only LTC. Any scrypt POW coin. It does not have to have a higher hash rate. |
|
|
|
Thanks for the explanation.
I wish I could combine multiple auxPOW coins but I thought Doge is still the only auxPOW enabled coin right now or am I miss something?
There are others but I haven't looked into them since it requires you to run their wallet and I have limited resources. |
|
|
|
Merge mining is working with p2pool!
Currently merge mining DOGE with POT, GLC and NYAN. Will soon add DGC, WDC, CRC, CSC, and ANC.
Need to figure out how to payout any found doge blocks to the miners! Let me know if anyone comes up with something.
Going to try using proxypool to handle the autopayout of doge by having miners use their DOGE address as the password but if anyone else has a better way please post!
What, how are you doing that? I thought the only scrypt coins merge mineable right now were doge and LTC. When did all the other coins get the AUXpow merge patch added? How could this news not be all over the place? Can anyone else confirm? Thx LOL, what...you don't believe me Vlad2Vlad?  DOGE will accept any POW scrypt coins as it's AuxPOW. Get the DOGE daemon going and then add --merged http://rpcuser:rpcpassword@127.0.0.1:22555 to the end of your startup script replacing u/p and IP with whatever your using. You can combine multiple auxPOW coins...not just DOGE but I haven't bothered looking into the other ones. You will see something like "Got new merged mining work!" every so often in the console. Limitations: - Only the local node's hashrate is used for finding merge mined coins (DOGE in this case). Not the entire p2pool's hashrate.
- Reward on found merge mined blocks go to the local wallet.
- Have not figured out an easy way to distribute found DOGE blocks to the local nodes workers.
Room for improvement: - Enable the entire p2pool's hashrate to work on merge mined coins or at least combine the nodes that are using merged mined coins.
- Immediate payout on found merged mined coins as cleanly minted coins with no transaction history just like the main coin.
These two item could be accomplished by having an auxP2PoolShareChain for the coins that support auxPOW. It would need to identify the coin and miners working on it as only the workers on nodes with the merged mined coin enabled should get the block reward. Not a trivial task and beyond my time and skill level. |
|
|
|
|
Merge mining is working with p2pool!
Currently merge mining DOGE with POT, GLC and NYAN. Will soon add DGC, WDC, CRC, CSC, and ANC.
Need to figure out how to payout any found doge blocks to the miners! Let me know if anyone comes up with something.
Going to try using proxypool to handle the autopayout of doge by having miners use their DOGE address as the password but if anyone else has a better way please post!
|
|
|
|
I'm in awe of the density and power of the SP30 mine. But really, is that the best you can do with the cables?
Exactly what I was thinking! All that money and that's what they do with cabling? Geesh. |
|
|
|
The problem with mining at ghash.io is they auto sell ANC to BTC or LTC bringing down the price due to sell pressure  The only coins you have to option not to convert are LTC, DOGE, FTC, AUR. |
|
|
|
Found I had to install the 32bit versions as there is no python win32 api wmi wrapper for 64bit and it won't install to the 64bit python dir.
Found this out on a 2008 server so just did plain 32bit python install as per your readme.
You can get the 64 bit version to work but it's more effort than it's worth. I just do 32 bit as well. |
|
|
|
|
Try btc=11 just for kicks...
|
|
|
|
I would think what we would need to make a proxy work is some type of automated escrow. I.E. many small miners mine through a proxy, the proxy tracks the individual miner work and submits the combined work to P2Pool under a single address. A payout threshold would be set (say .005 BTC to start), and the proxy would issue payouts as the individual miner reward crossed the threshold.
That is similar to how this "proxypool" works but it keeps a local DB of the payouts. It also changes the payout method to miners using it to: I am tempted to see if I can get it to work  |
|
|
|
Has anyone looked into using proxypool as a solution for smaller miners? https://github.com/erkmos/proxypoolhttps://github.com/dogestreet/proxypoolproxypool is a pool server that splits work from an upstream pool server and redistributes them to its miners, handling both share submission and sharelogging for it's patrons. It was used for a while on http://doge.st/ with the dogecoin p2pool. I do not know the reasons why they shutdown. I would investigate further but my time is limited :/ |
|
|
|
...
Getting a response from forrestv would be a bit of a milestone in itself......he's not even logged in for over a month.......  Agreed, sent him an email... Hope to hear back but not optimistic  He hangs out on IRC. You might want to try him there. |
|
|
|
|
It appears someone is exploiting a known bug with KGW. Have seen it on multiple other coins and am surprised ANC has escaped it up until now. The solution is to fix KGW with something like Digishield or anything the devs find appropriate.
|
|
|
|
|
Show Posts
