> For the complete documentation index, see [llms.txt](https://web3wed.gitbook.io/web3wed/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://web3wed.gitbook.io/web3wed/litepaper/digital-identities.md).

# Digital identities

The Vow Ritual is, technically speaking, a blockchain marriage between two digital identities.

When you sign in with Google, Apple, or another account, Web3Auth creates a blockchain wallet tied to that identity. Your vow is then recorded as a transaction between two wallets — two digital selves, cryptographically bound to a single moment.

This is what gets written into the ledger:

* Two verified digital identities
* A timestamp
* A permanent link between them

The technology is invisible. You sign in as yourself, speak your vow, and the blockchain handles the rest. No crypto knowledge required.

But make no mistake about what is actually happening: two digital identities are entering a recorded union. The vow is the human layer. The blockchain marriage is the infrastructure beneath it.


---

# 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://web3wed.gitbook.io/web3wed/litepaper/digital-identities.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.