Studio console

Connect your studio

What a studio sees: live economy, fee revenue, treasury and risk.

No signup — sandbox data from this deployment.


Already have a key

New studio
Overview
Live economy across your game
—
Players
—
wallets provisioned
Fee revenue
—
your share of trading fees
Trading volume
—
USDC settled
Marketplace GMV
—
NFT sales
Economy health

Scores are indicative and derived from ledger activity — emissions versus sinks, holder spread, and liquidity depth.

Integration status
Wallets live
Exchange live
Marketplace live
Risk engine monitoring
On-chain settlementtestnet
View integration guide
Emitted via rewards
—
$DRAGON minted to players
Holders
—
non-zero balances
Circulating
—
held by players
Emission vs sinks

Every $DRAGON in circulation was minted by a gameplay reward and is tracked as a ledger entry against system:mint:DRAGON. Sinks — marketplace fees, trading fees and crafting costs — return supply to the platform.

Sources
—
quest & boss rewards
Sinks
—
fees collected in USDC
Volume settled
—
USDC
Open reservations
—
funds held by live orders
Halted pairs
—
circuit breakers engaged
Trading pairs
PairFees (taker / maker)Your shareStatus
Open trading terminal →
GMV
—
completed sales
Active listings
—
on sale now
Creator royalty
5.0%
enforced at settlement
Live listings
ItemAssetPrice
Token holders
—
Emissions
—
Trading volume
—
Marketplace GMV
—
Health signals
How these are computed

Every figure here is derived from the double-entry ledger rather than from counters that could drift. Emissions sum the reward transactions against the mint account; volume sums the quote leg of settled trades; holders count distinct non-zero player balances. If a number here is wrong, the books are wrong — and a continuous invariant job would have caught that first.

Withdraw fee revenue

Funds leave your spendable balance immediately. Payouts above $10,000 require a second approver before they can be signed.

How a payout works
1Requested — the policy engine checks limits, velocity and risk, and the amount moves to a hold.
2Approved — one approver under the threshold, two distinct approvers above it.
3Signed — the vault signs with a nonce persisted before signing, so a retry can't pay twice.
4Broadcast — awaiting a funded hot wallet on this deployment.
Withdrawal history
AmountDestinationStateApprovalsActions
Risk events (24h)
—
Circuit breakers
—
pairs currently halted
Detection
Active
wash · velocity · price anomaly
Recent findings
TypePairDetailWhen
Active key
—

Only a SHA-256 hash of this key is stored, so it can't be recovered — mint a new one if it's lost.

Keep keys server-side

A studio key authenticates as your whole studio. Never ship one in a game client or a web bundle — call GameFi Rails from your game server, and give players player-scoped sessions instead.

Quickstart
server.ts
import { GameFiClient } from '@gamefi-rails/sdk-js';

const gamefi = new GameFiClient({
  baseUrl: '',
  apiKey: process.env.GAMEFI_KEY,
});