Author

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 149. (Read 2591920 times)

sr. member
Activity: 266
Merit: 250
If that is the situation what will stop the node owner from running his node with 100% fees and keep all coin?

What's to stop any pool doing that?

A miner can find out what fees a node is charging by adding "/fee" to end of the node address (most nodes charge 0 fees).

If you're thinking of starting up a node (preferred), or are interested in mining a p2pool node, have a read of the p2pool wiki & through this thread -you'll find answers to all your questions  Wink
sr. member
Activity: 357
Merit: 250
As I tried to have clarified in this seperate topic:

https://bitcointalksearch.org/topic/blockswarm-protocol-proposition-solo-mining-full-node-cooperative-1077798

I thought that all nodes are working on their own version of the next block, with a common coinbase transaction (based on the share chain). Thus, participating in p2pool is more akin to a mining cooperative than a conventional pool, such that in p2pool a bunch of independent full nodes (ledger + hashing power) are working together but independently on unique nodes, whereas in a conventional pool, everyone is working to hash on one node (so miners are really just submitting hash, not creating their own blocks).

So, they're not *really* working on the same block in the sense that my p2pool node could include a different bunch of transactions than yours (depending on my fee levels etc), but they *are* working on the same block in the sense that our coinbase transaction is common and, more or less, the block is pulling from the same mempool, so the transactions will be similar.

From what i understand that is the node that submit the right share will take the fees .

If that is the situation what will stop the node owner from running his node with 100% fees and keep all coin?
legendary
Activity: 1260
Merit: 1008
quotes kinda hacked for clarification
question

2) Does all nodes working on the same block ? and how they share between nodes?

Answer

2) yes and P2P divide work in shared jobs (that why P2Pool have his sidechain with his shares)

( snip )
(snip)

As I tried to have clarified in this seperate topic:

https://bitcointalksearch.org/topic/blockswarm-protocol-proposition-solo-mining-full-node-cooperative-1077798

I thought that all nodes are working on their own version of the next block, with a common coinbase transaction (based on the share chain). Thus, participating in p2pool is more akin to a mining cooperative than a conventional pool, such that in p2pool a bunch of independent full nodes (ledger + hashing power) are working together but independently on unique nodes, whereas in a conventional pool, everyone is working to hash on one node (so miners are really just submitting hash, not creating their own blocks).

So, they're not *really* working on the same block in the sense that my p2pool node could include a different bunch of transactions than yours (depending on my fee levels etc), but they *are* working on the same block in the sense that our coinbase transaction is common and, more or less, the block is pulling from the same mempool, so the transactions will be similar.
sr. member
Activity: 357
Merit: 250
sr. member
Activity: 266
Merit: 250

Is this correct.

If this is correct then this is will be a major concern about p2pool.

Thank you

No, It's not correct  Wink
sr. member
Activity: 357
Merit: 250
1) the reward, not the shares ...

2) yes and P2P divide work in shared jobs (that why P2Pool have his sidechain with his shares)

3) P2Pool system with sidechain shares (if you don't work in the sidechain, you don't have reward)

4) Yes, because the sidechain of shared work contain somes jobs already done by your miner (jobs are associated at bitcoin receive adress).

5) Yes, but it's automated by P2Pool system (not by the admin. of node).

6) launch p2pool command with ? (or help) to view ALL the command available to set a node for miners.

Thanks for clarification .

I have one more question with one major concern about p2pool.

Let us say one farm has 1 PH miners.

When that farm pointed to a p2pool he will have his revenue according to his hash power.

Let us assume that farm run his own p2pool node locally .

let us also assume that the total hash power of p2pool became 4 PH after that farm pointed it is miners to p2pool .

The chance for that farm to submit the right share for blocked mined by p2pool will be about 25% , right?

So, what if the farm owner run his own local node by choose to give his local node 100% fees , this mean what ever block mined by other p2pool nodes he will get 25% of the revenue and he will keep 100% of the coins mined by his node because he run it node with 100% fees.

Is this correct.

If this is correct then this is will be a major concern about p2pool.

Thank you
legendary
Activity: 1512
Merit: 1012
1) the reward, not the shares ...

2) yes and P2P divide work in shared jobs (that why P2Pool have his sidechain with his shares)

3) P2Pool system with sidechain shares (if you don't work in the sidechain, you don't have reward)

4) Yes, because the sidechain of shared work contain somes jobs already done by your miner (jobs are associated at bitcoin receive adress).

5) Yes, but it's automated by P2Pool system (not by the admin. of node).

6) launch p2pool command with -h to view ALL the command available to set a node for miners.


Code:
>run_p2pool -h

usage: run_p2pool [-h] [--version]
                  [--net {bitcoin,fastcoin,litecoin,terracoin}] [--testnet]
                  [--debug] [-a ADDRESS] [-i NUMADDRESSES] [-t TIMEADDRESSES]
                  [--datadir DATADIR] [--logfile LOGFILE]
                  [--merged MERGED_URLS] [--give-author DONATION_PERCENTAGE]
                  [--iocp] [--irc-announce] [--no-bugreport]
                  [--p2pool-port PORT] [-n ADDR[:PORT]] [--disable-upnp]
                  [--max-conns CONNS] [--outgoing-conns CONNS]
                  [--external-ip ADDR[:PORT]] [--disable-advertise]
                  [-w PORT or ADDR:PORT] [-f FEE_PERCENTAGE]
                  [--bitcoind-config-path BITCOIND_CONFIG_PATH]
                  [--bitcoind-address BITCOIND_ADDRESS]
                  [--bitcoind-rpc-port BITCOIND_RPC_PORT] [--bitcoind-rpc-ssl]
                  [--bitcoind-p2p-port BITCOIND_P2P_PORT]
                  [BITCOIND_RPCUSERPASS [BITCOIND_RPCUSERPASS ...]]

p2pool (version 14.0)

optional arguments:
  -h, --help            show this help message and exit
  --version             show program's version number and exit
  --net {bitcoin,fastcoin,litecoin,terracoin}
                        use specified network (default: bitcoin)
  --testnet             use the network's testnet
  --debug               enable debugging mode
  -a ADDRESS, --address ADDRESS
                        generate payouts to this address (default:                         requested from bitcoind>), or (dynamic)
  -i NUMADDRESSES, --numaddresses NUMADDRESSES
                        number of bitcoin auto-generated addresses to maintain
                        for getwork dynamic address allocation
  -t TIMEADDRESSES, --timeaddresses TIMEADDRESSES
                        seconds between acquisition of new address and removal
                        of single old (default: 2 days or 172800s)
  --datadir DATADIR     store data in this directory (default:                         run_p2pool.py is in>/data)
  --logfile LOGFILE     log to this file (default: data//log)
  --merged MERGED_URLS  call getauxblock on this url to get work for merged
                        mining (example:
                        http://ncuser:[email protected]:10332/)
  --give-author DONATION_PERCENTAGE
                        donate this percentage of work towards the development
                        of p2pool (default: 1.0)
  --iocp                use Windows IOCP API in order to avoid errors due to
                        large number of sockets being open
  --irc-announce        announce any blocks found on
                        irc://irc.freenode.net/#p2pool
  --no-bugreport        disable submitting caught exceptions to the author
  --disable-upnp        don't attempt to use UPnP to forward p2pool's P2P port
                        from the Internet to this computer
  --disable-advertise   don't advertise local IP address as being available
                        for incoming connections. useful for running a dark
                        node, along with multiple -n ADDR's and --outgoing-
                        conns 0

p2pool interface:
  --p2pool-port PORT    use port PORT to listen for connections (forward this
                        port from your router!) (default: bitcoin:9333,
                        fastcoin:23660, litecoin:9338, terracoin:9323)
  -n ADDR[:PORT], --p2pool-node ADDR[:PORT]
                        connect to existing p2pool node at ADDR listening on
                        port PORT (defaults to default p2pool P2P port) in
                        addition to builtin addresses
  --max-conns CONNS     maximum incoming connections (default: 40)
  --outgoing-conns CONNS
                        outgoing connections (default: 6)
  --external-ip ADDR[:PORT]
                        specify your own public IP address instead of asking
                        peers to discover it, useful for running dual WAN or
                        asymmetric routing

worker interface:
  -w PORT or ADDR:PORT, --worker-port PORT or ADDR:PORT
                        listen on PORT on interface with ADDR for RPC
                        connections from miners (default: all interfaces,
                        bitcoin:9332, fastcoin:5150, litecoin:9327,
                        terracoin:9322)
  -f FEE_PERCENTAGE, --fee FEE_PERCENTAGE
                        charge workers mining to their own bitcoin address (by
                        setting their miner's username to a bitcoin address)
                        this percentage fee to mine on your p2pool instance.
                        Amount displayed at http://127.0.0.1:WORKER_PORT/fee
                        (default: 0)

bitcoind interface:
  --bitcoind-config-path BITCOIND_CONFIG_PATH
                        custom configuration file path (when bitcoind -conf
                        option used)
  --bitcoind-address BITCOIND_ADDRESS
                        connect to this address (default: 127.0.0.1)
  --bitcoind-rpc-port BITCOIND_RPC_PORT
                        connect to JSON-RPC interface at this port (default:
                        bitcoin:8332, fastcoin:9527, litecoin:9332,
                        terracoin:13332                         not provided>)
  --bitcoind-rpc-ssl    connect to JSON-RPC interface using SSL
  --bitcoind-p2p-port BITCOIND_P2P_PORT
                        connect to P2P interface at this port (default:
                        bitcoin:8333, fastcoin:9526, litecoin:9333,
                        terracoin:13333                         not provided>)
  BITCOIND_RPCUSERPASS  bitcoind RPC interface username, then password, space-
                        separated (only one being provided will cause the
                        username to default to being empty, and none will
                        cause P2Pool to read them from bitcoin.conf)


sr. member
Activity: 357
Merit: 250
Hello:

I have a few questions about p2pool:

1) When a block found the share will be splitted between all node on all p2pool nodes. is this correct?

2) Does all nodes working on the same block ? and how they share between nodes?

3) Which node responsible on how to calculate every miner share on all nodes?

4) Let say a work on node for a day and left p2pool and after 2 days the p2pool hit a block can i still get paid for the shares a submit before 2 days from hitting a block or do i need to be active miner when the block hit?

5) If a node submit the right share and p2pool hit a block and that node have a fees of 1% does the node have it is fees first the the rest splatted on the other miners on every node?

6) when we run the p2pool what is the code to determine the node fees?

Thank you very much.
legendary
Activity: 2576
Merit: 2267
1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

Code:
python ./run_p2pool.py RPC_USER RPC_PASS

RPC user and pass always set, it may work without it on localhost, will give it a try when I get a chance.

Hmm, what do you see when you do a 'ps -ef' ?
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
This errors in log happens when s1 try double spend and send txes that are using used inputs - like message shows.
sr. member
Activity: 266
Merit: 250
legendary
Activity: 1512
Merit: 1012
When market crash (not bitcoin), shit happens on P2Pool (well, no ... it's Bitcoin Core) ...  Grin

Code:
2015-08-24 15:35:51 CreateNewBlock(): total size 749841
2015-08-24 15:36:08 CreateNewBlock(): total size 749924
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:23 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:23 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:25 CreateNewBlock(): total size 749906
2015-08-24 15:36:42 CreateNewBlock(): total size 749906
2015-08-24 15:36:59 CreateNewBlock(): total size 749909
2015-08-24 15:37:16 CreateNewBlock(): total size 749979
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:33 CreateNewBlock(): total size 749983
2015-08-24 15:37:49 CreateNewBlock(): total size 749879
2015-08-24 15:38:06 CreateNewBlock(): total size 749921
2015-08-24 15:38:23 CreateNewBlock(): total size 749904
2015-08-24 15:38:40 CreateNewBlock(): total size 749991
2015-08-24 15:38:58 CreateNewBlock(): total size 749915
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:15 CreateNewBlock(): total size 749965
2015-08-24 15:39:31 CreateNewBlock(): total size 749987
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:48 CreateNewBlock(): total size 749993
2015-08-24 15:40:05 CreateNewBlock(): total size 749859
2015-08-24 15:40:07 UpdateTip: new best=000000000000000002f685ba27822de3e4d6f7c00942534a6830a6192495f020  height=371329  log2_work=83.253971  tx=81009383  date=2015-08-24 15:38:57 progress=0.999999  cache=0.1MiB(0tx)



full member
Activity: 213
Merit: 100
I really wish i could do this without reinstalling bitcoin core over and waiting for the blockchain to download.
I don't know about whatever P2Pool issues you may be facing - but you can install XT over Core and Core over XT and just have them use the existing block chain data files - no need to re-download it all.

That's what I thought too I thought I was going to have a separate icon and I was just eager to try XT. Even though it does use the Core it changes it changes certain Core default values and after reading more about it I'm less opportunistic about XT and if it's going to cause latency issues it could be counter productive. I want to check this out more. Anyone have a link for a front-end with all the graphs to measure latency and such....
full member
Activity: 213
Merit: 100
Just checked on my node and I haven't received a share for a while and my payments are going down using XT.
Since I changed nothing else I'm assuming it has something  to do with the new default settings in XT.
Yea I have to figure out how to revert back now. I really wish i could do this without reinstalling bitcoin core over and waiting for the blockchain to download.


could be the sudden BIG hashrate that showed up snatching some shares & shares do expire in p2p after some time.

when hashrate goes up, min p2p share difficulty goes up too & it is more difficult to get a share if your hashrate is too low.

maybe you can try to use YOUR_BTC_ADD/1 ... "/1" tells the node to give your miner min p2p share diff instead of high diff but high diff shares is more valuable but min share diff enables you to get more share.

also try to point your miners to the closest node to you as latency plays a BIG role in p2p.

stand to be corrected.

I was considering a the higher hashrate but that doesn't explain why i haven't had a share for 24 hours. The difficulty I use for my miners should be the ok because of past experience. I think that they changed the default blocksize to current max which why it was taking longer to get a share because at first started off great was grabbing shares like normal then I check on it a day later and the orphan rate shot up. The next day the stats haven't changed so I recently restarted it seems to be doing better but I'm keeping an eye on it. You may be right about the latency because the blocksizre increase to the full 1mb is by default on XT but I get anywhere from 100 to 160MB/s which i think is really fast latency shouldn't be an issue unless comcast is fucking something up like they do. Maybe I'm overlooking something else they changed hope a reset is all my miner, node and bitcoin needed.
I did what you said too I let it kick to the backup node and my payout started to go up while I reset XT.

Update: Seems like after restarting things went back to normal.
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
Just checked on my node and I haven't received a share for a while and my payments are going down using XT.
Since I changed nothing else I'm assuming it has something  to do with the new default settings in XT.
Yea I have to figure out how to revert back now. I really wish i could do this without reinstalling bitcoin core over and waiting for the blockchain to download.


could be the sudden BIG hashrate that showed up snatching some shares & shares do expire in p2p after some time.

when hashrate goes up, min p2p share difficulty goes up too & it is more difficult to get a share if your hashrate is too low.

maybe you can try to use YOUR_BTC_ADD/1 ... "/1" tells the node to give your miner min p2p share diff instead of high diff but high diff shares is more valuable but min share diff enables you to get more share.

also try to point your miners to the closest node to you as latency plays a BIG role in p2p.

stand to be corrected.
hero member
Activity: 686
Merit: 500
FUN > ROI
I really wish i could do this without reinstalling bitcoin core over and waiting for the blockchain to download.
I don't know about whatever P2Pool issues you may be facing - but you can install XT over Core and Core over XT and just have them use the existing block chain data files - no need to re-download it all.
full member
Activity: 213
Merit: 100
Just checked on my node and I haven't received a share for a while and my payments are going down using XT.
Since I changed nothing else I'm assuming it has something  to do with the new default settings in XT.
Yea I have to figure out how to revert back now. I really wish i could do this without reinstalling bitcoin core over and waiting for the blockchain to download.


Update: Seems like after restarting things went back to normal.
legendary
Activity: 1258
Merit: 1027
http://p2pool-nodes.info/ is listed on the site but it ain;t working anymore.

looks like the hunt for 3rd block of the day has just begun.

use this : http://nodes.p2pool.co/

This has been updated.
sr. member
Activity: 266
Merit: 250
Has there been any word from forrestv as to weather this new "XT" client is actually compatible with p2pool with it's different block size params?

Forrestv - if you're lurking, it would be interesting to hear your point of view  Wink

If the fork to 8MB blocks happens, P2Pool will require changes to support 8MB blocks and its own fork to get everyone using the changes. That said, it's a ways off and the changes should be pretty straightforward.

Thanks forrestv - good to hear your point of view. Having said that, I am totally opposed to the new Bitcoin XT client for a few reasons, one of which I pointed out on a different thread:  https://bitcointalksearch.org/topic/bip-101-blocks-1157317

ie: Hard coded TOR exit nodes hand picked by "someone" is a massive security danger to anyone using them. I definitely won't be using the XT client.

newbie
Activity: 58
Merit: 0
XT is compatible now. It will not be compatibile after the arranged fork date (January 11th 2016)

The main change is it implements BIP 101, Gavin Andresen's proposal to increase the blocksize limit to 8MB, followed by a doubling of that limit every two years until a final target limit of 8 gigabytes is reached in the year 2033.

Other significant changes are:

  • Longest chain no longer wins, chain validity is determined using checkpoints periodically added by the XT devs to the code
  • Tor nodes are deprioritised from connection as an anti-DOS measure
  • Permitted Tor exit nodes are, at present, hard coded into the XT client

As p2pool miners, I would investigate the implications of the blocksize changes, and also of the changes to the chain consensus rules.


Also be aware: this model of absolute blocksize limits isn't a very good one (it worked well up to now, but it is true that we are beginning to "run out of road" using this paradigm). A dynamic limit of some type is perhaps a better option, but I am also interested to hear any other concepts that haven't yet been given an airing. There is a productive discussion (no, really!) going on in the Development and Technical sub (https://bitcointalksearch.org/topic/bip-106-dynamically-controlled-bitcoin-block-size-max-cap-1154536). Here's what I had to say about this in another thread:

"Is it really such a great plan to make predictions about what technology we'll be running the bitcoin network on, decades into the future? I would argue that as we approach the steeper part of the curve of technological progress, making accurate predictions will become increasingly more difficult. Perhaps it is worth taking an optimistic view of progress when conducting some aspects of long term planning. But when you're designing something vital, prudence and conservatism is a much more appropriate strategy. Only the absolute basics in life are more vital than monetary systems."

Thank you.

The changes to the consensus rules are appalling, as well as some of the other features of Bitcoin XT.
BIP101 may be an answer, but there could be a better solution that we can all stand behind.  We must work to all agree on a plan for the future that scales and doesn't divide us.  A solution that everyone can support will eventually be found.
Jump to: