You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User Story
As a Protocol Dev, I want to interact with the Gateway contract on Lisk blockchain and use its supported stablecoins (bridge USDC) for swaps and transactions, with gas fees sponsored by a paymaster. Bridge to Lisk
Lisk bridge USDC token router scan
Acceptance Criteria
GIVEN Given that Gateway contract is deployed to Lisk Blockchain WHEN bridge USDC is supported THEN Then the aggregator and anyone should be able to create order
GIVEN Given that Gateway contract is deployed to Lisk Blockchain WHEN All configurations have been made, THEN The ownership should be transfer to the main address
GIVEN Given that Gateway contract is deployed to Lisk Blockchain WHEN Fee are configured, THEN It should use the same fees on other chains
GIVEN Given that Gateway contract is deployed to Lisk Blockchain WHEN Deployment is done THEN The Gateway contract should be verified
Tech Details
Add Lisk as a supported network in the system.
Update hardhat.config to support Lisk network
Notes/Assumptions
Lisk is an EVM-based chain
Open Questions
Does Shield3 support Lisk?
Do we require an API for verification?
The text was updated successfully, but these errors were encountered:
User Story
As a Protocol Dev, I want to interact with the Gateway contract on Lisk blockchain and use its supported stablecoins (bridge USDC) for swaps and transactions, with gas fees sponsored by a paymaster.
Bridge to Lisk
Lisk bridge USDC token
router scan
Acceptance Criteria
GIVEN Given that Gateway contract is deployed to Lisk Blockchain
WHEN bridge USDC is supported
THEN Then the aggregator and anyone should be able to create order
GIVEN Given that Gateway contract is deployed to Lisk Blockchain
WHEN All configurations have been made,
THEN The ownership should be transfer to the main address
GIVEN Given that Gateway contract is deployed to Lisk Blockchain
WHEN Fee are configured,
THEN It should use the same fees on other chains
GIVEN Given that Gateway contract is deployed to Lisk Blockchain
WHEN Deployment is done
THEN The Gateway contract should be verified
Tech Details
Notes/Assumptions
Open Questions
The text was updated successfully, but these errors were encountered: