7
The answer is hidden in this forum post here.
"You have the same problem that is common in P2Pool threads, your miner is (relatively) slow compared to the size of the pool, as such you are not solving the required 1 P2Pool share every 24 hours (not the work your miner is submitting). You will get paid when your miner solves a share with a difficulty ...
5
Broadly speaking, there are two ways of paying pool miners. The first way is to have a wallet and send payments to miners through that when they ask for them.
The second way, which both eligius.st and p2pool use, is to keep track of how many shares people get, and set the coinbase transaction to pay the block reward directly to them once a block is found. ...
4
Many of these are irrational, but this is the summation of feelings from the P2Pool thread on Bitcointalk. P2Pool would be preferable for decentralization, but without a larger share of the global hashrate it seems doomed to obscurity.
P2Pool has high latency, high variance payouts. You get paid as much on average as any other pool, but people generally ...
4
According to Greg Maxwell:
4.14kB/sec in, 10.7kb/s out; averaged over the last 30 days. 38GB in transfer total.
Significantly less than the full node that goes with it... p2pool used to be fairly large relative to the node; but greater amounts of load on the Bitcoin network have shifted the balance.
3
Many exchanges don't have a fixed deposit address for each client.
This means that when you want to make a deposit, it will give you an address and it will log that you are depositing to it. However, when they don't receive anything on the address, the address expires and might be reused for another client.
So when you use the address for mining, it's ...
3
Yes, the failover setting will tell cgminer to mine on a secondary pool when the first pool is unavailable.
Run cgminer with the following:
cgminer.exe --scrypt -o http://p2pool.org:9327 -u username -p password
--failover-only -o http://backuppool.org -u username -p password
This example mines LTC at p2pool and will mine at another pool of your ...
3
P2Pool allows individual miners to band together and find blocks with the reward being shared directly with the miners who participated in finding the block. If you didn't contribute a pool share during a round, you wouldn't receive a payment for a block found by the round. The pool has a lower difficulty than the network but greater than an individual ...
3
The disadvantage of merged mining is the additional coin daemons you have to run in the background. They all use disk space, memory, cpu cycles and bandwidth. A more annoying issue is that most of them are no longer maintained and have bugs. You may find that they crash frequently - at least namecoind does.
3
This looks like plain old bad luck.
P2pool is a small pool and 3 weeks is a short time. With current hashpower at pools this is like measuring BTCGuild for less than 12 hours. BTCGuild can have bad luck for 12 hours, and P2pool can have bad luck for 3 weeks.
That said, all pools underperform on average when compared to a simple expected income. That's ...
3
BitPenny seems to be half the solution - it has centralized control, but its clients can verify it behaves nicely in some sense. But it still has central management. A 51% pool can pull off subtle attacks that aren't prevented by BitPenny. For example, it can prune competitors' blocks, which is not always detectable due to the network latency. It can also ...
3
There are several methods for a bitcoin client to find other nodes.
First of all they save a list of nodes from previous connections.
Of course this only works when they don't connect the first time.
If a client has no IPs stored it falls back to DNS-Seeds:
Bitcoin looks up the IP Addresses of several host names and adds those to the list of potential ...
3
Dead On Arrival. The term is referring to about valid shares your miner discovers that were found too late to be included in the P2Pool internal block chain and therefor aren't paid to the miner. Counter intuitively a DOA share can still be a valid Bitcoin block.
3
You can restart p2pool at any time without losing your shares, because your shares are recorded in p2pool's share chain and permanently associated with your payout address.
From the wiki:
Whenever a peer announces a new share found (new block in the P2Pool block chain), it is received by the other peers, and the other peers verify that this block ...
3
The pool calculates your hash performance from the number of shares that your miner produces. With so little hashing power, it's likely that your miner did not generate a single share, so to the pool it's indistinguishable from doing no work at all.
2
with p2pool at least for the coins are 'merged' mining you cannot reconfigure them to go to any other account except for the default account of that wallet. However you may be able to work around this in one of the following ways depending on your coding ability.
Monitor P2Pool logs and trigger script
Watch the p2pool logs and when a block is found trigger ...
2
Running a public pool comes with the obligation to understand the underlying asset.
Rublik seems to have own proprietary software.
To run a public pool you at least need the following:
Knowledge of linux system administration/security.
A dedicated server.
A coder to write/edit a frontend, reward structure and payout process.
Of course the pool software.
...
2
2013-07-09 00:46:43.467000 Local: 0H/s in last 0.0 seconds Local dead
on arrival: ??? Expected time to share: ???
There is no miner attached to the pool, "0H/s" means zero hashes per second. And since no hashing is being performed the dead on arrival and time to share cannot be calculated, and thus are unknown.
2013-07-09 00:46:43.468000 Shares: 0 (...
2
I am now using cgminer 3.4.2 (Ubuntu 12.04LTS) as it is much more stable than bfgminer and all the bugs in cgminer have been worked out (it also supports hot plugging)
The best way is to compile cgminer from git direct. There is some dependency on usbdev1 that needs to be compiled into cgminer.
Install the dependencies using apt-get (including all the ...
2
I think I figured it out. "curl" doesn't add the "Content-Type" header, which seems important to the pool when parsing the JSON body. Adding that header fixed it.
So, a working curl command would be:
curl -H "Content-Type: application/json" -u [Wallet ID:gibbrish] -d '{"id": 0, "method": "getblocktemplate", "params": [{"capabilities": ["coinbasetxn", "...
2
You won't see a value there until you mine a share, so seeing a ??? is normal for the moment. The efficiency is a measure of how many shares have been counted in the share chain verses the ones you have found.
At 2GH/s you should be expecting to see a share soon, given an average of 2 days 8 hours to find a share at 2GH/s at difficulty 88800 (the current ...
2
You can use a local node with no issue. The p2pool instance will eventually increase the difficulty of the shares it asks of the miner if it is getting too many of them. 99% of those "accepted" shares are simply faked to keep the mining client happy anyway, the current share difficulty of the p2pool network is over 500k.
2
P2Pool works differently from most mining systems - it aims to have a completed "mini-block" about every 10 seconds, so latency of the p2pool hosting server is critical - milliseconds count.
So it absolutely must be in a decent datacentre on a high-quality (aka not-cheap oversold contended junk) network, not on your home connection if you expect ever to get ...
2
When p2pool is started with --debug, it submits all shares to the node (dogecoind, bitcoind etc.).
2
Are you aware that there is no 2nd option in your post? :)
Despite that, your second 1. option is better. If connection to the miner is one of the poor quality ones, p2pool will just adjust the share diff accordingly, decreasing the theoretical penalty.
However, if connection from your pool to the Internet is poor, it doesn't matter if you find block or ...
2
You actually don't use the addresses, but the RPC info for the daemons. For example you'd start the pool with the following switches:
python run_p2pool.py --net vertcoin3 --merged http://*RPCuser1*:*LongRPCpass1*@127.0.0.1:6888 --merged http://*RPCuser2*:*LongRPCpass*2@127.0.0.1:7817
You will see "Got new merged mining work!" in console as confirmation.
2
Look at it this way:
Everyone trying to solve a Bitcoin block is actually competing
against everyone else (I win you lose.)
Pools in general are essentially a pack of miners who collectively
agree not to compete with each other, but agree to collectively
compete against everyone else who is not in the pool. Pools grew in
popularity as the difficulty grew ...
2
Are you sure the link you gave is for a P2Pool block? I just found this resource which lists the blocks solved by the P2Pool. This was the top block listed, and it has many outputs in the generation transaction, paying to each of the miners in a pool who contributed to the share chain within the last N blocks (N is some pool-specific number).
1) How does ...
2
The p2pool sharechain and the bitcoin blockchain operate similarly, but independently. I do not believe there is any requirement that a "real" block be accepted into the p2pool sharechain.
What I think you are really concerned about is that the p2pool nodes may see a "real" block and not do their part to get it into the blockchain so that everyone gets paid....
2
This has nothing to do with any proposed hard forks of Bitcoin.
The hard fork being referred to is internal to P2Pool, and has already happened.
P2Pool has something called a sharechain is parallel to Bitcoins blockchain, only using a 30 second block time rather than a 600 second block time. It is internally used for tracking mining progress in the pool, ...
2
So I found the reason behind the block downloading issue.
I had forgot to point to the block's data dir when running bitcoind. So instead of utilizing the block downloaded from the GUI it was downloading an entirely new block and using that one instead.
Only top voted, non community-wiki answers of a minimum length are eligible
