Skip to content
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 Mar 17, 2025
42d3435
Merge branch 'cardano-foundation:master' into master
Kammerlo Jul 8, 2025
912e6a2
docs: changing the metadata label for reeve after the official launch
Kammerlo Jul 8, 2025
3c66f10
docs: adding reeve soft launch metadata back
Kammerlo Jul 9, 2025
03c9ea4
docs: first version of CIP 1447 to start receiving feedback
Kammerlo Jul 17, 2025
4f3384d
Merge branch 'cardano-foundation:master' into master
Kammerlo Jul 17, 2025
f08d67a
docs: added json schema + cddl description
Kammerlo Jul 17, 2025
c0bcf5a
docs: added id to transactions as required field
Kammerlo Jul 17, 2025
1fbe657
docs: added more explanation about the tradeoff in motivation
Kammerlo Jul 18, 2025
7b1d9d6
docs: incorporating feedback
Kammerlo Jul 18, 2025
808cb6b
docs: incorporating feedback
Kammerlo Jul 18, 2025
506132b
docs: added CPS for linking offChain identites
Kammerlo Jul 22, 2025
1952ecd
applying `Tools` category
rphair Jul 23, 2025
0ccfacf
applying seminal discussion link to header
rphair Jul 23, 2025
1af1f1e
docs: update template, incorporated feedback
Kammerlo Jul 23, 2025
8c81002
correcting title capitalisation after https://github.com/cardano-foun…
rphair Jul 23, 2025
b27dc02
Merge branch 'cardano-foundation:master' into master
Kammerlo Sep 17, 2025
e0c56b2
Merge branch 'cardano-foundation:master' into master
Kammerlo Nov 5, 2025
bb30aa8
docs: first draft of the KERI CIP
Kammerlo Nov 5, 2025
bb97df1
chore: removed reeve cip draft
Kammerlo Nov 5, 2025
fe4ccf3
docs: adjusted placeholders in markdown
Kammerlo Nov 5, 2025
ad492a5
docs: added linebreaks for better readability
Kammerlo Nov 5, 2025
13e4782
docs: updated texts, removed todos, added diagrams
Kammerlo Nov 6, 2025
1b26e71
docs: updated texts, removed todos, added diagrams
Kammerlo Nov 6, 2025
0bc2645
docs: added copyright
Kammerlo Nov 6, 2025
b160e25
docs: some feedback incorporated
Kammerlo Nov 7, 2025
d83834c
docs: incorporated feedback
Kammerlo Nov 10, 2025
c7e8a70
docs: added rationale
Kammerlo Nov 10, 2025
ac4057a
docs: added example data
Kammerlo Nov 10, 2025
2f2948e
docs: replaced old schema
Kammerlo Nov 10, 2025
9b2525a
docs: renamed files to cesr and linked revocation in doc
Kammerlo Nov 10, 2025
8621abc
docs: incorporated feedback
Kammerlo Nov 10, 2025
47f7207
docs: incorporated feedback
Kammerlo Nov 10, 2025
fc38ac9
docs: typos
Kammerlo Nov 11, 2025
817f7c3
Merge pull request #2 from Kammerlo/feat/keri-cip
Kammerlo Nov 11, 2025
9338979
add trailing CIP-0010 DB array comment (coding standard & CI validation)
rphair Nov 13, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 50 additions & 0 deletions CPS-????/README.md
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.

## 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.