Bitcoin Forum
July 20, 2019, 02:39:51 PM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: « 1 ... 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 [808] 809 810 811 812 813 814 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2580383 times)
jtoomim
Hero Member
*****
Offline Offline

Activity: 819
Merit: 1001


View Profile WWW
January 22, 2018, 01:49:13 AM
Last edit: January 22, 2018, 05:05:04 AM by jtoomim
 #16141

I pushed two changes to 1mb_segwit that change how pseudoshare difficulty is calculated for miners.

First, I fixed a bug for Litecoin that was limiting difficulty to about 15k. This resulted in excessive CPU and bandwidth usage on p2pool nodes that have more than about 10 GH/s. I fixed that bug, which means that Litecoin difficulties will be more reasonable (e.g. 226k on my node with 100 GH/s.

Second, I increased the target pseudoshare rate on all networks to 10 per second (from 1 per second, except for Litecoin's bug).

This should result in smoother hashrate graphs for all nets except Litecoin, at the expense of slightly higher CPU and bandwidth usage. For Litecoin, expect rougher hashrate graphs but substantially lower CPU and bandwidth usage.

If you're running my code, a git pull should grab the changes. Unless you're running a large Litecoin node, these changes are not likely to make a big difference for you, so feel free to skip this update.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
1563633591
Hero Member
*
Offline Offline

Posts: 1563633591

View Profile Personal Message (Offline)

Ignore
1563633591
Reply with quote  #2

1563633591
Report to moderator
1563633591
Hero Member
*
Offline Offline

Posts: 1563633591

View Profile Personal Message (Offline)

Ignore
1563633591
Reply with quote  #2

1563633591
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1563633591
Hero Member
*
Offline Offline

Posts: 1563633591

View Profile Personal Message (Offline)

Ignore
1563633591
Reply with quote  #2

1563633591
Report to moderator
Tornado_of_Coins
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile WWW
January 22, 2018, 01:41:52 PM
 #16142

I have an S9 and tried to connect to several JT pools and it's not showing work at all, does it take a while to show connection?

This is the current one I tried : ml.toom.im:9332

EDIT: Ok, its connected took about 3-5minutes
jtoomim
Hero Member
*****
Offline Offline

Activity: 819
Merit: 1001


View Profile WWW
January 22, 2018, 09:24:30 PM
 #16143

I'm moving the rest of our L3+s onto p2pool. P2pool's LTC hashrate should now be around 500 GH/s, enough for 2-3 blocks per day on average.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
Kiefff
Newbie
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 23, 2018, 04:22:10 AM
 #16144

Awesome work Jtoomim. I'm currently running your fork and enabled the 1% dev fee. Will the hash you put on the pool be staying with us?As in not rentals?
jtoomim
Hero Member
*****
Offline Offline

Activity: 819
Merit: 1001


View Profile WWW
January 23, 2018, 06:02:01 AM
 #16145

FYI, the dev fee does not go to me. It goes to forrestv.

Our LTC hashrate will probably be staying on p2pool as long as merged mining and multipool mining has a small or zero advantage over straight LTC mining.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
Kiefff
Newbie
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 23, 2018, 06:14:15 AM
Last edit: January 23, 2018, 06:40:18 AM by Kiefff
 #16146

Awesome. So I'm running your fork and seem to have some issues. Only 2 submitted shares this whole time with 8GH on my node. It seems that the diff for each is going everywhere? http://cyberdyne-mining.io:9327/static/

*edit* no longer using 1mb_segwit fork. Will test some more later
Kiefff
Newbie
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 23, 2018, 05:23:20 PM
Last edit: January 24, 2018, 05:45:03 AM by Kiefff
 #16147

so back at it again this morning running 1mb_segwit fork. My miner are showing a diff of 4.07k and still no shares from any miners on my node. If you goto http://cyberdyne-mining.io:9327/static/UI/ you see can the differences in the share diff for each miner. Miners of same hashrate sometimes have crazy diff. Not getting any errors on my back end. Seemed yesterday I got 2 valid shares then after that nothing.

**edit**
seems I may have freaked out a bit  Cheesy I guess the network is that much more difficulty with the added hash now? My node seems to be getting shares, staying in the 95-100% efficiency range so far running PYPY. I've also gathered a growing group of miners already on my node, they smelt the blocks with the newly added hashrate?  Cool . My node is currently pushing ~13.9GH

http://cyberdyne-mining.io:9327/static/
http://cyberdyne-mining.io:9327/static/UI/ for those that like it fancy
Kiefff
Newbie
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 23, 2018, 05:29:33 PM
 #16148

I lied about no errors....also, adding ANY +diff number and my miner always shows Diff of 8.04M
Running on ubuntu server

Code:
Traceback (most recent call last):
  File "/usr/local/lib/pypy2.7/dist-packages/Twisted-15.4.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 501, in _startRunCallbacks
    self._runCallbacks()
  File "/usr/local/lib/pypy2.7/dist-packages/Twisted-15.4.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 588, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File "/home/skynet/p2pool/p2pool/util/deferral.py", line 256, in gotResult
    it(res2)
  File "/home/skynet/p2pool/p2pool/util/deferral.py", line 233, in it
    res = gen.send(cur) # external code is run here
--- <exception caught here> ---
  File "/home/skynet/p2pool/p2pool/util/deferral.py", line 284, in _worker
    self.func(*self.args, **self.kwargs)
  File "/home/skynet/p2pool/p2pool/util/expiring_dict.py", line 109, in <lambda>
    self._expire_loop = expire_loop = deferral.RobustLoopingCall(lambda: self_ref().expire())
exceptions.AttributeError: 'NoneType' object has no attribute 'expire'

Unhandled Error
Traceback (most recent call last):
  File "/usr/local/lib/pypy2.7/dist-packages/Twisted-15.4.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 501, in _startRunCallbacks
    self._runCallbacks()
  File "/usr/local/lib/pypy2.7/dist-packages/Twisted-15.4.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 588, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File "/home/skynet/p2pool/p2pool/util/deferral.py", line 256, in gotResult
    it(res2)
  File "/home/skynet/p2pool/p2pool/util/deferral.py", line 233, in it
    res = gen.send(cur) # external code is run here
--- <exception caught here> ---
  File "/home/skynet/p2pool/p2pool/util/deferral.py", line 284, in _worker
    self.func(*self.args, **self.kwargs)
  File "/home/skynet/p2pool/p2pool/util/expiring_dict.py", line 109, in <lambda>
    self._expire_loop = expire_loop = deferral.RobustLoopingCall(lambda: self_ref().expire())
exceptions.AttributeError: 'NoneType' object has no attribute 'expire'
GabitKZ
Newbie
*
Offline Offline

Activity: 24
Merit: 0


View Profile
January 24, 2018, 03:22:33 AM
 #16149

Hi !

I have S9

Is this correct for him ?

Pool 1: crypto.mine.nu:9334

Pool 2: low-doa.mine.nu:9332

Pool 3: 31.41.40.25:9332

Worker: BTC address from your wallet
Kiefff
Newbie
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 24, 2018, 04:43:18 AM
 #16150

Hi !

I have S9

Is this correct for him ?

Pool 1: crypto.mine.nu:9334

Pool 2: low-doa.mine.nu:9332

Pool 3: 31.41.40.25:9332

Worker: BTC address from your wallet

If those are the closest nodes to you, it all looks good.
kano
Legendary
*
Offline Offline

Activity: 2856
Merit: 1181


Linux since 1997 RedHat 4


View Profile
January 24, 2018, 06:14:20 AM
 #16151

Hi !

I have S9

Is this correct for him ?

Pool 1: crypto.mine.nu:9334

Pool 2: low-doa.mine.nu:9332

Pool 3: 31.41.40.25:9332

Worker: BTC address from your wallet
You should point it at your own p2pool first - remember p2pool is supposed to be decentralised ... according to the thread title Tongue

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
Discord support invite at https://kano.is/ Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
Kiefff
Newbie
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 24, 2018, 07:53:46 PM
 #16152

http://cyberdyne-mining.io:9327/static/ <--rock solid, 1mb_Segwit fork running PYPY

Besides the invalid block this morning(im guessing invalid?), I just had someone dump 15GH+ alone on my LTC p2pool node. That puts me at ~29GH with everything looking smooth so far. Current efficiency at time of post = 101% with 83 total shares as of now. Now we just need the block train to come thru =] Again, well done Jtoomim.
quinten.miller
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
January 25, 2018, 12:49:39 AM
 #16153

Hi,

Looking for some assistance in setting up p2pool as a mining node for Vertcoin.

I've got all the prerequisites installed and configured.
I've got the bitcoind up and running with the entire blockchain downloaded (~165GB on disk)

bitcoin-cli getnetworkinfo gives the following:
Code:
  "version": 150100,
  "subversion": "/Satoshi:0.15.1/",
  "protocolversion": 70015,
  ....

when i run p2pool I'm getting the following:
Code:
2018-01-25 00:08:15.008000 p2pool (version 3d0f826-dirty)
2018-01-25 00:08:15.008000
2018-01-25 00:08:15.008000 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'XXXXXXXXXXX'...
2018-01-25 00:08:15.024000 Coin daemon too old! Upgrade!
2018-01-25 00:08:16.037000 Coin daemon too old! Upgrade!
2018-01-25 00:08:17.050000 Coin daemon too old! Upgrade!

I've checked the p2pool source code and the and followed (i think) the trail to a method/function called VERSION_CHECK (python is not my natural programming language - please excuse) https://github.com/p2pool/p2pool/search?utf8=%E2%9C%93&q=VERSION_CHECK&type=

I'm running the bitcoind for Bitcoin, thus I'm looking at p2pool/p2pool/networks/bitcoin.py

VERSION_CHECK = lambda v: None if 100000 <= v else 'Bitcoin version too old. Upgrade to 0.11.2 or newer!' # not a bug. BIP65 support is ensured by SOFTFORKS_REQUIRED

That looks like i should be OK with 150100 (the newest stable version of bitcoin).

I'm still getting up to speed on Bitcoin, mining nodes etc, so please forgive me.
I did read a few posts around bitcoin core not being suitable to mining for altcoins (dated around september last 2017). I'm running Bitcoin core AFAIK.

Where have I gone wrong?

Do i need to be running btc1 (https://github.com/btc1/bitcoin) instead of Bitcoin core (https://bitcoincore.org/en/download/)?

If not, how can I use Bitcoin core with P2Pool to run a mining node for Vertcoin?
jtoomim
Hero Member
*****
Offline Offline

Activity: 819
Merit: 1001


View Profile WWW
January 25, 2018, 03:24:17 AM
 #16154

We're having some trouble with our primary internet connection at our datacenter. ml.toom.im:9332, :9334, :9336, and :7903 will be unavailable probably for a few days. woff.toom.im:9348 and woff.toom.im:9327 should still be working, but our miners can't reach those ports any longer due to how our LAN and firewalls are currently configured during failover situations, so we will not be contributing any BCH or LTC hashrate until we get this issue resolved.

I lied about no errors....also, adding ANY +diff number and my miner always shows Diff of 8.04M
"'NoneType' object has no attribute 'expire'" messages can safely be ignored. They happen even when the node is working properly. That's just a cosmetic bug AFAIK. Not sure why address+XXXXX isn't working; I noticed that too on an earlier version of the code. That seems to be mostly cosmetic though, so I might not look into it for a while.

Only 2 submitted shares this whole time with 8GH on my node. It seems that the diff for each is going everywhere? ... *edit* no longer using 1mb_segwit fork.
1mb_segwit and p2pool/p2pool master should have the same litecoin share difficulty. They may have different pseudoshare difficulties, but pseudoshare difficulty is only used for statistics and does not affect revenue (unless it's so low that your CPU gets saturated, at least). Difficulty will be much higher than before due to the higher pool hashrate.

If those are the closest nodes to you, it all looks good.
Single-threaded CPU speed (including whether you're running pypy) is about 10x as important on Bitcoin p2pool as network latency is. It typically takes somewhere between 0.5 seconds and 3 seconds to process a share and issue new work on p2pool, depending on CPU speed, but it only takes between 0.001 seconds and 0.3 seconds to transmit stratum jobs to and from the miner and node.


Besides the invalid block this morning(im guessing invalid?)

As for the invalid LTC block from Wednesday Jan 24 at 12pm GMT, my litecoin debug.log says this:

Code:
2018-01-24 12:09:34 CreateNewBlock(): total size: 36290 block weight: 144287 txs: 95 fees: 10300975 sigops 1227
2018-01-24 12:09:49 CreateNewBlock(): total size: 38752 block weight: 154135 txs: 102 fees: 10740075 sigops 1283
2018-01-24 12:10:04 CreateNewBlock(): total size: 43993 block weight: 174106 txs: 113 fees: 11370458 sigops 1362
2018-01-24 12:10:19 CreateNewBlock(): total size: 61073 block weight: 242426 txs: 126 fees: 13213178 sigops 1482
2018-01-24 12:10:29 ERROR: ConnectBlock(): coinbase pays too much (actual=2511370458 vs limit=2511291614)
2018-01-24 12:10:29 InvalidChainFound: invalid block=496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28  height=1355999  log2_work=69.614049  date=2018-01-24 12:10:05
2018-01-24 12:10:29 InvalidChainFound:  current best=815e95cd59cdc16d20dc8add274fe3f5683174fdbe8c297eac5cfd3adfbd239f  height=1355998  log2_work=69.614023  date=2018-01-24 12:07:47
2018-01-24 12:10:29 ERROR: ConnectTip(): ConnectBlock 496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28 failed
2018-01-24 12:10:29 InvalidChainFound: invalid block=496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28  height=1355999  log2_work=69.614049  date=2018-01-24 12:10:05
2018-01-24 12:10:29 InvalidChainFound:  current best=815e95cd59cdc16d20dc8add274fe3f5683174fdbe8c297eac5cfd3adfbd239f  height=1355998  log2_work=69.614023  date=2018-01-24 12:07:47
2018-01-24 12:10:29 ERROR: AcceptBlockHeader: block 496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28 is marked invalid
2018-01-24 12:10:29 Peer 14 sent us invalid header via cmpctblock
2018-01-24 12:10:29 ERROR: AcceptBlockHeader: block 496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28 is marked invalid
2018-01-24 12:10:29 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-01-24 12:10:30 ERROR: AcceptBlockHeader: block 496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28 is marked invalid
2018-01-24 12:10:30 Peer 18 sent us invalid header via cmpctblock
2018-01-24 12:10:34 CreateNewBlock(): total size: 64138 block weight: 254686 txs: 137 fees: 13520639 sigops 1562
2018-01-24 12:10:49 CreateNewBlock(): total size: 68992 block weight: 273439 txs: 152 fees: 15049509 sigops 1672
2018-01-24 12:11:05 CreateNewBlock(): total size: 75486 block weight: 298755 txs: 163 fees: 16182859 sigops 1750
2018-01-24 12:11:14 UpdateTip: new best=924b90b24a8003352e01c6e3bdb183466b718850e1da82ed1662d907e5e486de height=1355999 version=0x20000000 log2_work=69.614049 tx=20103178 date='2018-01-24 12:11:08' progress=1.000000 cache=22.9MiB(7817tx)
2018-01-24 12:11:14 CreateNewBlock(): total size: 1753 block weight: 6904 txs: 4 fees: 152800 sigops 432
2018-01-24 12:11:29 CreateNewBlock(): total size: 7627 block weight: 30400 txs: 15 fees: 1095648 sigops 576

The error is "coinbase pays too much (actual=2511370458 vs limit=2511291614)". Someone was trying to earn 0.00078844 LTC too much in that block. That invalid block was mined by LZzzELrQifCah5oafpNuCA6dLiyacVJNDa, and they were not using my code (they were voting for v17 shares). If anyone can find the node used by that miner, that would be helpful. You can sometimes get hints by browsing to (node IP:port)/static/share.html#496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28 and seeing which peer it was received from, then repeating the process. This gets harder when nodes have non-standard UIs, though, and when I tried to do this on this share, the first node I ran into was running a non-standard UI. Someone else might have better luck.

It may be necessary to add some code to p2pool to check the coinbase payments to make sure that they don't violate rules like this, and punish (orphan) shares that are invalid in this way. But that sucks, because it means more code that I don't have time to write.


Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
Tornado_of_Coins
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile WWW
January 25, 2018, 03:49:14 AM
 #16155

So what happen to all the shares I had on that node?
jtoomim
Hero Member
*****
Offline Offline

Activity: 819
Merit: 1001


View Profile WWW
January 25, 2018, 08:14:57 AM
 #16156

It looks like we have resolved our networking problems. ml.toom.im:9332, :9334, and :7903 should be available again outside our LAN once again, and woff.toom.im:9348 and :9327 once again have hashrate on them.
So what happen to all the shares I had on that node?
Your shares were not on that node. They were on the p2pool network. When my nodes go down, they're no longer contributing to the p2pool network, but the shares that were mined before my nodes went down have been copied to all other nodes on the same network (i.e. jtoomimnet).

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
jtoomim
Hero Member
*****
Offline Offline

Activity: 819
Merit: 1001


View Profile WWW
January 25, 2018, 09:34:30 AM
 #16157

You get paid whenever a block is found. For Litecoin, that will average about once a day, but there may be no payouts at all on some days if we are unlucky. Your payments for the first few days will start smaller and will ramp up. After you stop mining, your payments will slowly ramp down over a few days.

Hosting bitcoin miners for $65 to $80/kW/month on clean, cheap hydro power.
http://Toom.im
Tornado_of_Coins
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile WWW
January 25, 2018, 10:46:56 AM
 #16158

It looks like we have resolved our networking problems. ml.toom.im:9332, :9334, and :7903 should be available again outside our LAN once again, and woff.toom.im:9348 and :9327 once again have hashrate on them.
So what happen to all the shares I had on that node?
Your shares were not on that node. They were on the p2pool network. When my nodes go down, they're no longer contributing to the p2pool network, but the shares that were mined before my nodes went down have been copied to all other nodes on the same network (i.e. jtoomimnet).
Ahh, blockchain...Ii should have thought. Thanks JT
momentmc
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
January 25, 2018, 03:40:27 PM
 #16159

Hi, I have a few questions.  Huh

1- I started mining with 20 "antminer" s9. I did not build my own Node. I'm mining for p2pool (http://p2pool.org/stats/node.php) It is stated that a payment will be made in 72 hours. If I do not find a block, can not I get this money?

2- Have you received money within 3 days of those who mining up until now? S9 or Bitcoin?

3- Do I receive a reward for the transfer fee from the scavenging I made in the P2pool pool or mining a block?

4- What do I understand when I see the following? Didn't find 6 daytime blocks?

https://image.ibb.co/cuHXgw/doa.png

Ps: I'm so sorry my english isn't good.

Thanks
Kiefff
Newbie
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 25, 2018, 04:33:55 PM
 #16160

Hi, I have a few questions.  Huh

1- I started mining with 20 "antminer" s9. I did not build my own Node. I'm mining for p2pool (http://p2pool.org/stats/node.php) It is stated that a payment will be made in 72 hours. If I do not find a block, can not I get this money?

2- Have you received money within 3 days of those who mining up until now? S9 or Bitcoin?

3- Do I receive a reward for the transfer fee from the scavenging I made in the P2pool pool or mining a block?

4- What do I understand when I see the following? Didn't find 6 daytime blocks?

https://image.ibb.co/cuHXgw/doa.png

Ps: I'm so sorry my english isn't good.

Thanks

1 - first you are mining on p2pool mainnet, I suggest Jtoomimnet for BTC mining. Or at least find a node that seems to be more efficient than the one you are on. If no block is found, there is no BTC to payout to the miners. This isnt a PAY PER SHARE pool. You get paid based on blocks found and shares you submitted into the sharechain. So that means whatever your PREDICTED PAYMENT is at the time of a found block, thats what you will get for your mining work.

2- you will receive BTC when a block is found by the pool. Everyone is paid almost immediately after found blocks. The coins are generated coins that no one touches but your wallet.

3- p2pool pays the miners the founds blocks and transaction fees of that block. So normal BTC block = 12.5 BTC + extra transfer fees. Same with LTC network, just block reward is 25 LTC + transaction fees. Sometimes transfer fees almost make the block reward DOUBLE. p2pool, Kano.is, and Slushpool are the only pools that I know payout the transaction fee, in the BTC world. I could be wrong..

4- what you are highlighting is found blocks, but im pretty sure those are invalid? Not 100%, I mostly follow LTC p2pool. Like i said before, get off mainnet p2pool btc and join jtoomim net. More hash and smoother network.

Hope I answered your questions...and again, get off mainnet p2pool and join a Jtoomimnet node. ~80day est BLOCK time vs ~15-20days is a big difference. Not to mention the difference in block sizes between the two... LETS CRUSH BLOCKS!

-Keith
Pages: « 1 ... 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 [808] 809 810 811 812 813 814 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!