Topic: P2Pool Detailed Settings for Altcoins - page 2. (Read 12917 times)

I think that it hurts the nodes that don't have it vs the ones that do?

What's the purpose/advantage of removing the block punishing code? That's an area I've never looked at and am clueless about.

In ravs repo it does this with the following:


Same result?

Separated CHAIN_LENGTH and REAL_CHAIN_LENGTH into two different sections and expanded on the explanation.

Hey i made new altcoin and i want to run a p2pool with it.

Source for coin : http://github.com/skatecoin/skatecoin

i set in coin P2Port to: 21607
               RPCport to : 21606
Now i download p2pool-rav and edit p2pool/networks.py and p2pool/bitcoin/networks.py

.skatecoin/src/skatecoin.conf

rpcuser=skatecoinrpc
rpcpassword=my password
listen=1
addnode=91.230.204.187
server=1
daemon=1
rpcallowip=77.45.47.126
rpcallowip=91.230.205.78
rpcport=21606
port=21607
rpcallowip=127.0.0.1
rpcallowip=*.*.*.*



Here is: skatecoin=math.Object(
        PARENT=networks.nets['skatecoin'],
        SHARE_PERIOD=25, # seconds target spacing
        CHAIN_LENGTH=24*60*60//25, # shares
        REAL_CHAIN_LENGTH=24*60*60//25, # shares
        TARGET_LOOKBEHIND=25, # shares coinbase maturity
        SPREAD=20, # blocks
        IDENTIFIER='cacacacae0e0e0ee'.decode('hex'),
        PREFIX='fefeefcf0e0f3434'.decode('hex'),
        P2P_PORT=31606,
        MIN_TARGET=0,
        MAX_TARGET=2**256//2**20 - 1,
        PERSIST=False,
        WORKER_PORT=31707,
   BOOTSTRAP_ADDRS=''.split(' '),
        ANNOUNCE_CHANNEL='#p2pool-alt',
        VERSION_CHECK=lambda v: True,
    ),

AND..


skatecoin=math.Object(
        P2P_PREFIX='fcd9b7dd'.decode('hex'),
        P2P_PORT=21607,
        ADDRESS_VERSION=25,
        RPC_PORT=21606,
        RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            'skatecoinaddress' in (yield bitcoind.rpc_help()) and
            not (yield bitcoind.rpc_getinfo())['testnet']
        )),
        SUBSIDY_FUNC=lambda height: 25*100000000,
        POW_FUNC=lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data)),
        BLOCK_PERIOD=90, # s
        SYMBOL='SK8',
        CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'SkateCoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/SkateCoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.skatecoin'), 'skatecoin.conf'),

        BLOCK_EXPLORER_URL_PREFIX='http://skatechain.info/block/',
        ADDRESS_EXPLORER_URL_PREFIX='http://skatechain.info/address/',
        TX_EXPLORER_URL_PREFIX='http://skatechain.info/tx/',
        SANE_TARGET_RANGE=(2**256//1000000000 - 1, 2**256//1000 - 1),
        DUMB_SCRYPT_DIFF=2**16,
        DUST_THRESHOLD=0.03e8,


Now i run p2pool

python ./p2pool-rav/run_p2pool.py --net skatecoin -a BGysxf56z6cX1e68EoRv8fzwa8J6V1HLoQ -f 1 -w 31707 --give-author 0 --bitcoind-p2p-port 21607 --bitcoind-rpc-port 2106 skatecoinrpc my rpc pass from skatecoin.conf


Output:


2014-03-15 18:55:21.413497 p2pool (version 13.3-247-g2ffa4af-dirty)
2014-03-15 18:55:21.413580
2014-03-15 18:55:21.413636 Testing bitcoind RPC connection to 'http://127.0.0.1:21606/' with username 'skatecoinrpc'...
2014-03-15 18:55:21.416764 >     Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2014-03-15 18:55:22.419917 >     Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2014-03-15 18:55:23.422838 >     Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!


Tell me please what i'm doing wrong?

Oh ok I see, thanks for the explanaion

Are the 2 networks.py files the only to modify to get an alt-coin based on scrypt working on p2pool?

I doesn't really...it produces blocks of only 10,000 DOGE when the SUBSIDY_FUNC is actually used. The blockchain has many examples of this happening. Funny thing is others have used that same value for other coins that have random block rewards. I was staging a protest by not running a DOGE node for a while but finally gave in  

Fortunately changing SUBIDY_FUNC is not a value that requires a new fork of the coins p2pool sharechain so it can be done node by node whenever they like. I think the DGB p2pool started a new fork (changing ident/prefix) not knowing this 

Yeah I saw that for dgb, I've set up a pool with the subsidy function from the py_module made by chaeplin. Sounds promising for other alts

But if you look at dogecoin in networks.py from Rav3nPL github the subsidy function is: SUBSIDY_FUNC=lambda height: 10000*100000000. How can it works?

I've try but it dont work...
But there must be a chance to make it there are many p2pools for so much coins. 

Its not the PREFIX i've test it on an other coin, i search the point...

There is a promising new pull request that takes the subsidy function out into a 'module' to return a value. Have been meaning to dig into it as a solution not only for DOGE, etc. but also for WDC and it's decreasing reward.

Thanks for this thread! Very helpful but how can you configure a coin with random block reward? I saw on Rav3nPL github settings for dogecoin for example but there's nothing particular, I wonder how it works.

Hi, i try and try but it don't work.

I do all like in the "tutorial" but i think the identifier and prefix is more...
If i change the identifier of an existing coin twisted fall in a loop.
And i try to add a simple coin 4 test =>

2014-03-06 21:06:47.817990     Current block hash: 1f08c0cb6ff064bf911b3e73756bc553cacb166dbd4552d399ed6c2cf4dd30c8
2014-03-06 21:06:47.818232     Current block height: 74250
2014-03-06 21:06:47.818441
2014-03-06 21:06:47.818728 Testing bitcoind P2P connection to '127.0.0.1:11656'...
2014-03-06 21:06:52.819332     ...taking a while. Common reasons for this include all of bitcoind's connection slots being used...

and this is on every coins i try

in /bitcoin
and:
in the /p2pool folder
any idea???
chain length and so not editet because try for run only

thanks 4 help

the maximum custom difficulty you can set

hmm, nm, i'm not 100% sure about that actually, would have to look at the source again.   i think that's what it is, though.

btw, for any coin with, say, block times of 2 or 3 minutes or less, you should remove the following in data.py:

if best is not None:
            best_share = self.items[best]
            punish, punish_reason = best_share.should_punish_reason(previous_block, bits, self, known_txs)
            if punish > 0:
                print 'Punishing share for %r! Jumping from %s to %s!' % (punish_reason, format_hash(best), format_hash(best_share.previous_hash))
                best = best_share.previous_hash

...  first off, these blocks are too fast to have that anyway.  not to mention that the vast majority of the time this will be beneficial to your node.  if you build off of that old valid *share that's just getting punished because of a new block, all the other clients will follow your chain (as it'll be the longest).  this way you don't end up making a share some 3 seconds later and have some slow (or modified, heh heh) node build off the original share

Great resource, will be using this to get P2Pools running for some of the newer coins

What is MAX_TARGET?  I've noticed it's different for various coins but not sure how it's computed.

Assuming Novacoin is POW/POS then yes...work off of that one. I have no experience with POW/POS coins and P2Pool.

I want to work on some coins with POW/POS - is it best to use your repo - or use the one developed for NVC?

Added comments to p2pool/bitcoin/networks.py in SUBSIDY_FUNC and DUST_THRESHOLD sections.

Added coin examples to p2pool/networks.py in the SPREAD section.

Added how to generate unique values for IDENTIFIER and PREFIX in p2pool/networks.py.

Updated RPC_CHECK= ... 'litecoinaddress' to also include:
You can also find this in rpcdump.cpp after "dumpprivkey <"

Thanks deeppurple72