Since the launch of Hyperledger FireFly 1.1 in October, the community has been hard at work on a number of improvements, and today we’re pleased to announce that version 1.2 is now available. In version 1.2, we’ve introduced a number of changes focused on the user, making it easier and faster than ever to make and run your web3 applications at scale.
Token API Enhancements
We’ve added support for a much wider variety of ERC-20, ERC-721, and ERC-1155 contracts.
OpenZepplin Wizard Support: Hyperledger FireFly’s token APIs now work for variations of ERC-20, ERC721, and ERC-1155 contracts generated by the OpenZepplin Contract Wizard. The older sample token contracts ERC20NoData and ERC721NoData contracts have been deprecated.
Additional controls and feedback make the Hyperledger FireFly experience even more powerful.
Error Feedback: Custom smart contract error types are now returned on the API.
Data Management: Data objects and blob rows may be removed from the FireFly database and Data Exchange microservice. This can be very useful if your organization has data retention requirements for sensitive, private data and needs to purge data after a certain period of time.
Dynamic Reload of Core Config File: You can now edit the configuration file and have FireFly automatically reload it, without having to restart the whole service.
Distributed Request Tracking: The X-FireFly-Request-ID HTTP header is now passed through to FireFly dependency microservices to allow for distributed request tracking through various systems.
Custom HTTP Header Passthrough: Custom HTTP headers can be passed through to FireFly dependency microservices.
Evmconnect is now the default blockchain connector for Ethereum-based FireFly stacks. Differences compared with Ethconnect include:
Policy Management Engine: Engine for gas cost estimation and automatic transaction resubmission
Signing and Nonce Management: Compatibility with public blockchains
The Next-gen Platform
Hyperledger FireFly 1.2 is another step toward bringing the enterprise closer to realizing the full potential of web3—both with permissioned chains and connections to public ecosystems. It’s designed to make application development easier and faster to deploy.