ConsensusTopicInfo
memo
Short publicly visible memo about the topic. No guarantee of uniqueness.
runningHash
When a topic is created, its running hash is initialized to 48 bytes of binary zeros. For each submitted message, the topic’s running hash is then updated to the output of a particular SHA-384 digest whose input data include the previous running hash. See the TransactionReceipt.proto documentation for an exact description of the data included in the SHA-384 digest used for the update.
sequenceNumber
Sequence number (starting at 1 for the first submitMessage) of messages on the topic.
expirationTime
Effective consensus timestamp at (and after) which submitMessage calls will no longer succeed on the topic and the topic will expire and after AUTORENEW_GRACE_PERIOD be automatically deleted.
ledger_id
bytes
The ledger ID the response was returned from; please see HIP-198 for the network-specific IDs.
Last updated