· Skinvestments
Trade-Up Contracts as Portfolio Decisions
CS2 trade-ups are not loot box entertainment when capital is at stake. Frame them as portfolio decisions: input cost, outcome distribution, and what you will do with the output.
cs2 · trade-up · portfolio · risk
Trade-ups spend real inventory
A trade-up consumes inputs that already had mark-to-market value. Mentally treating inputs as “already owned leftovers” is how people hide losses.
Frame every contract as:
Risking the sum of input values for a distribution of outputs.
Pre-trade checklist
- Sum today’s liquid marks for all inputs (not what you hope Steam says).
- Estimate realistic output values across likely results (not only the dream skin).
- Subtract expected fees on the way out if you will sell.
- Ask whether a flat sale of inputs would be cleaner.
- Size the experiment so a bad outcome does not distort the whole portfolio.
Cost basis of the output
Whatever comes out inherits the sum of inputs as cost basis (plus any direct fees). Log it immediately. See cost basis record-keeping.
Common failure modes
- Using Steam asks for inputs and Buff dreams for outputs
- Ignoring that several “okay” outcomes still lose after fees
- Chaining trade-ups to avoid admitting a stagnant pile should be sold
- Celebrating a win without updating the ledger
When trade-ups can make sense
- You explicitly want a play skin and accept EV loss for utility
- Inputs are illiquid junk with poor exit paths
- You have modeled the distribution and sized small
- You are documenting results to learn - not chasing losses
When to stop
If trade-ups become a way to avoid stagnation decisions, pause. Selling inputs on a cash market may be the higher-ROI “contract.”
Tie it back to the book
Track inputs and outputs in Skinvestments, keep venue context via Steam / Skinport / Buff, and review ROI with fee math. The contract is optional. Honest accounting is not.