https://github.com/paritytech/chainextension-registry
Registry of ChainExtensions for pallet-contracts
https://github.com/paritytech/chainextension-registry
Last synced: over 1 year ago
JSON representation
Registry of ChainExtensions for pallet-contracts
- Host: GitHub
- URL: https://github.com/paritytech/chainextension-registry
- Owner: paritytech
- License: apache-2.0
- Created: 2022-07-11T17:42:48.000Z (almost 4 years ago)
- Default Branch: main
- Last Pushed: 2023-09-05T09:02:51.000Z (over 2 years ago)
- Last Synced: 2025-01-06T18:36:46.592Z (over 1 year ago)
- Homepage:
- Size: 10.7 KB
- Stars: 10
- Watchers: 7
- Forks: 4
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# chainextension-registry
A list of known
[`ChainExtensions`](https://paritytech.github.io/substrate/master/pallet_contracts/chain_extension/index.html)
for
[`pallet-contracts`](https://github.com/paritytech/substrate/tree/master/frame/contracts).
A `ChainExtension` should be registered here when it is generally useful and offered as an
off-the-shelf module to other developers. The reason for that is to coordinate on their
IDs.
The extensions are defined in a json file. Example:
```json
[
{
"id": 1,
"repository:": "https://github.com/paritytech/polkadot",
"typeName:": "XcmExtension"
},
{
"id": 99,
"repository:": "https://github.com/paritytech/substrate",
"typeName:": "AssetExtension"
}
]
```
## Process
1. Open a PR to add a new chain extension to `registry.json`.
2. Don't make backwards incompatible changes to the extension after it is registered.
3. Add a new version under a new ID if you need to make incompatible changes.