Comments (6)
Thank you very much, that is perfect!
Two questions:
- Would it make sense to link these documents prominently in the CAIP-2 and CAIP-19? Our team was using those two documents as a reference and obviously, we failed to find the proper namespace definitions. Maybe this helps other newbies, too.
- Would it be beneficial, if the namespaces would be referenced on the ITSA docs or the website? Not sure about the form yet, but I think that creating a list with all namespaces, that gets updated regularly, would be a good resource.
from caips.
Ok, nice.
So do you want chainlist.org to be the source for the CAIP-2 identified chainIds? Right now, chainlist.org only contains EVM chains.
from caips.
I guess, you should have a look at https://github.com/ChainAgnostic/namespaces repository. There you could see what CAIPs are available per blockchain = namespace. For example, you could see that for eip155 = Ethereum-based chains 4 CAIPs are standardised, while fil = Filecoin has only CAIP-2.
Everything in that repository is community-approved.
from caips.
- Good thinking, I'll run it by the editorial group.
- Yes, we would appreciate references that bring attention to both repos, /CAIPs/ and /namespaces/. They are both slow-moving but ever-growing references. I think my personal preference would be for links to root rather than lists of links to what's there at any one point in time.
from caips.
- If you need help, let me know. I am new (to CASA) and happy to help. I will also be in Berlin on Sept. 15th.
- a) Agree. I envision something like a "list" in this repo. This "list" is the unique source of truth (at least it tries). Other sources link /reference these. ITSA is one of the first institute to link/reference this.
- b) Maybe there should be some kind of versioning for the "list". Could be as easy as a last updated at timestamp. This would allow institutes to put the data in their own design and logic.
My rational why this could be beneficial, please correct if I am wrong: In the end CASA defines standards. Only a wide spread adoption defines the success of the standard, if I get it right. So making it easy to non-techy people to access the data is IMHO an important step. I can tell from experience of multiple discussions that even the different labels (namespace / id / type) are complicated to understand. So this really is my approach to boild down the whole CAIP-2 / CAIP-19 identification to an API that is easily understood by business people without technical background.
from caips.
Chainlist https://chainlist.org/ is the published source of truth for ChainIDs. I forget if there is again / still a JSON version of that list as we once had.
I know there was an earlier thread around that domain / website, I'll just re-iterate what needs to be done:
- verify / secure ownership of the
chainlist.org
domain, and build process - add CASA logo and link back to github org
- add JSON version so that
chainlist.org/chainlist.json
or similar is a machine readable version - (optional) IPFS publishing flow to get versioned links and/or ENS path
For CAIP 19, we need to also publish those identifiers to a site following a similar pattern.
from caips.
Related Issues (20)
- [CAIP-27] Corner-cases around accounts assumptions HOT 1
- Draft: Add CAIP-2 for edeXa blockchain
- User feedback: No way to address a NON-ASSET deployed smart contract in a namespaced way HOT 7
- User feedback: No way to address a specific transaction HOT 2
- [CAIP-122] Add guideline to match on `domain` term HOT 1
- How to refer to attestations as asset class? HOT 17
- fix github link on jekyll template
- [CAIP-122] Why only ASCII? HOT 4
- [CAIP-171] - drop cryptographic/entropic UUID requirement? HOT 1
- 168ff88295830ada21c45d828a6551bf57861568
- [CAIP-196] UCANs with header entries HOT 3
- [CAIP-196] Timestamp precision
- Problem rendering list of CAIPS required HOT 1
- register CAIP URI scheme with IANA?
- CAIP for domain/address resolution protocols list HOT 1
- Converting Scopes into ReCaps
- [CAIP-19] Assets versus Actors or Entities? HOT 1
- [Multichain] Has anyone seen ERC-4804-style URI schemes for non-EVM chains?
- Supporting multiple chains with CAIP-122 HOT 2
- Implementer Feedback: CAIP-122<>EIP-4361 mismatch HOT 12
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from caips.