Skip to main content
First things first!

Tell us where your smart contract is so we can read your events from it.

This is the chain where your contract is deployed to.
Address of your smart contract, starts with 0x
Starting point

What is the starting point? From which block number should we start looking for your events? This is usually the block on which your smart contract was deployed.

Kenshi uses this as the starting block to look for events emitted from your smart contract.
Oracle logic

We will send matching events to this endpoint for processing, the returned response will be sent to your smart contact. This endpoint should implement the Kenshi Custom Oracle Protocol.

Address of the oracle's HTTP endpoint
Contract ABI

Kenshi needs to understand your smart contract to be able to look for its events or call its methods.

Human readable ABI of your contract.
Event Signature

We will send events with this signature (emitted from your smart contract) to your oracle endpoint.

Event signature to look for
Concurrency

How many requests at max should the oracle be able to process at the same time? This affects a multitude of factors, read more here.

Defines how many requests can be processed at the same time
Billing

Custom oracle's cost a fixed monthly fee for the infrastructure, plus a variable cost depending on how many requests are processed.