We have relationships with the major pools and will bootstrap all solo nodes directly to them. Any block found by a futurebit solo miner will propagate to the major pools first before the rest of the network.
So if you are only selling a total of 50 of these, that 'may' be possible.
If you are selling more than 100 of them, it's not possible.
Bitcoin wont allow 100's of connections by default since that would cause dramatic network performance issues.
No pool in their right mind would allow that either.
If instead you said you setup a transaction/block distribution network like bluematt used to run, for all these apollos, then yes that would be possible.
However, without that, it's not possible what you said.
Our CPU is pretty fast as well and block creation is not a bottle neck.
It is a bottleneck on
every CPU.
The question that matters is how long it takes.
e.g. does it include the CPU instructions to dramatically speed it up? (no it doesn't)
Can it average block template generation well under 100ms? (no)
Also a valid block is a valid block, even if it shows up seconds late as long as no other block is found within those few seconds it will be included. 10 min block times were created for reasons like this where even small miners running regular computers can still participate at base layer...
Um, nope, seconds late is too late.
It dramatically increases the chances of an orphan.
Orphans still happen with the large pools every so often, they just don't tell anyone.
Since I have a world wide distribution of nodes and I track/report the block submissions/reorgs that happen in my monitoring, I can see them when they happen.
If the blocks generated by these nodes all say they are solo futurebit nodes, then that will be interesting to see what actually happens ...