8 commits

Author	SHA1	Message	Date
t-bast	e15344889a	Clarify blocksonly whitelistforcerelay test ... As discussed in https://github.com/bitcoin/bitcoin/issues/19943, this test may be a bit misleading to newcomers. We underscore the fact that our peer needs to run a modified version of Bitcoin Core to actually relay transactions to a `blocksonly` node and benefit from the `whitelistforcerelay` parameter.	2020-09-21 10:16:09 +02:00
John Newbery	85165d4332	scripted-diff: Rename mininode to p2p ... -BEGIN VERIFY SCRIPT- sed -i 's/\.mininode/\.p2p/g' $(git grep -l "mininode") git mv test/functional/test_framework/mininode.py test/functional/test_framework/p2p.py -END VERIFY SCRIPT-	2020-08-21 15:52:20 +01:00
Fabian Jahr	cacd85209e	test: Use wtxid relay generally in functional tests	2020-07-19 02:10:42 -04:00
MarcoFalke	fab5586122	doc: Use precise permission flags where possible	2020-07-10 15:37:42 +02:00
MarcoFalke	fa0540cd46	net: Extract download permission from noban	2020-07-09 12:48:05 +02:00
glowang	be01449cc8	Add test for param interaction b/w -blocksonly and -whitelistforcerelay	2020-05-04 21:57:47 -07:00
Suhas Daftuar	0ba08020c9	Disconnect peers violating blocks-only mode ... If we set fRelay=false in our VERSION message, and a peer sends an INV or TX message anyway, disconnect. Since we use fRelay=false to minimize bandwidth, we should not tolerate remaining connected to a peer violating the protocol.	2019-09-04 14:58:36 -04:00
MarcoFalke	fa320de79f	test: Add test for p2p_blocksonly	2019-05-13 10:44:42 -04:00