Skip to content
YieldTruth

For people who allocate capital

Don’t ask how high the yield is.

Ask what is actually paying you. YieldTruth names the source. Your policy, not a language model, decides whether money may follow it.

Inspect a marketHow your wallet signs

Plain language

“Borrower interest” is easier to trust than a ticker and a percentage.

Your key stays yours

Writes are signed in the browser with genlayer-js. The server never holds a wallet key.

History is not rewritten

When a market drifts from interest into incentives, the old reading stays on the record.

What happens before money moves

  1. Step 1

    Name the market

    A protocol, an asset, and a handful of public pages. Not a free-form prompt.

  2. Step 2

    Read the evidence

    Only HTTPS pages on hosts the contract already trusts.

  3. Step 3

    Agree on the source

    GenLayer validators classify where the yield comes from. They do not vote yes or no.

  4. Step 4

    Apply your policy

    Structured rules decide approved, rejected, or needs review. The model cannot write that line.

The signature is yours

Connecting a wallet is not a login to our server. When you submit a market or ask for a new reading, genlayer-js calls your browser wallet. You see the function name and the arguments, then you sign. If there is no injected wallet, nothing is sent.

Open the sign screen
  1. 1. Connect. RainbowKit talks to the wallet already in this browser.
  2. 2. Review. The screen names the contract call before anything is broadcast.
  3. 3. Sign. writeContract uses your account, never a key stored on the server.
  4. 4. Wait. A transaction hash is not a verdict. The status has to say final.
  5. Studionet contract 0x23C029E1aB24f74b355EF05f7b540296BEdD6279. The wallet in this browser still has to sign.

Why the model does not get the vote

Validators can agree and still be wrong if they all read the same poisoned page. Pages are treated as data. The classifier may return a source, a confidence, and one short sentence. After they agree, ordinary code applies your policy. An instruction hidden in a webpage cannot mint an approval.

Read the method

Yield changes its story

A market that was borrower interest in spring can be mostly token incentives by autumn. Reassessment adds a new revision. The gate reads the latest one. The history shows what changed.

See a teaching example of drift

Where this is going

Full roadmap

  1. Now

    Classification, policies, labelled records, and a wallet-signed write path.

  2. Next

    Scheduled re-reads and a plain alert when the source of yield changes.

  3. Then

    A small SDK so a vault can consume a finalized assessment.

  4. Later

    Policy-gated capital routing. Not built, and not implied.