Log Message (Logging Content)

Catenis allows any message, containing any type of digital content at any size to be logged to the Bitcoin blockchain. You are never limited to a simple text string, you can log a PDF, word document, a movie, music or send it any data your project needs to log and secure via the blockchain. With automated intelligence Catenis does the hard work, by handling the data, encrypting the content, producing read receipts and placing the data in decentralized storage. It also transparently takes care of the bitcoin transaction and fees needed to use the underlying blockchain. This is all done in real-time.

Logging Off-chain Message

Catenis defaults to logging messages via its second layer capabilities. This is called off-chain message logging and leverages its robust peer-to-peer network without encumbering bitcoin’s transactional network. All off-chain messages are logged to the Bitcoin blockchain via Catenis’ eventual blockchain logging technology. Eventual blockchain logging aggregates all messages and logs them in aggregate using only one bitcoin transaction. This Allows Catenis to handle millions of messages while leveraging the Bitcoin Blockchain as a control-plane. Giving you the ability to deliver messages in real-time and the capability to cryptographically verify all messages via the blockchain for proof of occurrence, existence, authenticity, and auditing. For more information see section titles “off-chain messages and aggregation”.

Logging Standard Message

Alternatively, our customers can use Catenis’ standard message logging capabilities (standard messages carry additional fees). These logged messages correlate one-to-one with a bitcoin transaction and for every logged message a bitcoin blockchain entry is made. It also leverages the bitcoin peer-to-peer network and is intrinsically linked to real-time bitcoin transaction broadcast.

Catenis allows any message, containing any type of digital content and any size to be logged onto the Bitcoin blockchain. However, the Bitcoin Blockchain has a limited logging storage capability of 80 bytes. Message < 75 characters (75 bytes) will be stored directly into a Bitcoin transaction on the blockchain. Catenis can also log large data payload (documents, movies, CAD files, music, etc.) onto the blockchain via a cryptographic hash and store its content in an external storage location. Catenis defaults all of its large payload storage to IPFS (Interplanetary File System).

Intelligent message logging technology allows a Catenis device to dynamically determine if content should be stored directly in a Bitcoin transaction or if a hash of the content should instead be inserted and it’s content stored on IPFS. Larger messages (above 75 bytes) that are beyond the size of a single Bitcoin transaction’s capability to store content are intelligently cryptographically hashed for blockchain inclusion. Catenis will, therefore, insert the message’s hash reference in a Bitcoin transaction and place the information content on IPFS. Allowing the log message API method to log and inscribe (cryptographically locking) a message of any size. When the API method is instructed to encrypt the message, the result is not only a cryptographically locked and inscribed payload but the message is also encrypted with military-grade security.

Note: 5 bytes on the transactions null data output is always reserved for system transaction identification. The prefix “CTN” is always added

Catenis handles all of the difficult interactions with the Bitcoin protocol, blockchain, IPFS, encryption, creating transactions, paying fees, etc. making it easy to build applications. Catenis performs the following process when the message content is larger than 75 bytes and the log message API method is used:

Process of logging a message

  1. Encrypts the message content with dynamically generated Bitcoin private/public key pair (default and optional)
  2. Stores the encrypted message content onto IPFS
  3. Creates a Bitcoin transaction
    1. Adds the message’s hash returned by IPFS to the transaction’s “null data output” (where arbitrary data is stored on a Bitcoin transaction)
    2. Pays the proper Bitcoin network fees for the transaction
  4. Transmits the transaction to the Bitcoin peer network
    Returns a message ID and IPFS hash pointer of the content to the end-user

When logged messages are 75 bytes or smaller these messages are placed directly into a Bitcoin transaction and the IPFS storage procedure is skipped.

Note: The IPFS hash of the Message Content placed in the bitcoin transactions is base 56 encoded

Note: Messages above 11MB in length need to use Catenis Large message chunking capabilities. See Large Message handling here:

For detailed specifications on the Logging API and associated method see the latest release of the Catenis developer documentation here:

Related Articles

How can we make things Better for you?
  • Accepted file types: jpg, gif, png, pdf.
  • This field is for validation purposes and should be left unchanged.