Affects
Teams operating Matcher aggregator connections, audit-chain checks, or fee expressions.
What changed
An aggregator connection can be created without
accountRef while it awaits end-customer consent. A hosted consent token binds or renews the vendor reference; only bound connections can be tested.
Audit-chain verification accepts fromSeq as a resumable floor. A run above sequence 1 trusts that record’s stored previous hash, so it does not verify earlier records. Rate-shaped expressions that scale exactly one gross by numeric literals must stay between 0 and 1.
This corrects documentation of implemented contracts. It does not announce a runtime release.
Impact
Classification: Review recommended. Consent orchestration, incremental audit checks, and fee formula validation need to reflect their documented boundaries.
What you need to do
1
Offer connection testing only after hosted consent binds the vendor account reference.
2
Use
fromSeq only when the trusted lower audit-chain boundary is explicit.3
Validate rate-shaped fee expressions as fractions between
0 and 1.