Example deposit testnet transaction fails on chain: "Fail with error 'qp'" about zksync2-python HOT 7 CLOSED

I'am getting this error too, can anyone help with this?

from zksync2-python.

I'am getting this error too, can anyone help with this?

I think its just broken rn

from zksync2-python.

The 0.5.0 version of SDK has been released and should fix this issue. Here is the example how to deposit assets to zksync.

from zksync2-python.

The 0.5.0 version of SDK has been released and should fix this issue. Here is the example how to deposit assets to zksync.

still same error, Fail with error 'mv'

from zksync2-python.

The 0.5.0 version of SDK has been released and should fix this issue. Here is the example how to deposit assets to zksync.

still same error, Fail with error 'mv'

I successfully ran the deposit example on the Goerli testnet and ZkSync Era testnet without any issues.

L1 transaction: 0x24c3932a7c5aacbe5896007ea0c2ed3e609b43264c4c00e0af42bfb8b6518025
L2 transaction: 0x9b2a1c76786f50383d66e155ff1321968ef734ad25d87dfb818ded31b9a0d247

The mv error code in smart contract indicates that specified transaction value is lower than deposit transaction fee (tx value < base cost + l2Value). The deposit function in sdk follows the same logic, so transaction value is calculated correctly.

The possible issue here is that the base cost might have increased due to the high traffic on the Goerli testnet, which has been ongoing for some time.

I also noticed in the posted example that a custom RPC endpoint is used to submit the deposit transaction. There might be a possibility that, due to high traffic, the custom RPC node experiences latency and is temporarily out of sync. This situation could result in the calculation of an outdated base cost for the transaction.

from zksync2-python.

The 0.5.0 version of SDK has been released and should fix this issue. Here is the example how to deposit assets to zksync.

still same error, Fail with error 'mv'

I successfully ran the deposit example on the Goerli testnet and ZkSync Era testnet without any issues.

L1 transaction: 0x24c3932a7c5aacbe5896007ea0c2ed3e609b43264c4c00e0af42bfb8b6518025 L2 transaction: 0x9b2a1c76786f50383d66e155ff1321968ef734ad25d87dfb818ded31b9a0d247

The mv error code in smart contract indicates that specified transaction value is lower than deposit transaction fee (tx value < base cost + l2Value). The deposit function in sdk follows the same logic, so transaction value is calculated correctly.

The possible issue here is that the base cost might have increased due to the high traffic on the Goerli testnet, which has been ongoing for some time.

I also noticed in the posted example that a custom RPC endpoint is used to submit the deposit transaction. There might be a possibility that, due to high traffic, the custom RPC node experiences latency and is temporarily out of sync. This situation could result in the calculation of an outdated base cost for the transaction.

This is the correct solution

This is the solution your team found, but the solution was not updated to the latest code package. I lost hundreds of dollars using the 0.5.0 version of the package because of this

The solution is in this github link: #10 (comment)

from zksync2-python.

This is fixed in the next release. This is how we are calculating value now.

gas_price_for_estimation: int
        if transaction.max_priority_fee_per_gas is not None:
            gas_price_for_estimation = transaction.max_fee_per_gas
        else:
            gas_price_for_estimation = transaction.gas_price

        base_cost = self.get_base_cost(transaction.l2_gas_limit, transaction.gas_per_pubdata_byte, gas_price_for_estimation)

        if transaction.token.is_eth():
            transaction.value = base_cost + transaction.operator_tip + transaction.amount
        else:
            transaction.value = base_cost + transaction.operator_tip

        check_base_cost(base_cost, transaction.value)

from zksync2-python.