> open methodology
Methodology
SOG records stablecoin history with source-backed notes, conservative status labels, visible uncertainty, and separate event records.
Moderegistry
Scoresnone
Status
Status labels describe registry state. Event records describe what happened.
Events
Material events are kept separate from stablecoin status to avoid overstatement.
Sources
Claims should be backed by public sources where possible.
| Registry | SOG is a historical registry for stablecoins, issuers, reserve references, event timelines, evidence, and open questions. |
|---|---|
| Not a ranking | SOG does not rank stablecoins, score stablecoins, recommend stablecoins, or provide investment advice. |
| Source-backed | Records should point to issuer statements, reserve references, public notices, market references, regulatory documents, archives, or other relevant public sources. |
| active | Recorded as operating or available based on the sources currently linked in the registry. |
|---|---|
| limited | Operating with notable limits such as access, geography, redemption, minting, or market availability. |
| impaired | Material issues are recorded, but the record does not support a discontinued or failed label. |
| discontinued | Issuance, support, or operation has ended or entered a wind-down state. |
| failed | The registry records a severe historical event or lifecycle outcome that supports failed status. |
| rebranded / migrated | The stablecoin or related product moved to a new name, structure, contract, or successor relationship. |
| unknown | The available sources are not enough to classify the record. |
| Minor movement | SOG does not try to record every small peg movement or short-lived market deviation. |
|---|---|
| Notable event | A depeg can be recorded when it is material, sustained, historically relevant, or supported by public sources. |
| Major event | A major depeg record should include context such as trigger, recovery, duration, evidence, and whether status changed. |
| Status separation | A depeg event does not automatically mean a stablecoin failed. Recovered events and failed lifecycle outcomes are recorded separately. |
| Known unknowns | When a field needs more review, SOG keeps the uncertainty visible instead of guessing. |
|---|---|
| Confidence | Confidence describes the current record quality, not the safety of the stablecoin. |
| Corrections | Public, source-backed corrections can be submitted through GitHub Issues. A Google Form route will be added later. |