user3940: I'm wondering, do I need to always generate a new protocols parameters JSON file when generating the min transaction fee?
I have a few transactions to make and I really don't like to be creating a new protocol parameters file before calculating the min fee. Is there a better approach for that?

user4302: Generating a new protocol parameters file just dumps the node's current parameters into a JSON format. Since the parameters are not constantly changing, generating a new params file each time is not strictly necessary - you can reuse it. However, if the parameters do change (as the did just now at the E319 boundary), then your fee calculation might be impacted if you use an outdated file.
Personally, I like to generate a new params file every epoch - this can be easily automated with cron.

3940: <p>I'm wondering, do I need to always generate a new protocols parameters JSON file when generating the min transaction fee?</p>
<p>I have a few transactions to make and I really don't like to be creating a new protocol parameters file before calculating the min fee. Is there a better approach for that?</p>
 4302: <p>Generating a new protocol parameters file just dumps the node's current parameters into a JSON format. Since the parameters are not constantly changing, <strong>generating a new params file each time is not strictly necessary</strong> - you can reuse it. However, if the parameters do change (as the did just now at the E319 boundary), then your fee calculation <em>might</em> be impacted if you use an outdated file.</p>
<p>Personally, I like to generate a new params file every epoch - this can be easily automated with <code>cron</code>.</p>
