Rips technical overview
Rips combines vaulted physical cards, fixed-odds pack machines, Solana settlement, and encrypted ownership records. This page describes the system and its limits.
System model
Each outcome is a real graded Pokémon, sports, or One Piece card held by Collector Crypt. The physical asset is represented one-to-one by a Solana asset. A successful pull assigns that specific card to the player.
Collector Crypt supplies the inventory, published odds, market values, and buyback rules. Rips provides the pack interface and private ownership flow.
Pack flow
- 1
Pick a pack
Choose a live pack tier. Each tier has its own published odds and value ranges.
- 2
Open it
Pay in USDC. The pack machine returns one card, its grade, metadata, and insured value.
- 3
Keep it or cash out
Keep the card or use the displayed buyback path. Rates are fixed by the pack machine. Eligibility and timing are shown before a sale.
Odds and settlement
Odds and value bands are read from the active Collector Crypt machine and shown before payment. Rips does not alter the distribution. The machine selects one outcome, then the backend records the pull and returns the card data used by the client.
Private collecting
A normal token account makes the wallet-to-asset link public. Rips keeps that link in an encrypted ownership record while the card remains in the shared vault.
The vault is public. The owner-card link is encrypted. The chain shows the vault and its assets, but not which player owns a given card.
The client derives a private identity key from a wallet signature. The key proves ownership without being the wallet address. Claiming a card submits an encrypted destination and lets the network check the record before release.
A vaulted buyback uses the same private ownership check. The sale path can reveal the destination wallet because the card must leave the private vault before settlement. A card that remains vaulted keeps its owner-card link private.
Privacy scope
Payments, vault activity, and program transactions remain public. Rips hides the owner-card link, not the existence of the system. Timing can still reduce privacy, especially at low volume.
The operator can access operational records for support, refunds, and compliance.
Encrypted execution
Rips uses Arcium, an encrypted-computation network for Solana. The ownership record is stored as data that can be processed inside a cryptographic computation, rather than read from the public ledger.
The private logic runs in an Arcium MXE using encrypted circuits written with Arcis and deployed with arcium-anchor. Results return to the Solana program through verified callbacks.
1. MPC shares the secret
Independent nodes jointly compute over encrypted data using secure multi-party computation. Each node holds a mathematical share, not the plaintext. Under the stated protocol model, one honest node is enough to preserve secrecy. Invalid computation causes an abort rather than an unverified result.
2. Ownership is an encrypted record
The card enters a program-controlled vault. Its ownership record does not contain the wallet address. It stores identity material as Enc<Mxe>, usable by the MPC network but opaque to chain observers.
3. Identity is separate from the wallet
The client derives a reproducible identity key from a wallet signature. It is not stored by the server and is separate from the public wallet address. The identity key authorizes private card actions.
4. Claiming runs inside MPC
The client encrypts a destination under the identity key. MPC checks the encrypted ownership record, card identifier, and destination binding. A successful result is threshold-signed and verified by the vault program before release. The record then leaves the vaulted state, preventing replay.
5. The backend relays sealed requests
Arcium computations require Solana transactions. The backend submits them on the player's behalf. The relayed payload is already encrypted, and the identity key is separate from the wallet.
Trust assumptions
Privacy assumes at least one honest Arcium node. The vault program is on-chain and cards move only after network-verified approval. Timing remains observable. Batching and randomized delays reduce, but do not eliminate, that leak.
Why it's safe
- Real assets. Graded cards are held in a professional vault and represented one-to-one.
- Verified release. Cards leave the vault only after the private ownership check and on-chain verification.
- Defined buyback. Rates and eligibility come from the active machine.
- Published odds. The active machine exposes its distribution before payment.
Summary
Rips opens fixed-odds packs of real graded cards. Cards are vaulted, odds are published, and ownership stays encrypted while the card remains in the private vault.