Backdoor Token Helper

@lib/backdoorToken/BackdoorToken.ts provides a guarded escape hatch that can reset a specific token’s usage record after it has been consumed. It exists for QA/demo flows where you need to reuse the same NFT without minting/burning every time.

How It Works

1. Environment flags (BACKDOOR_TOKEN, TOKEN_ID, BACKDOOR_ADDRESS) describe which token/address pair is eligible.
2. /api/form-submission-gate calls scheduleTokenReset(tokenId, address, reqId) after marking the token as used.
3. The helper validates inputs via shared Zod schemas, ensures the configured token/address match, and in production requires BACKDOOR_ADDRESS to be set.
4. It loads the appropriate Prisma delegate and flips the used, usedBy, and usedAt fields back to the unused state.

await scheduleTokenReset(42, '0xabc...', requestId);

• In development, logs include loud emoji-prefixed messages indicating whether the backdoor was activated.
• In production, all messaging is intentionally vague (“Special handling activated”) so the feature can stay hidden.

Environment Flags (server.env)

File Tree

• app/lib/backdoorToken