Skip to content

Add explicit registry verification and source relationships - #56

Open
0xBreadguy wants to merge 10 commits into
mainfrom
codex/verification-schema
Open

0xBreadguy wants to merge 10 commits into
mainfrom
codex/verification-schema

Conversation

@0xBreadguy

@0xBreadguy 0xBreadguy commented Sep 17, 2026

Copy link
Copy Markdown
Member

Summary

  • Adds a required verification record with issuer, community, and infrastructure trust levels.
  • Pairs each level with a fixed review method: source-submission, maintainer-review, or official-infrastructure.
  • Emits sourceChain and sourceAddress on generated non-origin entries so consumers can match an exact relationship without metadata heuristics.
  • Migrates all 28 current token records: 24 issuer, 1 community, and 3 infrastructure.
  • Updates contributor guidance, the PR template, generation tests, and token-list version 1.1.0.

Trust model

The submitter proposes a verification level. Merging the entry is the registry maintainer attestation that the proposal satisfies registry policy.

New permissionless factory submissions should request community verification by default. Issuer verification is reserved for relationships supplied or approved by the issuer or its official organization. Infrastructure verification is reserved for official MegaETH protocol assets.

For this initial migration, existing source-submitted assets are marked issuer verified. CROWN is marked community verified. ETH, MEGA, and WETH are marked infrastructure verified.

Review focus

  • Confirm that CROWN is the only community-verified entry in the initial migration.
  • Confirm that ETH, MEGA, and WETH are the complete infrastructure set.
  • Confirm that merged Git history is sufficient evidence for migrated entries; future PRs expose an evidence field in the submission template.

Generated token-list files are intentionally not included. The existing post-merge workflow will regenerate them from data.

Validation

  • npm test: 17 passing
  • TypeScript: passing
  • Prettier: passing
  • Generated wstETH entry includes the exact Ethereum source address and issuer verification.

Dependency check

The repository dependency audit is being addressed by PR #55. This branch intentionally leaves package.json and package-lock.json unchanged. Rebase this branch after #55 merges to clear the inherited dependency audit failure.

@0xBreadguy 0xBreadguy left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've reviewed all file changes and modified any/all that needed to updated status

@0xBreadguy
0xBreadguy marked this pull request as ready for review September 17, 2026 19:20
@0xBreadguy

0xBreadguy commented Sep 17, 2026

Copy link
Copy Markdown
Member Author

Will rebase and merge after dependency PR which breaks the lint is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants