Skip to content

chore: remove misleading "v2" from DIPs migration and docs#965

Merged
MoonBoi9001 merged 1 commit intorefactor/billion-entities-pricingfrom
chore/rename-dips-migration
Mar 3, 2026
Merged

chore: remove misleading "v2" from DIPs migration and docs#965
MoonBoi9001 merged 1 commit intorefactor/billion-entities-pricingfrom
chore/rename-dips-migration

Conversation

@MoonBoi9001
Copy link
Member

Motivation

The codebase has references to "DIPs v2" implying there was a v1 that preceded it. There wasn't -- the off-chain voucher-based system was abandoned before deployment. DIPs is the on-chain RecurringCollectionAgreement system, full stop. The "v2" label is confusing and should be removed.

Summary

  • Renames migration 20260209000000_dips_v2 to 20260302000000_dips_pending_proposals -- describes what the migration does rather than implying a version lineage that doesn't exist
  • Fixes DipsConfig doc comment from "DIPS V2 configuration" to "DIPs configuration"
  • Clarifies the migration ownership comment in service.rs: the indexer-service does not run migrations by convention, the agent owns DDL, and the SQL files here are for local dev and tests only

There is no DIPs v1 -- the off-chain voucher system was abandoned before
deployment. DIPs refers exclusively to the on-chain RCA system. Rename
the migration from dips_v2 to dips_pending_proposals and clean up doc
comments that referenced "V2".

Also clarifies the migration ownership comment in service.rs: the
indexer-service does not run migrations by convention, the agent owns
DDL, and the SQL files here are for local dev and tests only.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@MoonBoi9001 MoonBoi9001 merged commit b695ad8 into refactor/billion-entities-pricing Mar 3, 2026
7 checks passed
@MoonBoi9001 MoonBoi9001 deleted the chore/rename-dips-migration branch March 3, 2026 02:13
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.

1 participant