dbd517b279
- Update dbis_core, cross-chain-pmm-lps, explorer-monorepo, metamask-integration, pr-workspace/chains - Omit embedded publish git dirs and empty placeholders from index Made-with: Cursor
112 lines
2.9 KiB
Markdown
112 lines
2.9 KiB
Markdown
# Explorer Transaction Compliance Matrix
|
|
|
|
Purpose: define the first explorer-side heuristic for grading how well a transaction is evidenced, decoded, and aligned with the repo's GRU, x402, and ISO-20022 posture.
|
|
|
|
This matrix is intentionally operational and observational. It is not a legal opinion, regulatory ruling, or substitute for off-chain compliance controls.
|
|
|
|
## Scope
|
|
|
|
Use this score to:
|
|
- triage transactions in the explorer
|
|
- understand how much structured evidence is visible
|
|
- highlight transactions that deserve deeper human review
|
|
|
|
Do not use this score as:
|
|
- final regulatory approval
|
|
- final settlement approval
|
|
- a substitute for policy-engine, KYC, AML, or ledger review
|
|
|
|
## Score
|
|
|
|
Total: `100`
|
|
|
|
### 1. Execution Integrity
|
|
|
|
Weight: `25`
|
|
|
|
Signals:
|
|
- success vs failure
|
|
- presence of mined execution context
|
|
- overall confidence that the transaction actually completed as intended
|
|
|
|
### 2. Decode Clarity
|
|
|
|
Weight: `15`
|
|
|
|
Signals:
|
|
- method label is known
|
|
- decoded input parameters are visible
|
|
- explorer can show structured intent rather than raw calldata only
|
|
|
|
### 3. Counterparty Traceability
|
|
|
|
Weight: `15`
|
|
|
|
Signals:
|
|
- sender visible
|
|
- recipient or created contract visible
|
|
- block anchoring visible
|
|
- timestamp visible
|
|
|
|
### 4. Asset Posture
|
|
|
|
Weight: `20`
|
|
|
|
Signals:
|
|
- transferred assets appear GRU-aware
|
|
- transferred assets appear x402-ready where relevant
|
|
- transferred assets appear ISO-20022-aligned in the local explorer posture
|
|
|
|
Notes:
|
|
- this is neutral rather than punitive for transactions that do not include token transfers
|
|
- this is an explorer-side view based on local GRU intelligence, not a final institutional judgment
|
|
|
|
### 5. Audit Richness
|
|
|
|
Weight: `15`
|
|
|
|
Signals:
|
|
- token transfers indexed
|
|
- internal calls visible
|
|
- raw input visible
|
|
- decoded input visible
|
|
|
|
### 6. Exception Hygiene
|
|
|
|
Weight: `10`
|
|
|
|
Signals:
|
|
- explicit revert reason
|
|
- failed execution
|
|
- obvious exception posture that lowers confidence
|
|
|
|
## Grades
|
|
|
|
- `A`: `90-100`
|
|
- `B`: `80-89`
|
|
- `C`: `70-79`
|
|
- `D`: `60-69`
|
|
- `E`: `<60`
|
|
|
|
## Interpretation
|
|
|
|
- `A` means the explorer has strong structured evidence and the transaction is easy to review operationally.
|
|
- `B` means the transaction is still strong, but some context is missing.
|
|
- `C` means the transaction is understandable but not richly evidenced.
|
|
- `D` means review confidence is thin.
|
|
- `E` means the explorer-visible posture is weak and deserves caution.
|
|
|
|
## Current Limitations
|
|
|
|
- The matrix does not ingest off-chain policy decisions.
|
|
- The matrix does not prove legal or regulatory sufficiency.
|
|
- The matrix does not parse full ISO-20022 payloads.
|
|
- The matrix depends on explorer indexing quality and local GRU intelligence coverage.
|
|
|
|
## Next Upgrades
|
|
|
|
- add log-level standards and event scoring
|
|
- add ISO correlation identifiers when available
|
|
- add bridge-lane and cross-chain settlement evidence
|
|
- add reserve and governance posture where directly linked to tx context
|