Crosschain revnets

## One directional cross chain
          
[chain 1]-----|
[chain 2]-----|
[chain 3]-----|
[chain 4]-----|
              -->> [primary chain]

- Can only exit (access revenue) from primary chain.
- No need for tokens on non-primary chains.
- "balance" and "$TOKEN supply" only on primary chain.

We're not doing one directional.

- Biggest risk is the fact that primary chain and all other chains are different -- they serve different purposes, makes the system more complex.



## Multi directional cross chain

on-deploy:
[chain 1]<<---|
[chain 2]<<---|
              | (jbdao approves a Zora chain sucker, revnet operator can add the Zora chain.)
[chain 3]<<---|
[chain 4]<<---|
              -->> [primary chain]


- Can exit (access revenue) from any chain.
- Tokens on all chains so no need to bridge to access revenue.
- "balance" and "$TOKEN supply" on all chain.

- Biggest risk is economic risk.


We're doing multi directional.

~~- Can only exit (access revenue) from primary chain.~~
~~- No need for tokens on non-primary chains.~~