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,…

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.

May I ask you to open a GitHub issue on the Java SDK repository so that the Algorand Technologies team who maintains the library can investigate this?

Transaction Response with no fee attribute when fee = 0

General

francescamartinucci March 19, 2025, 1:25pm 5

Sure, I’ll do it as soon as possible. Thanks for your reply.

Topic		Replies	Views
Understanding tx fee	6	843	July 4, 2019
Cannot calculate suggested fees for inner transactions General smart-contracts	10	1795	February 2, 2022
Dealing with fees in smart contracts General teal , smart-contracts	4	977	December 2, 2021
Python getting suggested_fee in v2	4	559	August 26, 2021
Having a smart contract pay transaction fee for the caller	0	170	January 22, 2024

Transaction Response with no fee attribute when fee = 0

Related topics