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 ...
Yes we are in the process of creating a few regional supernodes that are all connected to major pools, and those nodes are connected to our backend infrastructure that will send a block notify to every single solo miner that is opted in within milliseconds of a valid block detected. Backend is a propriety network that bypasses the p2p bitcoin network similar to what all major pools use among themselves.
Regardless you are still exaggerating the chances of an orphaned block even on the normal p2p network. There are 600 seconds within a block, lets say you are on a slow network and broadcast hits the major pools 6 seconds late, thats just a 1% chance someone will find another block before you (ie if EVERYONE solo mining has a slow connection, for ever 100 solo blocks found one will be extremely unlucky and get their block orphaned).
If you really want to get into the meat of the matter and the type of research I do to come up with the systems we do you can read these research publications for a deep dive on the topic:
https://sites.cs.ucsb.edu/~rich/class/cs293b-cloud/papers/bitcoin-delay#:~:text=The%20median%20time%20until%20a,not%20yet%20received%20the%20block.https://www.researchgate.net/publication/363879722_Analysis_of_segregated_witness_implementation_for_increasing_efficiency_and_security_of_the_Bitcoin_cryptocurrencyMean block propagation times were on the order of 6 seconds in the early days (2013 when the first article was published), due to more efficient core upgrades/computational increase/network bandwidth increases the mean has come down to around 2 seconds.
For everyday users trying to secure the network a .333% chance of orphaning a block compared to lets say major pools of .1% wont matter at the end of the day (and im not discounting the fact that it will matter HORRIBLY for that one person that will find a solo block after mining solo for years and it ends up orphaning but that is the nature of the bitcoin network and the risk solo miners take).