|
Just to add to this excellent post. Besides being by definition completely de-centralized, p2pool also allows you to merge-mine a number of coins. At present, you can merge-mine NMC, IXC, I0C, DVC, FSC, HUC (My apologies if I'm missed any). Other coins have either talked about, or are actively working on supporting merged mining (MZC).
Furthermore, a number of p2pool node operators have committed to donating those proceeds right back into the p2pool. There are even wallet addresses provided by mdude77 to which you can donate coins:
DVC: 1f56VqR9ajX3K42qSaDezvKXFmruSDg1B
IXC: xaNQ54gxowcwHyxqGtFM4vwCfS84V6fmKF
NMC: N1XhWNmvGhFL145zmQGQv7Vug6mThNh1iQ
I0C: jMDtRnMAk2WxaoAw8HUceMaxPPqAuZ8AEN
To prove he's a man of his word, mdude77's node found a block and he donated the proceeds from merge mining to the p2pool miners.
|
|
|
|
Since shares are constantly dropping off the chain, you have to keep finding shares, otherwise as your shares drop off the chain, your payout will also drop? If you have a dry spell your payout will drop, because more shares are dropping off than are being found. Likewise if you have a hot spell your payout will increase as more shares are added than dropped. How do dead and orphaned shares fit into this? Is this a reasonable accurate understanding?  Yes, this is largely correct. Dead/orphan shares can still be valid Bitcoin blocks that pay the pool. The Dead/orphan refers to the share-chain, not the Bitcoin block-chain. Let me expand upon that just a little bit to hopefully help qumqats understand what you mean. Finding shares in p2pool is equivalent to solving a block. Your miners, when they find one, are announcing to the p2pool network that they have found a low enough hash to satisfy requirements and are thus adding a new block to the chain. An orphan share means that somebody else also found a solution that satisfied the requirements and announced their solution to the network. Unfortunately for you, their solution was accepted and added to the chain prior to yours. You're not completely out of luck, though, because your solution might also satisfy the Bitcoin network's requirements. In that case, your orphaned share would solve the BTC block, and everyone gets their share of the reward. Take a look at the following contrived example to see how it might work: You find a share of difficulty 10,000,000,000 Another miner finds a share of difficulty 1,000,000,000 Both of you submit your work. His is accepted as a share and yours becomes orphaned. Yours is, however, accepted by the BTC block chain as a valid solution. The block is added to the chain, 25 BTC are generated and distributed to the miners in p2pool, along with transaction fees from the generated block. Dead shares work similarly, except for the fact that they never make it out of your local environment. Whereas an orphan share means you announced to the p2pool network that you found a solution, a dead share you don't even bother announcing because you have already been informed by the network that the share is invalid (i.e. the block height is lower than the current block being mined). Just like with an orphaned share, your solution might be a valid solution to the BTC network, and if so, it solves the block and everyone gets paid. |
|
|
|
only unfortunate thing is my merged coins do not seem to be paying out to the wallets. I see new work for merged coming in but doesn't seem to be dumping any in the wallets. IT used to work. Any known gotchas that may stop merged coins from paying out?
You have to find shares of high enough difficulty to solve a block of the merged coins. If you happen to find the share that solves the BTC block, then by default you'll also find blocks of every coin you're merge-mining because the BTC hash will satisfy every other one. Effectively you're solo mining the merged coins. Which is why I'm trying to get a movement started for all the p2pool nodes to convert their merged mining proceeds to BTC and share it with the entire pool. That way we're all effectively merge mining together. I took the first step and shared the proceeds from the block I got on my node. M I'm right there with you. I think it's a great idea and hope every p2pool miner who runs a node follows suit. |
|
|
|
only unfortunate thing is my merged coins do not seem to be paying out to the wallets. I see new work for merged coming in but doesn't seem to be dumping any in the wallets. IT used to work. Any known gotchas that may stop merged coins from paying out?
You have to find shares of high enough difficulty to solve a block of the merged coins. If you happen to find the share that solves the BTC block, then by default you'll also find blocks of every coin you're merge-mining because the BTC hash will satisfy every other one. Effectively you're solo mining the merged coins. |
|
|
|
cheers dude i kinda figured it out just need to isolate a few lines of code which are spuriously placed. supposedly in the main.h but missing. found similar code in another file. think what i will do is reverse engineer a coin so take one from ravens source grep all the codes/lines in ravens and take note of the lines there on and which files. maybe just maybe il have a huc and bns p2pool running. just hope i can handle the traffic 8mb ram octocore amd. 75mb tinterwebs. should be plenty right>? RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
(yield check_genesis_block(bitcoind, '000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f')) and
not (yield bitcoind.rpc_getinfo())['testnet'] its that im struggling with mainly lol. and then the algo for it as each one seems fdifferent That is checking to make sure you're actually connecting to the proper daemon on the designated port. So, if you've defined the SpongeBobCoin, you'd do something like this:
RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
'spongebobcoinaddress' in (yield bitcoind.rpc_help()) and
(yield bitcoind.rpc_getinfo())['testnet']
))
Someone more knowledgable than me would be able to help you out further. Regarding your question about HUC and BNS... mdude77 tried to get HUC up and running merge mining with BTC on p2pool, but ended up taking it down because of random disconnects and errors with the coin. He might be able to give you specifics on what the problems were with the setup. I'm not sure if you'd face similar problems just running a standard p2pool node with it, however. |
|
|
|
And another one! 300600. If only my miners weren't acting like they are on strike today and only finding like 7 shares in the past 30 hours... EDIT: squashpile beat me to it  |
|
|
|
|
Which is an accurate assessment of things. P2Pool relayed block 300520, and all addresses that had submitted shares were paid from the 25BTC reward and transaction fees based upon the normal p2pool payout logic. Well, it turns out that block 300520 was also submitted by someone else, and that block made it into the main chain, while the p2pool block did not and became orphaned. Thus the potential double spend.
|
|
|
|
Thanks, I had not seen that before.
No problem. First time it's happened in a while. p2pool.info shows blocks for the past couple months, and this morning's is the only orphan in that time. |
|
|
|
IYFTech, you are correct - regtable69, you need to define the math.Object for your coin in both p2pool/networks.py and p2pool/bitcoin/networks.py.
t.y is it a case of duplicating the info from one to the other? No. Your best bet is to reach out to rav3n and see if you can get some help there. Since his fork has virtually every coin, he's definitely a good resource. For example, here's the math.Object values for BTC: p2pool/networks.py: bitcoin=math.Object(
PARENT=networks.nets['bitcoin'],
SHARE_PERIOD=30, # seconds
CHAIN_LENGTH=24*60*60//10, # shares
REAL_CHAIN_LENGTH=24*60*60//10, # shares
TARGET_LOOKBEHIND=200, # shares
SPREAD=3, # blocks
IDENTIFIER='fc70035c7a81bc6f'.decode('hex'),
PREFIX='2472ef181efcd37b'.decode('hex'),
P2P_PORT=9333,
MIN_TARGET=0,
MAX_TARGET=2**256//2**32 - 1,
PERSIST=True,
WORKER_PORT=9332,
BOOTSTRAP_ADDRS='forre.st vps.forre.st portals94.ns01.us 54.227.25.14 119.1.96.99 204.10.105.113 76.104.150.248 89.71.151.9 76.114.13.54 72.201.24.106 79.160.2.128 207.244.175.195 168.7.116.243 94.23.215.27 218.54.45.177 5.9.157.150 78.155.217.76 91.154.90.163 173.52.43.124 78.225.49.209 220.135.57.230 169.237.101.193:8335 98.236.74.28 204.19.23.19 98.122.165.84:8338 71.90.88.222 67.168.132.228 193.6.148.18 80.218.174.253 50.43.56.102 68.13.4.106 24.246.31.2 176.31.208.222 1.202.128.218 86.155.135.31 204.237.15.51 5.12.158.126:38007 202.60.68.242 94.19.53.147 65.130.126.82 184.56.21.182 213.112.114.73 218.242.51.246 86.173.200.160 204.15.85.157 37.59.15.50 62.217.124.203 80.87.240.47 198.61.137.12 108.161.134.32 198.154.60.183:10333 71.39.52.34:9335 46.23.72.52:9343 83.143.42.177 192.95.61.149 144.76.17.34 46.65.68.119 188.227.176.66:9336 75.142.155.245:9336 213.67.135.99 76.115.224.177 50.148.193.245 64.53.185.79 80.65.30.137 109.126.14.42 76.84.63.146'.split(' '),
ANNOUNCE_CHANNEL='#p2pool',
VERSION_CHECK=lambda v: 50700 <= v < 60000 or 60010 <= v < 60100 or 60400 <= v,
VERSION_WARNING=lambda v: 'Upgrade Bitcoin to >=0.8.5!' if v < 80500 else None,
) And in p2pool/bitcoin/networks.py bitcoin=math.Object(
P2P_PREFIX='f9beb4d9'.decode('hex'),
P2P_PORT=8333,
ADDRESS_VERSION=0,
RPC_PORT=8332,
RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
(yield check_genesis_block(bitcoind, '000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f')) and
not (yield bitcoind.rpc_getinfo())['testnet']
)),
SUBSIDY_FUNC=lambda height: 50*100000000 >> (height + 1)//210000,
POW_FUNC=data.hash256,
BLOCK_PERIOD=600, # s
SYMBOL='BTC',
CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'Bitcoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/Bitcoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.bitcoin'), 'bitcoin.conf'),
BLOCK_EXPLORER_URL_PREFIX='https://blockchain.info/block/',
ADDRESS_EXPLORER_URL_PREFIX='https://blockchain.info/address/',
TX_EXPLORER_URL_PREFIX='https://blockchain.info/tx/',
SANE_TARGET_RANGE=(2**256//2**32//1000 - 1, 2**256//2**32 - 1),
DUMB_SCRYPT_DIFF=1,
DUST_THRESHOLD=0.001e8,
) What's with that last payout? There were two close together then one got revoked and now My wallet is now marked with a warning.
1JKVhFcR8GmwJFixRSeg46eXc7yEq7jzBB
Orphaned block. That's what happened. |
|
|
|
|
IYFTech, you are correct - regtable69, you need to define the math.Object for your coin in both p2pool/networks.py and p2pool/bitcoin/networks.py.
|
|
|
|
I especially like the dog door/tunnel. Never know when you might need it  |
|
|
|
Yes I'm a hobbyist and have my Ants set up in my living room. 2x Ants on 2x Corsair 600 and planning for a 3rd to split between the 2 power supplies.
That will be the limit. My house is old and in need of an electrical upgrade.
Might want to be careful there. Assuming you haven't over clocked the S1s, and if you believe Bitmain's claims of 360 watts each, you're looking at 1080 watts minimum on that circuit to power the miners when you get your third. Assuming you've got a 15a circuit breaker (or fuse since you said your house was old), you can draw 1440 watts continuously, or at most 1800 watts before that breaker/fuse trips. Hope you don't have too much other equipment drawing power in your living room  |
|
|
|
Hmm, someone just connected with a hashrate of about 1.4TH/s...but they're using an invalid bitcoin address, which means they won't get paid for it. Since I can't contact them directly, hopefully they see this message and rectify the mistake.
Does anyone know what happens to p2pool payments that don't have a proper place to go?
Yes, the pool's default payout address gets the coins. So, when you setup your p2pool node and start it up, typically you do something like this: ./p2pool.py -a SOMEBTCADDRESS. That address is what would get the coins from the miner with the invalid address. If you're not passing the -a parameter, then the bitcoind your node connects to would have a default address already setup by the p2pool software the very first time you start it up, and that address would get the coins. TL;DR: the same wallet that is getting the 2% fee gets the coins from the miner with the invalid address. |
|
|
|
Got the new front end up and running including miner detail pages with graphs, longer display periods for "recent blocks" & "node shares", more data integrated from the blockchain, etc... Take a look and tell me what you think http://mining.coincadence.com/If you have low latency to my server (US East) I'd love to try and get some additional load on it to see how the efficiency holds up. To figure out your latency Ping mining.coincadence.com from a computer on the same network as your miners. When your Ping is complete you should see something like below, the number you are looking for is highlighted in orange: --- mining.coincadence.com ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 9.674/ 10.968/11.726/0.748 ms WindPath's Quick n' Dirty P2Pool latency guide: Greater then 100ms – To far, look for a closer node Less then 100ms – Looking good Less then 50ms – Great, your in the zone! Less then < 30ms – It's raining hashes... Less then 10ms – Are you sleeping in my data center? If you are willing to help out with testing point some more mining power at this node for a week or more, it's currently a 0% fee and I'd appreciate it Pool URL: stratum+tcp://mining.CoinCadence.com:9332 User name: YOUR_BITCOIN_ADDRESS Pass: Not required If you would like to set your own difficulty use YOUR_BITCOIN_ADDRESS+DIFFICULTY for the user name, for example: 19vXrwKGUhK4cCU8tA4kWZgbChcmh9a6qj+256 Thanks to jonnybravo0311 for feedback and providing some of the code for the miner stats pages. And thank you for checking it out! http://mining.coincadence.com/--- mining.coincadence.com ping statistics --- 70 packets transmitted, 70 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 14.355/18.260/34.263/5.148 ms Looks like I know where my backup pool is going to be |
|
|
|
I was inspired by the OP and setup solo mining on my graphics card. The software i am using is cuda miner. It now says "stratum detected new block", does this mean that i have found a block? If yes, should i focus more mining power to the miner so it mines the block?
No, you haven't found a block. It means that your mining software has been informed there's a new block on which it needs to work. Lol! I guess i am not as lucky as i thought i was. Well, keep the faith i suppose!? Absolutely! It's why I solo mine. Chances are I'll never find that block, but why not try? It costs virtually nothing to do so (5 Antminer U2s driven by an rPi). |
|
|
|
Well 50% bonus is to high to be true. Most pool (like mine) pay the bonus for Block finders out of their private wallet, currently we dont offer any bonus for BTC (yet) but i will think on it . But it will be far less then 50%, maybe there will be a bonus for ~0.1 BTC or something like that. How much people are interested in a offer like this? p2pool does that now. The code divides the total block reward by 200. It gives 1/200th to the block finder, and splits the remaining 199/200 with the rest. So, assuming a block with 0 transactions in it is worth the 25BTC, the block finder gets 0.125BTC as a reward in addition to whatever reward he gets from submitted shares. |
|
|
|
Half divided to pool members = half of "normal" reward for most miners on most days. It is sufficient to cover electricity / operating cost.
That statement is where you're going to run into the most resistance to your idea. You're asking people to willing accept half of what they would normally get on the exceedingly slim chance that they might reap a significant reward should they be the one to find the block. In my own case, I have 5 Antminer U2s solo mining on the off chance that they might solve a block, mostly because the power requirements to do so are virtually negligible. I also play the lottery in the off chance that I might win the jackpot, which is an interesting analogy to what you're proposing. Let's assume for a second that you and a bunch of friends decide to play the PowerBall. You all purchase tickets and combine them together hoping that one of those tickets is a winner. Normal pool: If one of these tickets is a winner, we split the proceeds based upon how many tickets you contributed. Your pool: If one of these tickets is a winner, the person who bought the winning ticket gets half of the winnings and the rest of you split the remaining half. Which pool are you joining? |
|
|
|
Just got the same question: i've got iMac with core i3 and MBP with core i7, is there any point to mine? I believe i need to mine currency on CPU, as GPU’s are not powerful as CPU..And is it possible to mine using both of Macs via Wi-Fi?? Is there any point? I guess it depends on what you're expecting to get out of it. If your goal is to learn about the process of mining and crypto-currencies in general, then sure, try it out. If you're expecting a profit, there really is no point to mine with that hardware - especially if you want to mine BTC. |
|
|
|
Is there any hybrid pool out there?
For every block, if 12.5 BTC were shared with the pool and 12.5 BTC were rewarded to the miner who found the block, then mining would be a lot more interesting.
p2pool does indeed give a 0.5% bonus to the block finder. No pool that I know of exists which gives the block finder half of the block's value as a reward. It certainly would be "interesting". Good luck with convincing anybody it's a valid mining pool strategy |
|
|
|
Every time I add a new piece I monitor it and all associated connections very closely for at least the first few hours. You can do everything right and still get a bad board, etc.
Watch your connections. Don't over split!
Heat is your #1 enemy. If something is running abnormally hot there is a reason for it! It will not just go away!
You are a smart person! I am the same way when it comes to mining. 1 Had a qualified Electrician add 6 20 amp circuits in my garage. Cost was $1100, really only $600 as I built his website for $500. 2 Added north and south wall vents for airflow. With added fans the heat dropped by almost half. 3 All 19 S1 units are on a restaurant type metal rack, great for airflow. Every unit has an extra fan for overclocking. 4 Every unit I get in is tested for 24 hours and sits on a metal plate for that testing duration, before being added to the farm. 5 I use CGRemote software so I can see temps anytime I want and it will send me an email if any units go offline. 6 My wife knows where all of the breakers are and how to shut down the power to the whole house if I am not home. For most this is a hobby, but we don't need to burn down our house doing it. Safety first!!! Hope this helps. Rob  You replied right before I did... great post. You added extra circuits - a similar suggestion to what DeathAndTaxes made earlier. 19 S1s... nice garage setup |
|
|
|
|
Show Posts
