update: separated plug from gaugedUniERC20 #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
MultiGaugeUniERC20
,ConnectionPlug
&MultiGauge
MultiGaugeUniERC20
uniTransfer
: Instead of calling Socket outbound directly, MultiGaugeERC20 calls a specificConnectionPlug
contract which is connected to a specific switchboard.uniReceive
called by respectiveConnectionPlug
to mint tokens instead of Socket directlyConnectionPlug
MultiGaugeUniERC20
calls connection plug to send burn message to destinationChain via configured outboundSwitchboardreceiveInbound
to mint tokens on destinationChain via configured inboundSwitchboardMultiGauge
mapping(uint32 => Limits) public bridgeLimits
tomapping(address => Limits) public bridgeLimits
_siblingChainSlug
to_bridgeType
for all methods