![]() The floating-point representation is based on the fact that any number can be written in algebraic form as the product of a number less than 10, which is called a mantissa, and a power of ten, called an order. The following are examples of numeric constants: 123 0.0įractional constants can be represented as a floating-point number. If the constant is negative, a minus sign is placed immediately before the first digit. When writing fractional numbers, a period is used to separate the integer and fractional parts. In the text of the program, numerical constants are written in the usual way, that is, in the same way as numbers, for example, when solving mathematical problems. After Delphi I am seeing this happen more regularly despite the 5% added.In delphi, there are two kinds of constants: regular and named.Ī regular constant is an integer or fractional number, a string of characters or a single character, a Boolean value. I added a somewhat arbitrary 5% padding (prior to Delphi) to resolve transactions occasionally not getting picked up by bakers within a reasonable time or sometimes not until they expire from the mempool. (minimal_nanotez_per_byte * tx_size_in_bytes) (minimal_nanotez_per_gas_unit * consumed_gas) + My formula, using consumed_gas given by run_operation: fee = minimal_fees + Minimal_nanotez_per_byte is given by the node, and is now 250 nanotez. Minimal_nanotez_per_byte = 1000 nanotez (1 mutez) Minimal_nanotez_per_gas_unit = 100 nanotez The constants I was using before Delphi: minimal_fees = 100 000 nanotez (100 mutez) Since the Delphi protocol upgrade my calculated fees result in transactions which often take 15-60 blocks to confirm, assuming because baker's de-prioritize transactions with fees too low. I am using the following formula and associated constants to calculate fees: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |