0.7.0

Changes (Breaking)

BlockId has been added as a core type representing the hash of a block header and also contains the block number. Previously this library treated these values as Checksum256 types which wasn't entirely correct.

The 0.7.0 update makes changes to accomodate for this, some of which may break reverse compatibility if your application is strictly expecting certain types. Listed below is a summary of these changes.

• The get_block() and get_block_header_state() API methods parameters now expect a BlockId instead of a Checksum256Type.
• The API Client GetBlockResponse from get_block(), GetInfoResponse from get_info(), and GetTransactionStatusResponse from get_transaction_status() calls now return BlockId typed values.
• The P2P Client HandshakeMessage, ChainSizeMessage, NoticeMessage, RequestMessage, and BlockHeader now communicate using BlockId typed values.
• The P2P Client blockNum() method now returns a UInt32 value instead of a number.
• The P2P Client id() method now returns a BlockId value instead of a Checksum256.

For the majority of applications, these changes should not impact your application, as the BlockId implementation is very similar to the Checksum256 implementation. It will however provide applications the ability to work with BlockId values more easily, including extracting the block number from the hash with the .blockNum() method on each instance.

Full Changelog: 0.6.11...0.7.0