Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsRustChain’s bridge reconciliation under-reported committed supply because its formula subtracted voided transfers even though those transfers were already excluded from the locked and completed totals. In merged pull request #8517, the formula was corrected to add those two totals without subtracting the separately tracked voided amount.
How the bridge aggregation partitions transfer amounts
The cited implementation groups bridge_transfers by status and sums amount_rtc. It places pending, locked, and confirming amounts in locked_in; completed amounts go into completed_in; and voided amounts are recorded separately. The statuses are mutually exclusive, so a voided row is not included in either of the first two totals.
As an Amazon Associate I earn from qualifying purchases.
RustChain maintainer Scottcjn described the code in the review of pull request #8517: “Each bridge_transfers row has exactly one status, and _aggregate_bridge_state builds locked_in from pending|locked|confirming only (node/bridge_federation_routes.py:121-126).”
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why the old formula under-reported committed supply
The old calculation was:
locked_in + completed_in - voided_inThat subtraction counted voided amounts against a total that already excluded them. The correct committed-supply calculation for this status partition is:
#1 Best Overall
locked_in + completed_inFor the pull request’s example, 30.0 RTC locked plus 50.0 RTC completed equals 80.0 RTC committed. Subtracting 3.0 RTC of voided transfers would produce 77.0 RTC, an incorrect undercount. If the voided total exceeded the sum of locked and completed amounts, the old formula could even return a negative result.
What pull request #8517 changed and verified
The merged change removes voided_in from the committed-supply formula and updates the example’s expected values to 80.0 and 3.0. The pull request records 19 passing tests in node/tests/test_bridge_reconciliation.py. That is the verification reported in the PR; it is not evidence of a separate test run or of every production deployment using the fix.
Rank #2
How to review the invariant in code
When reviewing a bridge reconciliation calculation, first establish which statuses feed each aggregate, then make sure the formula does not adjust for a category that was never included. For this case, the invariant is that committed supply equals the sum of the locked and completed categories because voided transfers are excluded from both.
- Check the aggregation’s status filters and confirm that the categories are mutually exclusive.
- Trace the committed-supply expression to see whether it subtracts a separately tracked status already omitted from the input totals.
- Make test expectations reflect both ordinary totals and cases where the voided amount would otherwise distort or make the result negative.
What happens to snapshots written before the fix
The maintainer notes that snapshots written before the fix retain the old formula, so a comparison across the change can show a step. The PR review does not specify a backfill or historical-recomputation procedure; it does not establish how an operator should migrate those snapshots.
Rank #3
What this fix does—and does not—establish
Pull request #8517 establishes a code-level accounting error and its correction. It does not establish an observed bridge insolvency event, a consensus failure, or production harm. The reviewed sources also do not quantify how often this defect occurred or its financial scale.
The DEV Community article describing the example cites FEDERATION_BRIDGED_SUPPLY_SPEC.md as a governing document, while the maintainer review says that file is not in the repository. The exact broader specification therefore cannot be independently confirmed from the reviewed materials. For the code change itself, the merged PR is the primary record: RustChain pull request #8517. Project context is available in the RustChain repository.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →
