v1.1.1 Contract Deployment Fee Discount

This release represents the first major protocol upgrade since the Istanbul upgrade, encompassing four key enhancements:

1. Architectural optimization: The system architecture has been comprehensively refactored to improve modularity, clarify module dependencies, enhance component replaceability, and streamline protocol registration—thereby establishing a robust technical foundation for the ecosystem’s Layer-3 sidechain (L3 Chain).

2. Enhanced smart contract functionality: Contracts now support reading transaction messages and data blobs (Tx Message/Blob), enabling interoperable cross-chain bridging and allowing Layer-2 wallets to natively annotate and track payments.

3. Dynamic protocol fee mechanism: A time-sensitive fee discount has been introduced during off-peak network periods. Specifically, a 1 MB fee reduction is allocated every 1,000 blocks, with the discounted rate capped at a minimum of 0.1% of the base fee. This mechanism is designed to be further refined via on-chain consensus governance in future iterations.

4. Integration of Fitsh toolchain: The native smart contract language Fitsh—developed specifically for Hacash—along with its compiler (fitshc) and official download resources, has been officially incorporated into the release.

[Important Notes]

Note 1: Due to structural modifications to the underlying database schema, users must delete the existing local data directory and perform a full blockchain resynchronization. Importantly, the canonical block data remains unaltered; only the local storage format has changed.

Note 2: The configuration file hacash.config.ini has undergone schema updates—including revised field names and reorganized sections. Users are required to replace their current configuration file with the new version provided in the release package and customize relevant parameters accordingly. While most configuration syntax remains backward-compatible, several fields have been renamed or logically regrouped for clarity and maintainability.

Note 3: The P2P networking layer has been substantially redesigned. Certain protocol messages are no longer backward-compatible with prior versions. All full node operators are strongly advised to upgrade immediately. Failure to do so may result in network partitioning, with legacy mining nodes producing orphaned blocks on a divergent chain—leading to wasted computational effort and reduced network security.