Fork-time mining configuration

[freetrader]

First question of this thread:

Is there an existing configuration switch that can be used on a mining node that makes it only send out new blocks and accept incoming transactions, but not relay transactions?

Core's blocks-only mode doesn't seem to fit what I'm looking for.

An alternative would be some type of data diode that only allows transactions and blocks into a mining node, and only blocks out.

 

[adamstgbit]

why would you want this? to limit the amount you upload?

 

[freetrader]

I guess the reason I started this thread is to find out more about the needs of mining during a hard fork situation.

We've already seen that there would be a need for some kind of 'splitter' services which are able to operate on specific fork chains without risk of their transactions propagating "across" to other forks.

It would make sense to me if there was a miner on a particular fork, that it would be able to process incoming transactions, but not relay them (let the other nodes do that).
There could be a direct connection between such a mining node and a splitter service node which relays transactions to be mined only on that fork.

The splitter node would maintain connections to the various forks, and users could use it to ensure that their coins are separated into new addresses only usable on those forks.

At least, that's what I'm thinking. Perhaps I'm wrong.

Also, if hard forks are deployed, more people will be mining again using their home nodes and pools.
So this is to think about what existing configuration parameters may be useful in achieving these aims safely. It may turn out that additional parameters might be helpful to make forking time a safer time to transact.