v1 and v2 Branches
v2
main is the v2 platform branch. It contains the Deep Ops/modular platform work: modular FastAPI domains, v2 Supabase schema, feature flags, migration/backfill tooling, observability, SSO/OIDC/Supabase auth work, web3 v2 integration, dashboard refactors, and release/security hardening.
v1
v1 is a frozen branch created at:
b9ef9d5087dc14368120f659c81bc3706ca20af2
Short form: b9ef9d5
Commit title:
Merge pull request #234 from Almalgo/main
The title is slightly misleading in current branch context. The commit's second parent is the v1-era redesign/operations PR tip, and b9ef9d5 is not an ancestor of current v2 main.
Divergence
The effective merge-base between current main and v1 is:
10bca61b9c56e9cff9e3868b3f2d054e0a4aff55
Short form: 10bca61
Date/title:
2026-02-20 — Merge pull request #172 from Almalgo/web3_fix
After this point:
mainbecame the v2 / Deep Ops line.v1continued receiving selected v1-era feature and stabilization merges untilb9ef9d5.
Practical rule
- New platform work should target
main. - Only v1-specific hotfixes or historical audits should target
v1. - Do not assume v1 contains current v2 architecture.