I have an application call which contains inner transactions, written in PyTEAL. I set the inner fee parameter to 0 so that the sender must pay for fees of the inner transaction and not use the funds held by the application. InnerTxnBuilder.Begin(), InnerTxnBuilder.SetFields( { TxnFiel…

I think I might be confusing myself a bit. The real question might be: How do I get suggested fee per byte, and why does the API return fee-per-byte of 0?

Fees without inner transactions The fees are computed as indicated there: [image] Structure - Algorand Developer Portal Algorand Developer Docs, SDKs, REST APIs, CLI tools, ecosystem projects, metrics dashboard and sample code, how-tos, and news from the Algorand developer community …

Thanks for the reply. :slight_smile: The simplest solution for that is to set: suggested_params.min_fee = suggested_params.min_fee * 2 I have been trying this, but the min_fee has no effect on whether the transaction is accepted or rejected. For example, I have tried: # Delete Application Txn…

Sorry my bad, the code I gave you was wrong. Here is the correct one: from algosdk import constants suggested_params.fee = constants.MIN_TXN_FEE * 2 suggested_params.flat_fee = True or suggested_params.fee = suggested_params.min_fee * 2 suggested_params.flat_fee = True

suggested_params.fee = suggested_params.min_fee * 2 suggested_params.flat_fee = True Looks good. I did not know about the flat fee. I can see that if flat_fee = True, then fee is the total fee instead of the fee per byte (as I can see in py algosdk docs for the SuggestedParams). I think that wi…

[image] plasmatech8: If the fee-per-byte was available then I it would easier for development and more future-proof since then you do not need any fee calculation logic and your application is adaptive to changes in the fees if unexpected network congestion occurs. suggest_params.fee (before …

I have made an gh issue and I think it clarified a few things for me as well. The fee parameter (fee-per-byte) returned by the API is indeed correct (it is zero until network congestion occurs). The fee-per-byte is NOT a problem. Is this a bug? As stated above, suggested_params.min_fee has no eff…

Another thing, I do not think it is possible to calculate the num_bytes for inner transactions. (need to look into dryruns) That may complicate things a little bit since you need to pay for the bytes of inner transactions too. And there is no way to get it easily/conveniently. Then again, transacti…

Yes, your computation looks good for transactions that are signed with an ed25519 key (as opposed to multisig / smart signatures, as estimated_size assumes that the transaction is signed with an ed25519 key - but this is an issue with the SDK too). Thanks for this detailed code! Inner transactions…

Cannot calculate suggested fees for inner transactions

General

plasmatech8 January 30, 2022, 5:24am 7

Actually, there might be a way to get the exact total fee for a transaction using dryruns. You would need to construct and sign the transaction twice though.

Topic		Replies	Views
Dealing with fees in smart contracts General teal , smart-contracts	4	974	December 2, 2021
Python getting suggested_fee in v2	4	556	August 26, 2021
Understanding tx fee	6	843	July 4, 2019
Algroand go sdk SignTransaction wrong	3	684	June 17, 2019
Opt-in ALGO fee management General community , asa , mainnet , smart-contracts , algorand-wallet	10	737	February 28, 2024

Cannot calculate suggested fees for inner transactions

Related topics