Exact formula, per-tier weights, and worked examples for the 0–100 QorTrace exposure score.
The QorTrace Score is a 0–100 number we attach to each scanned address (and roll up at the portfolio level for Atlas). Lower = more exposure. Most enterprises target 90+ post-migration.
The formula
CODE
score = max(0, min(100, 100 - max_tier_penalty - history_penalty))
max_tier_penalty = TIER_WEIGHT[worst_tier_seen]
history_penalty = log10(1 + exposed_tx_count) * 6 (capped at 24)
Where TIER_WEIGHT:
| Tier | Penalty | Cumulative meaning |
|---|---|---|
| Critical | 60 | Worst-tier of 60 alone caps score at 40. |
| High | 35 | High alone caps score at 65. |
| Medium | 18 | Medium alone caps score at 82. |
| Low | 4 | Low + clean history → 96. |
| Quasi-resistant | 0 | Up to 100. |
Worked example #1 — fresh wallet, never spent
- Worst tier: Quasi-resistant (pubkey never broadcast).
- Exposed-tx count: 0.
max_tier_penalty = 0,history_penalty = 0.- Score = 100.
Worked example #2 — old hot wallet
- Worst tier: Critical (exposed pubkey + non-zero balance).
- Exposed-tx count: 412.
max_tier_penalty = 60.history_penalty = log10(413) * 6 ≈ 15.7.- Score = max(0, 100 − 60 − 15.7) = 24.
Worked example #3 — old wallet, swept clean
- Worst tier: High (exposed pubkey, now zero balance).
- Exposed-tx count: 412.
max_tier_penalty = 35,history_penalty ≈ 15.7.- Score = 49.
Notice the "swept" wallet still scores 49, not 100. Because the pubkey is forever on-chain, any future deposit to that address is HNDL-exposed. We recommend retiring the address entirely.
How tier classification works
- Critical — pubkey is broadcast on-chain AND current balance > 0.
- High — pubkey is broadcast AND balance is now 0 (still HNDL- exposed if used again).
- Medium — multi-sig where at least one signer's pubkey has been broadcast.
- Low — single-sig with pubkey-not-yet-broadcast (e.g. unrevealed P2WPKH on Bitcoin, unused EOA on Ethereum).
- Quasi-resistant — Low AND zero history.
Methodology version is stamped on every report
The score above is v3.2 (effective 2026-04-01). Reports always
carry their methodology version so older certificates remain
interpretable when the rubric evolves.
See /docs/methodology/versioning for how we deprecate / replace
versions.