Legacy Deployments

(Attention!) This page specifies our legacy deployments which will be deprecated in the future.

This page is for reference only. If you want to integrate with Brevis, please use our up-to-date deployments.

Brevis SDK v0.1

SDK version: https://github.com/brevis-network/brevis-sdk/tree/release/v0.1

Brevis SDK V1 only supports same chain proving. Developer can choose Optimism or Base Mainnet to prove on-chain information

RPC Endpoint

https://brvgw.brevis.network

Optimism Deployment

Contract	Address
BrevisRequest	0x9f5b558c95292f13fa9e0328ac4d3f129c2d9562
BrevisProof	0x6CD95817F275bDf5C9cC401CbCcbFfd99c7f186A

Base Deployment

Contract	Address
BrevisRequest	0x3463b37908cc3034c635f17f5a8012577cfc2663
BrevisProof	0x2294E22000dEFe09A307363f7aCD8aAa1fBc1983

Brevis SDK v0.2

SDK version: https://github.com/brevis-network/brevis-sdk/tree/release/v0.2

Brevis system supports proving data on the same chain including Sepolia, Holesky, and BSC testnet. You can choose proof request and the contract callback happens on the above chains. Meanwhile, data from Ethereum Mainnet is available for developers on Sepolia and Holesky, by configuring the chainID in the BrevisClient section with the correct gateway endpoint.

RPC Endpoint

https://appsdkv2.brevis.network

Sepolia

Contract	Address
BrevisRequest	0x841ce48F9446C8E281D3F1444cB859b4A6D0738C
BrevisProof	0xea80589a5f3A45554555634525deFF2EcB6CC4FF

Holesky

Contract	Address
BrevisRequest	0xce17b03d7901173cbfa017b1ae3a9b8632f42c18
BrevisProof	0x728b3c4c8b88ad54b8118d4c6a65fac35e4cab6b

BSC Testnet

Contract	Address
BrevisRequest	0xF7E9CB6b7A157c14BCB6E6bcf63c1C7c92E952f5
BrevisProof	0x2241C52472862038dFFdAb38b88410CAC2685D15