search

omgnetwork / research

43 stars 2 forks source link

Propose chained in-flight exits to allow chaining txs under MoreVP #110

Open pdobacz opened 4 years ago

pdobacz commented 4 years ago

Following discussions with @paulperegud and @boolafish. Also similar in concept to and inspired by some earlier ideas like "upgrading challenges", mentioned among others in #100.

pdobacz commented 4 years ago

High level wise I am lost why we need to care about E. Seems like the General flow + canonicity index + piggyback together is a generalized solution to chain morevp (?)

A couple of reasons: 1/ we leverage the uniquness of the actor E within a single cIFE process 2/ we leverage the assumptions Restricted Custody brings 3/ but most of all - it is there to hint towards the concrete application when the chained txs are settlements and E is exchange. However, see the last line of the docs, maybe with careful effort one can truly generalize and drop some of the assumptions

how do we block multiple exit on exited chain? (eg, SE on the middle of chain)

I think just like with vanilla IFEs. A tx from the cIFE chain can challenge SEs and there must be a way to relate the piggybacks done on cIFEs with SEs (just like it happens right now for IFEs - via exit_ids). This is the reason why output_id is required.