As a product, I want the alpha to be on the Canary Network

[pkucherenk0]

Problem to solve: It was agreed that the Alpa will be released on the Canary (network placeholder) main-net network. This should make Alpha more influential for testers, the team, and the community. Allowing us to transit to the main-net more easily, and find the issues and abuses prior to the public release. This will create adoption metrics for VC

Acceptance Criteria:

1. Deploy bridge DUCKIES (as a safety token) to (network placeholder) L1+L2
2. Index Price feed should support the market list on the (network placeholder)
3. ClearPort should be able to operate on (network placeholder)
4. ClearSync SC should be deployed and operation on (network placeholder) L2
5. User should connect his wallet on the (network placeholder)

[pkucherenk0]

Depends on the Business backlog and what network we will choose. Deadline December 13

[mod]

We can deploy anytime using our hardhat task but blocked by making a secure deploy:
https://www.openzeppelin.com/#secure-deploy

[mod]

TODO:

• @mnaichuk Index price
• @dpatsora Integrate pkg/quote
• @calj Secure deploy for adjudicator and maybe DUCKIES ERC20
• Study ERC20 bridging from L1 - L2 (optimism)

[calj]

I started a PR with a first attempt to use OpenZepplin Deploy
#138

I think the product allows to do what we want, if we can make it work.
I theory we can validate deployments and updates with a multi-sign contract.