Bitcoin Forum
February 20, 2019, 10:50:40 PM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 [654] 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 ... 814 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2570527 times)
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1344
Merit: 1015


Mine at Jonny's Pool


View Profile WWW
July 13, 2015, 05:50:39 PM
 #13061

OgNasty runs his node in the EU (Germany): https://nastyfans.org/nastypool/.  Not sure about west coast US nodes, though.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
1550703040
Hero Member
*
Offline Offline

Posts: 1550703040

View Profile Personal Message (Offline)

Ignore
1550703040
Reply with quote  #2

1550703040
Report to moderator
The forum was founded in 2009 by Satoshi and Sirius. It replaced a SourceForge forum.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
luthermarcus
Full Member
***
Offline Offline

Activity: 213
Merit: 100



View Profile
July 14, 2015, 03:30:03 AM
 #13062

Anyone know how to ban peers on bitcoin qt. I'm not sure it's possible.
Also can anyone point me in direction of a good tutorial for bitcoind?

Bitcoin 0.11.0 solves the freezing i was seeing (recommended to upgrade if you have issues)  This release supports running a fully validating node without maintaining a copy of the raw block and undo data on disk. AKA pruning which has to be manually activated by using below code in
bitcoin config and don't use it if you use the wallet function because it turns it off. (also incompatible with -txindex will auto. turn it of)

prune=N : where N is the number of MB to allot for raw block & undo data (don't know what is a good number they mention 550mb though)

They are also recommending these for the transaction flooding

minrelaytxfee=0.00005
limitfreerelay=5  defualt=10

I'm not sure you can ban peers directly with the core software.  If needed, I just add firewall rules to block the IP addresses of the bad peers.  If you're using Ubuntu and ufw, it's absurdly easy:
Code:
ufw deny from IP_ADDRESS

My local node has been updated to core 0.11.0 and 14.0-9.  While I'm still seeing higher-than-usual rejected hash rate percentages, I haven't experienced the freezing/lost contact issues again.  So far, so good.

I heard blocking peers can effect your bitcoin node in a weird way. If you are using    -addnode or -connect try using defualts and see if that fixes it.Depending on your peers take off firewall as well.

Donate Bitcoin
1Mz7ZHxPhoH1ZK2yQvo62NdHvvsS2quhzc
Donate TRX
TB3WiLEj6iuSBU5tGUKyZkjB4vqrBDvoYM
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 14, 2015, 01:01:38 PM
 #13063

I heard blocking peers can effect your bitcoin node in a weird way. If you are using    -addnode or -connect try using defualts and see if that fixes it.Depending on your peers take off firewall as well.

Where did you hear this - can you provide a link? I've never had any issues.....


Bitcoin Core 0.11.0 released

I will not have time to test it today, but it looks like there are a lot of speed improvements for the mempool that should speed up GBT latency.

https://bitcoin.org/en/release/v0.11.0

Would be interested in hearing anybody's experience Smiley

Been running this version since it was released, so far it's proven very stable with no disconnects - although I do have quite a few bad peers blocked, weather this has something to do with it I'm not sure, but generally I'm very happy with how it performs.

EDIT: Although I am having trouble with the relaynetworkclient disconnecting - anyone else having this problem?
Meuh6879
Legendary
*
Offline Offline

Activity: 1512
Merit: 1000



View Profile
July 14, 2015, 01:21:37 PM
 #13064

yes, mainly because of a corrupted share chain (of P2Pool).
verified share can't rease, too ... in this case of many disconnected clients.

i must have deleted 3 times (in 1 week) the sharechain of P2Pool to have a standard P2Pool reaction.

probably the old v13 that it tries to inject shares ... again.
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 14, 2015, 02:16:24 PM
 #13065

yes, mainly because of a corrupted share chain (of P2Pool).
verified share can't rease, too ... in this case of many disconnected clients.

i must have deleted 3 times (in 1 week) the sharechain of P2Pool to have a standard P2Pool reaction.

probably the old v13 that it tries to inject shares ... again.

I too experienced a corrupted p2pool sharechain & had to delete/redownload a new one a few days ago. It seems like p2pool is not fully banning older v13 releases, which seems to be causing the problem. Since I started proactively banning bad peers manually the problems have all but gone, but having to constantly monitor my logs for repeat offending IP's is a real bind & very laborious.
Also, looking around the various p2pool node finder sites, there's still a multitude of v13 nodes still mining away regardless - which makes me wonder if these nodes are actually still getting paid, as there have been zero complaints here about unpaid blocks. If these outdated nodes are still getting paid, that would mean that their owners are still blissfully unaware of any required upgrade & would also explain why there are still so many older nodes humming away......
iSOcH
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
July 15, 2015, 07:08:39 AM
 #13066

Hey, can anybody recommend some good nodes to use for Nicehash (Amsterdam) and Westhash (San Jose)? I'm ready to drop some rental hash on it, when the price is right.

i'm also running a node in germany; https://pascal-schwarz.ch/p2pool-node-status/
idonothave
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
July 16, 2015, 07:51:55 AM
 #13067

Howto get latency of bitcoin-qt low? I am just now around 0.5s

Install bitcoin v0.11. Add to your bitcoin.conf:

maxconnections=10

then run bitcoin-qt and look connections in debug witdow. Choose IPs with lowest latencies and add them to your bitcoin.conf. Add there not more then 4 the best.

addnode=x.x.x.x
luthermarcus
Full Member
***
Offline Offline

Activity: 213
Merit: 100



View Profile
July 16, 2015, 09:52:00 AM
Last edit: July 16, 2015, 10:49:09 AM by luthermarcus
 #13068

yes, mainly because of a corrupted share chain (of P2Pool).
verified share can't rease, too ... in this case of many disconnected clients.

i must have deleted 3 times (in 1 week) the sharechain of P2Pool to have a standard P2Pool reaction.

probably the old v13 that it tries to inject shares ... again.

I too experienced a corrupted p2pool sharechain & had to delete/redownload a new one a few days ago. It seems like p2pool is not fully banning older v13 releases, which seems to be causing the problem. Since I started proactively banning bad peers manually the problems have all but gone, but having to constantly monitor my logs for repeat offending IP's is a real bind & very laborious.
Also, looking around the various p2pool node finder sites, there's still a multitude of v13 nodes still mining away regardless - which makes me wonder if these nodes are actually still getting paid, as there have been zero complaints here about unpaid blocks. If these outdated nodes are still getting paid, that would mean that their owners are still blissfully unaware of any required upgrade & would also explain why there are still so many older nodes humming away......

How do you figure your sharechain was corrupted?
Mine seems to be kicking peers very often. Could that traffic just be rerouted to a dead zone where we dont have to worry about them affecting the majority who actually try to keep things up to date. It also ends up sending them a share before it kicks them could that be slowing the network down.

Just in case someone wants to block these peers manually i do this on windows.
https://serverfault.com/questions/117420/windows-firewall-ip-ban

Donate Bitcoin
1Mz7ZHxPhoH1ZK2yQvo62NdHvvsS2quhzc
Donate TRX
TB3WiLEj6iuSBU5tGUKyZkjB4vqrBDvoYM
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 16, 2015, 10:00:35 AM
 #13069

How do you figure your sharechain was corrupted?

I'm not sure, I can only put it down to the bad peers, which I've now blocked - no problems since  Smiley
rav3n_pl
Legendary
*
Offline Offline

Activity: 1360
Merit: 1000


Don`t panic! Organize!


View Profile WWW
July 16, 2015, 10:23:32 AM
 #13070

Howto get latency of bitcoin-qt low? I am just now around 0.5s

Install bitcoin v0.11. Add to your bitcoin.conf:

maxconnections=10

then run bitcoin-qt and look connections in debug witdow. Choose IPs with lowest latencies and add them to your bitcoin.conf. Add there not more then 4 the best.

addnode=x.x.x.x
Bull.
You can do same adding
timeout=150
BUT it will NOT give you better GBT.

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
Some stuff on https://github.com/Rav3nPL/
luthermarcus
Full Member
***
Offline Offline

Activity: 213
Merit: 100



View Profile
July 16, 2015, 10:56:50 AM
 #13071

Howto get latency of bitcoin-qt low? I am just now around 0.5s

Install bitcoin v0.11. Add to your bitcoin.conf:

maxconnections=10

then run bitcoin-qt and look connections in debug witdow. Choose IPs with lowest latencies and add them to your bitcoin.conf. Add there not more then 4 the best.

addnode=x.x.x.x
Bull.
You can do same adding
timeout=150
BUT it will NOT give you better GBT.

Hey I've been trying to optimize my bitcoind for p2pool any tips. As to settings, what kind of peers I should allow, where to find those peers, etc.
What do you think about his I been banning rbf peers kind of an actives activity.
https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg08422.html
Like that you represent in your tag name!

Donate Bitcoin
1Mz7ZHxPhoH1ZK2yQvo62NdHvvsS2quhzc
Donate TRX
TB3WiLEj6iuSBU5tGUKyZkjB4vqrBDvoYM
luthermarcus
Full Member
***
Offline Offline

Activity: 213
Merit: 100



View Profile
July 16, 2015, 12:56:06 PM
 #13072

How do you figure your sharechain was corrupted?

I'm not sure, I can only put it down to the bad peers, which I've now blocked - no problems since  Smiley

Ok so i started to block peers who are not up to date and now i am seeing a spam request of parent share over and over which will not go away.

Donate Bitcoin
1Mz7ZHxPhoH1ZK2yQvo62NdHvvsS2quhzc
Donate TRX
TB3WiLEj6iuSBU5tGUKyZkjB4vqrBDvoYM
Duce
Full Member
***
Offline Offline

Activity: 175
Merit: 100


View Profile
July 16, 2015, 01:36:36 PM
 #13073

Howto get latency of bitcoin-qt low? I am just now around 0.5s

Install bitcoin v0.11. Add to your bitcoin.conf:

maxconnections=10

then run bitcoin-qt and look connections in debug witdow. Choose IPs with lowest latencies and add them to your bitcoin.conf. Add there not more then 4 the best.

addnode=x.x.x.x
Bull.
You can do same adding
timeout=150
BUT it will NOT give you better GBT.

Hey I've been trying to optimize my bitcoind for p2pool any tips. As to settings, what kind of peers I should allow, where to find those peers, etc.
What do you think about his I been banning rbf peers kind of an actives activity.
https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg08422.html
Like that you represent in your tag name!

I update my P2P to version 14.0-9 and bitcoin to v0.11 and my GBT is now <1s as it was before the change from v13 to v14. I have not blocked any peers as the application seems to be doing it's job since now after the initial P2P v14 was not able to block v13 peers (thanks forrestv). My GBT had been at >3s before this last update. Can't say this is a coincident or not just providing my status.
kano
Legendary
*
Offline Offline

Activity: 2730
Merit: 1103


Linux since 1997 RedHat 4


View Profile
July 16, 2015, 01:43:34 PM
 #13074

It's transaction related.

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #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!
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1344
Merit: 1015


Mine at Jonny's Pool


View Profile WWW
July 16, 2015, 03:29:08 PM
 #13075

Not sure why your front-end is doing this windpath, but it's showing the latest block found by p2pool as orphaned:



That block wasn't orphaned...

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
windpath
Legendary
*
Offline Offline

Activity: 1235
Merit: 1001


View Profile WWW
July 16, 2015, 05:03:15 PM
 #13076

Not sure why your front-end is doing this windpath, but it's showing the latest block found by p2pool as orphaned:

http://i.imgur.com/HMCWsis.png

That block wasn't orphaned...

It's fixed now, thanks. It happens when I restart bitcoin and leave the node running, forgot to correct it yesterday Smiley
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1344
Merit: 1015


Mine at Jonny's Pool


View Profile WWW
July 16, 2015, 05:11:36 PM
 #13077

No problem.  I just happened to check the blocks and saw that was orphaned... and I was like, "Huh?  I swear I got BTC for that... let me check."

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
majsta
Hero Member
*****
Offline Offline

Activity: 558
Merit: 500


kittehcoin.info


View Profile
July 16, 2015, 05:44:07 PM
 #13078

I was building p2pool for joincoin.
https://github.com/joincoin/joincoin
Quote
from p2pool.bitcoin import networks

PARENT = networks.nets['joincoin']
SHARE_PERIOD = 5 # seconds
CHAIN_LENGTH = 24*60*60//10 # shares
REAL_CHAIN_LENGTH = 24*60*60//10 # shares
TARGET_LOOKBEHIND = 200 # shares
SPREAD = 50 # blocks
IDENTIFIER = '27392307bca64c44'.decode('hex')
PREFIX = '27392307bca64c44'.decode('hex')
P2P_PORT = 9050
MIN_TARGET = 0
MAX_TARGET = 2**256//2**20 - 1
PERSIST = False
WORKER_PORT = 9241
BOOTSTRAP_ADDRS = '194.135.90.171 194.135.92.4 194.135.94.113'.split(' ')
ANNOUNCE_CHANNEL = '#p2pool-alt'
VERSION_CHECK = lambda v: True
VERSION_WARNING = lambda v: None

Quote
import os
import platform

from twisted.internet import defer

from .. import data, helper
from p2pool.util import pack


P2P_PREFIX = 'f1b4dc9e'.decode('hex') #pchmessagestart
P2P_PORT = 17941
ADDRESS_VERSION = 43 #pubkey_address
RPC_PORT = 17942
RPC_CHECK = defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            'joincoinaddress' in (yield bitcoind.rpc_help()) and
            not (yield bitcoind.rpc_getinfo())['testnet']
        ))

SUBSIDY_FUNC = lambda height: 2*100000000
POW_FUNC = lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data))
BLOCK_PERIOD = 45 # s
SYMBOL = 'J'
CONF_FILE_FUNC = lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'joincoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/joincoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.joincoin'), 'joincoin.conf')
BLOCK_EXPLORER_URL_PREFIX = 'http://cryptexplorer.com/block/'
ADDRESS_EXPLORER_URL_PREFIX = 'http://cryptexplorer.com/address/'
TX_EXPLORER_URL_PREFIX = 'http://cryptexplorer.com/tx/'
SANE_TARGET_RANGE = (2**256//1000000000 - 1, 2**256//1000 - 1)
DUMB_SCRYPT_DIFF = 2**16
DUST_THRESHOLD = 0.03e8

Quote
server=1
listen=1
daemon=1
rpcuser=majsta
rpcpassword=x

rpcallowip=*
rpcallowip=127.0.0.1
rpcallowip=192.168.1.99
rpcallowip=192.168.1.103
rpcallowip=192.168.1.104
rpcallowip=192.168.1.105

rpcport=17942
port=17941
rpcconnect=*
rpcconnect=127.0.0.1
rpcconnect=192.168.1.99
rpcconnect=192.168.1.103
rpcconnect=192.168.1.104
rpcconnect=192.168.1.105
algo=scrypt


addnode=24.38.16.6
addnode=194.135.90.171
addnode=194.135.92.4
addnode=194.135.94.113
addnode=gdhtrc7qoh3qowvf.onion:17941
addnode=jsghu6d5lop757ml.onion:17941
addnode=iamzedqd6kmzi3qs.onion:17941
addnode=nwjw2badoulwc4yi.onion:17941
addnode=7wc53o5c3ox62azh.onion:17941
addnode=53zy47p5wly5penk.onion:17941
addnode=5k7xsbnnw3mpotx6.onion:17941
addnode=b2mgu5dvcw3m7cxw.onion:17941


Does anyone have ideas what is going on?

notbatman
Legendary
*
Offline Offline

Activity: 1848
Merit: 1013



View Profile
July 16, 2015, 06:06:53 PM
 #13079

I was building p2pool for joincoin.
https://github.com/joincoin/joincoin
Quote
from p2pool.bitcoin import networks

PARENT = networks.nets['joincoin']
SHARE_PERIOD = 5 # seconds
CHAIN_LENGTH = 24*60*60//10 # shares
REAL_CHAIN_LENGTH = 24*60*60//10 # shares
TARGET_LOOKBEHIND = 200 # shares
SPREAD = 50 # blocks
IDENTIFIER = '27392307bca64c44'.decode('hex')
PREFIX = '27392307bca64c44'.decode('hex')
P2P_PORT = 9050
MIN_TARGET = 0
MAX_TARGET = 2**256//2**20 - 1
PERSIST = False
WORKER_PORT = 9241
BOOTSTRAP_ADDRS = '194.135.90.171 194.135.92.4 194.135.94.113'.split(' ')
ANNOUNCE_CHANNEL = '#p2pool-alt'
VERSION_CHECK = lambda v: True
VERSION_WARNING = lambda v: None

Quote
import os
import platform

from twisted.internet import defer

from .. import data, helper
from p2pool.util import pack


P2P_PREFIX = 'f1b4dc9e'.decode('hex') #pchmessagestart
P2P_PORT = 17941
ADDRESS_VERSION = 43 #pubkey_address
RPC_PORT = 17942
RPC_CHECK = defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            'joincoinaddress' in (yield bitcoind.rpc_help()) and
            not (yield bitcoind.rpc_getinfo())['testnet']
        ))

SUBSIDY_FUNC = lambda height: 2*100000000
POW_FUNC = lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data))
BLOCK_PERIOD = 45 # s
SYMBOL = 'J'
CONF_FILE_FUNC = lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'joincoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/joincoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.joincoin'), 'joincoin.conf')
BLOCK_EXPLORER_URL_PREFIX = 'http://cryptexplorer.com/block/'
ADDRESS_EXPLORER_URL_PREFIX = 'http://cryptexplorer.com/address/'
TX_EXPLORER_URL_PREFIX = 'http://cryptexplorer.com/tx/'
SANE_TARGET_RANGE = (2**256//1000000000 - 1, 2**256//1000 - 1)
DUMB_SCRYPT_DIFF = 2**16
DUST_THRESHOLD = 0.03e8

Quote
server=1
listen=1
daemon=1
rpcuser=majsta
rpcpassword=x

rpcallowip=*
rpcallowip=127.0.0.1
rpcallowip=192.168.1.99
rpcallowip=192.168.1.103
rpcallowip=192.168.1.104
rpcallowip=192.168.1.105

rpcport=17942
port=17941
rpcconnect=*
rpcconnect=127.0.0.1
rpcconnect=192.168.1.99
rpcconnect=192.168.1.103
rpcconnect=192.168.1.104
rpcconnect=192.168.1.105
algo=scrypt


addnode=24.38.16.6
addnode=194.135.90.171
addnode=194.135.92.4
addnode=194.135.94.113
addnode=gdhtrc7qoh3qowvf.onion:17941
addnode=jsghu6d5lop757ml.onion:17941
addnode=iamzedqd6kmzi3qs.onion:17941
addnode=nwjw2badoulwc4yi.onion:17941
addnode=7wc53o5c3ox62azh.onion:17941
addnode=53zy47p5wly5penk.onion:17941
addnode=5k7xsbnnw3mpotx6.onion:17941
addnode=b2mgu5dvcw3m7cxw.onion:17941


Does anyone have ideas what is going on?

You've limited your connections to 8 and like the message says all slots are being used. Either remove '--max-conns 8' and '--outgoing-conns 4' or increase the number of connections you're allowing.
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 16, 2015, 06:43:11 PM
 #13080

Or just restart your coin daemon - p2pool will then kick in  Wink
Pages: « 1 ... 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 [654] 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 ... 814 »
  Print  
 
Jump to:  

Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
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!