Display confirmed BORO lock address #24

Closed

backmeupplz wants to merge 2 commits from bdt-kaneo-17-confirm-lock-address into main

backmeupplz commented

2026-05-25 23:00:54 +00:00

(Migrated from github.com)

Summary

add the verified Base mainnet BORO lock proxy as the frontend fallback address
record lock implementation/proxy deployment metadata and verification evidence in docs
keep the production claim/distributor state pending until Merkle distributor deployment/funding exists

Validation

bun run check
bun run test
bun run build
git diff --check
Sourcify exact-match verification for lock implementation 0x4086EE98cEE5929911EFbA6F77cc5c5E8b48b493
Base RPC proxy checks: owner 0x75DBd3d9d83baC30982627Dcbf3c0b46Ce001EA2, token 0x91f11Ad8fa616E95b41C88dFFde95D415F3F9C3c, lockDuration 31536000, implementation slot 0x4086EE98cEE5929911EFbA6F77cc5c5E8b48b493

Manual QA: production redeploy/browser lock-flow verification is still required after this PR lands; Merkle distributor/claim flow remains outside this PR because no distributor address/funding/proof source exists yet.

## Summary - add the verified Base mainnet BORO lock proxy as the frontend fallback address - record lock implementation/proxy deployment metadata and verification evidence in docs - keep the production claim/distributor state pending until Merkle distributor deployment/funding exists ## Validation - bun run check - bun run test - bun run build - git diff --check - Sourcify exact-match verification for lock implementation 0x4086EE98cEE5929911EFbA6F77cc5c5E8b48b493 - Base RPC proxy checks: owner 0x75DBd3d9d83baC30982627Dcbf3c0b46Ce001EA2, token 0x91f11Ad8fa616E95b41C88dFFde95D415F3F9C3c, lockDuration 31536000, implementation slot 0x4086EE98cEE5929911EFbA6F77cc5c5E8b48b493 Manual QA: production redeploy/browser lock-flow verification is still required after this PR lands; Merkle distributor/claim flow remains outside this PR because no distributor address/funding/proof source exists yet.

backmeupplz commented

2026-06-11 10:23:34 +00:00

(Migrated from github.com)

Closing as superseded — BDT-17's deliverable already shipped to main.

The core change in this PR ("add the verified Base mainnet BORO lock proxy as the frontend fallback address") is already present in main:

apps/frontend/src/launch-config.ts already defines the confirmed proxy fallback:
BASE_MAINNET_BORO_LOCK_ADDRESS = '0xfDD50a8eB2fc3Ef7325606aED1cf3FFBF3dC72e2'
docs/boro-deployments.md on main already records the proxy / implementation (0x4086EE98…) / token addresses and Basescan links.

What remains unique to this branch is now-conflicting churn rather than functional work:

apps/frontend/src/evm.ts: only a prettier import reformat (no behavior change).
docs: reordering of the deployment-metadata table and minor wording (e.g. a "Lock deployer / distribution wallet" line, a Sourcify "Verification" row, an "ownership handoff: not separate" clarification).

Since the frontend fallback address is already live on main and the branch is CONFLICTING, there is no functional gap to merge. Closing to clear the queue. If the minor doc clarifications above are still wanted, they can be re-added in a fresh, non-conflicting docs PR.

— automated Symphony PR-queue review

Closing as **superseded** — BDT-17's deliverable already shipped to `main`. The core change in this PR ("add the verified Base mainnet BORO lock proxy as the frontend fallback address") is already present in `main`: - `apps/frontend/src/launch-config.ts` already defines the confirmed proxy fallback: `BASE_MAINNET_BORO_LOCK_ADDRESS = '0xfDD50a8eB2fc3Ef7325606aED1cf3FFBF3dC72e2'` - `docs/boro-deployments.md` on `main` already records the proxy / implementation (`0x4086EE98…`) / token addresses and Basescan links. What remains unique to this branch is now-conflicting churn rather than functional work: - `apps/frontend/src/evm.ts`: only a prettier import reformat (no behavior change). - docs: reordering of the deployment-metadata table and minor wording (e.g. a "Lock deployer / distribution wallet" line, a Sourcify "Verification" row, an "ownership handoff: not separate" clarification). Since the frontend fallback address is already live on `main` and the branch is `CONFLICTING`, there is no functional gap to merge. Closing to clear the queue. If the minor doc clarifications above are still wanted, they can be re-added in a fresh, non-conflicting docs PR. — automated Symphony PR-queue review