We have upgraded our KMS version to version 0.7.2.
In the latest version we have removed issues associated with Zcash.
All minor issues reported have been resolved.
What`s new?
In summary, we added Tezos mainnet and ghostnet to blockchain data, with changes made to the following:
Removed endpoints
Tezos has been added to
As of today, we are now fully supporting the Stellar protocol.
Here is what`s new:
Blockchain Data Get Address Balance
Get Block Details By Block Height
Get Transaction Details By Transaction ID
List Confirmed Tokens Transfers By Address
Get Token Details by Contract Address
Events
New Confirmed Coins Transactions
New Confirmed Tokens Transactions
New Confirmed Coins Transactions And Each Confirmation
New Confirmed Tokens Transactions And Each Confirmation
List Blockchain Events Subscriptions
Get Blockchain Event Subscription Details By Reference ID
Activate Blockchain Event Subscription
Delete Blockchain Event Subscription
Get Address Details From Callback
Get Block Details By Block Height From Callback
Blockchain Tools
Stay tuned for more updates!
We have released two new endpoints for preparing token transfers as part of our Blockchain Tools:
Using these two separate endpoints, customers can prepare transfers for fungible and non-fungible tokens from an address with private and public keys. The address doesn’t have to belong to a wallet. The response will include the transaction fee in Wei.
What else is new:
Technical documentation updates:
We’ve added additional information on the paginated and list based endpoints and we’ve updated the values for API requests.
We've also updated our Key Management System (KMS) on GitHub.
Here is what's new in our latest release:
New endpoint: Prepare Transaction From Address
Through this endpoint customers can prepare a transaction from an address with private and public keys. The address doesn’t have to belong to a wallet. The response will include the transaction fee in Wei. The API is part of Blockchain Tools.
Improvement:
The endpoint Prepare An Account Based Transaction From HD Wallet has been renamed to Prepare A Transaction From an Address in HD Wallet (xPub, yPub, zPub) to more correctly reflect its purpose.
We’ve also updated our Node.js SDK and our Key Management System on GitHub.
Please update your libraries if you’ve used this endpoint.
The Crypto APIs Team
In our latest release we’ve introduced some product updates.
Here is what’s new:
TRON is added as a possible value to the following endpoints:
The endpoint "Freeze Tron Energy Or Bandwidth" has been renamed to "Freeze Tron For Energy Or Bandwidth".
Stay tuned for more product updates and new features.
We’ve updated our open-source Key Management System (KMS) to add support for more blockchains and make some improvements.
We’ve added as possible values Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash to the Prepare A UTXO-Based Transaction From HD Wallet (xPub, yPub, zPub) endpoint that can be used with the KMS.
Ethereum Classic is now supported in the Prepare An Account-Based Transaction From HD Wallet (xPub, yPub, zPub) API.
We’ve also made some small improvements and added a MIT License (MIT) that outlines the permissions of use.
If you’ve already implemented the KMS, you’ll need to upgrade the SDK to the latest version. Check it out on GitHub.
We’ve added two new blockchain-specific endpoints in our Wallet as a Service that can be used to stake and unfreeze TRX for bandwidth or energy on the TRON network. We’ve also made some changes and improvements to existing endpoints. See the details below:
New TRON-specific endpoints:
Improvements to existing endpoints:
Stay tuned with our updates page to be the first one to learn what's new with Crypto APIs!
We have upgraded our existing model for API Requests Credits.
The daily credits available for each plan have been multiplied by 100.
For example, if your current plan previously had 3,000 daily credits they are now 300,000
This is also reflected in the credits charged for each API endpoint.
For example, if a request used to cost 1 credit it is now changed to 100 credits.
The cost for each endpoint is available in the technical documentation.
With this change we are aiming at more flexibility with setting the credits for each API endpoint.
If you have any questions, please reach out to us at [email protected]