Season 2 introduces XP slashing alongside traditional credibility slashing. Where credibility slashes affect reputation scores, XP slashes transfer XP directly between parties. Think of it as a way to put your money where your mouth is — without the severity of permanent credibility consequences.
How it works
When you initiate an XP slash, you specify a stake amount. Both you and the target commit that staked XP to escrow. Upon resolution, the winner receives the loser's stake — a zero-sum transfer of conviction.
Neither party can initiate a slash and then withdraw when the evidence turns unfavorable. Once committed, the dispute plays out to conclusion, which encourages careful consideration before initiation.
It's not just about XP
XP slashes also affect credibility scores, creating real stakes beyond the XP transfer itself. Losing an XP slash means both forfeiting your stake and taking a reputation hit. This dual consequence encourages users to only initiate slashes when they have genuine conviction — the cost of being wrong extends beyond mere XP loss.
When to use XP slashing vs. credibility slashing
XP slashing suits disputes where parties want to back up their position without the full severity of credibility consequences. Consider a disagreement about whether a particular event occurred, or whether a prediction will come true by a certain date. Being wrong about a specific prediction shouldn't necessarily damage your overall reputation.
XP slashing provides an alternative: stake XP, let the community adjudicate, and transfer value based on the outcome. It enables productive disagreement — two users with genuine uncertainty can stake their positions and let resolution clarify who was correct.
Resolution outcomes
Slashes are resolved through community voting, with three possible bands:
Passes (above 60% consensus) — The slash is upheld. The target loses both the staked XP and suffers credibility damage.
Defended (below 40% consensus) — The slash fails. The slasher loses credibility and forfeits their stake, penalizing frivolous or malicious accusations.
Failed (40–60% consensus) — The community is divided. The slash doesn't resolve, and stakes are returned. This acknowledges that not all disputes have clear answers.
See "How does voting on XP slashes work?" for more on the resolution mechanism.