Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • crown-core crown-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 75
    • Issues 75
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Crown
  • crown-corecrown-core
  • Issues
  • #363

Closed
Open
Created Mar 01, 2020 by Mark Brooker@walkjiveflyMaintainer

Inconsistent nftoken registration fee

Summary

The fee rate and total fee for an nftoken register operation are inconsistent

Steps to reproduce

Issue a bunch of tokens for the same protocol, from the same wallet

Expected behavior

nftoken register fee rate should probably be consistent

Problematic behavior

Fee rate varies slightly for unknown reason(s)

Crown-core environment info

Ubuntu 16.04

Crown-core application info

(The wallet version, like v0.13.4.0; link to the pipeline/build if possible.)

Relevant logs, dumps and/or screenshots

mark@x230:~/.crowntest/testnet3$ tcrowncli nftoken register marbles 02 tCRWPpEZVu93MVGYS9FqEjV9XAW9sgKz3MMTp 0 metadata2
c52e7f5ae553ac464fe5b88b782c8848804cc333053891edbf9001f79ff365b6
mark@x230:~/.crowntest/testnet3$ tcrowncli nftoken register marbles 03 tCRWPpEZVu93MVGYS9FqEjV9XAW9sgKz3MMTp 0 metadata2
259517cef1584ad4e707c9160c1cb28b23b15abff84bbe4515f8b930a86750fb
mark@x230:~/.crowntest/testnet3$ tcrowncli nftoken register marbles 04 tCRWPpEZVu93MVGYS9FqEjV9XAW9sgKz3MMTp 0 metadata2
943ba6be615d5590030c9d8a586cf726e0dce5e2c18b44b19532a0e173d83c59

put these txns in mempool with slightly different fee rates and total fee image

All 3 transactions used a single UTXO input with a single UTXO output and identical size extra payload.

Drop full logs & dumps here: https://nextcloud.crownplatform.com/index.php/s/Q6H8enXNmJsQYCD

Possible fixes

(Any comments on what you think might be responsible for the problem, if you have particular insight.)

/cc @artem

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking