# Terms – DeFi Capital Flow-Price Gap (on-chain data)

Provider contact: deficapitalflow@gmail.com

1. What this is. Informational data computed from public on-chain records (Ethereum), by fixed, published rules
   (https://defi-flow.onchainproof.workers.dev/methodology).
   Coverage on 2026-11-16 (generated from the data): chains Ethereum; 11 protocols, 10 tokens, 145 protocol assets. Full list: /coverage.json.
   Not investment advice. No buy, sell or price-target statements are made. Use at your own
   discretion; no warranty of fitness, completeness or availability.
   What you pay for: measured, Bitcoin-timestamped on-chain data (capital inflow, holder value, prices) whose value does
   not depend on whether the signal predicts prices. The signal's predictive power is a separate claim, shown per tier
   (point 4); it is not yet proven on the live record. No return is promised.
2. Freshness. Paid routes charge only while the data day is at most 1 day old (UTC). Older data is never
   sold: the route answers 503 and nothing is charged (status: https://defi-flow.onchainproof.workers.dev/v1/status, fields data_age_days and
   paid_routes_open). If a day fails the quality gate, the last passed day is served with "stale": true.
2b. Re-fetch. Every paid response has a refetch block. When refetch.status is "issued", the same request with the receipt (HTTP: the same GET with header X-Receipt: <receipt>; MCP: the same tool with argument receipt) returns the same data without payment, at most 2 times, for the same route and token, until the end of the UTC day of purchase (refetch.expires_at) or until the next daily publication replaces that data (refetch.valid_for_fingerprint_sha256), whichever comes first. When it is "unavailable", no re-fetch was promised for that purchase. An invalid, used-up, replaced or expired receipt gets the normal payment offer with the reason unknown / exhausted / superseded / expired (HTTP: 402 with header X-Refetch-Status; MCP: the PaymentRequired result with _meta["dev.workers.onchainproof/refetch-status"]); if the receipt store is temporarily down the answer is 503 (MCP: an error result) and nothing is charged.
2a. "Not measured". A null value means the quantity could not be measured that day. It is never a zero and never an
   estimate. Wrong data is treated as worse than missing data.
3. Signal tiers are descriptive states (3 strong, 2 candidate, 1 watch) with a numeric reason (tier_reason). A tier
   name describes the measured on-chain state; it does NOT say how well that tier is proven. Every signal response
   carries a track_record block with each tier's current verdict and observation counts; details at https://defi-flow.onchainproof.workers.dev/performance.
   Risk flag (r1, from methodology 2.2.0): a separate, descriptive output for capital LEAVING a protocol while its token
   price holds up (outflow-price gap; 2 aggravated, 1 basic, 0 none; reason in risk_reason). It is NOT a sell signal and
   carries no performance claim until it has its own live record.
4. Track-record verdicts, per tier, on 7, 14 (main) and 28-day horizons. An observation = one flagged token on one day
   (consecutive days overlap). The last 4 calendar months of the data are the test segment (in effect about 3: the newest
   month holds few matured observations); each horizon needs at least 20 test observations. Placebo: 2000 random selections.
   A = works: every horizon passes (mean relative return > 0 and > random, better in more than half of the months),
       beats at least 1976 / 2000 random selections on the 14-day horizon and at least 1901 / 2000 on the 7 and 28-day
       horizons, and the relative return is >= 0 in both rising and falling markets.
   B = partial: at least one horizon passes and beats at least 1976 / 2000 there.
   C = cannot be distinguished from luck with the data so far (NOT "worthless").
   Backtest results are labelled "past test" and are shown per methodology version, never added together. The live
   verdict (from methodology 2.3.1) uses the same tests on the whole live period of the current major version, only
   after at least 60 live days. Every matured live observation whose files are all free (its horizon
   end is at least 7 days old) is listed with its numbers in
   https://defi-flow.onchainproof.workers.dev/performance-outcomes.csv and can be recomputed from the free, fingerprinted daily files; the exact
   computation is described in https://defi-flow.onchainproof.workers.dev/performance (verdict_rules.computation). The rules
   were fixed and Bitcoin-timestamped before results were seen (https://defi-flow.onchainproof.workers.dev/methodology; English translation:
   https://defi-flow.onchainproof.workers.dev/methodology.en – the Hungarian text is authoritative).
5. Licence. Fresh (paid) data: for your own use, do not redistribute. Every data day becomes CC BY 4.0 7 days after
   its date (field license.cc_by_from); then anyone may use it for any purpose with attribution (field attribution).
6. Verification. Every data day is fingerprinted (SHA-256) and timestamped on Bitcoin (OpenTimestamps). Files older
   than 7 days are free, byte-identical to the fingerprinted ones (https://defi-flow.onchainproof.workers.dev/free/index.json, https://defi-flow.onchainproof.workers.dev/verify/). Every
   row of a paid response names its original file and row (source_file, source_row). Example code that checks all of
   this: https://defi-flow.onchainproof.workers.dev/examples/.
7. Corrections are never silent. Rule changes are versioned in advance and listed in the change log of
   https://defi-flow.onchainproof.workers.dev/methodology.en. Any published value later found wrong, or confirmed after doubt, is listed with the published
   and the correct value, the reason and a reference in https://defi-flow.onchainproof.workers.dev/corrections.json (also .csv). Published, fingerprinted
   files are never rewritten.
8. Prices. Prices rise only if BOTH measurable demand (at least 100 returning paying addresses: paid on at least 2
   different UTC days within 30 days; own and test addresses excluded) AND evidence (a B or A
   verdict on the live track record, or materially wider coverage) exist; any change is announced 30 days ahead with
   its reason (field price_change_notice). The current state of both conditions is public: https://defi-flow.onchainproof.workers.dev/performance
   (price_policy). If the payment facilitator is unavailable before payment you get HTTP 503 and nothing is
   charged; unknown tokens return 404 before any payment is requested. If settling a signed payment fails, you get
   no data and this service does not retry the payment (the signed authorization can only be used until its own
   expiry, set by your client). In the rare case that the settlement reached the chain although the response
   reported a failure (for example a facilitator timeout), your wallet shows the transfer: send its transaction hash
   to deficapitalflow@gmail.com; we check it on-chain and answer.
9. MCP access. The same data, prices, rules and proofs are available as tools at https://defi-flow.onchainproof.workers.dev/mcp (Model Context
   Protocol; x402 payment inside the tool call). Every MCP answer is the same JSON as the corresponding HTTP route, and
   these terms apply to it in full.
10. Privacy. No accounts, no API keys, no cookies and no tracking scripts. Request logging of the service (Cloudflare Workers
   observability) is switched off: we do not store IP addresses, user agents or request contents. Re-fetch receipts
   (2b): we store only the SHA-256 of the random receipt, the route and the data version, and delete them at the end of
   the UTC day; the payer address is not stored. Besides that we keep only daily counters (payments, re-fetches,
   rejections) and aggregated request counts from Cloudflare's account analytics.
   Third parties, under their own policies: Cloudflare (hosting) processes connection data such as IP addresses; the
   x402 payment (payer address, amount, signature) is processed by the Coinbase CDP facilitator and settles on the
   public Base blockchain, where anyone can see it; the Coinbase x402 Bazaar publicly shows call and payer counts per
   route. E-mails to deficapitalflow@gmail.com are kept in that mailbox only to answer them and are not shared; to have yours deleted,
   write to the same address. This text is generated from the service's code and configuration and the build stops if
   a statement here stops being true (https://defi-flow.onchainproof.workers.dev/privacy).
