raidbak
Newbie
 Offline
Activity: 19
Merit: 0
|
 |
December 11, 2016, 07:11:34 AM |
|
HI all i was interested in setting up a rely node for the Kano pool if you guys would like. i dont have great bandwidth 10MB but i can hoist a machine in my DC to support the pool if it helps
Nah, it doesn't really help much. Getting the blocks to the relay is the basics of getting them to other pools fast to reduce the possibility of orphans, without going down the needless path of SPV greed that most of the Chinese pools have - they may gain a couple hundred milliseconds at the most - their greed is beyond understanding - since it does very little if anything, except risk the bitcoin network due to their SPV mining. We get them to every single relay (both the old relay and the newer fibre relay) about as fast as is possible - quite literally faster than any other pool. Great information! thanks well anything to help just let me know |
|
|
|
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4494
Merit: 1808
Linux since 1997 RedHat 4
|
|
December 11, 2016, 07:13:20 AM |
|
Web logins are disabled at the moment due to some brain-dead script kiddy pointing a botnet at the login page (~6:46 UTC)
As usual I'll re-enable it later.
|
|
|
|
firetreeactual
Legendary
Offline
Activity: 952
Merit: 1003
|
|
December 11, 2016, 03:46:17 PM |
|
My full node has been shut down. Apparently Oceanic, despite a specific "no data cap" policy, has decided to drop back ten and punt, citing "fair use." They blocked 8333 on their end (so my opening it on the modem does no good). I was only using around 200GB/mo (I don't do a lot of bandwidth otherwise), and maybe 80 or 90 connections on Core at a time. A rep said something to the effect of "we don't support mining," and then couldn't find words when I explained how this part of Bitcoin is not mining. Oh, well...  bitcoin.conf  port=8888 (etc) Thanks...next step. You're not mining to it so there is no need to have lots of connections either. maxconnections=12 12 is the minimum you can reliably run it with. Just got up...no coffee yet...argh. Anyway...thanks for that. What I had been doing was port forwarded 8333 on the cable modem, and then through my router likewise. Worked fine for quite a while. I've got 16 threads set on the Core options, and inbound connections allowed, no proxy. When the node was running "well," I had anywhere from 70 to 90 connections at a time...by its own devices, so to speak. Otherwise, I don't "get down" to this level at all and am functionally clueless in some regards...but have a passion for learning new stuff. I'll work on it more later today when I get back from town. It's no deal breaker...just a matter of principle, and I feel better about contributing. Mine on... |
To infinity and beyond...on two 741s and one of only 3...nope, make that 4...full nodes in Hawaii...on <30A. (I have other gear on the Hoth ice planet)
|
|
|
|
gt_addict
|
|
December 11, 2016, 04:44:38 PM |
|
BLOCK!!! wetsuit.594-1
|
**SUPPORT SIDEHACK** Miner Development Donations to: 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
Donations/Tips to:- 1GTADDicTXD1uachKKgW24DZDxDGhSMdRa
Join Bitconnect: https://bitconnect.co/?ref=gtaddict
|
|
|
|
wmabern
|
|
December 11, 2016, 04:46:55 PM |
|
Block trail has that block going to BW Pool. Is that an error or have we missed again?
|
BITMIXER.IO Gone Baby, Gone.. ;-)
Not any good sig campaigns out there that I want!
|
|
|
|
gt_addict
|
|
December 11, 2016, 04:49:15 PM |
|
Block trail has that block going to BW Pool. Is that an error or have we missed again?
Just got a notification from ckpool app "Block 442979 solved by wetsuit.594-1". Could well be an error I suppose   |
**SUPPORT SIDEHACK** Miner Development Donations to: 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
Donations/Tips to:- 1GTADDicTXD1uachKKgW24DZDxDGhSMdRa
Join Bitconnect: https://bitconnect.co/?ref=gtaddict
|
|
|
|
wmabern
|
|
December 11, 2016, 04:51:06 PM |
|
Block trail has that block going to BW Pool. Is that an error or have we missed again?
Just got a notification from ckpool app "Block 442979 solved by wetsuit.594-1". Could well be an error I suppose Yes, I saw that. But if you click on the block link, it takes you to Blocktrail. There they are showing BW Pool solved it. I guess we will find out shortly. Damn!! Fing orphan!  |
BITMIXER.IO Gone Baby, Gone.. ;-)
Not any good sig campaigns out there that I want!
|
|
|
|
wmabern
|
|
December 11, 2016, 04:57:32 PM |
|
December has not been extremely kind to us.  |
BITMIXER.IO Gone Baby, Gone.. ;-)
Not any good sig campaigns out there that I want!
|
|
|
ZedZedNova
Sr. Member
Offline
Activity: 475
Merit: 265
Ooh La La, C'est Zoom!
|
|
December 11, 2016, 04:58:43 PM |
|
My full node has been shut down. Apparently Oceanic, despite a specific "no data cap" policy, has decided to drop back ten and punt, citing "fair use." They blocked 8333 on their end (so my opening it on the modem does no good). I was only using around 200GB/mo (I don't do a lot of bandwidth otherwise), and maybe 80 or 90 connections on Core at a time. A rep said something to the effect of "we don't support mining," and then couldn't find words when I explained how this part of Bitcoin is not mining. Oh, well... bitcoin.conf port=8888 (etc) Thanks...next step. You're not mining to it so there is no need to have lots of connections either. maxconnections=12 12 is the minimum you can reliably run it with. Just got up...no coffee yet...argh. Anyway...thanks for that. What I had been doing was port forwarded 8333 on the cable modem, and then through my router likewise. Worked fine for quite a while. I've got 16 threads set on the Core options, and inbound connections allowed, no proxy. When the node was running "well," I had anywhere from 70 to 90 connections at a time...by its own devices, so to speak. Otherwise, I don't "get down" to this level at all and am functionally clueless in some regards...but have a passion for learning new stuff. I'll work on it more later today when I get back from town. It's no deal breaker...just a matter of principle, and I feel better about contributing. Mine on... Not sure if you have the option on your cable modem (it's been ~16 years since I worked with them directly), but on my DSL modem I have the option to have it run in bridged mode. So instead of the cable/DSL modem having the "public" IP address, your router does, and the modem just passes the traffic through. You could then set up your router to port forward as usual, and the cable modem treats it as normal traffic. |
No mining at the moment.
|
|
|
|
DarKSm0ke
|
|
December 11, 2016, 04:59:51 PM |
|
Block is orphan Not good :/ |
|
|
|
|
|
gt_addict
|
|
December 11, 2016, 05:05:36 PM |
|
Well two payments have appeared in my wallet from the pool even though it's an orphan. Let's hope they confirm soon.
|
**SUPPORT SIDEHACK** Miner Development Donations to: 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
Donations/Tips to:- 1GTADDicTXD1uachKKgW24DZDxDGhSMdRa
Join Bitconnect: https://bitconnect.co/?ref=gtaddict
|
|
|
|
wmabern
|
|
December 11, 2016, 05:13:44 PM |
|
Well two payments have appeared in my wallet from the pool even though it's an orphan. Let's hope they confirm soon.
Nothing in my Core wallet. |
BITMIXER.IO Gone Baby, Gone.. ;-)
Not any good sig campaigns out there that I want!
|
|
|
clgrissom3
Legendary
Offline
Activity: 1722
Merit: 1032
Carl, aka Sonny :)
|
|
December 11, 2016, 05:31:08 PM |
|
Block trail has that block going to BW Pool. Is that an error or have we missed again?
Just got a notification from ckpool app "Block 442979 solved by wetsuit.594-1". Could well be an error I suppose Yes, I saw that. But if you click on the block link, it takes you to Blocktrail. There they are showing BW Pool solved it. I guess we will find out shortly. Damn!! Fing orphan! Chin up people! We usually get on a block roll after an orphan like this hits us!  |
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4494
Merit: 1808
Linux since 1997 RedHat 4
|
|
December 11, 2016, 06:00:43 PM |
|
Yeah the only thing I can find to say why it was an orphan is that it would appear that data going in and out of the GFW was really slowed down.
The CN node for sending out blocks didn't get it until 99 seconds after we found the block.
So basically it would seem that the network was broken for a short while there and no one inside china saw blocks quickly from outside china (and visa versa)
All our other nodes got the share less than 100ms after it arrived at the pool and submitted it to their bitcoinds
The old relays show everything OK, but it looks like Matt turned off the bejing relay about 15 minutes before our block.
The new fibre relay uses bitcoind (no special relay program) so the logs are basically useless to work out for sure what happened.
|
|
|
|
|
wmabern
|
|
December 11, 2016, 06:03:00 PM |
|
Yeah the only thing I can find to say why it was an orphan is that it would appear that data going in and out of the GFW was really slowed down.
The CN node for sending out blocks didn't get it until 99 seconds after we found the block.
So basically it would seem that the network was broken for a short while there and no one inside china saw blocks quickly from outside china (and visa versa)
All our other nodes got the share less than 100ms after it arrived at the pool and submitted it to their bitcoinds
The old relays show everything OK, but it looks like Matt turned off the bejing relay about 15 minutes before our block.
The new fibre relay uses bitcoind (no special relay program) so the logs are basically useless to work out for sure what happened.
Who is this "Matt" and why would he shut it down? Is it back up now? Thanks. |
BITMIXER.IO Gone Baby, Gone.. ;-)
Not any good sig campaigns out there that I want!
|
|
|
kano (OP)
Legendary
Offline
Activity: 4494
Merit: 1808
Linux since 1997 RedHat 4
|
|
December 11, 2016, 06:08:48 PM |
|
Yeah the only thing I can find to say why it was an orphan is that it would appear that data going in and out of the GFW was really slowed down.
The CN node for sending out blocks didn't get it until 99 seconds after we found the block.
So basically it would seem that the network was broken for a short while there and no one inside china saw blocks quickly from outside china (and visa versa)
All our other nodes got the share less than 100ms after it arrived at the pool and submitted it to their bitcoinds
The old relays show everything OK, but it looks like Matt turned off the bejing relay about 15 minutes before our block.
The new fibre relay uses bitcoind (no special relay program) so the logs are basically useless to work out for sure what happened.
Who is this "Matt" and why would he shut it down? Is it back up now? Thanks. He's the bitcoin dev who runs the relay networks. Anyway ... our block was about 1.8 seconds before the other block - 16:43:57.141 UTC after processing and being accepted at the pool bitcoind The CN node saw the other block at 16:43:58.910 - so reasonably long after we got ours. Seems the fibre relay didn't help at all, but as I said above, I can't tell what the new fibre relay network did |
|
|
|
|
wmabern
|
|
December 11, 2016, 06:10:28 PM |
|
Who is this "Matt" and why would he shut it down?
Is it back up now?
Thanks.
He's the bitcoin dev who runs the relay networks. [/quote] Thank you. |
BITMIXER.IO Gone Baby, Gone.. ;-)
Not any good sig campaigns out there that I want!
|
|
|
firetreeactual
Legendary
Offline
Activity: 952
Merit: 1003
|
|
December 11, 2016, 06:19:21 PM |
|
Not sure if you have the option on your cable modem (it's been ~16 years since I worked with them directly), but on my DSL modem I have the option to have it run in bridged mode. So instead of the cable/DSL modem having the "public" IP address, your router does, and the modem just passes the traffic through. You could then set up your router to port forward as usual, and the cable modem treats it as normal traffic.
Yup...it's one of their new Technicolor all-in-ones. Not a bad device, really...just don't want/need it...but yeah, I basically can turn it off to anything but through traffic, and handle the rest on my R6700, which is what I had been doing. That hasn't helped. I'll try the .conf tweaks a bit later. Thanks for the input...made sense. |
To infinity and beyond...on two 741s and one of only 3...nope, make that 4...full nodes in Hawaii...on <30A. (I have other gear on the Hoth ice planet)
|
|
|
firetreeactual
Legendary
Offline
Activity: 952
Merit: 1003
|
|
December 11, 2016, 06:54:23 PM |
|
Well two payments have appeared in my wallet from the pool even though it's an orphan. Let's hope they confirm soon.
I suspect those were triggered by 442732. |
To infinity and beyond...on two 741s and one of only 3...nope, make that 4...full nodes in Hawaii...on <30A. (I have other gear on the Hoth ice planet)
|
|
|
kano (OP)
Legendary
Offline
Activity: 4494
Merit: 1808
Linux since 1997 RedHat 4
|
|
December 11, 2016, 07:39:30 PM |
|
OK, so it seems the answer to why the orphan happened is as follows:
1) 15 minutes before the orphan, the old relay stopped working in china
2) the new fibre relay isn't working
3) there was a 99 second GFW delay sending our block (share) to our china node
Result ... orphan ... even though we found it 1.8 seconds before them.
|
|
|
|
|
