> For the complete documentation index, see [llms.txt](https://docs.yolkfi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yolkfi.com/03.-stellar-ecosystem-integrations/privy.md).

# Privy (Embedded Wallets)

To achieve mainstream adoption, YolkFi integrates **Privy** for non-crypto agricultural investors.

***

### Architecture & Capabilities

* **Frictionless Web2 Login:** Email OTP, SMS, Google, Apple, or Passkeys.
* **Non-Custodial Ed25519 Provisioning:** Secure Shamir Secret Sharing in Trusted Execution Environments (TEEs).
* **Tier-2 Raw Sign Integration:**

  ```typescript
  // User signs 32-byte transaction hash
  const signatureBytes = await userWallet.rawSign({
    data: txHashBuffer,
  });
  ```
* **Seamless Claims:** Users can claim $YOLK yield distributions with a single tap without handling gas fees or raw private keys.

***

### Division of Responsibility & Transaction Construction

Because Stellar is supported as a Tier-2 wallet abstraction chain on Privy:

1. **Application Layer (YolkFi):** Constructs Soroban transaction operations, simulates resource footprints via Soroban RPC, assembles unsigned XDR, and broadcasts signed payloads to Stellar.
2. **Key Management Layer (Privy):** Holds non-custodial user shares in secure TEEs and returns cryptographic Ed25519 signatures over the transaction envelope hash.

***

### Roadmap: SEP-45 Passkey Smart Accounts

While Privy delivers instant, cross-platform email and social onboarding for launch, YolkFi's wallet architecture is designed with modular abstraction. As the Stellar ecosystem standardizes **SEP-45 (Passkey-Secured Smart Contract Accounts)**, the protocol can progressively incorporate native on-chain passkey accounts, offering users fully decentralized, browser-native biometrics directly on Soroban.


---

# 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.yolkfi.com/03.-stellar-ecosystem-integrations/privy.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.