A blockchain cannot look at the world by itself. An oracle is the bridge that brings a real-world figure on-chain. Opsikom is built so that no single party decides that figure.
◉
Open and free
Reading a feed needs no permission, key or payment. The project covers the cost of publishing updates.
◈
Many sources, many nodes
Each feed declares its public sources. Independent operators read them separately and sign what they see.
≈
Chainlink-compatible
Every feed can be read through the standard aggregator interface, so existing code only needs a new address.
Current status. Opsikom runs on the Sepolia test network. It is a beta: the code has not been independently audited and there is no real value at stake. Do not use it for real funds yet.
What it is not
Not a token. There is no Opsikom coin, and anyone using the name for a token is not us. It never asks you to connect a wallet or share keys.
Not a source of truth. A feed reports what its declared sources publish. If a source is wrong or later revised, the feed follows it.
Not an instant price feed. The first feeds are slow-moving public measurements, updated daily or monthly.
Create a coin
A coin that follows the planet.
With Opsikom anyone can make a coin that reacts to the real world. No company and no person controls it: only the data does.
The example: SunCodex
SunCodex is a test coin built on Opsikom. Every month Opsikom publishes the new temperature of the Earth, measured by five public climate datasets. If the planet got warmer, SunCodex burns some coins. If it cooled down, new coins are created. The number of coins moves with the climate, like a thermometer you can keep in your wallet.
Why nobody controls it
The rule is written into the coin once, when it is created. After that nobody can change the numbers: not the creator, not the Opsikom team. Independent computers read the official measurements on their own, and the blockchain accepts a value only when they agree. Your coin depends on one thing only: how the temperature moves.
Make your own, on a test network
Test networks use play money, so you can try everything for free and safely. You need a wallet like MetaMask, a little test ETH from the Opsikom faucet, and a simple rule: what happens when the number goes up, and when it goes down. The coin guide walks you through it step by step, in plain words, and can write the contract with you.
Good to know. Opsikom has no token of its own, and test coins have no value. Nobody from Opsikom will ever ask for your secret recovery phrase or private key.
Architecture
One oracle. Many real-world signals.
Opsikom separates data sources from signing nodes. Sources provide the measurement, independent nodes verify and sign it, and the contract applies quorum, majority and median before publishing.
Data path
From reality to blockchain.
01 · SourcesCSV files, APIs and public datasets from institutions.
→
02 · NodesIndependent operators read the sources and sign the value.
→
03 · ContractChecks signatures, quorum, majority, limits; computes the median.
→
04 · On-chainA numbered round with value and timestamp, readable by anyone.
What happens in one update round
Operators read the sources. Each node downloads the declared public data on its own and computes the feed value. Operators must not copy each other: independence is the point.
Each node signs a report. The report is an EIP-712 message containing the feed, the next round number and the value. Signing costs nothing and needs no funds.
A relayer collects the signatures. Anyone can run a relayer. It contacts the registered nodes, checks each signature, sorts them by signer address and sends them in one transaction. The relayer pays the gas.
The contract verifies. It checks that the feed exists, enough time has passed since the last round, every signer is a registered operator, no signer appears twice, the number of signatures reaches the quorum and exceeds half of the operators.
The contract aggregates. It takes the median of the signed values. With an even number it averages the two middle ones. An optional step limit rejects a result that moves too far from the previous round.
The round is stored. Value, round number and block timestamp are written on-chain. A Chainlink-compatible adapter exposes them to other contracts.
Why the median
With five operators reporting 1.46, 1.46, 1.47, 1.46 and a faulty 3.20, the average is pulled up to 1.81 while the median stays at 1.46. A minority of wrong or dishonest nodes cannot move the published value.
Security model
Built around consensus, not a single number.
These are the protections implemented in the contract today, and the ones that are still open.
✓
EIP-712 signed reports
A signature covers the feed, the round and the value, inside a domain bound to the chain and to the oracle contract. It cannot be replayed on another chain or contract.
◈
Quorum + strict majority
A round needs the feed's quorum and more than half of its registered operators. Three colluding nodes cannot decide a feed of ten.
◎
Median aggregation
Extreme values from a minority have no influence on the final figure.
↻
Round binding
Each report is tied to a specific round number, so an old signature cannot be reused for a later round.
☰
No duplicate signers
Signatures must come in strictly increasing signer order, which makes counting one operator twice impossible.
△
Step and interval limits
Each feed has a maximum movement per round and a minimum time between rounds, against implausible jumps and spam.
Governance
The owner creates feeds, approves operators and sets limits. Operator applications are open to anyone but approval is deliberately manual, to keep fake nodes out.
lockFeed permanently freezes a feed's operators and parameters once its committee is stable.
Ownership is meant to move to a multisig before any use with real value.
Known limits
Be clear about what is not yet proven.
The code has not been independently audited.
The four operators now run on three separate machines, but all of them are still run by the project, so independence from the team is not yet demonstrated. It needs operators run by other people.
Feeds depend on their sources. A wrong or revised source value reaches the feed.
Reports sign the value only. The measurement time is not part of the signature: the on-chain timestamp is the time of publication.
Network
Who signs today.
Four operator keys on three machines. A round needs three signatures, so no single machine can publish a value on its own. The list below is read from the contract.
Quorum 3 of 4 + strict majorityThen the contract publishes the median of the signed values.
What this shows, and what it does not. Losing one machine does not stop the oracle, and taking over one machine is not enough to publish a false value. All three machines are still run by the project: real independence needs operators run by other people.
Feed catalog
Twenty-four feeds, free to read.
Six topics, from global temperature to earthquakes. The values on the cards are read from the blockchain by your browser as you open the page.
reading the chain…
Median of the sourcesEach source gives its latest reading; with three or more, the feed is their median.
One or two sourcesThe feed takes the most recent reading, and its card says so.
As soon as the source publishesThe nodes check every source every 30 minutes: when a source publishes a new figure, the feed gets a new round within the hour. Exceptions with their own rhythm: earthquakes (QUAKES_M5) once a day at a random hour, the solar wind every day at 10:30 UTC.
+
Add your feed
Have public numeric data the world should be able to read on-chain? Propose it. You need at least three independent public sources, a clear definition and a licence that allows republishing.
A number without a definition is a guess. Before a feed is activated, its sheet is published with every field below.
Field
What it fixes
Example
Feed ID
The name, hashed with Keccak-256 to get the on-chain identifier.
GLOBAL_TEMP
Quantity and unit
What is measured and how it is expressed.
Anomaly in °C versus pre-industrial
Decimals
Values are integers scaled by 10decimals. Fixed at creation, never changed.
4 decimals: 14600 = 1.46
Scope
Global, a region, or a fixed list of locations.
Global mean
Aggregation
How the value is computed from each source and across operators.
Latest reading of each source, median; with fewer than three sources, the most recent reading
Sources
The public datasets read independently by every operator, with a minimum number of valid ones.
Several datasets, at least 3 valid; or one declared source
Cadence
How often a round is expected, and the on-chain minimum interval.
Weekly or monthly, depending on how often the source updates · minimum interval fixed on-chain
Limits
Quorum, maximum step per round, freshness advice for consumers.
Quorum 3 · step 0.5 °C
Licence and attribution
The source licence and the credit that goes with the data.
Open Government Licence v3
Proposing a feed
Anyone can propose one. A good proposal gives public numeric data, preferably from at least three independent sources, a clear definition and a licence that allows republishing. Where only one source exists, the feed says so on its card and takes that source’s most recent reading. Feeds that could create an incentive to cause harm, or that rely on personal data, are not accepted.
Operators
Run a node.
Nodes are light: they read a few files, compute a figure and sign it. A Raspberry Pi 3 or a small VPS is enough.
Requirements
Linux (Raspberry Pi OS, Debian or Ubuntu)
Node.js 18 or newer, about 1 GB of RAM
Always on, with internet access
A reachable address for your node (for now)
What it costs
Signing needs no funds
A few cents of test ETH, once, to apply
Whoever sends the signatures (the relayer) pays the gas
Operators are volunteers; there is no reward today
How to join
Install the node software and set the network, the oracle address and your public address in the configuration file.
The node creates its own signing key on first start and prints its address. Back the key up and never share it.
It applies by itself with one small transaction. Your application appears in the pending list.
The owner approves. Every operator is checked before joining a feed's committee.
You are in. The relayer finds your node from the address you registered on-chain and collects your signature each round.
# after unpacking the node software
cd node && npm install
cp .env.example .env # RPC_URL, HUB_ADDRESS, FEEDS, PUBLIC_URL
npm run node # key creation + application happen on first start
Coming next: an "outbound" mode where the node sends its signatures out instead of waiting to be contacted, so a home Raspberry Pi will need no public address and no open port. The source code will be published with the first release.
Independence matters. Read the sources yourself, from the original institution, and do not share data or keys with other operators.
Developers
Use a feed in your contract.
Every feed has an adapter that speaks the standard Chainlink aggregator interface. If your code already reads such a feed, you only change the address.
Solidity
// FEED_ADAPTER = address of the feed's adapter (see Contracts)
AggregatorV3Interface feed = AggregatorV3Interface(FEED_ADAPTER);
(, int256 answer,, uint256 updatedAt,) = feed.latestRoundData();
// always reject stale data; pick the age that suits your feedrequire(block.timestamp - updatedAt < 35 days);
// the value has feed.decimals() decimal places (4 → 14600 = 1.46)
See all of this live, with current values and operators, on the status page.
Test deployment
Addresses on the Sepolia test network.
These contracts have no real value. Addresses for any main network will be published only on this website and in the official repository.
Contract
Address
The temperature of the planet (GLOBAL_TEMP) is also published on Arbitrum Sepolia, with the same reading interface: hub 0xEDED95E0cB80A8Da4aeF1cd2c3fa8b6960Ede9b6, GLOBAL_TEMP reader 0xc7bEeC2e6349392dDc90799b44D21a4AB3A9De0a. Want to build a coin on it? Start from Create a coin.
Roadmap
Where it stands, and what is next.
No dates are promised. The order matters more than the calendar.
Done on the test network
Hub contract with feeds, operators and rounds
Chainlink-compatible adapters
Node and relayer software
Operator applications and approval
Automated tests of quorum, ordering, median, limits
Rounds published, a node switched off, a new operator joined
35 feeds with declared public sources
Scheduled publishing: earthquakes every 3 days, weekly and monthly feeds
Operators split across three machines: none can reach the quorum alone
SunCodex, a test coin that follows the temperature of the planet
Live status page
Feeds also published on Base, Robinhood Chain and Arbitrum test networks
A free test ETH faucet and a guide to create your own coin
Next
Publish the feed sheets and the source code
Operators run by other people, not by the project
"Outbound" node mode for home devices
Design and build multi-location feeds
Longer minimum interval and multisig ownership
Before real value
Independent security audit
Enough independent operators per feed
Choice of the main network
Bug-report channel and a small reward fund
Legal review of any token or reward idea
FAQ
Questions people ask.
Is it really free?
Reading is free: no key, subscription or waiting list. Publishing a round costs a little gas, which the project pays for now. Making that sustainable over time, through grants or sponsors, is an open question.
Can I create my own coin?
Yes, on a test network and for free. Open the coin guide with the "Create a coin" button: it explains each step in simple words, with SunCodex as the example. Your coin will follow the data, not anyone's decision.
Is there a token?
No. Opsikom has no coin. If you see a token using the name, it is not ours. Operators are volunteers and there is no reward today.
Who decides the value?
The operators' signatures, through the median. The owner cannot write a value: it can only manage feeds and approve operators. The sources are public and declared for every feed.
What if a source publishes a wrong number?
The feed follows it. Using several independent sources and requiring a minimum number of valid ones limits the damage, but cannot remove it. Many datasets are also revised later; the feed sheet tells how this is handled.
Why a median and not an average?
One faulty or dishonest value drags an average away, while a median ignores it as long as the majority agrees.
Can anyone become an operator?
Anyone can apply with one transaction. Approval is manual, on purpose: automatic approval would let one person register many fake nodes and take over the quorum.
How can I get a new feed added?
Send a proposal with public numeric data, at least three independent sources, a clear definition and a licence that allows republishing. Anything that could encourage harm, or that depends on a single source or on personal data, is declined.
Can I use it with real money?
Not yet. It is a beta on a test network and has not been audited. Wait for the audit and for independent operators.
How fresh is the data?
As fresh as the feed's cadence: monthly feeds publish once a month. Always check the update time of the round against the feed's sheet, as shown in the code examples.
How do I report a problem?
Errors in the contracts or in the node software are welcome and will be rewarded when a fund exists. A reporting channel will be published with the source code.
Glossary
Terms used here.
Feed
One measured quantity published by the oracle, identified by the hash of its name.
Round
One accepted update of a feed: a number, a value and a time.
Operator
A person or organisation running a node that reads sources and signs reports.
Relayer
Whoever sends the collected signatures to the contract and pays the gas.
Quorum
The minimum number of valid signatures needed to publish a round.
Strict majority
More than half of the feed's registered operators must have signed.
Median
The middle value of those signed; robust against a minority of wrong ones.
EIP-712
A standard way to sign structured data, bound to a chain and a contract.
Adapter
A small contract that exposes a feed through the standard aggregator interface.
Step limit
The maximum change allowed between two consecutive rounds of a feed.
Anomaly
A difference from a reference average, such as a temperature versus pre-industrial.
Testnet
A practice blockchain where tokens have no value, used to test safely.
Opsikom
Observe. Verify. Publish.
An oracle layer for applications that need real-world measurements to become transparent, verifiable blockchain data.