All notable changes to the core components will be documented in this file.
- Rejected transactions are now stored in the database for 2 weeks only.
MetricsCounter
structure was removed because it is not used.- The limit on the number of withdrawals in the block.
- Type aliases (
TokenId
,AccountId
,Nonce
,BlockNumber
,PriorityOpId
,EthBlockId
) are replaced with wrapper structures. prometheus_exporter
was made a library to be used by several crates.prover_run_for_next_commit
function uses a parameterized timeout instead of a hard-coded one.- (
storage
):action_type
column type in db is changed fromtext
toenum
for optimization. - (
FeeTicker
): Increased gas price estimate for transaction. - (
loadtest
): Scenario execution was made parallel. - Increased completeWithdrawal gas limit, that decreased the chance of the users to face the out-of-gas error
prometheus_exporter
is launched by every microservice.tokens_acceptable_for_fees
endpoint that returns the list of tokens acceptable for fees was added to REST API v0.1.
- (
FeeTicker
): Performance for getting the batch fee was heavily optimized.
gen_token_add_contract
crate is rewritten in ts.- Metrics were added to some functions from lib/storage.
get_tx_by_hash
function was simplified.
closest_greater_or_eq_packable_fee_amount
andclosest_greater_or_eq_packable_token_amount
functions.test_float_conversions
test was expanded.- Loadtest scenario for stressing transaction batches
- Sequential Sparse Merkle Tree implementation was removed because it has been replaced by the parallel implementation.
- Bug with
to_float
function. Now, it really rounds to the closest less or equal float number. - Wrong index type used in the database causing some queries to take too much time.
- A possibility to get an Ethereum tx hash for withdrawal operation.
- Support for non-standard Ethereum signatures.
- Robustness of the fee ticker's API interacting module was increased.
- Blocks that contain withdraw operations are sealed faster.
eth_sender
module now can be disabled.- Transfer to zero address (0x00..00) is now forbidden in zkSync.
- WebSocket server now uses more threads for handling incoming requests.
- Bug with delay between receiving a job and starting sending heartbeats.