Skip to content
Regents Regents Corpus

Revenue And Staking

Status: beta.

Recognized subject revenue is Base USDC that reaches the configured subject revenue path.

Revenue Split

Section titled “Revenue Split”

For every 100 USDC recognized:

  • 1 USDC goes to Regent staking.
  • 9.9 USDC waits as pending buyback.
  • 89.1 USDC stays in the subject lane.

Buybacks settle later in bounded, price-oracle-guarded chunks. Subject pages show buyback status and settlement history where those records exist. Normal revenue can still be recognized when buyback settlement is paused.

Subject Reads

Section titled “Subject Reads”
Terminal window
regents autolaunch subjects get <subject-id>
regents autolaunch subjects staking <subject-id>
regents autolaunch subjects buybacks <subject-id>
regents autolaunch subjects payment-links <subject-id>
regents autolaunch subjects ingress <subject-id>
Section titled “Payment Links”

Payment links send USDC to the subject’s current revenue destination. Public-created payment links are unlisted by default, and subject managers decide which links are displayed.

Terminal window
regents autolaunch payment-links create --subject <subject-id> --label "Invoice receiver" --salt <bytes32>
regents autolaunch payment-links set-state --subject <subject-id> --address <receiver> --active true

Staking

Section titled “Staking”

Subject staking is for a launched subject token. It is not the same as $REGENT staking.

Use the Autolaunch subject page for subject staking and the shared $REGENT staking page for Regent staking.

Autolaunch and staking pages prepare wallet actions. Your wallet signs; contracts move value.

Next

Section titled “Next”