# Validation

Once an asset is created, there are multiple ways to validate it.

## Public Asset Pages

The simplest way for anyone to validate an asset in Tephra is Each asset is given its own public page on [Tephra Validate](http://v.tephra.co). The page contains details about the contents of the asset, when it was created, when it was granted, etc.

The url for any Tephra asset is simple to construct:

```typescript
`http://v.tephra.co/a/${theAssetAddress}`

// e.g.,
// http://v.tephra.co/a/7f9e9041-86cb-4250-9eb8-eb9fdd03bc9e
```

You can view some example asset pages below ***(COMING SOON)***:

* **Branded** —  
* **Minimal** — A registered address with no owner and no content.

## Tephra SDK

Using the SDK, you can pull details about any address on the platform, and all related transactions on the changeset.

```typescript
const asset = await tephra.get("7f9e9041-86cb-4250-9eb8-eb9fdd03bc9e")

// Example Output
{
  address: "7f9e9041-86cb-4250-9eb8-eb9fdd03bc9e",
  lastUpdated: "Mon Jul 26 2021 12:40:45 GMT-0400 (EDT)",
  content: {
    name: "Painting of a Field",
    description: "A painting of a field."
  },
  status: "active",
  owner: "d015372b9ac1"
}
```

## Reconstructing Preserves

The changeset is regularly chunked, compressed, uploaded publicy in IPFS, and the address is timestamped on Ethereum *(see* [*Preservation*](https://tephra.gitbook.io/tephra-sdk/preservation)*)*. This means the state of the network can be reconstructed at any time from publicly available means.

All of the IPFS chunks are gzipped JSON. By unpacking them and placing them in order, you can reconstruct every transaction accross the entire network.


---

# Agent Instructions: 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:

```
GET https://tephra.gitbook.io/tephra-sdk/getting-started/validation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.