Do your public claims match the chain?

One token, three disclosure checks.

1. Advertised versus realized yield. Dated, first-party claims compared with ERC-4626 share-price growth over the agreed historical window, where the data supports it. Projected and historical rates stay distinct.
2. Document and address consistency. Token, vault and privileged-role references in the agreed documents compared with public contract reads at stated blocks.
3. Oracle and attestation posture. What the public documentation says is signed or verified, what the published verification path shows, and where data, freshness or access limits prevent a conclusion.

The fixed scope covers one token on Base or Ethereum, up to five public disclosure pages and up to ten relevant contract addresses, with one historical yield window of up to 30 days. We confirm feasibility and exact sources first. Unsupported data or a larger scope is declined or quoted separately before any payment; no automatic upsell.

What you receive for $499.

• A private written report, typically 1,500 to 2,500 words, with the agreed scope, dated claim register, findings across all three checks, severity rationale and explicit unknowns.
• An evidence appendix with source URLs, chain IDs, block numbers, exact reads and reproduction commands. A snapshot records what was observed at that time.
• A JSON findings summary with its signing address, payload hash, EIP-191 signature and verification instructions. The signer is identified in the scope and delivery. A signature proves authorship and integrity, not that a protocol is secure or solvent.
• One round of written clarification requested within seven days of delivery. New chains, new documents or a new time window require a new agreed scope.

You may publish your report and summary. We deliver privately and do not publish a customer engagement without consent. Payment does not buy favorable findings.

Read the sample and method.

Open the full illustrative report sample. It shows all three sections, evidence format and the summary format using a fictional protocol. It is explicitly unsigned, contains no live findings and is not a customer engagement.

Read the historical scrvUSD yield-method demonstration. That July 2026 article demonstrates the yield check only. It is not a complete three-part report or a signed customer deliverable.

From request to delivery.

1. Request. Provide your role, token address and chain, public disclosure URLs, decision and deadline. A received form is an inquiry. Existing agreed engagements keep their original terms.
2. Qualification. We check the problem fits, the public data is reproducible, and the $499 scope is appropriate. We confirm the person responsible for delivery and capacity.
3. Written scope. Both sides confirm the exact sources, exclusions, deliverables, signing identity, price, kickoff and deadline. A request or an automatically generated invoice is not an accepted engagement.
4. Invoice and verified payment. Only after scope and availability are agreed do we provide an invoice and payment instructions. The current settlement rail is USDC on Base; no bank-wire availability is promised. We independently verify the transaction and match it to the engagement. Never pay from an old page or an unsolicited message.
5. Kickoff and delivery. Within 72 hours of the kickoff agreed in writing, after scope, required public data, reviewer availability and verified payment are confirmed. The fee is earned on delivery. If the agreed deadline is missed, the fee is refundable. If a report figure fails to reproduce at the stated block or its signature fails verification, you may request a correction/re-run or a refund.

Who provides the work.

The Kerne Protocol team combines automated reads with manual review. The engagement is contracted personally with the co-founder identified on the written scope and invoice. Kerne has no incorporated company and cannot provide a registered-company tax invoice. Confirm that this counterparty works for your organisation before buying. See the team and terms.

We build a yield protocol ourselves, which is a potential commercial conflict. Review our deployed-versus-source disclosures and security audit reports. Those audits do not attest to this service. Current availability and evidence limits take precedence over historical examples elsewhere on this site.

The limits are part of the deliverable.

This is disclosure review of public data. It is not a smart-contract security audit, vulnerability search, solvency or credit opinion, rating, legal or compliance determination, or investment advice. We do not certify that a protocol is safe, solvent or compliant. We cannot prove off-chain reserves from a public contract read. Missing evidence is reported as missing.

Request scope and availability.

Paid starts are paused. We will assess the request and confirm whether and when we can deliver. Submitting does not reserve capacity or start the 72-hour clock.

Already paid under an earlier scope? Email your engagement reference and transaction hash to kerne.systems@protonmail.com so we can reconcile delivery under the original terms. Do not pay again.

If the form cannot save your request, it will say so and keep your entries. Email the same details to kerne.systems@protonmail.com. Your email is an inquiry until we explicitly confirm scope and availability.

Reporting a vulnerability or security concern? Use the contact page and select Security / bug report. Security submissions are handled separately and are never counted as sales leads.