| namespace-identifier | title | author | status | type | created | requires (*optional) | replaces (*optional) |
|---|---|---|---|---|---|---|---|
<same as name of folder> |
<{namespace common name} [, aka ecosystem name]> |
<["FirstName1 LastName1 (@GitHubUsername1)", "AnonHandle2 <[email protected]>"]> |
Draft |
Informational |
<date created on, in ISO 8601 (yyyy-mm-dd) format> |
<["CAIP-X", "CAIP-Y"]> |
<CAIP-Z> |
As the old saying goes, "If you can't explain it simply, you don't understand it well enough." Here is where you can provide a simplified and layman-accessible explanation of what is particular to this namespace or how it differs from EVM chains, where the CAIPs are easiest to apply/understand.
A short (~200 word) description of any technical issues being addressed by the naming of the namespace, or other informational asides about the particularities of the namespace.
A short (~200 word) description of the improvement proposal process or other specification/governance context that a first-time implementer of cross-chain work in this namespace/ecosystem should know.
Links to external resources that help understanding the namespace or the specification/applied-CAIP better in this context. This can also include links to existing implementations.
The preferred format, for browser-rendering and long-term maintenance, is a
bulletted list of [Name][] links (rather than classical Name links),
followed by - and a summary or explanation of the content. In a separate
section below, add the name-referent pairs in the [Name]: https://{referent}
format-- this will be invisible in any Github-flavored Markdown rendering
(including jekyll/github pages, aka github.io, but also docusaurus and many
dev-docs rendering engines).
Copyright and related rights waived via CC0.