cross-chain peg; e.g. to Agoric

[dckc]

I recently saw a demo of Pegasus, a dApp for pegging ERTP rights to or from remote assets via the Agoric Network API.

It looks like one could implement that network API using the RChain web api and the pegasus.js contract would largely just work. (Some refactoring is needed first: Agoric/dapp-pegasus#2)

[michaelfig]

It looks like one could implement that network API using the RChain web api and the pegasus.js contract would largely just work.

Yep, that's the idea. The main invariant is that each unique "network" connection has to be identified so that the protocol can decide on a unique name for the pegged assets.

[dckc]

Another possibility...

Compared to IBC and PoS light client based cross-chain communication, Optics has weaker security guarantees, and a longer latency period. However, Optics may be implemented on any smart contract chain, with no bespoke light client engineering. Because it does not run a light client, Optics does not spend extra gas verifying remote chain block headers.
-- https://github.com/celo-org/optics-monorepo

It's not obvious how to do token transfers over Optics, actually...

cc @tgrospic @jimscarver