Association
Create an association between account. An association can represent any kind of relationship. The meaning is defined by the association type.
JSON
id
andheight
should be omitted when broadcasting. These fields are set by the node.subject
is optional.Binary strings are base58 encoded.
timestamp
andexpires
is in microseconds since epoch.fee
includes 8 digits, soLTO * 10^8
Associations that are recently expired may still be returned by the node. The public node will use the time of the last mined block to determine if an association is expired or not.
Association identifier
An association is identified by the sender, recipient, association type, and subject. With this information, the association can be revoked.
Submitting a new association transaction with the same sender, recipient, association type, and subject will overwrite the expiry date and data.
Since the subject is part of the identifier, it's not possible to change the subject of an existing association.
Data entries
Since version 4, association transactions can have data entries. These are similar to those of the data transaction.
Binary schema
The binary data structure of the unsigned transaction.
Version 4 of the anchor transaction is part of the Titanium release.
If the association doesn't expire, the expiry timestamp in the binary data must be zero.
Network id can be obtained by taking the 2nd byte from the sender address.
Each key type has a numeric id in addition to the reference from the JSON.
Integers (short, int, long) have a big endian byte order.
The encoding of a data entry depends on the type. For more information see "Binary schema of data entries".
Last updated