Provide bloom services to whitelisted nodes.

rebroad commented at 7:59 am on August 25, 2016: contributor

Don’t disconnect whitelisted nodes when bloom services are requested.

in src/main.cpp: in 6ab8fd4fac outdated

4899-            pfrom->fDisconnect = true;
4900-            return false;
4901-        }
4902+               strCommand == NetMsgType::FILTERCLEAR)) {
4903+        LOCK(cs_main);
4904+        Misbehaving(pfrom->GetId(), 5);

rebroad commented at 8:01 am on August 25, 2016:

The idea here is that it will be banned if it continues to connect and request bloom services 20 times… I suspect the misbehave count gets reset upon disconnection though..!

laanwj commented at 8:13 am on August 25, 2016: member

NACK on overloading whitelisting even further. It’s already not well-defined nor documented.

jonasschnelli added the label P2P on Aug 25, 2016

paveljanik commented at 12:07 pm on August 25, 2016: contributor

NACK

I doesn’t even compile! It is fWhitelisted and not fWhiteListed.

rebroad renamed this:
~~Provide bloom services to whitelisted nodes.~~
{WIP} Provide bloom services to whitelisted nodes.
on Aug 26, 2016

rebroad force-pushed on Aug 26, 2016

rebroad commented at 3:35 am on August 26, 2016: contributor

@laanwj Where would be the best place to document this please? I would certainly be willing to give this a go. My thinking is that whitelisted peers are nodes that we trust to not do anything detrimental or misbehave. They are usually nodes we have control of. Therefore, in this example, we could set up a node that doesn’t advertise BLOOM and doesn’t provide bloom services to nodes other than our own. This would allow us to configure a SPV node to use our node but not let it be used by other SPV nodes. Many SPV nodes, allow it to be configured which full-node to use and trust, but currently there isn’t a way to set up a full-node that only provides SPV services to specific nodes (as far as I know anyway), hence this pull request.

I agree that “Whitelisted” is somewhat vague and generic though but it seemed the closest to what was already apt for the job - and it might still be so, but yes, the documentation would be useful.

Checking through previous commits, e.g. beceac9bbf14bf4a81f6f63b9cca2a64157054ae (#8078), it does look like Whitelisting feature is already being used to provide BLOOM services to whitelisted nodes and no other nodes, so I don’t think this pull req deviates from the current use so far.

Regarding who is most qualified to document what Whitelisting is, I would propose that it is the authors who have used it so far, so this would be @petertodd (#8078) @morcos (#7542) @sipa (#7125 #5157 #4378) @gmaxwell (#7166) @pstratem (#7406 #6374) @jonasschnelli (#6984) @laanwj (#6974) @sdaftuar (#5875) @rubensayshi (#5942) - this is an exhaustive list.

rebroad renamed this:
~~{WIP} Provide bloom services to whitelisted nodes.~~
Provide bloom services to whitelisted nodes.
on Aug 26, 2016

rebroad force-pushed on Sep 11, 2016

rebroad force-pushed on Sep 13, 2016

rebroad commented at 2:40 am on September 13, 2016: contributor

@venzen your message above seemed to get mangled somehow - not sure if I read your message about VERACK - will check the pull request now.

Provide bloom services to whitelisted nodes. 86574e55a1

rebroad force-pushed on Dec 11, 2016

rebroad commented at 4:56 am on December 11, 2016: contributor

@paveljanik Apologies for it not compiling. Just to let you know I test everything with “make check” as a minimum now before PR anything, and more often than not have tested things for months beforehand.

fanquake commented at 0:23 am on January 21, 2017: member

Closing this. Two NACKS and no other comments. A new PR could be opened to some whitelist documentation.

fanquake closed this on Jan 21, 2017

MarcoFalke locked this on Sep 8, 2021

Provide bloom services to whitelisted nodes. #8587