Monday, October 31, 2016

Translating contract parameters

In the Trading Pit.  The site owner publishes the bot contract, that contract has to be operational for the bots.  Read the documentation doesn't work, there is a closed parameter spacefromwhich the site owner has to choose.  If the site owner wants 30% of the graoh cycles, say it in a standard resource parameter.  Any depth limit, define a  seignoriage parameter, and stick to it.  Posted prifes for graph cycles.

The Ethereum folks should have figured out a lot of this, take their experience and build it int othe pit software, in fact, build the pit for use in the ethereum network.

Folks who are writing these financial algos know of which I speak, it is the difference between being in the pit or hearing about it a week later.  So they will readily come up with the fair parameter set, ifit allows them  to launch their software into a fair pit.

How should the trader see this?

The trader's bot is doing real time chart analysis, in the pit, and making trades on the spot.  The site owner, under contract, is expected to spend some time organizing a probability tree for the pit, to reduce trader cycle times in finding bids.  That is the contract.

No comments: