While StarkGate is referred to as a bridge, technically, each supported token has its own bridge, each of which is defined in a corresponding pair of L1 and L2 contracts, as described in Components of a bridge for an individual token.
StarkGate 2.0 provides a contract that enables seamless backward compatibility with the previous version of StarkGate.
When you update the code in your contract, make sure that you use the most up-to-date versions of all StarkGate contracts.
You can check if a token is currently supported with the L1 function
You can permissionlessly add support for ERC-20 tokens to the multi-token bridge using the
StarkGate includes the following administration components:
- The StarkGate Manager
is responsible for adding bridges
- The StarkGate Registry
contains the addresses to all supported bridges
enables a bridge developer to stop servicing an existing bridge
By default, StarkGate imposes no limit on withdrawals. However, in order to mitigate risks associated with critical vulnerabilities that could result in the loss of user funds, StarkGate can enable a withdrawal limit.
If a serious security issue arises, the security agent in the StarkGate contract can limit withdrawals to 5% of the Total Value Locked (TVL) per day for any affected token by calling the
setWithdrawLimitPCT() function in the
WithdrawalLimit.sol contract. A dedicated team can then investigate and resolve the issue.
Only a security admin quorum can disable the withdrawal limit. The quorum will consist of Starknet Foundation members, Starknet ecosystem contributors, and StarkWare representatives. This diverse group will ensure that decisions reflect the Starknet community’s broad interests.
This approach, blending manual oversight with automated detection, aims to minimize potential losses.