Skip to content

Documentation

How to use the desk

Start with a labelled example if you want to learn the language. Sign a write only when a contract address is configured, and only from your own wallet.

If you allocate capital

  1. Open Explore and read the source in words, not just the rate.
  2. Open the evidence links. Those are the only pages validators are allowed to read.
  3. Read the policy as a sentence. The sentence is generated from switches, so there is no hidden clause.
  4. Connect the wallet in this browser. YieldTruth does not ask you to paste a seed or a private key.
  5. On the sign screen, review the call, then approve it in the wallet.
  6. Wait until the status says final. A hash by itself is not a decision.
  7. Come back later. Drift keeps the earlier reading beside the new one.

How a write is signed

The button calls genlayer-js writeContract with the account your wallet just exposed. The library uses that injected provider. There is no server-side signer, and the read API cannot approve, reject, or move funds.

This desk is pointed at Studionet 0x23C029E1aB24f74b355EF05f7b540296BEdD6279. The button still sends the call to your wallet. It does not sign on the server.

Open the sign screen

If you are integrating

The Python contract is the authority. The HTTP API is a public index of the same records. It will not invent a verdict, and it will not accept a write.

  • GET /api/v1/health/live
  • GET /api/v1/health/ready
  • GET /api/v1/config
  • GET /api/v1/opportunities
  • GET /api/v1/opportunities/:id
  • GET /api/v1/opportunities/:id/assessments
  • GET /api/v1/assessments/:id
  • GET /api/v1/policies
  • GET /api/v1/policies/:id
  • GET /api/v1/sources
  • GET /api/v1/activity

The longer method notes live on the methodology page. The build order is the roadmap.