{"componentChunkName":"component---src-pages-sips-sip-markdown-remark-frontmatter-sip-tsx","path":"/sips/sip-96/","result":{"data":{"markdownRemark":{"fileAbsolutePath":"/vercel/path0/content/sips/sip-96.md","frontmatter":{"sip":96,"sccp":null,"title":"Blockchain Forks Framework for Synths","network":"Ethereum","author":"Jackson Chan (@jacko125), Garth Travers (@garthtravers), Clinton Ennis (@hav-noms)","type":"Governance","proposal":null,"implementor":null,"release":null,"created":"2020-11-16T00:00:00.000Z","updated":null,"status":"Implemented"},"html":"\n

Simple Summary

\n\n

Proposes a blockchain fork framework for Synthetix protocol. When the underlying blockchain asset has an upcoming hard fork, the related synths will be suspended 72 hours beforehand and exchanges stopped. Blockchain hard forks can split the consensus of the forked network and price feeds become unreliable.

\n

Abstract

\n\n

Suspend synths 72 hours before an upcoming hard fork. This will prevent the synths from being exchanged and transferred. If the fork is contentious and there are two resulting chains, the framework provides the option to delist the synths temporarily, until the dominant fork and price feeds are established and then re-examine its listing using the Delphi asset listing framework.

\n

Motivation

\n\n

When a blockchain undergoes a hard fork, there could be two different versions of the chain that are running simultaneously creating uncertainity in the price feeds for the asset. Exchanges and miners can choose to adopt a prevailing fork of a chain and this process could take a few days to stabilise.

\n

To protect traders and SNX stakers against this uncertainty, this framework proposes to suspend the affected Synths 72 hours before the hard fork event.

\n

In the case of contentious hard forks where there are two competing forks, a SIP could be proposed, for example in the case of the recent BCH fork, to the community and stakers to delist the synths and then re-examine relisting the synths once the dominant fork and price feeds are established.

\n

Rationale

\n

Hard forks happens when a blockchain protocol makes an upgrade to their underlying software and require miners (which can be measured in hashrate) to choose to adopt the hard fork or not. Some upgrades can be contentious whereby the majority of a blockchain community (miners and exchanges) may choose to not adopt.

\n

The uncertainity a hard fork introduces requires the protocol to suspend the exchange and trading of the synths until the community and stakers can decide on whether to re-enable trading or delisting the affected synths.

\n

Specification

\n\n
    \n
  1. Notify stakers and traders that the synths will be suspended 72 hours ahead of the fork.
    2. \n
  2. The Protocol DAO will suspend the long and inverse synths.
    3. \n
  3. SIP raised if the synths need to be delisted and purged back into sUSD before the fork happens.
    4. \n
  4. Spartan council is able to resume the trading of suspended synth/s via governance process.
    5. \n
\n

Copyright

\n

Copyright and related rights waived via CC0.

"}},"pageContext":{"id":"51496a1d-6bbe-5152-b1a4-15613c32c280","frontmatter__sip":96,"__params":{"frontmatter__sip":"96"}}},"staticQueryHashes":[]}