Routers
This section contains a full API reference of all public functions & events related to routers and router liquidity management.
Last updated
This section contains a full API reference of all public functions & events related to routers and router liquidity management.
Last updated
Emitted when a new router is added
Name | Type | Description |
---|---|---|
Emitted when an existing router is removed
Name | Type | Description |
---|---|---|
Emitted when the recipient of router is updated
Emitted when the owner of router is proposed
Emitted when the owner of router is accepted
Emitted when a router adds liquidity to the contract
Emitted when a router withdraws liquidity from the contract
Returns the approval status of a router for the given router address.
Returns the recipient for the specified router
The recipient (if set) receives all funds when router liquidity is removed
Returns the router owner if it is set, or the router itself if not
Uses logic function here to handle the case where router owner is not set. Other getters within this interface use explicitly the stored value
Returns the currently proposed router owner
All routers must wait for the delay timeout before accepting a new owner
Returns the currently proposed router owner timestamp
All routers must wait for the delay timeout before accepting a new owner
Gets balance of asset for the specified router.
Used to set router initial properties
Used to remove routers that can transact crosschain
Sets the designated recipient for a router
Router should only be able to set this once otherwise if router key compromised, no problem is solved since attacker could just update recipient
Current owner or router may propose a new router owner
New router owner must accept role, or previous if proposed is 0x0
This is used by anyone to increase a router's available liquidity for a given asset.
The liquidity will be held in the local asset, which is the representation if you are not on the canonical domain, and the canonical asset otherwise.
This is used by any router to increase their available liquidity for a given asset.
The liquidity will be held in the local asset, which is the representation if you are not on the canonical domain, and the canonical asset otherwise.
This is used by any router owner to decrease their available liquidity for a given asset.
This is used by any router to decrease their available liquidity for a given asset.
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|