> For the complete documentation index, see [llms.txt](https://docs.onta.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onta.network/basics/interactive-blocks/vaultlink.md).
# VaultLink
VaultLink reimagines crypto wallets through passkey-powered smart wallets with social login. Unlike traditional crypto wallets that require managing private keys or seed phrases, VaultLink eliminates this complexity entirely. Users can access their funds securely without worrying about losing seed phrases or having their keys compromised.
The system uses Web Authentication (WebAuthn) standards, connecting wallet access to your device's biometrics and security hardware. When you create an account, a unique key pair is generated in your device's secure enclave - the public key is registered on-chain while the private key never leaves your device. This maintains security while feeling as familiar as logging into your favorite apps.
Social login integration (like Gmail) makes the experience even smoother by linking these secure credentials to accounts you already use, enabling one-click setup and recovery across all your devices. This approach delivers bank-grade security with the simplicity of everyday apps, making blockchain accessible without requiring any technical knowledge.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.onta.network/basics/interactive-blocks/vaultlink.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
