Embalmer == User who creates a sarcophagus (dead man’s switch).
Recipient == The ETH address that will have access to the file once resurrected.
Archaeologist == Third party incentivized node operators.
Curse == The agreement between the Embalmer and Archaeologist.
Resurrection == The time the outer layer of the sarcophagus will be decrypted if not attested to.
Litepaper == A place to see how Sarcophagus works in more detail.
The user that creates a sarcophagus is called the Embalmer. When creating a sarcophagus, the Embalmer must provide several things:
When creating the sarcophagus, the Embalmer will be quoted a price for their settings denominated in SARCO tokens.
We call the contract between an Embalmer and an Archaeologist a 'curse'. When an Embalmer selects an Archaeologist to be responsible for resurrecting their file at the correct time, a portion of the Archaeologist’s posted bond is locked.
If the Archaeologist resurrects the sarcophagus too early (or late), this portion of their posted bond is burned, and the bounty is returned to the Embalmer.
Once cursed, an Archaeologist must perform their resurrection duties within specific parameters or they will be slashed. The Archaeologist must also post a bond in SARCO tokens to be available for new curses.
An Archaeologist is a third-party, disinterested, incentivized service provider. They operate the Archaeologist server, post bonds in SARCO, resurrect files when needed, and are rewarded for good behavior (They are also harshly punished for bad behavior).
After spinning up an Archaeologist server, the operator must set their own parameters for minimum digging fees, minimum bounty, and maximum resurrection time. This will allow the Embalmer to see the minimum price in SARCO that an Archaeologist will accept in order to be cursed.
Since the first step the Embalmer takes is to encrypt their payload client-side the Archaeologist is unable to view the contents of any sarcophagus, even if they maliciously attempt to resurrect it prematurely.