Ricardo Guilherme Schmidt f8cbcc6956 fix(ata): lock down ATA::Transfer recipient contract ...

Enforce at the ATA layer that the recipient token holding is already
initialized, owned by the same token program as the sender ATA, decodes
to a valid `TokenHolding`, and points at the same token definition as
the sender. Align the core instruction doc and guest wrapper doc with
that contract, and cover the boundary with unit tests (default,
foreign-owned, malformed, mismatched-definition recipients, plus the
missing-owner-auth and happy paths) and end-to-end integration tests
(default and mismatched-definition recipients).

Without this, the downstream `token::Transfer` default-recipient
`Claim::Authorized` path was reachable through ATA, so integrators had
to reverse-engineer recipient semantics from token/runtime internals.

2026-05-13 13:32:09 +02:00

..

core

fix(ata): lock down ATA::Transfer recipient contract

2026-05-13 13:32:09 +02:00

methods

fix(ata): lock down ATA::Transfer recipient contract

2026-05-13 13:32:09 +02:00

src

fix(ata): lock down ATA::Transfer recipient contract

2026-05-13 13:32:09 +02:00

Cargo.toml

chore: update LEZ to v0.2.0-rc3

2026-05-12 08:46:36 +02:00