What's the makeup of the transaction object?

Question

If you read "The Anatomy of a Transaction" it seems the transaction ends after the nonce but if you look at the IRI class "transaction.java" I see the following:

buffer.put(Serializer.serialize(validity));
        buffer.put(Serializer.serialize(type));
        buffer.put(Serializer.serialize(arrivalTime));
        buffer.put(Serializer.serialize(height));
        //buffer.put((byte) (confirmed ? 1:0));
        buffer.put((byte) (solid ? 1 : 0));
buffer.put(Serializer.serialize(snapshot));

Have these new fields recently been added to the format and what are they for?

score 3 · Accepted Answer · edited Dec 24 '17 at 11:51

The latest description of the transaction format as it is sent "on the wire" is in this IOTA Stack Exchange question: What is the IOTA transaction data structure?

And the last field is still the nonce (although its size decreased).

The code you are referring to is not the "on the wire" format, but what is serialized in iri's database. This contains a few more "trusted" flags to speed up transaction processing (like whether the transaction is solid, i.e. all its referenced transactions are already known to this node).

What's the makeup of the transaction object?

1 Answers1