Files
zeekayandHanzo Dev f3e0ed38dc the receive specs run against the bank, not a stub of it
They intercepted /v1/bank/wallet and /v1/bank/overview and rewrote the
answers, so what they proved was that the page renders a fixture — the
addresses, the bank name, the routing number and the IBAN were all written
in the spec. Nothing is intercepted now: an address the page shows is one
bankd derived from the mnemonic, and the coordinates beside it are the
ones it would give a payer.

That costs the exact-value assertions, so what is asserted is what the
screen has to get right whatever those values are: the address belongs to
the asset picked and changes with it, each is shaped for its own chain,
the US rail shows a routing number and no IBAN line, and the two pages
that carry the account's coordinates carry the same ones.

The IBAN market spec is gone rather than rewritten, because the state it
asserted cannot be reached: ProvisionCustomer sets every account to USD
and nothing else ever writes that field, so receivingFor's IBAN branch
answers no account this bank can open. Stubbing was the only way it could
pass, which is the thing worth knowing.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-27 15:53:20 -07:00
..