-
Couldn't load subscription status.
- Fork 83
to add lip9/readme and /caip2 #17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
bumblefudge
wants to merge
8
commits into
main
Choose a base branch
from
feat/add-lip9
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
fd87b14
to add lip9/readme and /caip2
bumblefudge 52c2b7e
Update lip9/README.md
98cb4e8
Update lip9/README.md
3371f98
Update lip9/caip2.md
14ee1a4
to replace reference-links
bumblefudge b49ff60
typo
bumblefudge c772544
to fix frontmatter
bumblefudge 7c509a0
stray newline nixed
bumblefudge File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| --- | ||
| namespace-identifier: lip9 | ||
| title: LIP9 Namespace, aka Lisk | ||
| author: Simon Warta (@webmaster128) | ||
| status: Accepted | ||
| type: Informational | ||
| created: 2019-12-05 | ||
| updated: 2020-01-16 | ||
| replaces: CAIP-6 | ||
| --- | ||
|
|
||
| # LIP9 Namespace | ||
|
|
||
| This document is about the details of the Lisk namespace as defined by | ||
| [LIP-9][], including Lisk Mainnet and Testnet, forks and side chains. | ||
|
|
||
| ## Syntax | ||
|
|
||
| The namespace `lip9` refers to Lisk namespace as defined above. | ||
|
|
||
| ## Governance | ||
|
|
||
| The Lisk namespace is governed by the Lisk Improvement Proposal [LIP][] system. | ||
|
|
||
| ## References | ||
|
|
||
| - [LIP-9][] - The Lisk Improvement Proposal that defined chain IDs for making | ||
| transactions resistant to cross-chain and cross-fork replay. | ||
|
|
||
| [LIP]: https://github.com/LiskHQ/lips/ | ||
| [LIP-9]: https://github.com/LiskHQ/lips/blob/main/proposals/lip-0009.md#specification | ||
|
|
||
| ## Copyright | ||
|
|
||
| Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| --- | ||
| namespace-identifier: lip9-caip2 | ||
| title: LIP9 Namespace, aka Lisk - Chains | ||
| author: Simon Warta (@webmaster128) | ||
| discussions-to: https://github.com/ChainAgnostic/CAIPs/issues/7, https://github.com/ChainAgnostic/CAIPs/pull/1 | ||
| status: Draft | ||
| type: Standard | ||
| created: 2019-12-05 | ||
| updated: 2020-01-16 | ||
| requires: CAIP-2 | ||
| supersedes: CAIP-6 | ||
| --- | ||
|
|
||
| # CAIP-2 | ||
|
|
||
| *For context, see the [CAIP-2][] specification.* | ||
bumblefudge marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| ## Rationale | ||
|
|
||
| In CAIP-2 a general blockchain identification scheme is defined. This is the | ||
| implementation of CAIP-2 for the Lisk ecosystem as defined in [LIP-9][]. | ||
|
|
||
| ## Semantics | ||
|
|
||
| The definition is delegated to LIP9. | ||
|
|
||
| ## Syntax | ||
|
|
||
| The reference format is a 16 character string extracted from the first 16 | ||
| characters of the network identifier defined in LIP9 (a 64-character SHA256 hash | ||
| in lowercase hex). | ||
|
|
||
| ### Backwards Compatibility | ||
|
|
||
| LIP-9 introduced a hard fork, but no cross-fork/cross-chain replay protection | ||
| (or other validating chain identification scheme) predates it. | ||
|
|
||
| ## Test Cases | ||
|
|
||
| This is a list of manually composed examples | ||
|
|
||
| ``` | ||
| # Lisk Mainnet (https://github.com/LiskHQ/lips/blob/master/proposals/lip-0009.md#appendix-example) | ||
| lip9:9ee11e9df416b18b | ||
|
|
||
| # Lisk Testnet (echo -n "da3ed6a45429278bac2666961289ca17ad86595d33b31037615d4b8e8f158bbaLisk" | sha256sum | head -c 16) | ||
| lip9:e48feb88db5b5cf5 | ||
| ``` | ||
|
|
||
| ## References | ||
|
|
||
| - [LIP-9] - The Lisk Improvement Proposal that defined chain IDs for making | ||
| transactions resistant to cross-chain and cross-fork replay. | ||
|
|
||
| [LIP-9]: https://github.com/LiskHQ/lips/blob/main/proposals/lip-0009.md#specification | ||
|
|
||
| ## Copyright | ||
|
|
||
| Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.