Error: Reached maximum depth for account resolution

[miaomiaowu0428]

i cant understand why this could reach 16 depth of resolution while building instruction

[SkymanOne]

Coral TS client fails to auto-resolve seeds that are Big-Endian encoded; you need to derive the PDA address on the client side and explicitly provide it with the instruction

[acheroncrypto]

The previous comment is correct — we currently don't store the endianness and assume the seeds are little-endian.

The error message includes the problematic accounts in v0.31, see:

• ts: Include unresolved accounts in the resolution error message #3207
• https://www.anchor-lang.com/docs/updates/release-notes/0-31-0#error-improvements

Additionally, using the seeds constraint with mint constraints is most likely not what you want to do.

[nick-720]

@miaomiaowu0428 Anyway you remember how you resolved this? Did you change the seeds? I'm using

seeds = [token_lottery.total_tickets.to_le_bytes().as_ref()]

from the bootcamp and the test is throwing this error

Reached maximum depth for account resolution. Unresolved accounts: ticketMint, destination, ticketMetadata, ticketMasterEdition

so it seems to be getting triggered by the ticket_mint seeds