Skip to content
This repository has been archived by the owner on Jul 27, 2022. It is now read-only.

Problem: incorrect fee estimation #1001

Closed
leejw51crypto opened this issue Feb 5, 2020 · 3 comments
Closed

Problem: incorrect fee estimation #1001

leejw51crypto opened this issue Feb 5, 2020 · 3 comments
Assignees
Milestone

Comments

@leejw51crypto
Copy link
Collaborator

with this config
"initial_fee_policy": {
"base_fee": "1.1",
"per_byte_fee": "1.25"
},
"withdrawal from unbonded" doesn't working

  1. don't use mocking, use tx-query directly to get encryption size
    or
  2. use some deterministic method not using tx-query
@tomtau
Copy link
Contributor

tomtau commented Feb 6, 2020

@leejw51crypto no. 2 solution.

can you post steps to reproduce? that configuration you posted is the same as https://github.com/crypto-com/chain/blob/master/integration-tests/with_fee_cluster.json#L21 and the existing tests (should) execute withdrawal and seem to succeed

@tomtau
Copy link
Contributor

tomtau commented Feb 6, 2020

to-be-confirmed: it may be due to this "hack" https://github.com/crypto-com/chain/blob/master/chain-tx-enclave/tx-validation/app/src/server/mod.rs#L172

should disappear after this is resolved: #866

@tomtau
Copy link
Contributor

tomtau commented Feb 24, 2020

possibly fixed with #1118

@tomtau tomtau closed this as completed Feb 24, 2020
@tomtau tomtau added this to the CRO Sprint 24 milestone Feb 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants