Tuesday, November 8, 2016

How would a trading pit automatically?

The jamming pattern sticks out, that is, it is an almost consistent probability graph.  So, the pit boss, under contract, rolls up the jamming graph, and ships it off to another machine  where traders can trade on the tree imbalances.  The jamming pattern is hedged.

What about infinite spawn, the ethereum issue?  I am having  hard time seeing that happen if Ito gets is space contraction on each spawn.  The precision is a small number 3-9 are good estimates. Further, the pits are segmenting, we will not get 2^9 spawned pis, likely two, maybe four, significant to isolate the price fixers.

Significant changes of the jamming tree occur asynchronously, and are passed to parent or daughter (depending on tyhe split proess) , Traders can split their bets between the pits, hedge the jam. But the traders are going to run the limit on precision, and the spawning stops. I think the lowest precision possible is the prevision of arrival of the local sheriff, and he can be sneaky.

Leave an option in the pit boss contract
Pit.boss.spawn = [True,False]

In doing this, let all the bit error roll up to he original parent pit, distribute bit error there, by contract.  Notify all the bots that they could to trade all the spawned pits.  Basically the parent is simply spawning off various integer multiply machines, to handle the known bit error fairly.  That is, it should trap and hedge insider price fixing.

It is about understanding price fixing and maximum entropy channel trading. The price fixer has residual flow, otherwise they are inconsequential.  The consequential flow shows up as a contiguous  disordering of the singleton IO stream, and the pit boss is on the graph more, the free traders less.  It is not soon before the pit boss and a few residual traders and furiously studying a single jamming pattern, looking for its theory.  Price fixing will be extinguished..

No comments: