You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.
application specific sidechain dealing with state (and maybe block producers of that chain)
end-user client submitting Tx
The first version of this can be a very simple draft. Point 3) could also be skipped in a first diagram if that simplifies things. Additionally, more detailed diagrams explaining all touching points and interactions between all three would be great.
The text was updated successfully, but these errors were encountered:
I think this is still useful but these diagrams are not necessary to live in the specs repository but for developer focused documentation. Let's aim for testnet and incentivized testnet the latest.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We should add architecture diagrams that clarifies at least the following relations:
The first version of this can be a very simple draft. Point 3) could also be skipped in a first diagram if that simplifies things. Additionally, more detailed diagrams explaining all touching points and interactions between all three would be great.
The text was updated successfully, but these errors were encountered: