Practical overview
When it fits
Use it when building or operating Kaia-connected smart-contract applications that need oracle data, randomness or operator-managed oracle services.
Who it is for
- Smart-contract developers integrating oracle data or verifiable randomness.
- Node operators managing VRF or request-response services.
- Teams building off-chain oracle aggregation or delegated fee-payment workflows.
Documented uses
- Provide request-response data to smart contracts through an oracle service.
- Operate a VRF service for applications requiring verifiable randomness.
- Access oracle service data through the API and manage services through the CLI.
- Run off-chain aggregation and delegated transaction fee-payment components.
Requirements & limits
The repository is public and specifies the MIT license.
- The repository separates on-chain contracts from off-chain implementations and services.
- The API serves service data to other components; the CLI is intended for node-operator management.
- The documented Docker configuration runs either VRF or request-response at a time.
- Local setup requires wallet credentials and chain configuration; VRF setup also calls for chain-specific key configuration.
- For non-local chains, the README describes using existing contract addresses rather than deploying Coordinator and Prepayment contracts.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Prepare a local VRF or request-response service
Build the local Docker images and configure the documented service prerequisites.
Before you start
- Docker Compose
- Wallet address and private key values for the environment file
- A CHAIN selection of baobab or cypress
- VRF key configuration file when setting up VRF
Steps
Build the images with
docker-compose -f docker-compose.local-core.yaml build.Set
ADDRESSandPRIVATE_KEYin.core-cli-contracts.envand selectbaobaborcypressforCHAIN.For VRF, update the key file corresponding to the selected chain.
Expected outcome
The local images are built and the documented wallet, chain and (for VRF) key settings are prepared.
Guide limitations
- These steps cover image building and configuration, not starting or validating a running service.
- The Docker implementation is designed for one of VRF or request-response at a time.
- For chains other than localhost, the README says existing Bisonai contract addresses are used rather than deploying Coordinator and Prepayment contracts.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- Bisonai/orakl · Official homepage title · retained in its source language

