Hi everyone! In my Java backend, when retrieving txn information with the indexer client, i find out that the chain response with all params of a txn with fee = 0 (because of part of a txn group where just one txn pays fees for all txns in the group itself) doesn’t cointain the param fee. Therefore, the java algorand sdk, while parsing the chain response, gets fee as null and sets it as Account.MIN_TX_FEE_UALGOS. So, there’s no way to discriminate between 0 fee txn and a MinFee one.
Is there a reason to this behaviour?
This behavior likely occurs because the indexer omits the ‘fee’ field when it’s explicitly set to 0. Since the SDK defaults to MIN_TX_FEE_UALGOS when parsing a null fee, distinguishing between a true zero-fee txn and a MinFee one becomes tricky.
Yeah, that’s exactly the same i wrote in the topic. So, nothing new, not solved yet! It sounds like a bug or a wrong management of the param fee in the java sdk.
