> For the complete documentation index, see [llms.txt](https://privy-labs.gitbook.io/privy-labs-protocol-whitepaper-v-1.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://privy-labs.gitbook.io/privy-labs-protocol-whitepaper-v-1.0/the-core-technology/systems-overview.md).

# Systems Overview

### Core Systems

Utilizing our **VAS (Virtual Account System)**, creators can anonymously and globally associate themselves with every piece of content they create, allowing people to establish ownership over works they’ve created under any pseudonym or username, maintaining their privacy, mystery, and artistic integrity.

Utilizing our **CCTS (Content Certificate & Tracking System),** creators can mark their and certify content as original through our unique watermarking and certificate issuance; the resulting effect is deterring content piracy and theft (as the question on who “owns” the work is available in the public domain), as well as reducing the time/effort asymmetry in verifying said work.

With our **CVN (Content Verification System)**, we aim to offer creators greater control over where their content is shared and re-shared by utilizing affirmative domain permissioning. When this permissioning system is combined with our CCTS marking, it creates an irrefutable basis upon which to show or remove content per original publisher intent, fortifying legal standards like the Digital Millennium Copyright Act (DMCA) and setting the stage for an internet where every piece of content is fully controlled end-to-end by creators themselves. 

### EVM Compatibility

As an EVM-compatible protocol, our technology can be used with the majority of leading level 1 smart contract networks (Polygon, Avalanche, Ethereum, Binance Smart Chain, etc) and infrastructure tooling (i.e. any EVM-compatible wallet like Metamask, Phantom, Rainbow, Trust, etc.) that are recognized by the Ethereum nodes, maintaining lower cost without sacrificing speed, flexibility, and reliability.

<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://privy-labs.gitbook.io/privy-labs-protocol-whitepaper-v-1.0/the-core-technology/systems-overview.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.