Bridge v1.2.0 - Cross-Chain Token Bridge with Enhanced Ledger System

🚀 Bridge v1.2.0 - Cross-Chain Token Bridge with Enhanced Ledger System

Overview

This release introduces a comprehensive cross-chain token bridge between Junction and Sepolia testnet, featuring an advanced ledger system for tracking cross-chain token movements.

✨ Key Features

🔒 Lock & Unlock Mechanism

• Lock Tokens: Secure token locking on Cosmos chain with EVM address mapping
• Unlock Tokens: Authorized token unlocking with governance-controlled permissions
• Cross-Chain Ledger: Complete audit trail of all token movements

🏛️ Governance Integration

• Parameter-Based Authorization: Whitelist system controlled by governance
• Authority Management: Only authorized addresses can unlock tokens
• Transparent Updates: All permission changes are voted on by the community

📊 Enhanced Ledger System

• Cross-Chain Records: Track cosmos address, EVM address, and amounts
• Event Tracking: Complete history of lock/unlock events
• Status Management: Real-time tracking of token lock status
• Immutable Records: All data stored on-chain for transparency

🔧 Technical Improvements

• Cosmos SDK v0.50.9: Latest stable version compatibility
• Ignite CLI v28.6.0: Modern development tooling
• Go 1.25.1: Latest Go version support
• Comprehensive Testing: Full test coverage for all bridge operations

🛠️ Technical Specifications

Component	Version
Cosmos SDK	v0.50.9
Ignite CLI	v28.6.0
Go Version	1.25.1
Bridge Version	v1.2.0

🔐 Security Features

• Address Validation: Comprehensive EVM and Cosmos address validation
• Balance Verification: Multi-layer balance checking
• Authorization Checks: Governance-controlled permission system
• Event Emission: Complete audit trail for all operations

📈 What's New

• ✅ Cross-chain ledger database implementation
• ✅ Governance-controlled authorization system
• ✅ Enhanced event tracking and emission
• ✅ Comprehensive address mapping system
• ✅ Improved error handling and validation
• ✅ Complete audit trail for all operations

🚀 Getting Started

1. Deploy the bridge module on your Cosmos chain
2. Configure governance parameters for authorized unlockers
3. Start locking tokens to bridge to EVM chains
4. Use authorized addresses to unlock tokens when needed

---

Built with ❤️ by the ComputerKeeda

v0.2.0

Release v0.2.0 - Trackgate Module & External Sequencer Integration

Highlights

We are excited to announce the release of version v0.2.0 of the Junction project! This version brings a major feature upgrade introducing the Trackgate Module, enabling the Junction chain to accommodate interactions with different external sequencers. We have also included several key enhancements and optimizations across various parts of the system.

Key Features

1. Trackgate Module: Introduced a new module, Trackgate, to enable the Junction chain to interface seamlessly with external sequencers. This module includes:
   • Schema engagements for external sequencer interactions.
   • Extensions for supporting various external track stations.
2. External Track Station Management:
   • Added support for listing, retrieving, and managing external track stations using new gRPC methods.
   • Added protobuf definitions to support serialization and deserialization of external sequencer data.

Enhancements

• Upgrade Handler: Added upgrade handler logic for jip-2 and included necessary features to handle the store loader during software upgrades.
• Schema Versioning: Added version tracking mechanisms for schema creation to support multiple schema versions and their evolution.
• Improved Storage Efficiency:
  • Reduced GetFileDescriptorsProto size in query p.p.op by reducing the gzip size from 1541 bytes to 1318 bytes.
  • Removed redundant data entries and unused fields to reduce storage and enhance overall system performance.

Bug Fixes

• Fixed Redundant Track Removal:
  • Removed unused fields, including Track from QueryRetrieveSchemaKey, reducing serialization overhead and improving efficiency.
• Station SchemaKey Fix:
  • Corrected the issue of missing StationSchemaKey in ExitTrackStations protocol buffers, ensuring consistent updates during external sequencer changes.

Breaking Changes

• Removed MsgSchemaEngage.schemaKey:
  • Removed the schemaKey field from MsgSchemaEngage struct, simplifying schema definitions and enhancing maintainability.
• Migration Changes:
  • Deprecated the TrackSchema engagement protocols in favor of new, modular methods that improve flexibility.

Detailed Changes

• Add Schema Creation and Engagement Functionalities:
  • Added the ability to create and manage multiple track engagements for external sequencers.
  • Implemented functionality for schema creation and validation during the proposal submission process.
• Refactored and Optimized Protobuf Messages:
  • Updated the ExtTrackSchema protobuf messages, making them compatible with the new Trackgate module and adding support for interactions with external track stations.
• CLI Updates:
  • Added new commands to create, list, and manage external track stations and schema engagements.

Improvements to Developer Experience

• Reduced Complexity in Migration:
  • Migration steps related to trackgate were made simpler, with updated binding protocols for message validation and schema management.
• Code Clean-up:
  • Removed outdated comments and redundant code sections to enhance readability.

How to Upgrade

1. Prepare for the Software Upgrade: Make sure all nodes are synced to the correct block height and have access to the required binaries.

2. Use the subsequent suitable binary: To initiate the synchronization process, begin with the earliest binary version available. Proceed by synchronizing it with the instance where this particular binary was last utilized. Subsequently, replace the existing binary with the subsequent version in the chronological sequence until your node achieves complete synchronization with the current chain states.

3. Trackgate Module Activation:

   • After the upgrade, use the CLI commands to initiate trackgate and external sequencer engagements.

Contributors

We want to thank everyone who contributed to this release. Your hard work and dedication have helped us reach this significant milestone!

What's Changed

• Add upgrade handler for "jip-2" and handle store upgrades by @ComputerKeeda in #2

Full Changelog: https://github.com/ComputerKeeda/junction/commits/v0.2.0

v0.1.0

Junction v0.1.0 Testnet Release Note

We are pleased to announce the release of Junction v0.1.0 on our testnet. This update marks a significant enhancement in our platform, leveraging the latest technologies to deliver improved functionality and reliability. Here are the key highlights:

Highlights

• Upgraded to Cosmos SDK v0.50.3: Ensuring a more stable and efficient foundation for our network.
• Implemented VRF for Decentralized Tracks: Introducing verifiable randomness to enhance fairness and security in track management.
• Enhancements to Active Stations: Simplified processes for adding and removing tracks from active stations, alongside implementing track membership verification for greater transparency.

We are committed to continuous improvement and eagerly anticipate your feedback on this release. Thank you for being part of our journey towards a more decentralized future.

Airchains Team 💜

Full Changelog: v0.0.1...v0.1.0

v0.0.1

done