Comments (2)
Cross chain addressing of transactions should be fairly simple with a pattern like:
<chain-id>:tx:<tx-hash>
Examples:
eip155:1:tx:0x1cc5b5193db6f41c6b830660fe6e8e14a4c9bce66381956f065a5584272754b8
bip122:tx:f1d481508ce99ade1427b581ce0e240dd7258358bbfdee89ed08450de23c5e6c
Another possibility, to make references much shorter, one could take advantage of blockchain immutability and total ordering and use an index/location based addressing scheme:
<chain-id>:tx:<block-height>:<tx-index>
The above examples would be reduced to:
eip155:1:tx:15670909:268
bip122:tx:635359:1110
On UTXO chains you could also reference specific outputs (like an OP_RETURN) within a transaction by index:
<chain-id>:tx:<block-height>:<tx-index>:<output-index>
Example:
bip122:tx:635359:1110:0
would point to the first output within the transaction (an OP_RETURN in this case):
https://mempool.space/tx/f1d481508ce99ade1427b581ce0e240dd7258358bbfdee89ed08450de23c5e6c
from caips.
To give another example for a potential use case:
ISCC is an upcoming ISO standard for decentralised content identification (ISO/CD 24138), also see: https://core.iscc.codes/ and https://github.com/iscc.
ISCC codes, which are content-derived identifiers and lightweight fingerprints, can be declared together with declaration metadata (that bind product metadata, rights and licenses) on public blockchain networks, e.g. Ethereum, Polygon, for any reason, e.g. timestamping, content licensing, copyright claim, etc.
The input data
of the declaration transaction contain the ISCC code and the URI to primary declaration metadata on IPFS, see this example:
This means that the data is on-chain, but it is not stored in a smart contract, resulting in significantly reduced gas costs for content declarations, which might have to do with digital collectibles, compared to the minting of NFTs.
Example:
https://goerli.etherscan.io/tx/0x3edb98c24d46d148eb926c714f4fbaa117c47b0c0821f38bfce9763604457c33
0 | iscc | string | KACXDCTNRPRCRYPBDJNYOYLWTRAOKTTCAUS42ZO5T4IZVU467KHHNUY |
---|---|---|---|
1 | url | string | https://ipfs.io/ipfs/QmSBF81KWqGANVCc8AxgRvyoD1kiTjhrc5MypLevJoguV8 |
An ISCC declaration will create a declaration ID (called ISCC-ID), for which we have designed a W3C-compatible 'did:iscc' method, see: https://ieps.iscc.codes/iep-0015/. did:iscc will resolve to the ISCC code, the declaring and signing wallet, and the primary declaration metadata provided with the transaction (see example of did:iscc at https://dev.uniresolver.io/). The registry of cross-chain content declarations is decentralised in such a way that anyone can set up a registry and pull and verify the data from the blockchains and IPFS, see https://iscc.id or https://testnet.iscc.id, which both are run by ISCC Foundation.
See registry entry from the example transaction, above: https://testnet.iscc.id/registry/iscc_registry/isccid/449695081398566975/change/
In my opinion it would be of value to be able to address specific declaration transactions on multiple chains in a uniform way, abstracting out the unique syntax of block explorers, to build a multi-chain index of data stored in transaction metadata.
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
- [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.