Minimum Precision "bug"

[Thanos420NoScope]

The coin contract accepts transactions with more than 12 digits if they are 0s.
It is not a security threat and cannot break precision, but is permanent for both the sending and the receiving account.

[emilypi]

That could be a valid space attack, and I'd consider it a valid bug as a result.

[larskuhtz]

I think, this is a pact issue, since the chainweb-node is agnostic about semantics of payloads.

Resolving this on pact validation level could would probably require a fork. So, we may instead continue accept those numbers internally within pact evaluation (execValidateBlock, but reject pending zeros on input in pact-service (e.g. in the mempool or newBlock).

[chessai]

@jmcardon @edmundnoble is this still an issue? iirc this has been patched, but my recollection is only vague.

[AncientHodler-Demiurg]

Perhaps pact 5.0 is a good way to fix this. However, i dont really see how this could be used as an attaack, because hte moment you are using something with more than 12 decimals, it simply wont work.

The problem lies in how pact interprets decimals.
666.12345678900000 is still interpreted as having 9 decimals due to how the floor function works that does the enforcements. It is still seen as having 9 decimals.

If this is something that can be attacked in any way, it should be changed, but i dont see how an attack could be possible....