barely figured it out but got it. Whew!
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 184. (Read 2591920 times)
I just started my publicly accessible p2pool at http://50.70.132.95:9332/static/
barely figured it out but got it. Whew!
barely figured it out but got it. Whew!
And another block.
Best of all, I saw we were at 2.4 PH/s and it crossed 3 yesterday?!? Still fluctuating, but if we can get the mean above 2, I believe we will all be better off.
Best of all, I saw we were at 2.4 PH/s and it crossed 3 yesterday?!? Still fluctuating, but if we can get the mean above 2, I believe we will all be better off.
thx jb, i was thinking to do something about like windpath for the block history. but it's too much work. but happy with what is being shown atm at my pool.
btw, is there a way to ban/kick someone/ip from mining at my pool ?
there's an address with a incomplete btc address mining with very low hashrate & pool does not show it's share difficulty & time to share.
and another block today ... hope p2pool will keep it up
If it's an invalid BTC address, then if and when that miner finds a share, it'll be a donation to you. Whatever address your p2pool node uses as its default payout address will be the one that gets any credit for shares from invalid addresses. So, I suppose you could just let whoever it is mine away and thank them for the donation btw, is there a way to ban/kick someone/ip from mining at my pool ?
there's an address with a incomplete btc address mining with very low hashrate & pool does not show it's share difficulty & time to share.
and another block today ... hope p2pool will keep it up
thx jb, i was thinking to do something about like windpath for the block history. but it's too much work. but happy with what is being shown atm at my pool.
btw, is there a way to ban/kick someone/ip from mining at my pool ?
there's an address with a incomplete btc address mining with very low hashrate & pool does not show it's share difficulty & time to share.
and another block today ... hope p2pool will keep it up
btw, is there a way to ban/kick someone/ip from mining at my pool ?
there's an address with a incomplete btc address mining with very low hashrate & pool does not show it's share difficulty & time to share.
and another block today ... hope p2pool will keep it up
another block = happy yippie yippie
btw, i found the line to show the previous blocks mined. it goes like 24*60*60.
what should i put in to show the entire week ? i used to have it but i forgot.
i'm at 168*60*60 & it shows last 4 days.
thx.
If you look at that entire bit of code, you'll see why it's only showing a limited timeframe:btw, i found the line to show the previous blocks mined. it goes like 24*60*60.
what should i put in to show the entire week ? i used to have it but i forgot.
i'm at 168*60*60 & it shows last 4 days.
thx.
Code:
web_root.putChild('recent_blocks', WebInterface(lambda: [dict(
ts=s.timestamp,
hash='%064x' % s.header_hash,
number=p2pool_data.parse_bip0034(s.share_data['coinbase'])[0],
share='%064x' % s.hash,
) for s in node.tracker.get_chain(node.best_share_var.value, min(node.tracker.get_height(node.best_share_var.value), 24*60*60//node.net.SHARE_PERIOD)) if s.pow_hash <= s.header['bits'].target]))
ts=s.timestamp,
hash='%064x' % s.header_hash,
number=p2pool_data.parse_bip0034(s.share_data['coinbase'])[0],
share='%064x' % s.hash,
) for s in node.tracker.get_chain(node.best_share_var.value, min(node.tracker.get_height(node.best_share_var.value), 24*60*60//node.net.SHARE_PERIOD)) if s.pow_hash <= s.header['bits'].target]))
It's pulling data from the shares it knows about and getting the block data. Since p2pool only keeps a limited set of data (as kano pointed out), it will only be able to retrieve a limited date range to calculate whether or not any blocks have been found recently.
Even using blockchain.info APIs will only return a limited set of found blocks. For example, calling:
Code:
https://blockchain.info/blocks/P2Pool?format=json
Will return:
Code:
{
"blocks" : [
{
"height" : 357093,
"hash" : "000000000000000000040c489a058329c1aee111f8ad9651cac6a7050e58e52c",
"time" : 1432021066,
"main_chain" : true
},
{
"height" : 357023,
"hash" : "00000000000000000921e1b12a628c53aa4958dbcddc618141e0661a8cab983b",
"time" : 1431974068,
"main_chain" : true
},
{
"height" : 356722,
"hash" : "00000000000000001537af797fc306f8a8d5670aa4e1712b78a722cbd0b86c1f",
"time" : 1431808098,
"main_chain" : true
},
{
"height" : 356672,
"hash" : "00000000000000000e7e3e8519c56a6e9e3413632d3c05990fb299288570a73f",
"time" : 1431772821,
"main_chain" : true
},
{
"height" : 356638,
"hash" : "000000000000000010f11ea678a9447a348499255e11bfbc69b42f787292f19d",
"time" : 1431748262,
"main_chain" : true
},
{
"height" : 356621,
"hash" : "000000000000000016a0b7d559e4b49d69c863c7cb3e182f6aaacf8be524b4d7",
"time" : 1431738916,
"main_chain" : true
}
]
}
"blocks" : [
{
"height" : 357093,
"hash" : "000000000000000000040c489a058329c1aee111f8ad9651cac6a7050e58e52c",
"time" : 1432021066,
"main_chain" : true
},
{
"height" : 357023,
"hash" : "00000000000000000921e1b12a628c53aa4958dbcddc618141e0661a8cab983b",
"time" : 1431974068,
"main_chain" : true
},
{
"height" : 356722,
"hash" : "00000000000000001537af797fc306f8a8d5670aa4e1712b78a722cbd0b86c1f",
"time" : 1431808098,
"main_chain" : true
},
{
"height" : 356672,
"hash" : "00000000000000000e7e3e8519c56a6e9e3413632d3c05990fb299288570a73f",
"time" : 1431772821,
"main_chain" : true
},
{
"height" : 356638,
"hash" : "000000000000000010f11ea678a9447a348499255e11bfbc69b42f787292f19d",
"time" : 1431748262,
"main_chain" : true
},
{
"height" : 356621,
"hash" : "000000000000000016a0b7d559e4b49d69c863c7cb3e182f6aaacf8be524b4d7",
"time" : 1431738916,
"main_chain" : true
}
]
}
To truly build a history of found blocks, you'll have to get details on every block found to see if it happened to be added to the chain by P2Pool. Then you use the "block notify" event from bitcoind to tell you every time a block is found, so you can go and do the same thing for the newest block.
Once you do, you'll end up with something very similar to what windpath has.
another block = happy yippie yippie
btw, i found the line to show the previous blocks mined. it goes like 24*60*60.
what should i put in to show the entire week ? i used to have it but i forgot.
i'm at 168*60*60 & it shows last 4 days.
thx.
p2pool doesn't keep history forever - that could be why it stops at 4 days for whatever you are doing. btw, i found the line to show the previous blocks mined. it goes like 24*60*60.
what should i put in to show the entire week ? i used to have it but i forgot.
i'm at 168*60*60 & it shows last 4 days.
thx.
another block = happy yippie yippie
btw, i found the line to show the previous blocks mined. it goes like 24*60*60.
what should i put in to show the entire week ? i used to have it but i forgot.
i'm at 168*60*60 & it shows last 4 days.
thx.
btw, i found the line to show the previous blocks mined. it goes like 24*60*60.
what should i put in to show the entire week ? i used to have it but i forgot.
i'm at 168*60*60 & it shows last 4 days.
thx.
a block makes me happy n not b!tch abt BMT's p2p BS story.
c'mon blox come come come to the REAL p2p
c'mon blox come come come to the REAL p2p
It's a BS statement by AntPool. They have NO p2pool.
Truth.
So..
Anyone ever use the Antpool?
They claim its P2Pool, but it is obviously operating independent of the our P2Pool, as they have 67PH/s running.
I was curious if it has the same work retention as our pool and is trestles like ours.
Anyone who's mined out there have an impression for the rest of us?
S
It's a BS statement by AntPool. They have NO p2pool. They came out and announced in October of last year that they would be taking on p2pool and fixing the inherent problems. A ton of us were excited and couldn't wait to see what the Bitmain guys had in mind. Well, when they released their code it was plainly apparent it wouldn't work at all in the existing p2pool framework. In fact, all they really did was introduce some share tracking database and reliance upon a mysql server. The code was awful and didn't do anything to support the claims they were making. Time and time again we've called them out, and have posted multiple times in their thread about how they are not supporting decentralization and to remove all references to p2pool since their botched implementation is a farce. Anyone ever use the Antpool?
They claim its P2Pool, but it is obviously operating independent of the our P2Pool, as they have 67PH/s running.
I was curious if it has the same work retention as our pool and is trestles like ours.
Anyone who's mined out there have an impression for the rest of us?
S
So..
Anyone ever use the Antpool?
They claim its P2Pool, but it is obviously operating independent of the our P2Pool, as they have 67PH/s running.
I was curious if it has the same work retention as our pool and is trestles like ours.
Anyone who's mined out there have an impression for the rest of us?
S
Anyone ever use the Antpool?
They claim its P2Pool, but it is obviously operating independent of the our P2Pool, as they have 67PH/s running.
I was curious if it has the same work retention as our pool and is trestles like ours.
Anyone who's mined out there have an impression for the rest of us?
S
With 21 Inc's announcement, think we have a shot?
"@21dotco I hope you folks consider a distributed trust-less pool model, like P2Pool."
https://twitter.com/CoinCadence/status/600379349930528769
yes, it's run others programs without any issues (and not needed task manager or kill task job) for a minimal 35 days without reboot. 
Well, i have a serious problem with my P2Pool node :
- 0.9.1 rock stable with P2Pool node mining on USB Miner (for hobby)
- 0.9.2 = crash after 26h
- 0.9.3 = crash after 18h
- 0.10.0 = crash after 12h
- 0.10.1 = crash after 4h
- 0.10.2 (rc1) = crash before 1h ... of running time.
- 0.10.2 (rc1) without RPC server and P2Pool shutdown = rock stable
it's time to go back to solo mining ?
i need to change 0.9.x because blockchain have reach the more than 51 blocks of 100 in the new version ... like explain in early line on the top of my message by other member.
- 0.9.1 rock stable with P2Pool node mining on USB Miner (for hobby)
- 0.9.2 = crash after 26h
- 0.9.3 = crash after 18h
- 0.10.0 = crash after 12h
- 0.10.1 = crash after 4h
- 0.10.2 (rc1) = crash before 1h ... of running time.
- 0.10.2 (rc1) without RPC server and P2Pool shutdown = rock stable
it's time to go back to solo mining ? i need to change 0.9.x because blockchain have reach the more than 51 blocks of 100 in the new version ... like explain in early line on the top of my message by other member.
i've used all of the wallets as you mentioned before & had no issues running it with p2pool.
must be some config somewhere that's not right.
try to update everything to the latest version & chk your conf file.
is your hw able to support all of the above to run non stop 24/7 ?
Well, i have a serious problem with my P2Pool node :
- 0.9.1 rock stable with P2Pool node mining on USB Miner (for hobby)
- 0.9.2 = crash after 26h
- 0.9.3 = crash after 18h
- 0.10.0 = crash after 12h
- 0.10.1 = crash after 4h
- 0.10.2 (rc1) = crash before 1h ... of running time.
- 0.10.2 (rc1) without RPC server and P2Pool shutdown = rock stable
it's time to go back to solo mining ?
i need to change 0.9.x because blockchain have reach the more than 51 blocks of 100 in the new version ... like explain in early line on the top of my message by other member.
- 0.9.1 rock stable with P2Pool node mining on USB Miner (for hobby)
- 0.9.2 = crash after 26h
- 0.9.3 = crash after 18h
- 0.10.0 = crash after 12h
- 0.10.1 = crash after 4h
- 0.10.2 (rc1) = crash before 1h ... of running time.
- 0.10.2 (rc1) without RPC server and P2Pool shutdown = rock stable
it's time to go back to solo mining ? i need to change 0.9.x because blockchain have reach the more than 51 blocks of 100 in the new version ... like explain in early line on the top of my message by other member.
well, so far so good. upgraded & it runs fine but i'm running with armory opened & it works too. not using core wallet anymore (indirectly).
I am sure I was not the only one to update Bitcoin Core yesterday as part of the procrastinators group. Ironic how the luck went up, guess time will tell if there is any correlation.
i was still on the old core, just updated. Hope it brings some luck to us all.
keep the blocks rollin' in
Yea, I was both surprised and a little concerned that we moved from version 2 blocks to version 3 so quickly (core version 0.9.x to 0.10.x).
I was not sure how it all went down, so researched it a little...
My first thought was that core devs set the "Warning: This version is obsolete, upgrade required!" via the alert system to see how fast we could move the network from 0.9.x to 0.10.x, in anticipation of scheduling the hard fork to increase block size next year, I'm happy to report I was wrong.
After a little digging, it's all controlled by bitcoin core (go Satoshi!).
Basically it works like this:
Code:
if more than 50 of the last 100 blocks are a higher version then what your node is working on = trigger alert
Core code reference: https://github.com/bitcoin/bitcoin/blob/2a822987dd710427328fa458a4141e060c39a755/src/main.cpp#L2019
What this does indicate is that the majority of the network (in this case big china mines) are pushing a new block version (3 vs. 2), and the alert will be triggered as intended.
As far as my node goes, if it aint' broken I'm not going to upgrade it...
I'm happy to see that the major players are updating relatively quickly, and that if a hard fork to increase block size is scheduled, it will most likely be accepted by the network.
Just a heads up in case anyone didn't realize yet - UNO is also now merge mineable. I've only used the Linux wallet from git so am not sure about the winblows wallet yet - it's in beta & there's no daemon yet.....
I am sure I was not the only one to update Bitcoin Core yesterday as part of the procrastinators group. Ironic how the luck went up, guess time will tell if there is any correlation.
i was still on the old core, just updated. Hope it brings some luck to us all.
keep the blocks rollin' in
I am sure I was not the only one to update Bitcoin Core yesterday as part of the procrastinators group. Ironic how the luck went up, guess time will tell if there is any correlation.
Jump to: