Skip to content
Changelog

Public Updates

Release notes, methodology adjustments, and transparency announcements from the ByKaranteli ops team. Only reports flagged public land here; the full internal ops log stays on the admin console.

Follow changes: RSS · JSON Feed

Infrastructure

Page requests have a per-address ceiling; programs use the API and the MCP server

Since 2 October the site admits page views per visitor address at a steady rate with room for bursts, and caps how many pages one address can have in flight at once. A browser never reaches these limits. A crawler that pulls thousands of pages in a few minutes now gets a 429 answer instead of slowing the site for everyone, as one did on the morning of 2 October. Programs that read our data should use the API with an account key, the datasets or the hosted MCP server, each with its own documented limits. Links also stopped preloading: a page no longer fetches every page behind a visible link, only the one you hover over or touch.

Infrastructure

BYK Data Layer catalog beta-0.4: 116 records sealed every five minutes

The onchain catalog grows from 35 to 116 records with no change to the protocol; only a 200-byte manifest goes on chain, so the cost stays the same. Existing feeds widen: composite funding and aggregate open interest to 12 assets (HYPE, SUI, LINK, ADA, AVAX and LTC join), five-minute liquidations to 11, spot depth within 2 percent to 9, the Kimchi premium to 6. New feeds: whale prints of $1M and more summed per window and side across 10 venues, flow toxicity (VPIN) for BTC, ETH and SOL, the Turkey premium against the live USD/TRY quote, tokenized stocks (median premium, 24 h DEX volume, onchain supply in dollars for the board and six stocks), the largest single liquidation of the trailing 24 hours, exchange insurance funds (hourly: four venues and the total), the share of withdrawal pairs each of eight venues keeps open, read hourly from the venue's own switch, quantum-exposed bitcoin from our own node, and the Coinbase premium close. Hourly and daily sources carry their own age inside the record, so a reader always sees how old a number is. Every record has its proof at /proof and in the Proof API; each feed's methodology text is sealed by hash with every epoch.

Infrastructure

BYK Data Layer beta: 35 data feeds sealed every 5 minutes, signed and written to Solana and Base

/proof now runs on Solana and Base mainnet. Every five minutes 35 feeds we compute (funding composite, aggregate open interest, long and short liquidations, order book depth within 2 percent, derivatives pressure scores, Kimchi and Turkey premiums) are sealed into one Merkle root. An isolated signing service with no network access signs the manifest; the manifest is written to Solana in a memo under its own witness key, and attested on Base through EAS once a day and at every change to the authorization log. A number changed afterwards would no longer match its anchor. The page verifies any record in your browser: the leaf, its Merkle path, the manifest, its commitment, the signature and the Solana transaction, read from a public node rather than from us. The full protocol verdict needs no browser and no ByKaranteli server: /byk-verify.mjs is one file for Node.js 20 or newer that reads only Solana and Base and checks every epoch from genesis. Every epoch, record and proof is served without a key at /api/v1/proof, and the MCP tool get_data_proof (npm 0.28.0) hands the same proofs to AI agents. The governance key that authorizes the data signer never touches our servers. Beta profile: one of one governance, Class B feeds.

Infrastructure

Source expansion: 56 feeds across 43 exchanges

The ingestion registry grew to 56 live feeds across 43 venues, including Kraken spot. Every feed is tracked in the venue market snapshot with freshness monitoring.