Bitflow: accounting and reserve loss assessed separately

Clarity sources and review date

Documentation of 6 October 2026 mapped deployed Clarity code on Stacks separately from historical repository content. Independent counterreview examined a bounded slice, not the whole Bitflow offering.

Who benefits from the difference?

Economic review considered the direction and beneficiary of the accounting difference. A different result alone did not establish loss of third-party reserves. Accounting effect and alleged asset loss required separate evidence.

Gross and net

The example separates a fee assumption from a net amount using subtraction. Its values are invented and it is not a Bitflow formula. It illustrates why comparing two numbers requires their calculation assumptions.

1def net_amount(gross, fee):
2    assert 0 <= fee <= gross
3    return gross - fee
4
5assert net_amount(100, 2) == 98
6assert net_amount(100, 0) == 100

Countercheck for reserve loss

The second fixture changes allocation while preserving the total. Within the model it rejects the inference that every differing net amount necessarily means reserve loss. Historical counterreview examined actual artifacts; this example does not reproduce the private mechanism.

1expected = {"user": 98, "beneficiary": 2}
2observed = {"user": 100, "beneficiary": 0}
3assert sum(expected.values()) == sum(observed.values())
4assert expected != observed
5# Allocation changed; a reserve-loss claim needs separate evidence.

Different source families

Source mapping kept deployed variants distinct. The hash comparison illustrates that principle without asserting a real contract count. A repository name did not replace mapping the code actually reviewed.

1import hashlib
2artifacts = [b"fixture-a", b"fixture-a", b"fixture-b"]
3family_ids = {hashlib.sha256(x).hexdigest() for x in artifacts}
4assert len(family_ids) == 2

Two separate dispositions

The historical accounting observation received a conditional Low/Medium classification. A separate candidate for Critical reserve loss was rejected. Those dispositions must not be combined into a confirmed High or Critical finding.

Assessment remains scope-specific

Fresh economic assessment requires current sources and state assumptions. These results concern the historical examined slices. This report did not assess subsequent remediation or current security of other Bitflow components.

Review limits

• As of 6 October 2026. Two separate counterreviews, not review of every Bitflow product.

References

The links provide project context. The judgment rests on the evidence described in the audit. Review models and actual tool excerpts are labelled separately.