BugTrack - zoobc/zoobc-core GitHub Wiki

ZooBC Bug Tracking

This section tracks main resolved bugs and new features implemented, by week:

  • 3 Aug - 7 Aug 2020

    • Bug: node seed not acquired by node during setup: node seed is not acquired during node setup phase due to early initialization of nodeConfigurationService This leads to all nodes trying to register their address by using an incorrect public key (the one from nodeSeed = "") and failing to do so (because there is no such public key in node registry and only registered nodes can add their addresses to db)
    • Bug: Blocksmith Balance Not Updating: Current experimental branch node owner is not gaining new coin, their balance on account_balance table is updated with new version (height), but the balance remain the same. This is cause by wrong CoinBaseTime value set, and from genesis time, the time as long past, causing no coinbase being produced.
    • Bug: cli monitoring not showing data properly some case when showing monitored data on the command line not showing data properly
    • Bug: New Node Can't Get Valid Proof Of Ownership In Experimental Network: On experimental network, we can't get a proper proof of ownership for node registration demo
    • Bug: Snapshot Download Doesn't Try another Peer: node stop downloading snapshot chunks just after one chunk fail from one peer without trying from another peer
    • Bug: Account Dataset Body still use old Version: Account dataset transaction body still use the old one version. maybe when resolving conflict someone chooses the old one. this issued bug on removing account dataset
    • Bug: HTTPS without nginx: https is not working after merging the proxy with rpc handler. This is because we are binding the tls to the grpcserver instead of the httpServer (wrapper) someone chooses the old one. this issued bug on removing account dataset
    • Enhance: import wallet-generated certificate into node configuration/keys: when installing a node, if a certificate (file with .zbc) extension is present in resource folder, then the node will:
      • require user to input the password to decrypt the file (encrypted using AES symmetric encription)
      • unmarshal the json file and:
        • add node owner account address to config.toml (note: in hex format)
        • generate node_keys.json using the node pass phrase in the certificate
    • Bug: Fee Scale UniqueConstraint When ImportSnapshot: A unique constraint error occurred when importing snapshot, this is because we included block_height=0 to the snapshot, and we also generate fee_scale height 0 on genesis created Exclude height = 0 of fee_scale from snapshot data
    • Tech: Open Port Checker: add utility function to check for port if it's open or not, we'll use this later as one of the setup step to notify the user if they are trying to expose a closed port
  • 10 Aug - 14 Aug 2020

    • [BUG] genesis transaction have its own hardcoded timestamp differ from genesis block, this cause the explorer cannot fetch genesis related transaction or accounts correctly.
    • [BUG] mempool selection re-validate the transaction, which is a problem because the transaction type validation involves checking the spendable balance, which already deducted in ApplyUnconfirmed step, this affect account that spend >50% of their funds to be stuck in mempool.
    • [BUG] multisignature participant database unique constraint, this will happen when 2 or more multisig transaction including the multisig_info information got included in the same block height, it'll cause transaction validation success, but pushBlock fail.