[Don't merge until multichain released to testnet] Multichain overview and architecture #61
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
non-fungible-nelson
left a comment
non-fungible-nelson
left a comment
There was a problem hiding this comment.
Consider cross referencing and adding in the material thats in here as well: Integration Guide HackMD
| interface regardless of which chain you're deploying to, or which consumers are using your AVS. This enables a “code once, | ||
| deploy everywhere” workflow that reduces cross-chain complexity, eases integration with other AVSs, and simplifies ongoing maintenance. | ||
|
|
||
| ## Contract Interaction |
There was a problem hiding this comment.
should we consider adding the larger mermaid somewhere ? Maybe when we have more content.
There was a problem hiding this comment.
To give an 'it depends' answer -> is the additional context provided by the larger mermaid needed by AVS/app devs, or Operators implementing/operating multichain? If yes, I think we should include. But if it's largely showing more detailed views of the internal calls/contracts, I'd lean to no.
Let me know what you think.
There was a problem hiding this comment.
Added some content from the integration guide. Will create another PR for the how to content.
MadelineAu
requested review from
MC1823315,
NimaVaziri,
afkbyte,
antojoseph,
dabit3,
mmurrs,
scotthconner and
shrimalmadhur
as code owners
|
should just update this content against the ELIP |
When the repo docs are merged, needs links added to the relevant spots.