Friday, June 28, 2019

Provability of trader's code

Contract rules must obey finiteness and roundness.



My contracts manager gains entry to a pit for portfolio adjustment, I provide the algorithm, Ipick some standard S/L watching, speculating trading code. It must be provable, in at entry by the sandbox engineers.

Sandbox have codes that prove the contract unfolds to a finite size, which fits the instruction cache. The code verifies that all node checks lead to trusted ledgers, already in the instruction cache. It verifies all valid exits. Timeouts conditions met on ledger calls. The trader is good to go and the microprocessor can meet spectre specs.

On timeouts, the general rule is that roll backs have the most  costly queue fees. Bounded crawl back for one step. Roll back triggers scofflaw services, but roll backs are a necessity at times of sudden congestion. Timeout limited.

Make  a special variety of micro processor, show the NSA provability back to the foundry. The meeting is soon, go lobby the legislature on this.

No comments: