[Dev] Feathercoin - P2Pool-Neoscrypt - Now Available

Wellenreiter

Update:

I restarted the pools at p2pool.neoscrypt.de (46.4.0.101) and pool20.neoscrypt.de (95.85.57.10) from scratch.

Both pools are synced now.

I connected from a third instance to the p2pool cloud and got connected and synced within seconds.

Please try the following:

modify networks.py and extend the bootstrap_addrs line :

BOOTSTRAP_ADDRS=‘atlas.phoenixcoin.org prometheus.phoenixcoin.org p2pool.neoscrypt.de pool20.neoscrypt.de’.split(’ '),
set the Persist entry to ‘True’
delete/move the data directory from the p2pool directory tree
start p2pool without the -n parameter you may have used

I also updated Github to reflect the new networks.py. No other changes in todays commit.

ghostlander

Wellenreiter, is your GitHub code up to date? It produces incorrect targets like before:

[2014-09-14 14:42:38] JSON protocol response:
{
   "result": {
      "midstate": "311837dffa033b15a23fc919c0aed94890a7aa2897e06f3f699feb37f177a055",
      "hash1": "00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000",
      "target": "a6c64b37894160e5d022dbf97e6abc74931804560e2db29defa7c64b37894100",
      "submitold": true,
      "identifier": "0",
      "data": "020000008afe19481a16bcc09a5515e4b3eccaac451f445cbab4dcb469abfc6dddd6f644b1cfefa8c856e823443e1af8f3ec08a82425087720777045f08363a2cb1f34c3277f1554ffff0f1e00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000"
   },
   "error": null,
   "jsonrpc": "2.0",
   "id": 0
}

By the way, midstate and hash1 are deprecated. I’ve removed them already from my P2Pool. data may be reduced to 80 bytes.

ghostlander

One more thing. Your today’s commit added 192.168.0.113 to bootstraps. This is a gray IP of your LAN.

Wellenreiter

Oh sorry,

that one was for testing.

thought, that I removed it.

It’s fixed now.

ghostlander

p2pool-neoscrypt

This is the latest P2Pool with NeoScrypt. Supports Phoenixcoin and Feathercoin. It needs patching in order to provide miners with correct targets, etc.

lizhi

I had updated from wellenreiter01’s code. Now PXC-P2Pool work normal . I can mine blocks. :)

In addition, I think the OpenCL kernel may fix some problems. I had mined pxc in p2pool about 3 hours, No HW error.

Start phoenixcoin daemon :
phoenixcoind -daemon -debug 

Start pxc-p2pool:
python run_p2pool.py --net phoenixcoin  --bitcoind-p2p-port 9555 --bitcoind-rpc-port 9554 p2pool PoAzL52WzHRJovA6kZkptwVTdX9xMxPkwi

Start cgminer.exe with stratum:
cgminer.exe --neoscrypt --worksize 256,256,256 --thread-concurrency 8960,8960,4000 -I 13,13,12 -g 1 -o stratum+tcp://pool.ftc-c.com:11554 -u PfF9PKBjkmz7gFAkA7h6ajY5AHc9B1mijW -p x

lizhi

FTC(testnet)-P2Pool work normal too. :)

ghostlander

Both my or Wellenreiter’s code behaves the same if you start on the PXC testnet with PERSIST=False and no shares in the P2Pool chain. The share difficulty is very low and incorrect. Maybe it becomes correct later when the chain grows up, but it’s better to have it correct right from the start.

darksaber

Looks like mine is working now for PXC. Downloaded the shares right away. You can check out my node here: http://104.131.5.165:10554.

Thanks!

Wellenreiter

Yes, your node is connectred and synced.

I can see it in the peer list od the other nodes

lizhi

My share may be wrong, But I get PXC normal , some hashrate not display in p2pool.

Wellenreiter

did you delete the data directory and restart the pool?

The display of your last but one posts shows also a wrong list of shares found. Compare to the list on p2pool.neoscrypt.de and pool20.neoscrypt.de

It seems your data directory is corupted.

ghostlander

I have launched atlas, prometheus and menoetius again. Getwork and Stratum work fine. They don’t join your existing nodes due to code differences.

ghostlander

My P2Pool source code is ghostlander/p2pool-neoscrypt

I suggest you either to update your nodes or move to a different prefix, because there are share conflicts. My nodes generate shares every 30 seconds to minimise stales, your nodes produce them every 15 seconds.

Wellenreiter

I will move to 30 secs time to share

ghostlander

I will move to 30 secs time to share

Can you connect to my nodes now? I’ve also updated SANE_TARGET_RANGE = (2**256 - 1 >> 30, 2**256 - 1 >> 12), but these are for Getwork. Stratum uses DUMB_SCRYPT_DIFF = 2**16

darksaber

I have tried both new versions (ghostlander’s & wellenreiter’s) and I am back to not being able to download shares again. If I copy my old data directory over I can get it running, though it’s split brained.

ghostlander

I have tried both new versions (ghostlander’s & wellenreiter’s) and I am back to not being able to download shares again. If I copy my old data directory over I can get it running, though it’s split brained.

You need to clean up your data directory first. Make sure you have PERSIST = True set.

darksaber

Yep, id that. PERSIST = True. Here is an exert from the log:

2014-09-18 12:18:39.247856 Loading shares...
2014-09-18 12:18:39.248590     ...done loading 0 shares (0 verified)!
2014-09-18 12:18:39.248912
2014-09-18 12:18:39.249201 Initializing work...
2014-09-18 12:18:39.348426     ...success!
2014-09-18 12:18:39.348967
2014-09-18 12:18:39.349484 Joining P2Pool network using port 10555...
2014-09-18 12:18:39.378120     ...success!
2014-09-18 12:18:39.378794
2014-09-18 12:18:39.380525 Listening for workers on '' port 10554...
2014-09-18 12:18:39.392583     ...success!
2014-09-18 12:18:39.393179
2014-09-18 12:18:39.393579 Started successfully!
2014-09-18 12:18:39.393984 Go to http://127.0.0.1:10554/ to view graphs and statistics!
2014-09-18 12:18:39.394453 Donating 0.0% of work towards the NeoScrypt development :(
2014-09-18 12:18:39.394812
2014-09-18 12:18:39.401381 Outgoing connection to peer 162.217.250.224:10555 established. p2pool version: 1300 '13.4-53-gdd55fa7-dirty'
2014-09-18 12:18:42.395641 P2Pool: 0 shares in chain (0 verified/1 total) Peers: 1 (0 incoming)
2014-09-18 12:18:42.396364  Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-09-18 12:18:44.774816 Incoming connection to peer 95.85.57.10:41458 established. p2pool version: 1300 '13.4-22-g0c7c431-dirty'
2014-09-18 12:18:45.397174 P2Pool: 0 shares in chain (0 verified/3 total) Peers: 2 (1 incoming)
2014-09-18 12:18:45.397358  Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-09-18 12:18:47.727850 Incoming connection to peer 95.133.102.185:55690 established. p2pool version: 1300 '13.4-53-gdd55fa7-dirty'
2014-09-18 12:18:48.397701 P2Pool: 0 shares in chain (0 verified/3 total) Peers: 3 (2 incoming)
2014-09-18 12:18:48.398471  Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-09-18 12:18:48.555249 Outgoing connection to peer 115.28.24.213:11555 established. p2pool version: 1300 '13.4-32-gf3abd63-dirty'
2014-09-18 12:18:50.163271 Outgoing connection to peer 107.161.164.223:10555 established. p2pool version: 1300 '13.4-53-gdd55fa7-dirty'
2014-09-18 12:18:51.399398 P2Pool: 0 shares in chain (0 verified/3 total) Peers: 5 (2 incoming)
2014-09-18 12:18:51.399588  Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-09-18 12:18:52.412369 Incoming connection to peer 46.4.0.101:57470 established. p2pool version: 1300 '5b90f6c'
2014-09-18 12:18:54.399976 P2Pool: 0 shares in chain (0 verified/3 total) Peers: 6 (3 incoming)
2014-09-18 12:18:54.400492  Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-09-18 12:19:00.401199 P2Pool: 0 shares in chain (0 verified/4 total) Peers: 6 (3 incoming)
2014-09-18 12:19:00.401803  Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-09-18 12:19:08.525252 Incoming connection to peer 217.253.113.14:63158 established. p2pool version: 1300 '13.4-31-g47a6475-dirty'
2014-09-18 12:19:09.403070 P2Pool: 0 shares in chain (0 verified/4 total) Peers: 7 (4 incoming)
2014-09-18 12:19:09.403688  Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???

Wellenreiter

@Ghostlander,
The pools can connect now, but no share information is exchanged, so no common cloud is formed.
I think it is due to the different handling of endianess, that is also influencing the communication between the pool nodes.
I see messages like gent_x doesn’t match local gent_x (something like that )