> For the complete documentation index, see [llms.txt](https://docs-v4.venus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v4.venus.io/technical-reference/reference-oracle/oracles/sequencer-chainlink-oracle.md).

# SequencerChainlinkOracle

## SequencerChainlinkOracle

### Mainnet versions

The following proxy implementations were read on August 27, 2026 and match the [`SequencerChainlinkOracle` v2.16.0 source](https://github.com/VenusProtocol/oracle/blob/v2.16.0/contracts/oracles/SequencerChainlinkOracle.sol):

| Network      | Checked block | Proxy                                        | Implementation                               |
| ------------ | ------------: | -------------------------------------------- | -------------------------------------------- |
| Arbitrum One |   `498888003` | `0x9cd9Fcc7E3dEDA360de7c080590AaD377ac9F113` | `0x4256f572B8738126466e864D453BCCD0281b3C6C` |
| Optimism     |   `156113793` | `0x1076e5A60F1aC98e6f361813138275F1179BEb52` | `0x1Abf4919dE8ae2B917d553475e9B1D9CdE6E36D3` |

The sequencer feed is immutable in each implementation. Resolve and verify that immutable rather than assuming the network name alone selects the correct feed. Token feeds, stale periods, direct overrides, ownership, and ACM permissions are still dynamic proxy configuration.

This contract inherits the complete [ChainlinkOracle API](/technical-reference/reference-oracle/oracles/chainlink-oracle.md), including `initialize`, `NATIVE_TOKEN_ADDR`, `prices`, `tokenConfigs`, `setDirectPrice`, `setTokenConfig`, `setTokenConfigs`, `owner`, `pendingOwner`, `transferOwnership`, `acceptOwnership`, `renounceOwnership`, `accessControlManager`, and `setAccessControlManager`. Its override adds the one-hour sequencer recovery grace-period check before returning a price.

Oracle to fetch price using chainlink oracles on L2s with sequencer

## Solidity API

#### sequencer

L2 Sequencer feed

```solidity
contract AggregatorV3Interface sequencer
```

***

#### GRACE\_PERIOD\_TIME

L2 Sequencer grace period

```solidity
uint256 GRACE_PERIOD_TIME
```

***

#### constructor

Contract constructor @param \_sequencer L2 sequencer @custom:oz-upgrades-unsafe-allow constructor

```solidity
constructor(contract AggregatorV3Interface _sequencer) public
```

***

#### getPrice

Gets the price of a asset from the chainlink oracle

```solidity
function getPrice(address asset) public view returns (uint256)
```

**Parameters**

| Name  | Type    | Description          |
| ----- | ------- | -------------------- |
| asset | address | Address of the asset |

**Return Values**

| Name | Type    | Description                                                       |
| ---- | ------- | ----------------------------------------------------------------- |
| \[0] | uint256 | Price in USD from Chainlink or a manually set price for the asset |

***


---

# 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-v4.venus.io/technical-reference/reference-oracle/oracles/sequencer-chainlink-oracle.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.