Bitcoin Forum
June 13, 2026, 03:34:06 PM *
News: Latest Bitcoin Core release: 31.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [Feedback] Stable or Gone — a source-backed stablecoin history registry  (Read 15 times)
badjoke-lab (OP)
Newbie
*
Offline

Activity: 22
Merit: 10


View Profile
June 12, 2026, 03:29:53 PM
 #1

I am building a small public registry called Stable or Gone.

https://sog.badjoke-lab.com/

It is not a token, not an exchange, not a ranking site, not a price prediction site, and not investment advice.

The purpose is not to tell people which stablecoin is “safe” or which one they should buy. The goal is to keep a source-backed historical record of stablecoins: what happened to them, who issued or operated them, what reserve and redemption information was available, what depegs or wind-downs occurred, and which sources support each record.

Most stablecoin lists focus on current price, market cap, trading volume, yield, or supported chains. Those are useful, but Stable or Gone is trying to do something different.

The kind of history I want to preserve includes:

  • whether a stablecoin is still being issued
  • whether issuance has stopped while redemption continues
  • whether it failed, collapsed, wound down, rebranded, or migrated
  • whether a depeg was temporary, recovered, partial, or terminal
  • which issuer, protocol, reserve manager, custodian, or redemption agent was involved
  • where reserve reports, attestations, or transparency pages can be found
  • whether issuer redemption is being confused with secondary market liquidity
  • which official statements, regulator documents, court materials, audits, attestations, docs, or other sources support the record
  • which questions are still unresolved or not yet verified

The dataset is still small. The initial version starts with around 20 stablecoin records, including USDT, USDC, DAI, UST, BUSD, FRAX, TUSD, FDUSD, PYUSD, USDD, GUSD, LUSD, crvUSD, RLUSD, EURC, USDP, USDG, and USDS.

The site separates more than just the stablecoin name itself. It also tries to track:

  • stablecoin records
  • organization / issuer / protocol relationships
  • events
  • evidence and source records
  • reserve references
  • known unknowns
  • redemption-related notes
  • regulatory and lifecycle context

One important principle is to avoid overclaiming.

For example, a token trading near $1 on the market is not the same thing as the issuer offering direct 1:1 redemption to everyone. A reserve disclosure, a full audit, instant redemption, and secondary market liquidity are also different things. The registry tries to keep those concepts separate.

This is not a finished project. At this stage, I am trying to build a structure that will not break later, using a small number of records to test the classification, source model, and page layout. The plan is to expand the number of records gradually, but not at the cost of duplicate entries, weak sources, or bad classification.

Feedback would be useful, especially on:

  • important stablecoins that are missing
  • classification mistakes in the existing records
  • incorrect issuer, protocol, or organization relationships
  • missing depeg, collapse, wind-down, migration, or regulatory events
  • better primary sources
  • missing reserve reports, attestations, or redemption terms
  • confusing page layout or wording
  • old Bitcointalk threads or announcements that may be useful as historical sources

I am especially interested in older stablecoins, failed stablecoins, discontinued stablecoins, projects that changed issuer or brand, and official announcements that are still available somewhere.

Again, this is not meant to be an investment tool. It is closer to a quiet archive or historical ledger for stablecoin records.

Corrections, missing records, source suggestions, and classification feedback are welcome.

badjoke-lab (OP)
Newbie
*
Offline

Activity: 22
Merit: 10


View Profile
June 12, 2026, 03:31:38 PM
 #2

I also want to clarify the direction for future additions.

Stable or Gone is not intended to become only a list of USD fiat-backed stablecoins. USDT, USDC, BUSD, PYUSD, GUSD, and similar fiat-backed stablecoins are important, but they do not show the full history of stablecoin design, failure, redemption access, depegs, and lifecycle changes.

The registry should also be able to classify other types, such as:

  • protocol-based stablecoins
  • synthetic dollar assets
  • crypto-collateralized stablecoins
  • algorithmic stablecoins
  • failed or discontinued stablecoins
  • floating-target stable assets
  • commodity-referenced stable-value assets
  • yield-bearing stablecoin-adjacent assets

That does not mean all of these should be treated as the same thing.

The point is the opposite: the differences should be visible.

For example, an asset with issuer redemption, an asset with only protocol-based exits, an asset that can only be exited through the market, an asset without a fixed fiat peg, and a receipt or wrapper token should not all be displayed as if they were the same category.

The next small test batch I am considering includes:

  • USDe
  • sUSD
  • MIM
  • FEI
  • USDN

This batch is meant to test USD-referenced assets that are not simple fiat-backed stablecoins.

After that, I am also considering a more difficult classification batch:

  • RAI
  • PAXG
  • XAUT
  • SPOT
  • Nuon

That second batch is intended to test non-fiat references, floating targets, commodity-referenced assets, and basket / index-style references.

These are not final inclusions yet. At this stage, the goal is not to expand the scope too quickly, but to check whether the classification and display model can handle these cases without becoming misleading.

Stable or Gone should grow carefully. I would rather keep the categories strict than add more records in a messy way.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!