API

GET /api/cover

What the contract owes every holder, and what it actually holds. No parameters, no authentication.

Request

GET /api/cover

Takes no parameters. Anything in the query string is ignored.

Response

200 application/json

{
  "contract": "0x389699d7C3A754d6b82EbBBa0ebE5757ccfA1dD7",
  "balanceWei": "70367814399680116",
  "outstandingWei": "70367814399680116",
  "covered": true,
  "paused": false
}

Field	Type	Meaning
`contract`	string	The factory the other figures were read from.
`balanceWei`	string	ETH the contract holds, read from the node rather than from storage.
`outstandingWei`	string	Sum of every live node balance. What the contract owes all holders together.
`covered`	boolean	The contract's own `isSolvent`. True when the balance is at least the outstanding.
`paused`	boolean	Whether minting is paused. Pausing has never been able to block a withdrawal.

Where the numbers come from

Unlike /api/stats, this endpoint reads the chain rather than our database, and it does so deliberately. The whole value of the figure is that it does not depend on our records being honest. Both numbers come out of the same block, because a balance compared against an outstanding read one block later is a rumour rather than a check.

You do not have to take the answer from us at all. Call outstanding and read the contract balance yourself on Blockscout, and you are reading the same two storage slots this route does.

A 503 is not a zero

When the chain cannot be read the route answers 503 and returns no figures, and it never serves a cached covered through an outage. An answer about whether somebody's money is there must not outlive the ability to check.

Caching

Cached for 15 seconds. The numbers move on the scale of a credit round, not of a request, and every dashboard visit asks.