> For the complete documentation index, see [llms.txt](https://docs.projectcatalyst.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectcatalyst.io/open-funding/funding-basics/integration-guides/on-chain-identity-cip-0170.md).

# On-chain identity (CIP-0170)

#### What it is

CIP-0170 brings verifiable, tamper-resistant identity to Cardano through KERI-backed metadata attestations (KERI is a decentralized key-management protocol; it lets an identity prove itself cryptographically without depending on any single blockchain or registry). Organizations and individuals can anchor signed, decentralized-identity attestations on-chain, and increase trust by proving their real-world identity. The Cardano Foundation's Reeve is the reference implementation: think verifiable organizational identity and audit-grade reporting.

#### What you could build

* Verifiable organizational identity for businesses transacting on Cardano
* Tamper-resistant reporting and attestations (Reeve-style audit trails)
* Identity-anchored credentials for access, compliance, or reputation systems

#### What the pilot expects

Leveraging CIP-0170 means valid signed attestations carrying your declared identifier, anchored on mainnet. The fee counts only when it isn't paid from your own wallets (Standard §5.2). If your architecture has your operator submit attestations on users' behalf, those fees will not count, so plan for users or independent parties to anchor their own. Floors and target guidance for this category are in the Transaction Integrity Standard (§3.1, §3.3).

#### Get building

* [CIP-0170 proposal (CIPs PR #1113)](https://github.com/cardano-foundation/CIPs/pull/1113) ·[ CIP-0170 in the CIPs repo](https://github.com/cardano-foundation/CIPs/tree/master/CIP-0170)
* [CIP-0170 explained, Developer Office Hours, Jan 2026](https://developers.cardano.org/blog/2026-01-16-media-cardano-developer-office-hours/)
* Tooling:[ signify-ts](https://github.com/WebOfTrust/signify-ts) ·[ cf-signify-java](https://github.com/cardano-foundation/cf-signify-java)

#### Readiness & constraints

**The earliest-stage of the areas, so set your expectations accordingly**. CIP-0170 pairs well with the other areas of interest in this pilot - for example, combining identity with a stablecoin or programmable-token integration in the same proposal. CIP-0170 is a proposed standard, ready to be adopted but not yet formally finalized. Reference tooling exists and works; some supporting components are still maturing. If you build here, you're an early adopter, with the visibility and the rough edges that implies.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.projectcatalyst.io/open-funding/funding-basics/integration-guides/on-chain-identity-cip-0170.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.