Our data, sealed on-chain every 5 minutes
Funding, open interest, liquidations, depth, premiums and scores that we compute are sealed into one Merkle root per five-minute window, signed, and written to public blockchains. Nobody, including us, can change a published number afterwards without it showing. You do not have to trust this page: every check below can be repeated from the chains alone.
Punctuality
One bar per five-minute window: the seconds between the end of the window and the block that carries its seal on Solana. The protocol asks for a signature within 60 seconds and calls an anchor late after 120.
Seconds from window end to the Solana anchor
recordedNewest epochs, UTC
Verify a record in your browser
Pick a record of the newest sealed epoch. Your browser fetches its proof, recomputes every step itself with open cryptography (Keccak-256, secp256k1) and reads the anchor from a public Solana node. The signature is compared with the signer this page names; the independent verifier under Verify without us checks every epoch against the authorization log on chain.
- 01The record is a valid 104-byte leafwaiting
- 02The leaf hashes up the Merkle path to the rootwaiting
- 03That root is the one inside the signed manifestwaiting
- 04The manifest hashes to the published commitmentwaiting
- 05The signature recovers to the stream's data signerwaiting
- 06The manifest is written on-chain under its witness keywaiting
Newest epochs
Each row is one five-minute window. The links open the transaction that carries the seal.
| Epoch | Window end (UTC) | Status | Records | Commitment | Solana | Base | Anchored after |
|---|---|---|---|---|---|---|---|
| #96 | 2026-09-18 12:10 | OK | 35 | b29b30392a…740baf | final ↗ | daily | +55 s |
| #95 | 2026-09-18 12:05 | OK | 35 | 08f99f205b…d18819 | final ↗ | daily | +54 s |
| #94 | 2026-09-18 12:00 | OK | 35 | ca166c282c…f28d61 | final ↗ | daily | +52 s |
| #93 | 2026-09-18 11:55 | OK | 35 | b6f7faa5c7…56bf93 | final ↗ | daily | +51 s |
| #92 | 2026-09-18 11:50 | OK | 35 | 9f72b502d1…99cce3 | final ↗ | daily | +49 s |
| #91 | 2026-09-18 11:45 | OK | 35 | 092e98072c…015147 | final ↗ | daily | +49 s |
| #90 | 2026-09-18 11:40 | OK | 35 | 4606b2a26a…edab7d | final ↗ | daily | +48 s |
| #89 | 2026-09-18 11:35 | OK | 35 | d5c5fd4abe…5fd717 | final ↗ | daily | +46 s |
| #88 | 2026-09-18 11:30 | OK | 35 | 523f94ac63…6268fc | final ↗ | daily | +60 s |
| #87 | 2026-09-18 11:25 | OK | 35 | 08c298131f…001589 | final ↗ | daily | +59 s |
| #86 | 2026-09-18 11:20 | OK | 35 | 72d09bf236…463b6b | final ↗ | daily | +208 s |
| #85 | 2026-09-18 11:15 | OK | 35 | d33c8548d1…806a97 | final ↗ | daily | +54 s |
| #84 | 2026-09-18 11:10 | OK | 35 | 25be238169…2e481d | final ↗ | daily | +53 s |
| #83 | 2026-09-18 11:05 | OK | 35 | f5959f55b5…dc8074 | final ↗ | daily | +51 s |
| #82 | 2026-09-18 11:00 | OK | 35 | bb0f52a4be…cd2e6c | final ↗ | daily | +48 s |
| #81 | 2026-09-18 10:55 | OK | 35 | de1ebc49cb…226f0b | final ↗ | daily | +46 s |
| #80 | 2026-09-18 10:50 | OK | 35 | 15a7fc88ac…ce9ee1 | final ↗ | daily | +45 s |
| #79 | 2026-09-18 10:45 | OK | 35 | a987c08dfa…04e2f0 | final ↗ | daily | +59 s |
| #78 | 2026-09-18 10:40 | OK | 35 | b614fbb89b…65e8c6 | final ↗ | daily | +58 s |
| #77 | 2026-09-18 10:35 | OK | 35 | eb9098aed3…178707 | final ↗ | daily | +57 s |
What is sealed
The catalog of the current schema: our own derived and aggregated data, never a venue's raw rows. Values are the newest sealed epoch.
| Feed | Asset | Value | Unit | Status | Sources | Methodology |
|---|---|---|---|---|---|---|
| BYK.TURKEY.PREMIUM.INDEX | BTC | -12.07 | bps | OK | 5 / 6 | Turkey Premium Index |
| BYK.TURKEY.PREMIUM.INDEX | ETH | -9.98 | bps | OK | 5 / 6 | Turkey Premium Index |
| BYK.TURKEY.USDT.PREMIUM | USDT | -14.89 | bps | OK | 4 / 7 | Turkey USDT premium |
| BYK.LIQUIDATIONS.LONG.USD.5M | BTC | 6627.23 | USD | OK | 2 / 9 | Liquidations, 5-minute totals |
| BYK.LIQUIDATIONS.LONG.USD.5M | ETH | 648.99 | USD | OK | 1 / 9 | Liquidations, 5-minute totals |
| BYK.LIQUIDATIONS.LONG.USD.5M | SOL | 0.00 | USD | OK | 0 / 9 | Liquidations, 5-minute totals |
| BYK.LIQUIDATIONS.LONG.USD.5M | ALL | 78841.50 | USD | OK | 4 / 9 | Liquidations, 5-minute totals |
| BYK.LIQUIDATIONS.SHORT.USD.5M | BTC | 0.00 | USD | OK | 0 / 9 | Liquidations, 5-minute totals |
| BYK.LIQUIDATIONS.SHORT.USD.5M | ETH | 377.44 | USD | OK | 1 / 9 | Liquidations, 5-minute totals |
| BYK.LIQUIDATIONS.SHORT.USD.5M | SOL | 0.00 | USD | OK | 0 / 9 | Liquidations, 5-minute totals |
| BYK.LIQUIDATIONS.SHORT.USD.5M | ALL | 49019.06 | USD | OK | 4 / 9 | Liquidations, 5-minute totals |
| BYK.FUNDING.COMPOSITE.B | BTC | 0.0000074162 | fraction per hour | OK | 24 / 28 | Composite funding rate (Class B) |
| BYK.FUNDING.COMPOSITE.B | ETH | 0.0000110080 | fraction per hour | OK | 23 / 28 | Composite funding rate (Class B) |
| BYK.FUNDING.COMPOSITE.B | SOL | 0.0000125506 | fraction per hour | OK | 23 / 27 | Composite funding rate (Class B) |
| BYK.FUNDING.COMPOSITE.B | XRP | 0.0000077844 | fraction per hour | OK | 23 / 27 | Composite funding rate (Class B) |
| BYK.FUNDING.COMPOSITE.B | DOGE | 0.0000125409 | fraction per hour | OK | 21 / 26 | Composite funding rate (Class B) |
| BYK.FUNDING.COMPOSITE.B | BNB | 0.0000130742 | fraction per hour | OK | 21 / 25 | Composite funding rate (Class B) |
| BYK.OPEN_INTEREST.AGGREGATE.USD | BTC | 34161628019 | USD | OK | 25 / 28 | Aggregate open interest |
| BYK.OPEN_INTEREST.AGGREGATE.USD | ETH | 20625748912 | USD | OK | 25 / 28 | Aggregate open interest |
| BYK.OPEN_INTEREST.AGGREGATE.USD | SOL | 4554557691 | USD | OK | 24 / 27 | Aggregate open interest |
| BYK.OPEN_INTEREST.AGGREGATE.USD | XRP | 1922306644 | USD | OK | 23 / 26 | Aggregate open interest |
| BYK.OPEN_INTEREST.AGGREGATE.USD | DOGE | 982852300 | USD | OK | 22 / 26 | Aggregate open interest |
| BYK.OPEN_INTEREST.AGGREGATE.USD | BNB | 984751914 | USD | OK | 21 / 25 | Aggregate open interest |
| BYK.DERIVATIVES.PRESSURE.SCORE | BTC | 1 | score | OK | 1 / 1 | Derivatives pressure score |
| BYK.DERIVATIVES.PRESSURE.SCORE | ETH | 5 | score | OK | 1 / 1 | Derivatives pressure score |
| BYK.DERIVATIVES.PRESSURE.SCORE | SOL | 11 | score | OK | 1 / 1 | Derivatives pressure score |
| BYK.DEPTH.BID.USD.2PCT | BTC | 78168491 | USD | OK | 5 / 5 | Spot order book depth within 2 percent |
| BYK.DEPTH.BID.USD.2PCT | ETH | 42879099 | USD | OK | 5 / 5 | Spot order book depth within 2 percent |
| BYK.DEPTH.BID.USD.2PCT | SOL | 20949837 | USD | OK | 5 / 5 | Spot order book depth within 2 percent |
| BYK.DEPTH.ASK.USD.2PCT | BTC | 98783454 | USD | OK | 5 / 5 | Spot order book depth within 2 percent |
| BYK.DEPTH.ASK.USD.2PCT | ETH | 69075285 | USD | OK | 5 / 5 | Spot order book depth within 2 percent |
| BYK.DEPTH.ASK.USD.2PCT | SOL | 19870121 | USD | OK | 5 / 5 | Spot order book depth within 2 percent |
| BYK.KIMCHI.PREMIUM | BTC | 3.36 | bps | OK | 2 / 2 | Kimchi premium |
| BYK.KIMCHI.PREMIUM | ETH | 6.17 | bps | OK | 2 / 2 | Kimchi premium |
| BYK.KIMCHI.PREMIUM | XRP | 8.75 | bps | OK | 2 / 2 | Kimchi premium |
How it works
Collect
At the end of every five-minute window the engine reads our recorded tables. Only inputs stamped before the window end count, and a window is never built late: an outage becomes one visible gap, never invented values.
Seal
Each record becomes a fixed 104-byte leaf with its value, source count, coverage and age. The leaves form a Merkle tree; the root goes into a 200-byte manifest that also names the previous manifest, so the epochs form a chain.
Sign
An isolated signing service signs the manifest. It has no network access and refuses to sign a second, different manifest for the same epoch, whoever asks.
Anchor
The signed manifest is written to Solana every epoch and to Base once a day under an address derived from the stream and the epoch number, so anyone can find it without asking us.
What this proves, and what it does not
Plain limits, stated up front.
- It proves that a number was published at that time and has not been changed since. It does not prove that the number is right: methodology and sources remain ours, and the methodology text is sealed by hash with every epoch.
- Beta: the stream's governance is a single key held offline by the founder. The production stream will use two of three hardware keys.
- Beta: Base receives one seal a day instead of one per epoch. Epochs are hash-chained, so that daily seal covers everything before it.
- Most feeds are Class B: computed from our recorded tables, which are not republished. The first Class A feed, recomputable by anyone from retained raw inputs, is in preparation.
Verify without us
Everything on this page comes from a public API and from the two chains. The stream id below is the one value to pin; the rest follows from it.
curl -O https://bykaranteli.com/byk-verify.mjs node byk-verify.mjs --stream 46b69e107bc75175e86a336662311c6e198bbf0dab271c06bc5248888238f66d --network mainnetbyk-verify.mjs ↓
Questions
Why put market data on a blockchain at all?
So that history cannot be rewritten. A data vendor can quietly fix, backfill or restate numbers. Once a five-minute epoch is sealed and anchored, any later change to a record breaks the Merkle proof and everyone can see it.
Is the data itself on-chain?
No. Only a 200-byte manifest with the Merkle root and a signature goes on-chain. The records stay with us and are served with their proofs. That keeps the cost at a few dollars a month and lets paid data be sealed without being given away.
What does a missing epoch mean?
If the engine is down or late, it does not invent the window. The next epoch carries one gap manifest that states which windows were missed. Gaps are part of the public record.
Can I check this with my own code?
Yes. The format is documented byte by byte, the hash is Keccak-256, the signature is secp256k1 over the manifest hash, and the Merkle tree follows RFC 6962. The Proof API returns every byte you need, and the anchors can be read straight from Solana and Base.
Does it cost members anything?
No. Proofs are free and need no account. A proof that required an account to be checked would prove little.