> For the complete documentation index, see [llms.txt](https://docs.blockscholes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockscholes.com/blockchain-oracle/overview.md).

# Overview

Introduction to Block Scholes Oracles and how to choose between Push-Based and Pull-Based integration methods.

Block Scholes provides robust and reliable oracle solutions tailored for decentralized finance applications. Our oracle infrastructure supports two integration models, allowing developers to choose the best fit for their use case:

* **Push-Based Oracle** (Simplicity and Lowest On-Chain Integration Effort)
* **Pull-Based Oracle** (Maximum Control and Real-Time Freshness)

Both oracle types deliver high-quality financial data — including implied volatility surfaces, instrument pricing across asset classes, and derived metrics — but differ in how this data is retrieved and verified.

### Oracle Types at a Glance

| Feature                | Push-Based Oracle                                                     | Pull-Based Oracle                                       |
| ---------------------- | --------------------------------------------------------------------- | ------------------------------------------------------- |
| Data Retrieval         | On-chain smart contract query                                         | Off-chain via REST/WebSocket                            |
| Data Freshness         | Updated at ≥1-minute intervals or based on price deviation threshold. | Real-time                                               |
| Integration Complexity | Low                                                                   | Medium                                                  |
| Signature Verification | Not required                                                          | Available (via EIP-712)                                 |
| Best For               | Simplicity, Fast Integration, Prototyping, Cost-Effectiveness         | Latency-Sensitive & Real-time Applications, Flexibility |

### When to Use What?

* Use the **Push-Based Oracle** for simple integrations where ≥1-minute update frequency is sufficient.\
  It also supports **% deviation triggers** to also push updates whenever markets move meaningfully.
* Use the **Pull-Based Oracle** when you need full control over update timing, especially for **high-frequency use cases.** Signature verification is **available via EIP-712** for trustless use.


---

# 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.blockscholes.com/blockchain-oracle/overview.md?ask=<question>&goal=<user_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.