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

0.6.11

Changes

• Added types for linked_actions on v1/chain/get_account results. ed691d1
• Added support for v1/chain/get_producer_schedule. 1a5295f
• Added support for v1/chain/get_accounts_by_authorizers. b85448b
• Added support for v1/chain/get_activated_protocol_features. 4b5782a

PRs

• Merge get_producer_schedule into new APIs branch by @aaroncox in #58
• Updated README and added bug-report unit test by @aaroncox in #64
• Add support for additional API endpoints by @aaroncox in #59

Full Changelog: 0.6.10...0.6.11

0.6.10

What's Changed

• Add ignoreInvalidUTF8 to decoder by @aaroncox in #54

Full Changelog: 0.6.9...0.6.10

0.6.8

Full Changelog: 0.6.7...0.6.8

0.6.4

• Modified AccountObject returned from v1.chain.get_account call to make total_resources optional.
• Exporting ChainAPI and HistoryAPI helpers.

Full Changelog: 0.6.3...0.6.4

New Transaction APIs & Bug Fixes - v0.6.3

What's Changed

• Adding features from Antelope v3.1 by @aaroncox in #29
• PrivateKey generation fixes by @jnordberg in #31

APIClient

Support for the following API endpoints are included in this newest release.

compute_transaction

Accepts a Transaction type object, submits it to the defined API server, and returns a response which can be used to estimate network resource costs.

await client.v1.chain.compute_transaction(transaction)

Documentation | Implementation

get_transaction_status

Accepts a Checksum256 (Transaction ID) type parameter and returns the status of the transaction.

await client.v1.chain.get_transaction_status(transaction_id)

Documentation | Implementation

send_transaction2

Accepts a SignedTransaction type object and submits it to the defined API server.

Defaults

Utilizes the new /v1/chain/send_transaction2 API endpoint to submit a transaction.

await client.v1.chain.send_transaction2(signedTransaction)

Return Failure Traces

Enable or disable the return of failure traces. Defaults to a value of true, even if not specified. Set to false to disable.

await client.v1.chain.send_transaction2(signedTransaction, {
    return_failure_trace: true,
})

Transaction Retry

Allows a transaction to be retried for a number of blocks (0.5 seconds per block). Using this feature will await the specified number of blocks to ensure the transaction makes it on to the network.

await client.v1.chain.send_transaction2(signedTransaction, {
    // Enable Retry
    retry_trx: true,
    // Number of blocks to retry
    retry_trx_num_blocks: 10, 
})

Documentation | Implementation

Full Changelog

0.6.2...0.6.3