Skip to content
This repository was archived by the owner on Jan 16, 2022. It is now read-only.

Testnet competition#134

Open
mesozoic-technology wants to merge 2 commits intooverlay-market:mainfrom
mesozoic-technology:testnet-competition
Open

Testnet competition#134
mesozoic-technology wants to merge 2 commits intooverlay-market:mainfrom
mesozoic-technology:testnet-competition

Conversation

@mesozoic-technology
Copy link
Copy Markdown
Contributor

This pull request is dedicated to exposing the contracts in a testnet competition.

This will include

  • Refinement of the oracle mocks to occlude the feed data as much as possible in order to afford a fair playing ground for community involvement.
  • Scripts to deploy the testnet suite and perform any potential future actions required by the competition

@mesozoic-technology
Copy link
Copy Markdown
Contributor Author

mesozoic-technology commented Jan 7, 2022

For a successful testnet competition this pull request is fairly complete.

The only things remaining is an exhaustive deploy script and a choice.

Which is, should any interesting behavior with regard to dynamic caps be included to occur somewhere along the duration of the competition?

If so, then we will need to synthesize a liquidity feed that performs these various behaviors. Vanishing liquidity, thin liquidity, thick liquidity, ect.

This seems fairly doable.

@mesozoic-technology
Copy link
Copy Markdown
Contributor Author

Another thing to consider is how much the future information of the testing competition should be occluded from view.

I have taken the mock and made the public state private, which will prevent a moderately technical user from interrogating the future prices.

But what about a very sophisticated user who could look directly at the patricia tries?

Are more strategies to occlude this information desirable? Are they easily doable?

One answer is to supply the price information manually using a bot. New prices could be added periodically. I have several thousand ETH on Kovan and could fund this. That doesn't quite get beyond the possible problem, though. The original transactions could be interrogated.

Alternatively, it could simply be a friendly game.

@mesozoic-technology
Copy link
Copy Markdown
Contributor Author

A solution occurred to me in the commit reveal pattern. Simply, the oracle mock is constructed with a method that asserts the hash of incoming data matches, in order, a previously committed hash.

That allows the oracle data to live on a centralized repository but sustains the guarantees that it was not changed after the start of the contest.

This occludes the data from those not associated with this process, who will have to be trusted to not look or to sit the competition out.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant