Flow public chain | flow dynamic transaction fee will be launched soon

The heart of the meta universe 2022-04-06 17:05:11 阅读数:230

flow public chain flow dynamic

Link to the original text :https://forum.onflow.org/t/variable-transaction-fees-are-coming-to-flow/2941

translate :Flow Technical Ambassador ,Lanford.

After months of work ,FLIP-660: Dynamic transaction fee (https://github.com/onflow/flow/blob/master/flips/20211007-transaction-fees.md) The implementation of has been merged , And is ready to be included in 2022 year 4 month 6 The day comes  spork(https://docs.onflow.org/node-operation/upcoming-sporks/). Dynamic transaction fees are allowed to be submitted to Flow The transaction is priced based on its total execution workload , Instead of the current simple 0.00001 FLOW Fixed value .


Why do we need dynamic transaction fees ?

With Flow stay  "Stable Cadence" (https://forum.onflow.org/t/the-path-to-stable-cadence/2702) And license free smart contract deployment , There must be some way to consider the different usage patterns of shared resources . about Flow, The pricing of storage cost and transaction cost has always been separated .FLIP-660 Improved this kind of cleavage , Allow the network to collect transactions based on the following factors :

  • Total transaction execution workload

  • The cost of incorporating the network into the transaction

  • Surge coefficient ( translator's note : Refers to the coefficient related to the network load , You can refer to here :https://github.com/onflow/flow/blob/master/flips/20211007-transaction-fees.md)

By increasing this granularity ,Flow Better measure the impact of transaction execution on all users and network operators . This can improve the overall security of the network , The more expensive the operation, the higher the cost ( Ultimately, reduce spam and useless transactions ), Keep basic at the same time 、 Common operations have low prices .


Let's do it !

And Flow Chain interactive Dapp、 Tools and wallets must be in 5 Before the main network enables dynamic transaction fees in the second ten days of the month , Check that they are right in the transaction gasLimit Use , And whether and how to display the total transaction cost to the user .


Important date

( translator's note :FLIP-660 It is proposed to introduce dynamic transaction fee , The mathematical model of cost calculation is put forward ;FLIP-753 Based on FLIP-660 A model is proposed , Used to measure different functions in transactions 、 The execution workload corresponding to the operation and the execution workload corresponding to each unit FlOW expenses )

  • 2022 year 3 month 31 Japan : The community is right FLIP-753 Review and feed back the dynamic transaction fee amount proposal .

  • 2022 year 4 month 6 Japan : Dynamic transaction fee function (FLIP-660) Publish to the test network and the main network , But it will not be enabled for the time being .Dapp You should start evaluating and implementing changes to present and process dynamic transaction fee amounts .

  • 2022 year 4 month 8 Japan : Enable the dynamic transaction fee function on the test network .

  • 2022 year 4 month 8 solstice 4 month 15 Japan : The community will vote on the amount of dynamic transaction fee to be applied .

  • 5 late : Waiting for the results of the vote , Enable dynamic transaction fees on the main network (FLIP-753). here ,Dapp You should be prepared to present and process dynamic transaction fee amounts . Read the FAQ below for more information .


common problem

■  When will this update take effect ?

stay 4 month 6 Japanese spork after , The cost will not change immediately . Community voting will take place soon after the code goes online , Specific fee structure with approval as the starting point . Details of this vote will be available on FLIP-753 After the merger .

■  What is the transaction cost after applying the changes ?

Dapps And wallets must be able to support costs greater than  0.001 FLOW  Transactions . although FLIP-753 The goal is to make the average transaction price lower than the existing cost , But it does mean that some transaction costs can exceed the current 0.0001 FLOW Fixed value of . Any in Flow Applications or wallets that display transaction prices in should be aware of this , And according to FLIP-753 Calculate the actual price based on the final value in .

  How to determine the execution workload of my transaction (gas) ceiling , namely gasLimit?

There is currently no to estimate the transaction workload API, Therefore, it is recommended that developers take advantage of Flow Simulator And test network to analyze transactions and determine the scope of their execution workload .

For transactions that can use any execution workload , It is recommended to use the maximum value 9999.

■  FCL Or others SDK Will there be any change ?

FCL At present, it is allowed to Dapp Set... For the transaction gasLimit, But if it is not set , It defaults to a lower value . This function will remain unchanged after this update .

If not set gasLimit And used  NewTransaction(),Flow Golang SDK At present gasLimit The default setting is 9999, Otherwise, the default setting is 0.

It is worth noting that ,Dapp They should reassess their current fixed gasLimit Whether you can work under the new transaction cost proposal .

■  When can I test the deal ?

FLIP-753 The amount of fee proposed in the community vote will be in  4 month 6 Japan spork  Update to the test network after successful completion . When the , You will be able to observe FlowFees.FeesDeducted Event to test the transaction , The incident will be reported in spork Then it changes , To reflect the new execution workload of the transaction .

at present , by Flow Emulator Support for the new fee structure in is in progress .


Other information

  • FLIP-660 link :https://github.com/onflow/flow/blob/master/flips/20211007-transaction-fees.md

  • FLIP-753 link :

  • Community Governance Forum :

版权声明:本文为[The heart of the meta universe]所创,转载请带上原文链接,感谢。 https://netfreeman.com/2022/04/202204061656467608.html