The sacrifice vault
Two stocks: the reserve, which is never opened, and a small second vault that is.
Two stocks
Every sweep splits its cases 95 to 5. The 95 go to the reserve account and are never opened. The 5 go to a separate account, the sacrifice vault, and exist to be opened. Two accounts, two counters, and the mandate only ever applied to the first.
This gives the project two forces instead of one. Accumulation asks how big the sealed reserve can get. Sacrifice asks what happens when a tiny part of the stock is destroyed in public. Both are worth watching, and the second one produces content.
Milestones
Market cap milestones unlock opening events. The count of openings grows with the milestone, from five at the first to two hundred and fifty at the last.
| Market cap | Openings |
|---|---|
| $250K | 5 |
| $500K | 10 |
| $1M | 25 |
| $2.5M | 50 |
| $5M | 100 |
| $10M | 250 |
Tickets
A ticket attributes one opening to one participant. It is not a Steam key: since 2019 a key bought in the game is bound to the account that bought it, so keys cannot be handed out. The project opens the vault itself, live, on the sacrifice account, and reads the tickets out one by one.
Allocation rewards time held and participation rather than a last-minute snapshot: a guaranteed ticket above 1% of supply, a raffle above 0.25%, a bonus for wallets that held through the previous milestone, tickets for contributors, and a handful drawn at random. Tickets are never sold.
Why the counter stays at zero
Cases opened at an event never belonged to the reserve. They were bought with the 5% share and held on the sacrifice account from the day they were bought. The reserve account is public, so anyone can confirm that nothing left it.
A case, a key, a random result and a token-holding condition is the shape regulators look at for loot boxes and gambling. Keep the reserve and the events on separate accounts and separate pages, publish each event's rules first, and have them reviewed before an opening is presented as a prize.
Posting an event
Market cap, the vault size and event results are posted by the team through POST /api/admin/sacrifice with the x-admin-token header. The site reads them from Redis; without a post it shows the sample figures.
curl -X POST https://cs2rs.com/api/admin/sacrifice \
-H 'x-admin-token: ...' -H 'content-type: application/json' \
-d '{"marketCap": 1000000}'
# an event, case by case
-d '{"event": {"no": 1, "mc": 1000000, "at": "2026-10-01",
"openings": [{"no": 1, "grade": "Mil-Spec Grade", "skin": "MAC-10 | Classic Crate", "ticket": "@holder"}]}}'