interlockledger/specification

InterlockLedger Specification Documents.

specification's Issues

Proposal: ChainRefTag ChainBlockRefTag

This issue proposes two new tags, one called ChainRefTag and the other ChainBlockRefTag.

The ChainRefTag would use the reserved explicit tag ID 26 and have the same format of the StringTag. The payload would be the textual chain identification with a single character used to define its version.

The ChainBlockRefTag would use the reserved explicit ID 27 and will be a tag sequence with 2 tags, a ChainRefTag followed by a ILIntTag that represents the block ID.

If approved, those tags could be used to represent those two values in a more standard way.

Proposal: TimestampTag

This issue is proposing a new implicit tag called TimestampTag. It should use the ID 15 and have the same format of the ILIntSigned tag. The interpretation of this tag would be the number of microseconds from 1970-01-01T00:00.000000Z.

Please post your comments about this new tag before we can make it official.

Proposal: Define the concept of extended tag formats

Instead of adding more complex tags into the ILTags standard, it would be a nice idea to define the concept of extended tag formats.

Those extended tag formats are tag formats that are not part of the core standard but have a well defined internal format and purpose. Since they are not part of the standards, they do not have fixed assigned tag IDs but can be freely used by applications, such as IL2 itself and other IL2 based applications.

The tag libraries could than provide the implementation of those tag formats without enforcing any fixed TagID, just like the standard tags are implemented.

This concept has been first tested by go-iltags as a way to make reduce the amount of code required to write IL2 applications. It this concept is approved to be added to the standard, we can start to define names and formats to those tags.