Topic: Re: How (and why) to use the Relay Network - page 4. (Read 695 times)
Hi, i am using the windows exe version. Is it normal for it to be using 40+ % CPU usage on an i5 3570K at 4Ghz? Just wanted to check to see if it was perhaps something wrong.
Thank you Matt, I will try it on my Debian machine (bitcoind is also there) and for shure it will work.
I saw you on Youtube explaining the hole thing, wich helped a lot to understand the reason for it.
TCP sucks
I saw you on Youtube explaining the hole thing, wich helped a lot to understand the reason for it.
TCP sucks
The relay client will gladly work on a separate machine (most larger users do this, I believe), but is really only designed to run on the same LAN/on a network with incredibly low latency and great bandwidth between your relay client and your bitcoind. As for running it on Windows, it should work, in theory, but recent comments by other windows users indicate that it may not work at all (see https://github.com/TheBlueMatt/RelayNode/issues/16). Since I dont have anything running Windows I cant test it outside of Wine.
TY, changed that and opend the port 8333 to be on the linux machine.
Edit:
should I insert an addnode for the relay in the bitcoind.conf or using connect?
because the relayclient is running on a different machine, or is it generaly not possible to
have them seperated?
Maybe clear up some (stupid) questions:
What kind of Windows version the client is desigend to run on?
Is it possible to build a linux client version?
Well the title of this thread is "How a miner use the relay Network", the why is clearly stated but I realy miss the how to!
Well, is not my day today, sry!
Edit:
should I insert an addnode for the relay in the bitcoind.conf or using connect?
because the relayclient is running on a different machine, or is it generaly not possible to
have them seperated?
Maybe clear up some (stupid) questions:
What kind of Windows version the client is desigend to run on?
Well, is not my day today, sry!
Use bitcoind 8333 port, but not RPC port 8332
simple question:
is there a "how to" written somewhere where I can read a bit on how to install and use it for
bitcoind on a Linux System and cgminer on windows?
I tryed => relaynetworkclient.exe 192.168.2.112 8332 public.eu.relay.mattcorallo.com
where 192.168.2.112 is my bitcoind server on port 8332
The programm run on win but i see no messages or what so ever?
Using server public.eu.relay.mattcorallo.com is the only info it displayes
is there a "how to" written somewhere where I can read a bit on how to install and use it for
bitcoind on a Linux System and cgminer on windows?
I tryed => relaynetworkclient.exe 192.168.2.112 8332 public.eu.relay.mattcorallo.com
where 192.168.2.112 is my bitcoind server on port 8332
The programm run on win but i see no messages or what so ever?
Using server public.eu.relay.mattcorallo.com is the only info it displayes
Is anyone still accessing the Relay Network via the P2P protocol (ie via -addnode)? I would very much like to turn that off in the coming days....speak now or forever get your connections -j REJECT'ed.
Had 2 relay issues in the last few hours.
One where it went down for a short while.
Another, at the moment, where I'm only seeing blocks coming from the relay (for the last 3 blocks), no txns coming or going - so the blocks are about the same size 'on the wire'
It's also slower than one of my non-relay bitcoinds so I'm guessing there's a problem?
(code is of course current as at ea55c37)
Edit: restart (temporarily) fixed it, but it only lasted 327 txns until it stopped again.
(and a second restart lasted 326)
There were some server issues this evening (PST). I'm monitoring closely but expect some hiccups in the next day or two. Client restarts should (hopefully) not be required as they will reset when your connection to the server is reset, but do notify me if a client restart fixes things. One where it went down for a short while.
Another, at the moment, where I'm only seeing blocks coming from the relay (for the last 3 blocks), no txns coming or going - so the blocks are about the same size 'on the wire'
It's also slower than one of my non-relay bitcoinds so I'm guessing there's a problem?
(code is of course current as at ea55c37)
Edit: restart (temporarily) fixed it, but it only lasted 327 txns until it stopped again.
(and a second restart lasted 326)
Had 2 relay issues in the last few hours.
One where it went down for a short while.
Another, at the moment, where I'm only seeing blocks coming from the relay (for the last 3 blocks), no txns coming or going - so the blocks are about the same size 'on the wire'
It's also slower than one of my non-relay bitcoinds so I'm guessing there's a problem?
(code is of course current as at ea55c37)
Edit: restart (temporarily) fixed it, but it only lasted 327 txns until it stopped again.
(and a second restart lasted 326)
One where it went down for a short while.
Another, at the moment, where I'm only seeing blocks coming from the relay (for the last 3 blocks), no txns coming or going - so the blocks are about the same size 'on the wire'
It's also slower than one of my non-relay bitcoinds so I'm guessing there's a problem?
(code is of course current as at ea55c37)
Edit: restart (temporarily) fixed it, but it only lasted 327 txns until it stopped again.
(and a second restart lasted 326)
Yeah now seeing full 1M blocks with as low as 4k on the wire ... very nice 
Bytes on the wire seem lower than ever, good work.
Network performance for the past week or so has been rather dismal. 5 seconds seems pretty excessive, but either way I just pushed a rather large update to github and on the servers. It should improve compression a ton (and also drops connections for those using many-months-old clients).
Yeah as you probably know already
Those numbers I posted in the solo ckpool thread about the first solo ckpool orphan, they were my log of relay network times, not my pool bitcoind times.
So if f2pool is using the relay network, it took almost 5seconds for the east coast relay to see the f2pool block ...
Edit:
008f0 was f2pool
Those numbers I posted in the solo ckpool thread about the first solo ckpool orphan, they were my log of relay network times, not my pool bitcoind times.
So if f2pool is using the relay network, it took almost 5seconds for the east coast relay to see the f2pool block ...
Edit:
Code:
[2015-11-11 14:00:48.440+00] 0000000000000000045792b02a12ecf0767d50d392471a3fded2371d56ab7b8a recv'd, size 998146 with 111285 bytes on the wire
[2015-11-11 14:00:53.293+00] 000000000000000008f0667bc0b60726ea2035d1bc6ab1910f81f2ed19d8741e recv'd, size 999907 with 954717 bytes on the wire
00457 was solo[2015-11-11 14:00:53.293+00] 000000000000000008f0667bc0b60726ea2035d1bc6ab1910f81f2ed19d8741e recv'd, size 999907 with 954717 bytes on the wire
008f0 was f2pool
If you're not, update coming soon that you should really upgrade to as well .
.
If you're one of the many users still (somehow) using version "toucan twink" you need to upgrade NOW. At some point in the next day or two the servers will start simply dropping your connections.
Sorted, my dns were playing up....
Is the network down? 
No known issues atm.
Is the network down?
Oops, I didnt bother to update this thread when I switched servers around. Here are the latest updates from bitcoinrelaynetwork.org, copied:
September 16th: New topology is now active, but having some issues with GFW. New HK node is thus not yet available to connect to as it might have to move again. Got a new IP for the HK server, which seems to have fixed the GFW issues, so it has been enabled and the stats have been reset and reenabled.
September 15th: DigitalOcean Singapore's generally shitty service finally pissed me off enough and I destroyed that server when it went down yet again.Waiting on a new Hong Kong server to be provisioned from a new provider and switched to a different host in Singapore which has much better routing and will be used as a hop-only node (ie be used for transit and will not be connectable by clients). Stats are broken but the rest of the network should generally not have any problems.
September 16th: New topology is now active
September 15th: DigitalOcean Singapore's generally shitty service finally pissed me off enough and I destroyed that server when it went down yet again.
So currently the relay network *really* cant handle the spam attacks, because of things that need changed in the way mining works in bitcoin - see https://github.com/TheBlueMatt/RelayNode/issues/12 and https://github.com/bitcoin/bitcoin/issues/6531. When the next spam attacks start, expect block compression to go from 1/2 packets quite often to 500k very quickly (see-also http://bitcoinrelaynetwork.org/stats.html, though without changes I'll have to just turn off compression completely because of bandwidth costs, probably).
Matt, I just wanted to thank you for your great work on this and other projects.
FWIW, my RelayNode has not had any problems during the last 24+ hours of increased transaction activity (and for a pretty long time before).
Jump to: