Decoda Research
RWA Security Intelligence
Independent, evidence-grounded research into tokenized real-world assets: the Security Controls Index, research datasets on who controls each asset, what has changed onchain, what issuers disclose and what each asset depends on, and reviewed case studies of past incidents.
6 research modules
What the platform tracks
Each module publishes only what its sources support, with the date it was collected. A module with nothing verified says so.
Security Controls Index
Evidence coverage, unresolved controls, snapshot history and revalidation behind the published index.
- Evidence coverage by category
- Unverified controls
- Snapshot comparison
- Revalidation outcomes
Snapshot 21 SEP 202610 assets, 110 controls, Q3 2026 edition
Privileged Access
Who can administer, upgrade, mint, pause or freeze each asset, and how that authority is held.
- Admins and proxy upgrade authority
- Mint, burn, pause and freeze roles
- Multisig owners and thresholds
- Timelocks and role changes
Last run 23 Oct 2026, 11:37 UTC17 documented contracts; 0 of 80 authority reads verified onchain
Security Events
Decoded administrative events onchain, kept apart from reviewed observations and confirmed incidents.
- Role and ownership changes
- Upgrades and admin changes
- Pause and unpause
- Reviewed classifications
Last scan 23 Oct 2026, 11:37 UTC0 events; 0 of 22 contracts scanned
Reserve Transparency
What each issuer publicly discloses about supply, NAV, reserves, oracles and reconciliation.
- Token supply
- NAV and AUM reporting
- Disclosures and attestations
- Oracle freshness
Last run 23 Oct 2026, 11:37 UTCSupply read for 0 of 10 assets; reserves not publicly verified
Systemic Dependencies
Custodians, administrators, oracles, bridges and shared infrastructure each asset relies on.
- Issuers and administrators
- Custodians and settlement
- Oracle providers and bridges
- Shared dependencies
Last run 23 Oct 2026, 11:37 UTC19 relationships: 0 verified, 13 documented, 6 unresolved
Historical Security Incidents
Case studies of past incidents at tokenized assets, researched from public sources and reviewed before publication.
- Privileged access and key compromise
- Attack and response timelines
- Quantified impact, kept apart by kind
- Security control lessons
Not yet publishedNo case study published yet; 1 held for review
Research integrity
How research is published
- 1
Evidence first
Every published observation names its source, when it was retrieved, the chain and block where relevant, and how far it was verified.
- 2
Unknowns stay unknown
Unverified, not observed and integration unavailable are separate states. Missing evidence is never presented as insecurity.
- 3
Reviewed before it is consequential
Claims of absence and any security-event classification beyond routine administration are held until a named researcher approves them.
- 4
Dated, never live
Every view states when its data was collected or published. Snapshots are archived as released and never replaced.
Verification states
Research observations carry one of these states. They describe how an observation was established and carry no score.
- Verified onchain
- Read directly from contract state or event logs, at a stated chain and block.
- Verified source
- Deployed bytecode matched to published source code by a source-verification service.
- Documented
- Stated in an issuer-published source — documentation, a deployment manifest or a filing — and not independently checked onchain.
- Unverified
- Looked for; the evidence found cannot establish it either way. Not a finding, and not a failure.
- Not observed
- Looked for in a stated scope and not found there. A claim of absence, published only after research review.
- Integration unavailable
- Nothing was observed: the data source needed was unreachable or not configured when collection ran.
Open data
Downloads
Generated at build time from the published files. Each module page lists its own downloads beside the data they contain.
A · Security Controls Index
- Leaderboard CSVOne row per protocol in published order: position, status, score, coverage and category scores.
- Controls register CSVOne row per protocol and control: category, weight, state, multiplier, evidence count and sources.
- Evidence citations CSVOne row per cited source: title, URL, host, observation date and confidence.
- Full edition JSONVersion line, the board with positions, and every protocol record.
- Snapshot index JSONEvery archived release with a link to its frozen archive.
- Revalidation: sources CSVEvery cited source rechecked in each revalidation, with its outcome.
- Revalidation: protocols CSVPer protocol: sources rechecked, address and onchain checks, gaps and changelog.
- Revalidation records JSONEvery revalidation record as published.
B · Privileged Access
- Privileged access dataset JSONEvery published observation with its verification state, value and full provenance.
- Privileged access observations CSVOne row per observation: subject, verification, first source, run, chain and block.
- Collection runs JSONEvery run with what each integration answered, and the hash-chained ledger over the run files.
C · Security Events
D · Reserve Transparency
E · Systemic Dependencies
F · Historical Security Incidents
Important context
Scores measure publicly observable technical controls and documentation at the stated snapshot date. They are not smart-contract audits, credit ratings, investment recommendations, or assessments of an organization's complete security posture.