# Data Attestation

Clique provides various on-chain historical data sources. Check the following list to find what you need. For more information, please refer to a complete toolchain SDK here at [Clique Attestation SDK](/toolchain/clique-attestation-sdk.md).

#### List of Data Sources

* \[arbitrum one]
* \[ethereum mainnet]

### Example

A  more complex example pasted here:

```toml
name = "clique_arbitrumInfo"
spec-version = "1"
type = "Schema"

proof-type = ["TEE"]

[input]
address = { type = "string" }

[output]
createdBlock = { type = "u256", ref = "$tasks.clique_arbitrumCreatedBlock.data" }
lastActiveBlock = { type = "u256", ref = "$tasks.clique_arbitrumLastActiveBlock.data"}

[[tasks]]
name = "clique_arbitrumCreatedBlock"
proof-preference = "TEE"
[[tasks.input]]
address = { ref = "$input.address" }

[[tasks]]
name = "clique_arbitrumLastActiveBlock"
proof-preference = "TEE"
[[tasks.input]]
address = { ref = "$input.address" }
```

In this example,  we create a schema (phantom task) which includes two tasks -- [`clique_arbitrumCreatedBlock`](https://example.com), [`clique_arbitrumLastActiveBlock`](https://example.com), and reconstruct their outputs into the struct that we want.


---

# 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://docs.clique.tech/sample-task-tutorials/data-attestation.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.