It would be helpful to have more specific information included in the motion. How should the implementation of value dependent transaction fees be prioritised relative to other development tasks, such as B&C Exchange?
While it is possible to leave the specifications to be determined later, it would be better to do it now, so that shareholders can understand something about the cost in NuBits and developer distraction to prioritise this.
This will require a new voting mechanism, chunking of outputs (which might be more complex than the way we chunk NSR in blocks of 10,000) as well as new code regarding fees, which is more complex than you might think. Without clear specifications, I would expect this to cost between 10,000 and 20,000 NBT to code, test and deploy.
I would like to add that chunking is something that can only be implmented at the level of the client, not the protocol. This means that we canāt make assumptions about chunking being implemented in clients other than the core one. What about Coinomi? NuDroid? Surely the list will grow beyond our ability to effectively influence as adoption grows. The problem may not be serious enough to not implement this fee structure, but shareholders should at least be aware of it. To illustrate the issue, suppose Electrum supports NuBits and a user is using the Electrum wallet. He transfers 50,000 NBT into his wallet in a single transaction. Next, he spends 100 NBT. Unless Electrum implements chunking, transaction fees will be paid on 50,000 NBT, not 100 NBT.