Release notes for StarkGate v2.0.1
New Features
- Permissionless Bridging - In StarkGate v2.0.1 any user can add any ERC-20 token to StarkGate using the
enrollTokenBridge
function. - Deposit with Message - This feature let's the user add an arbitrary message to a deposit. The receiving contract must implement the
on_receive
callback to process the message. It allows enhanced and flexible processing of fund transfers.
New Components
- StarkGate Registry - a central contract in which all bridged tokens are registered, both tokens permissionlessly enrolled, and legacy bridged tokens.
- StarkGate Manager - Manages the registry and token bridging actions (enroll etc.).
What's Changed
- Migrated codebase from Cairo0 to Cairo.
initiate_withdraw
was renamed toinitiate_token_withdraw
. (initiate_withdraw
remains for backward compatibility).- Added token as a new field in
deposit
andwithdraw
API. Old format remains for backward compatibility in upgraded bridges. - Fees: a minimum fee is enforced in deposit and enroll transactions. User can use
estimateDepositFeeWei
andestimateEnrollmentFeeWei
to gauge the right fee value. - Withdrawal Limit - When enabled on a particular token, withdrawals of that token are limited to a daily cap.
This feature is a security measure that may be applied in extreme cases. See appropriate documentation for more information on this.
For more details, check out StarkGate's documentation here.
Full Changelog: https://github.com/starknet-io/starkgate-contracts/commits/v2.0.1