Repository navigation
v0.11.0-rc5
Pre-release
Pre-release
·
60 commits
to develop
since this release
π What's New
bridgesyncfrom_address/network_idsbridge-listing timeout fix (#1780):GET /bridge/v1/bridgeswas full-scanning the ~1.1M-rowbridgetable wheneverfrom_addresswas supplied, becauseUPPER(from_address) = UPPER($n)had no usable index. New migrationbridgesync0016adds an expression index onUPPER(from_address)matching the query predicate exactly.bridgetrackerAPI docs, fail-fast startup, and rate-limit cleanup (#1784, closes #1781, #1782, #1783): rewrotedocs/bridgetracker/API.mdto match the real wire format (most enums are bare strings; onlyErrorStep.error_type/CertificateData.statususe numeric+_string;eventnesting,omitemptyoptionals, and the never-populatedexpected_durationare now documented accurately). The proxy now fails fast at startup if[Tracker].L1GlobalExitRootAddressis unset instead of silently stalling every L1βL2 route atWaitingGERUpdate.MaxRequestsPerIPAndSecondnow defaults to0(unlimited) in[PublicREST]/[AdminREST]/proxy[REST], where it was never enforced anyway;[RPC]keeps its default of10since that section is enforced viatollboothingithub.com/0xPolygon/cdk-rpc.- SQLite query-planner regression fix: dropped
idx_bridge_destination_network(added, unreleased, by #1780's migration) after it was found to hijack the planner on a 1M-row fixture β aggkit never runsANALYZE, so the low-cardinality index stole the plan fromidx_bridge_deposit_count_descandidx_bridge_from_address_upper, regressing network-filtered paging ~0.5ms β ~600ms. Folded intobridgesync0016before its first release, so no extra migration is needed.
β οΈ Breaking Changes
- π οΈ Config: running the proxy with the
trackercomponent now fails at startup if[Tracker].L1GlobalExitRootAddressis unset/zero (previously it started and silently never resolved any L1βL2 bridge). Deployments running the tracker must set the address (#1784). - π οΈ Config:
MaxRequestsPerIPAndSeconddefault changes from10to0(unlimited) in[PublicREST],[AdminREST], and proxy[REST]. Behavior is unchanged in practice β these sections never enforced the limit β but explicit configs pinning10there should be reviewed.[RPC]'s default stays10and remains enforced (#1784). - ποΈ Storage: new migration
bridgesync0016(expression indexidx_bridge_from_address_upperonUPPER(from_address)) applies automatically on startup (#1780).
π Config Updates
- π§Ύ Tracker (proxy) β now required when running the
trackercomponent:[Tracker] L1GlobalExitRootAddress = "0x..." # <- now required; startup fails fast if unset
- π§Ύ REST rate limiting β new default, unlimited where the field was never enforced:
[PublicREST] MaxRequestsPerIPAndSecond = 0 # was 10; unlimited (never enforced here) [AdminREST] MaxRequestsPerIPAndSecond = 0 # was 10; unlimited (never enforced here) [RPC] MaxRequestsPerIPAndSecond = 10 # unchanged; IS enforced (tollbooth via cdk-rpc)
π Bug Fixes
GET /bridge/v1/bridgesno longer times out when filtering byfrom_addresson large bridge tables (#1780).docs/bridgetracker/API.mdnow matches the actual wire format (#1781/#1784).- Proxy
trackercomponent fails fast on missingL1GlobalExitRootAddressinstead of silently stalling (#1782/#1784). - Removed a low-cardinality SQLite index (
idx_bridge_destination_network) that regressed bridge-paging query performance (#1784).
Full changelog: v0.11.0-rc4...v0.11.0-rc5