\[ANN\] Community Pay Back P2Pool \[mine-ftc.co.uk\]
-
Payouts are made as blocks are found, this can be very random, there is no minimum payout they are passed directly to your wallet address and show up as mined coins. If you have a look here http://explorer.feathercoin.com/address/6qjeBxfNDA6nUZfruXZksbHk23vgs8sjXv you can see what I mean by random payouts
-
Have a look [url=http://forum.feathercoin.com/index.php/topic,7278.0.html]here[/url] to see where the Pay Back part of this is starting to fit in…
-
Shameless bump ;)
Hoping to get the next bit of this sorted out and with you guys later today
UM
-
and here it is…
-
Uncle_muddy,
Pool and raffle are great! I will redirect my FTC miners to your pool from tonight!
Looking forward catching up at the Oxford blue!
Bye -
Cheers Chirale, will be goof to catch up again :) see you next week
UM
-
Pool has now been upgrade to 0.8.6.2, I need to reinstall the web interface but mining connections are working and payouts are taking place.
UM
-
UM,
Did you modify the feathercoin math object code in p2pool/bitcoin/networks.py and p2pool/networks.py to reflect the hardfork changes?
-
wec,
No I didn’t change anything I just did another pull from git. Can someone tell me what needs to updated please? Just taken a look at the code and there looks to be some form of version checking in there, is this something we can use to our advantage?
VERSION_WARNING=lambda v: 'Upgrade Terracoin to >= 0.8.0.1!' if v < 80001 else None, ), feathercoin=math.Object( PARENT=networks.nets['feathercoin'], SHARE_PERIOD=30, # seconds CHAIN_LENGTH=60*60//10, # shares REAL_CHAIN_LENGTH=60*60//10, # shares TARGET_LOOKBEHIND=200, # shares SPREAD=120, # blocks IDENTIFIER='4665617468657221'.decode('hex'), PREFIX='b131010ba6d4729a'.decode('hex'), P2P_PORT=19339, MIN_TARGET=0, MAX_TARGET=2**256//2**20 - 1, PERSIST=False, WORKER_PORT=19327, BOOTSTRAP_ADDRS='pool.maeh.org pool2.maeh.org'.split(' '), ANNOUNCE_CHANNEL='#p2pool-alt', VERSION_CHECK=lambda v: True, ), -
We (Wellenreiter and I) did a bit of work on this as part of the testing. Spynnaples is now in charge of good Feathercoin p2pool fork.
I’ll contact them and tell them the updates can be ready for the fork. Most of the information automatically adjusted, it might need a couple of tweeks. I do’nt see any point in trying to automate the process sit will be a once only change, we just needs the updated version ready.
Its another reason Pool owners will need more warning.
-
It shouldn’t be a big problem.
In p2pool/bitcoin/networks.py we need to change
SUBSIDY_FUNC=lambda height: 200*100000000 >> (height + 1)//3360000,to
SUBSIDY_FUNC=lambda height: 80*100000000 >> (height + 1)//3360000,and
BLOCK_PERIOD=150, # sto
BLOCK_PERIOD=60, # sAs I’m not very falmiliar with the protocol I don’t know, what the '(height + 1)//3360000 ’ means, so more changes may be needed in that line
-
We could do with knowing for certain, so we can get the guides updated and a few instructions out for those that need to upgrade their p2pool nodes.
