if you were to design a token whose issuance rules lived on L1

but whose token "lives" on + had governance (which could control issuance etc) on an L2

where would you start?

probably something like op stack's cross domain messengers, right?

L1 sends mint messages to L2
L2 sends gov messages back to L1

if you were to design a token whose issuance rules lived on L1

but whose token "lives" on + had governance (which could control issuance etc) on an L2

where would you start?

probably something like op stack's cross domain messengers, right?

L1 sends mint messages to L2
L2 sends gov messages back to L1

https://docs.optimism.io/app-developers/bridging/messaging

I’d start here. Omnichain chain & battle tested

prev: /nook, protocol @ opensea, co-author seaport & stuff.
professional @slokh and @0xalexander fanboy

I’d start here. Omnichain chain & battle tested https://docs.juicebox.money/

Ethereum builder & people connector. Juicebox, Revnet, Defifa & Footy App

one big subgraph lol
seriously although there's a migration to ponder in the works

there's a jb funded project called nance that is a type of snapshot for jb that we use for gov voting. 

you can change the rules & schedules however you like. free free to slide into discord https://discord.gg/GCpYNtC3YQ feel free to tag

key things i'm thinking of (for funsies) are extremely custom + tuneable (by gov) issuance schedules and probably entirely novel vote tracking

how is gov handled in an omnichain world, snapshots hosted externally? or is there usually a canonical gov-chain