Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 20230323-transaction-fee.md #265

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions governance/20230323-transaction-fee.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Finally, Flow’s low transaction fee unfortunately makes FLOW use-cases less pe

## **Proposal**

Today, the functional specification of transaction fee on Flow looks as follows.
**Today**, the functional specification of transaction fee on Flow looks as follows.

**Transaction fee = {inclusion fee + (execution effort * unit cost)} x surge**

Expand All @@ -48,10 +48,13 @@ Today, the functional specification of transaction fee on Flow looks as follows.
- *Surge = 1.0 (currently constant);*
- *Execution Effort is variable based on transaction type, as [shown here](https://github.com/onflow/flow/blob/c05d847adf2f6fb509e42c17020484d7dd3e89bd/flips/20220111-execution-effort.md).*

**It is proposed that**
**The proposal** entails the addition of a new multiplier, alongside the surge multiplier, to the transaction fee calculation, resulting in the following formula:

1. *Inclusion fee is maintained as a constant, but increased 100x, from 1E-6 FLOW to 1E-4 FLOW for all transaction types*
2. *Unit Cost of Execution Effort is increased 100x, from 4.99E-8 FLOW to 4.99E-06 FLOW*
**Transaction fee = {inclusion fee + (execution effort * unit cost)} x surge x T**

- Presently, the Flow network fundamentally supports the dynamic adjustment of transaction fees in response to network congestion. The surge factor ('S') facilitates fee modifications during congested periods, ensuring optimal network functionality. Although currently fixed at 1.0, adjustments to this value may be proposed through a FLIP in response to sustained periods of high network demand and saturation.
KshitijChaudhary666 marked this conversation as resolved.
Show resolved Hide resolved
- Introducing a Transaction Fee Multiplier ('T') alongside the existing surge factor would additionally enhance the adaptability and responsiveness of transaction fees to economic conditions. Additionally, it would cater to future requirements for adjusting the unit cost of transactions on Flow, while also ensuring transparency, ease of understanding, and readability of the formula for our community members.
KshitijChaudhary666 marked this conversation as resolved.
Show resolved Hide resolved
- **The value of 'T' will be set at 100** to increase the transaction fee by 100 times compared to the current rate, thus increasing costs of each transaction by 100x as shown in the table below.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you use T then the variable shows up like a formula. Consider using ` blocks instead of ' ones.

T vs 'T'


| Transaction type | Effort | Current fee (FLOW) | Proposed fee (FLOW) | Proposed increase |
| --- | --- | --- | --- | --- |
Expand Down
Loading