Table of contents
IDs are generated as UUID V4 globally unique identifiers
Times are serialized to JSON on the API in RFC 3339 / ISO 8601 nanosecond UTC time
Times are persisted as a nanosecond resolution timestamps in the database.
On input, and in queries, times can be parsed from RFC3339, or unix timestamps (second, millisecond or nanosecond resolution).
Large integers of up to 256bits in size are common in blockchain, and handled in FireFly.
In JSON output payloads in FireFly, including events, they are serialized as strings (with base 10).
On input you can provide JSON string (string with an
0x prefix are
parsed at base 16), or a JSON number.
Be careful when using JSON numbers, that the largest number that is safe to transfer using a JSON number is 2^53 - 1.
Any JSON type. An
FireFly stores object data with the same field order as was provided on the input, but with any whitespace removed.
Any JSON Object. Must be an object, rather than an array or a simple type.