Skip to content

Commit

Permalink
Merge pull request #85 from silverpill/readme-fix
Browse files Browse the repository at this point in the history
Fix link to CONTRIBUTING.md
  • Loading branch information
bumblefudge authored Sep 1, 2023
2 parents 13189ec + 721035c commit c627a9e
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ They consist of a 1 high-level "README.md" file to contextualize the ecosystem,
Each "CAIP profile" defines the namespace's syntax, semantics, and context for that CAIP (i.e., it's address format, actor model, asset addressing model, etc.).
The intended audience of both the general "README.md" and each profile is a developer familiar with the CAIP being profiled but not familiar with the ecosystem being described, so the best namespaces provide all the links and entry-level explanations of the context needed for developers to build wallet and/or dapp interfaces that interact with assets, contracts, and accounts of a given namespace.

The namespaces are best read on the [namespaces][] "docs" website rather than in github. To contribute see the [Contributing file](./contributing)
The namespaces are best read on the [namespaces][] "docs" website rather than in github. To contribute see the [Contributing file](./CONTRIBUTING.md).

## How it works
Each namespace implements one or more [CAIPs](https://github.com/ChainAgnostic/CAIPs). The most important CAIPs to consider for a namespace are:
Expand Down Expand Up @@ -47,4 +47,4 @@ If, however, the *native* RPC interface, actor model, deployed-contract addressi
## References

[CAIPs]: https://github.com/ChainAgnostic/CAIPs
[namespaces]: https://namespaces.chainagnostic.org/
[namespaces]: https://namespaces.chainagnostic.org/
6 changes: 3 additions & 3 deletions _template/caipX.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,10 @@ requires (*optional): <["CAIP-X", "CAIP-Y"]>
replaces (*optional): <CAIP-Z>
---

<!--You can leave these HTML comments in your merged EIP and delete the
<!--You can leave these HTML comments in your merged CAIP and delete the
visible duplicate text guides, they will not appear and may be helpful to
refer to if you edit it again. This is the suggested template for new EIPs.
Note that an EIP number will be assigned by an editor. When opening a pull
refer to if you edit it again. This is the suggested template for new CAIPs.
Note that an CAIP number will be assigned by an editor. When opening a pull
request to submit your EIP, please use an abbreviated title in the
filename, `caipX.md`, all lowercase, no `-` between the CAIP and its
number.-->
Expand Down

0 comments on commit c627a9e

Please sign in to comment.