Summary: Cartridge is a gaming control plane. The useful point is not that it has a wallet, but that it bundles player onboarding, session policy, sponsorship, execution hosting, and game distribution under one operator surface.
What it does:
Provides Controller, a self-custodial embedded smart-contract wallet for Starknet gaming with passkeys, multiple signer types, session keys, and gasless transaction support
Exposes onchain session-token and meta-transaction flows so games can submit player actions without prompting for every move
Provides Slot, described as the execution layer of Dojo, for provisioning low-latency dedicated execution contexts plus related Katana, Torii, paymaster, RPC, and observability services
Provides Arcade, a game-registration and publishing layer where games and game editions are represented by ownership NFTs and can be published or hidden on a shared hub
Maintains a public GitHub org with controller, slot, explorer, cairo-webauthn, and related repos that reinforce the stack’s wallet, execution, and developer-tooling scope
Key claims:
The homepage describes Cartridge as “onchain gaming infrastructure for studios building player owned economies and real money rewards,” which is much broader than a wallet-only or middleware-only positioning
The Controller overview says the product is a gaming-focused smart contract wallet for Starknet with passkeys, self-custodial embedded wallets, session keys, paymaster-backed gasless transactions, identity, achievements, and customizable in-game UI
The Controller architecture docs are especially useful because they show concrete signer support across Starknet, secp256k1, secp256r1, EIP-191, WebAuthn, and SIWS, plus Merkle-scoped session policies, SNIP-9 outside execution, and threshold-based recovery flows
The Slot docs describe Slot as Dojo’s execution layer and claim rapid provisioning of low-latency, dedicated, provable execution contexts with team-based deployment management for Katana and Torii services
The Arcade docs show Cartridge is also building a permissionless discovery/publishing surface where ownership and admin rights are represented by NFTs, which pushes the platform beyond pure infra into distribution and ecosystem coordination
The docs llms.txt is itself a useful primary source because it exposes the product map clearly: Controller, native integrations, Arcade, Slot, paymaster, vRNG, RPC, and observability
Whitepaper: No canonical Cartridge whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official docs corpus, especially the Controller overview and architecture pages, the Slot docs, the Arcade docs, and the public GitHub organization; see ../whitepapers/cartridge-primary-sources-2026-04-27.md.
Read Cartridge when the real question is how much execution, session policy, sponsorship, and discovery logic gets pulled under one gaming-specific operator surface.