-
Notifications
You must be signed in to change notification settings - Fork 371
CPS-???? | Linking Off-Chain Identities #1059
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
Kammerlo
wants to merge
36
commits into
cardano-foundation:master
Choose a base branch
from
Kammerlo:master
base: master
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 3 commits
Commits
Show all changes
36 commits
Select commit
Hold shift + click to select a range
38bf5e4
Adding 1517 metadata label to registry for Reeve - transparent and ve…
Kammerlo 42d3435
Merge branch 'cardano-foundation:master' into master
Kammerlo 912e6a2
docs: changing the metadata label for reeve after the official launch
Kammerlo 3c66f10
docs: adding reeve soft launch metadata back
Kammerlo 03c9ea4
docs: first version of CIP 1447 to start receiving feedback
Kammerlo 4f3384d
Merge branch 'cardano-foundation:master' into master
Kammerlo f08d67a
docs: added json schema + cddl description
Kammerlo c0bcf5a
docs: added id to transactions as required field
Kammerlo 1fbe657
docs: added more explanation about the tradeoff in motivation
Kammerlo 7b1d9d6
docs: incorporating feedback
Kammerlo 808cb6b
docs: incorporating feedback
Kammerlo 506132b
docs: added CPS for linking offChain identites
Kammerlo 1952ecd
applying `Tools` category
rphair 0ccfacf
applying seminal discussion link to header
rphair 1af1f1e
docs: update template, incorporated feedback
Kammerlo 8c81002
correcting title capitalisation after https://github.com/cardano-foun…
rphair b27dc02
Merge branch 'cardano-foundation:master' into master
Kammerlo e0c56b2
Merge branch 'cardano-foundation:master' into master
Kammerlo bb30aa8
docs: first draft of the KERI CIP
Kammerlo bb97df1
chore: removed reeve cip draft
Kammerlo fe4ccf3
docs: adjusted placeholders in markdown
Kammerlo ad492a5
docs: added linebreaks for better readability
Kammerlo 13e4782
docs: updated texts, removed todos, added diagrams
Kammerlo 1b26e71
docs: updated texts, removed todos, added diagrams
Kammerlo 0bc2645
docs: added copyright
Kammerlo b160e25
docs: some feedback incorporated
Kammerlo d83834c
docs: incorporated feedback
Kammerlo c7e8a70
docs: added rationale
Kammerlo ac4057a
docs: added example data
Kammerlo 2f2948e
docs: replaced old schema
Kammerlo 9b2525a
docs: renamed files to cesr and linked revocation in doc
Kammerlo 8621abc
docs: incorporated feedback
Kammerlo 47f7207
docs: incorporated feedback
Kammerlo fc38ac9
docs: typos
Kammerlo 817f7c3
Merge pull request #2 from Kammerlo/feat/keri-cip
Kammerlo 9338979
add trailing CIP-0010 DB array comment (coding standard & CI validation)
rphair 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,50 @@ | ||
| --- | ||
| CPS: ???? | ||
| Title: Linking Off-Chain identity solutions to On-Chain Transactions | ||
| Status: Open | ||
| Category: Tools | ||
| Authors: | ||
| - | ||
| Proposed Solutions: | ||
| - | ||
| Discussions: | ||
| - https://github.com/cardano-foundation/CIPs/pull/1059 | ||
| Created: 2025-07-09 | ||
| License: _ | ||
| --- | ||
|
|
||
| ## Abstract | ||
|
|
||
| Transactions often involve multiple parties, including individuals and organisations. | ||
| To facilitate these interactions, it is essential to have a reliable way to verify the identities of participants. | ||
| Most of the organisations have off-chain identities, which they could leverage to enhance the trust and security of their on-chain transactions. | ||
| Off-chain identities could be solutions like: [GLEIF](https://www.gleif.org/en), [KERI Identifiers](https://identity.foundation/keri/), ... | ||
| While Cardano's on-chain data model provides a robust framework for transaction verification, it lacks a standardized mechanism for off-chain identity verification. | ||
|
|
||
| This limitation makes it difficult to verify the identity of participants, establish trust, and comply with regulatory requirements. | ||
| This problem statement outlines the need for a standardized solution for off-chain identity verification on Cardano to enhance trust, security, and adoption. | ||
|
|
||
| ## Problem | ||
|
|
||
| The core problem is the absence of a standardized, self-sustaining and user-friendly solution for linking decentralized off-chain identifiers to on-chain transaction on the Cardano blockchain. | ||
| This gap creates several challenges: | ||
| - **Trust and Security**: Without a reliable way to verify identities, it is difficult to establish trust between parties involved in transactions. This can lead to fraud, manipulation, and other security issues. | ||
| - **Compliance**: Many industries require strict compliance with regulations related to identity verification. The lack of a standardized solution makes it challenging for businesses and organizations to meet these requirements. | ||
| - **User Experience**: Current solutions for off-chain identity verification are often fragmented and complex, leading to a poor user experience. Making it impossible for others to integrate these solutions e.g. explorers | ||
|
|
||
| ## Use cases | ||
| The need for a standardized solution for decentralized off-chain identity verification on Cardano is driven by several use cases, including: | ||
| - **Accountability**: When publishing financial reports, it is essential to verify the identity of the individuals or organizations responsible for the report. This helps to ensure that the information is accurate and trustworthy. | ||
| - **Supply Chain Tracking**: In supply chain, parties involved in the process need to verify the identity of each other to ensure that the products are genuine and meet quality standards. | ||
| This is particularly important in industries such as pharmaceuticals, where counterfeit products can have serious consequences. | ||
|
|
||
Kammerlo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| ## Goals | ||
|
|
||
| The goal of this problem statement is to initiate a discussion within the Cardano community about the need for a standardized framework for off-chain identity verification. | ||
| The ultimate objective is to develop a solution that: | ||
| - **Is secure and trustworthy**: The solution should provide a high degree of security and be resistant to fraud and manipulation. | ||
| - **Is self-sustaining**: The solution should be able to operate independently of any single entity or organization, ensuring decentralization and resilience. | ||
| - **Is interoperable**: The solution should be compatible with a wide range of applications and services. (For example easy to integrate into existing solutions, like explorers, wallets, and dApps.) | ||
| - **Is compliant with regulations**: The solution should help businesses and organizations to comply with relevant regulations. | ||
|
|
||
| The solution should be able to handle different types of identify solutions, so it shouldn't be tied to a specific identity solution, but rather provide a framework for integrating different solutions. | ||
Kammerlo marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
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.