Currently we represent nockma atoms as non-negative integers. There is ambiguity when representing binary data as an integer because multiple integers can be decoded to the same binary.
In the future the Anoma node will have a binary interface (i.e we'll submit transaction candidates as binary data instead of via a textual representation of nockma as we do now).
We should:
Support binary atoms in the nockma backend
Jam (anomaEncode) should return a binary atom and work with binary data
Cue (anomaDecode) should also work with binary atoms
Currently we represent nockma atoms as non-negative integers. There is ambiguity when representing binary data as an integer because multiple integers can be decoded to the same binary.
In the future the Anoma node will have a binary interface (i.e we'll submit transaction candidates as binary data instead of via a textual representation of nockma as we do now).
We should: