|
|
|
You get merit points when someone likes your post enough to give you some. And for every 2 merit points you receive, you can send 1 merit point to someone else!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
CohibAA
|
|
September 10, 2015, 07:07:07 PM |
|
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).
|
|
|
|
Matt Corallo (OP)
|
|
September 10, 2015, 09:13:22 PM |
|
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). Yea, I didnt bother turning off compression, but set the mempool query code to only select a smaller set. This has resulted in a huge drop in compression effeciency (see graphs linked above), but it does till work...
|
|
|
|
Matt Corallo (OP)
|
|
September 25, 2015, 10:53:57 PM |
|
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.
|
|
|
|
p3yot33at3r
|
|
November 03, 2015, 09:25:49 PM |
|
Is the network down?
|
|
|
|
Matt Corallo (OP)
|
|
November 04, 2015, 10:47:44 AM |
|
Is the network down? No known issues atm.
|
|
|
|
p3yot33at3r
|
|
November 05, 2015, 01:46:15 AM |
|
Is the network down? No known issues atm. Sorted, my dns were playing up....
|
|
|
|
Matt Corallo (OP)
|
|
November 11, 2015, 09:27:43 PM |
|
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.
|
|
|
|
Matt Corallo (OP)
|
|
November 11, 2015, 09:28:06 PM |
|
If you're not, update coming soon that you should really upgrade to as well .
|
|
|
|
kano
Legendary
Offline
Activity: 4494
Merit: 1808
Linux since 1997 RedHat 4
|
|
November 11, 2015, 10:08:25 PM Last edit: November 11, 2015, 10:25:51 PM by kano |
|
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: [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 008f0 was f2pool
|
|
|
|
Matt Corallo (OP)
|
|
November 12, 2015, 04:23:15 AM |
|
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).
|
|
|
|
-ck
Legendary
Offline
Activity: 4102
Merit: 1632
Ruu \o/
|
|
November 12, 2015, 11:18:16 AM |
|
Bytes on the wire seem lower than ever, good work.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
kano
Legendary
Offline
Activity: 4494
Merit: 1808
Linux since 1997 RedHat 4
|
|
November 12, 2015, 01:49:02 PM |
|
Yeah now seeing full 1M blocks with as low as 4k on the wire ... very nice
|
|
|
|
kano
Legendary
Offline
Activity: 4494
Merit: 1808
Linux since 1997 RedHat 4
|
|
November 13, 2015, 03:10:53 AM Last edit: November 13, 2015, 03:32:26 AM by kano |
|
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)
|
|
|
|
Matt Corallo (OP)
|
|
November 13, 2015, 08:45:32 AM |
|
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.
|
|
|
|
Matt Corallo (OP)
|
|
November 23, 2015, 06:03:21 AM |
|
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.
|
|
|
|
o_solo_miner
Legendary
Offline
Activity: 2451
Merit: 1476
-> morgen, ist heute, schon gestern <-
|
|
December 14, 2015, 10:47:20 PM |
|
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
|
from the creator of CGMiner http://solo.ckpool.org for Solominers paused: passthrough for solo.ckpool.org => stratum+tcp://rfpool.org:3334
|
|
|
e46btc
|
|
December 15, 2015, 05:54:56 AM |
|
Use bitcoind 8333 port, but not RPC port 8332
|
|
|
|
o_solo_miner
Legendary
Offline
Activity: 2451
Merit: 1476
-> morgen, ist heute, schon gestern <-
|
|
December 15, 2015, 10:14:14 AM Last edit: December 15, 2015, 07:10:48 PM by o_solo_miner |
|
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!
|
from the creator of CGMiner http://solo.ckpool.org for Solominers paused: passthrough for solo.ckpool.org => stratum+tcp://rfpool.org:3334
|
|
|
|