don't let this one become another MAXCOIN
Its very difficult to beat MAXCOIN level. They're working hard. Maxcoin at least had a working command line wallet. |
|
|
|
wallet doesn't compile. Looks like typo in some hash  I really don't know why people insist in not learning a thing from other failed launches. You could provide a compiled wallet in PW protected zip beforehand. And you could give us some public node IPs to add to our riecoin.conf, so that it will be actually one network... |
|
|
|
erf tamereenslip@rie:~/riecoin/src# riecoind: main.cpp:2895: bool InitBlockIndex(): Assertion `block.hashMerkleRoot == uint256("0xb8fcc5eedac458fe02b8797ceff6c7ba4c05f749ff464b6ebf775e0eab0afa6c")' failed.
There is an updated file that contains the real implementation. Just sync & rebuild. did that and failed |
|
|
|
PS- It'd be nice if anyone else has tested my earlier diff to share feedback on it.
I implemented your patch to work.py for my VTC node at vtc.coinpools.de:9171. Looks good so far. I did some more minor changes to work.py and web.py to get information for the web frontend about network diff, pool diff and share diffs - I was interested to actually see what's going on  You can have a look at vtc.coinpools.de:9171. |
|
|
|
PS- It'd be nice if anyone else has tested my earlier diff to share feedback on it.
I implemented your patch to work.py for my VTC node at vtc.coinpools.de:9171. Looks good so far. One question, I can't find an answer to: where does this 1.67% of pools shares limit come from? This seems reasonable for a big network like p2pool for LTC or BTC, but many altcoins do have 5-10 pool nodes... Shouldn't this limit somehow be related to the pool node count? PS @roy7: sorry for the delay, I managed to miss the followup discussion here |
|
|
|
And please have some respect for the dev. He tried... have some tact for god sakes.
Nice try, indeed  We need public node IPs to add to the dopecoin.conf, so we get one network instead of about a dozen forks... |
|
|
|
|
difficulty adjustment is broken -> FAIL
|
|
|
|
blockchain splits like hell, because we have no reachable public nodes. Feel free to try in your dopecoin.conf |
|
|
|
what public nodes will we have at start? addnode=dopecoinpool.com
not so many... Sure this will work out? |
|
|
|
Does anyone have decent settings for R9 290x with Elpida RAM? I have 3 rigs with 3 cards each and am 'only' getting about 320kh per card
You could try: "intensity" : "13",
"worksize" : "256",
"gpu-threads" : "2",
"thread-concurrency" : "14080",
"shaders" : "2816",
"gpu-engine" : "950",
"gpu-fan" : "0-85",
"gpu-memclock" : "1500",
"gpu-powertune" : "20",
"temp-cutoff" : "92",
"temp-overheat" : "90",
"temp-target" : "78",
"auto-fan" : true,
"expiry" : "0",
"gpu-platform" : "0",
"queue" : "0",
"scrypt-vert" : true,
"temp-hysteresis" : "3",
Yes, thats two threads and a low intensity (generally not recommended). But it works for me with two cards, rock stable, 0 HW errors at a hashrate of 420 Kh/s and WU 385/m per card. Additionally you get a low latency (less rejects). Took me some time to figure out, so if it works for you, I'd appreciate some VTC  Vc3a3qjdSvUov5Ypm9dPFxyh2pbw3wy9NE |
|
|
|
You can lower your share difficulty by appending /diff to your p2pool username. That should generate more shares and more regular payouts, but of course you get paid less per share. I'm trying VTCPayoutAddress+0.001465/0.55 at the moment. I can tell tomorrow, if this makes things better or worse... address/diff won't let you set diff below the minimum share diff for the pool though. It's intended more to raise diff for giant miners than to lower diff, I thought? First, I've to admit that I'm not completely sure about how p2pool handle diffs and so on, just my own code reading + try and error. That said, pool minimum share diff (what you get e.g. with http://vtc.coinpools.de:9171/difficulty) is not what p2pool gives out to your miner as share difficulty (main reason, why the "share difficulty" displayed on the standard web client page is nonsense). p2pool uses a quite complicated algorithm to compute pseudo_share_difficulty (work.py lines 265-) and share_difficulty (data.py lines 111-) specifically for your miner client (see debug.log "New work for worker" entries). IMHO the main problem with this is, that p2pool tries to dish out share difficulties so that it expects no more than one solved share per minute from all connected clients. So as my VTC node has about 6 MH/s local rate at the moment, the log shows a standard share difficulty of 1.39 given to clients. Minimum share difficulty for the pool is 0.063 on the other hand. So it seems perfectly legit to specify a custom share difficulty of 0.55 for my miner. (If you specify it too low, p2pool seems to use the minimum pool difficulty anyway). I can tell tomorrow, if this makes things better or worse...
Did work perfectly for me during the last 12 hours, by the way |
|
|
|
Sadly when we did the first vertcoin nodes, we used spread=3 because we just copied litecoin. It really should have been 12-15... would avoid so much confusion for small miners right now. Doh.
You can lower your share difficulty by appending /diff to your p2pool username. That should generate more shares and more regular payouts, but of course you get paid less per share. I'm trying VTCPayoutAddress+0.001465/0.55 at the moment. I can tell tomorrow, if this makes things better or worse... |
|
|
|
Developers of new alt-coins should also release the right p2pool config immediately when a coin is launched.
This should become a standard practice, so that every p2pool node uses the exact same configuration creating one homogeneous mega pool. I've seen multiple p2pools for the same coin because multiple persons create different configurations. P2pool is pretty useless if the nodes for the same coin do not all act as one.
I like p2pool a lot but I still fail to find correct configurations for new alt-coins.
Yes I agree completely! How can we enforce this? I think https://github.com/Rav3nPL/p2pool-rav.githas the most complete network.py files for most altcoins. So if you want to add a new coin, probably the best way would be to clone that and do a merge request afterwards. That way there won't be 1001 different versions of p2pool on github, each of them working for exactly one altcoin Just my 2 cent. ... and thanks a lot @TVB for the hard facts. |
|
|
|
Searching through this thread, I saw some fairly alarming posts from folks who said mining vertcoin may have caused some damage to their cards. Has anyone else experienced this?
Got that two days ago during trying to tune my 2x R9 290x with vertminer 0.5.3 linux 32-bit. One fan went mad and the card got really hot. Even cold reboot didn't fix it. I finally switched off the whole thing for about 2 minutes and started with safe settings for normal scrypt on my cgminer-kalroth installation. That did the trick, everything back to normal. And vertminer works normal again after that, too. Problem didn't come back so far <knock>. |
|
|
|
Is anyone getting blocks with the cgminer they released? I keep getting rejected blocks. Wondering if I have to force the algorithm to keccak somewhere... but can't seem to find the option.
what cgminer? You need to run it with --keccak. But then it'll do nothing. Here's the github: https://github.com/Max-Coin/cgminerAnyone bothered to read the readme? That version is work in progress, aka does nothing at all. |
|
|
|
-My Windows client doesn't find peers.
Try using onlynet=ipv4
in your config. I think this finally did the trick for me. All these Micro$oft cloud nodes are on IPv6 which just doesn't work, at least from here. |
|
|
|
C:\Program Files (x86)\coins\Maxcoin>maxcoind.exe -rpcpassword=xxx getmininginfo
{
"blocks" : 149,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 128.37905466,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 12836029626,
"pooledtx" : 0,
"testnet" : false
}
12 GH/s aren't CPU only, I'm sure. Seems like this launch goes to the nvidia/cudaminer folks... Too bad I don't have a decent Nvidia GPU myself, but thanks for the entertaining evening anyway  |
|
|
|
on windows use to actually see whats going on. I can't get no single node connection, unfortunately. Anyone has a working node which could take a connection or two? |
|
|
|
Looks like cudaMiner will have some competition at launch, they just posted a cgminer on the maxcoin github.
From their cgminer readme: This is a work-in-progress version of cgminer for MaxCoin, including everything we have done so far. Feel free to continue development and push those changes in order to help create a working fork of cgminer. Doesn't sound like too hard a competition, does it? |
|
|
|
|
Show Posts
