Sibyl Credits

Credits

Credits are kept in USD. You buy them by depositing ETH or USDG into the SibylCredits contract on Robinhood Chain, and spend them per token on any model, from the chat or the API. Paid credits can also be sold to another wallet on the desk.

Deposit

  1. In the app, open Credits and click Connect wallet.
  2. Choose ETH or USDG (0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168, 6 decimals) and an amount. Minimums: 0.0002 ETH or 1 USDG.
  3. Confirm in your wallet: depositETH() for ETH, or an approval then depositUSDG(amount) for USDG. If your wallet is on another network, the app asks it to switch to Robinhood Chain (chain 4663) at this point, and adds the network if the wallet does not know it.
  4. The contract emits Deposited(account, asset, amount, stakersShare). The server reads it and credits the wallet that sent the deposit after 40 Robinhood Chain blocks, about five seconds. Each deposit is credited once, keyed by its transaction hash and log index.

The wallet that sends the transaction is the wallet credited. Credits are prepaid and cannot be withdrawn or refunded by us (you can sell them to someone else on the desk); the terms have the details.

How a deposit is valued

  • USDG counts one to one: 25 USDG adds $25.
  • ETH counts at the Chainlink ETH / USD price on Robinhood Chain (0x78F3556b67E17Df817D51Ef5a990cDaF09E8d3A9): the last round the feed wrote at or before the time of the deposit's block.

Where a deposit goes

In the same transaction, 20% of the deposit goes to the SibylStake contract for $SIBYL stakers and the rest goes to the operator wallet that pays the model gateway (0xe568F9e89F77D88399817Ec4046fa21Fc675E269). You are credited for the full amount either way.

Until the stake contract exists, the stakers' share waits inside SibylCredits and is pushed to SibylStake once, when it is set. The owner of SibylCredits can set the stake contract one time only, and can open or close new deposits. It has no path to deposited funds.

Balance and charges

If you have drawn on a credit line, a deposit clears what is drawn first and the rest goes to your balance.

Before a request runs, the server holds its maximum possible cost on your balance in one atomic step, so parallel requests cannot spend the same credit twice. When the answer ends, the hold is replaced by the real cost from the token counts and the rest is released. If the balance cannot cover a request, the chat asks you to add credits and the API answers 402 insufficient_credits.