Summary
This proposal seeks to edit minor parameters in the SWISE bridging contract and the Oracle config contract to allow for a larger volume of SWISE to be bridged to Arbitrum and to finalize the migration of the Oracle environment for P2P.org, one of the StakeWise Oracles.
Motivation
In this proposal, we bundle two minor edits in the contracts responsible for auxiliary services that support the workings of the StakeWise protocol.
The first proposed edit is related to the multichain capabilities of SWISE. The recently deployed Wormhole solution for allowing osETH to be easily bridged across various L2 networks has also been pre-emptively applied to SWISE to enable its expansion to Arbitrum and other L2s over time.
The initial deployment carried out by the team has set a low ceiling for the total amount of SWISE that can be bridged (10,000 SWISE). The deployment has assigned the StakeWise DAO as the owner of the contracts (a standard procedure), meaning that any change in the current config must now be approved by the DAO.
The team is proposing that the upper boundry for the total amount of SWISE that can be bridged is increased from 10,000 SWISE to 100,000,000 SWISE, to allow more adoption of SWISE on L2s. Without this change, bridging meaningful sums from mainnet to Arbitrum (and other L2s) in SWISE tokens will not be possible. This proposal seeks to set a sufficiently high limit to ensure that enough SWISE can circulate outside of mainnet.
The second proposed edit is related to the Oracle configuration. One of the StakeWise Oracles, P2P.org is looking to move the Oracle endpoints to new domain names - a change related to the team’s operational decisions. Changing the Oracle endpoint has no effect on the workings of the Oracle, and does not impact anything in the StakeWise protocol. However, it still requires a DAO vote, because all the StakeWise Oracle endpoints are saved in the Oracles Config smart contract. This is security measure aimed at codifying the participants of the StakeWise Oracles set, allowing other smart contracts that rely on the Oracles’ responses to know who to listen to.
Upon request from the P2P.org team, we are proposing that the endpoints for the P2P Oracle are changed to:
- v3-oracle-mainnet-1.el.p2p.world
- v3-oracle-mainnet-2.el.p2p.world
Specification
The following .json is used to introduce the changes:
[
{
"to": "0xE3620C1aE560AF090704899aCA62209C31C4c77b",
"operation": "0",
"value": "0.0",
"data": "0x1901717500000000000000000000000000000000000000000052b7d2dcc80cd2e4000000",
"method": "setOutboundLimit(uint256)",
"params": ["100000000000000000000000000"]
},
{
"to": "0x6B5815467da09DaA7DC83Db21c9239d98Bb487b5",
"operation": "0",
"value": "0.0",
"data": "0x8a76984d0000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000002e516d58334878335554424341793446546965745565536244394e506a546e5477427a4d78506450654a6779524a46000000000000000000000000000000000000",
"method": "updateConfig(string)",
"params": ["QmX3Hx3UTBCAy4FTietUeSbD9NPjTnTwBzMxPdPeJgyRJF"]
}
]
Considerations
This is a relatively straight-forward change that does not have any major impact on the StakeWise operations.
Discussion
Please vote for or against the proposal in the Snapshot: Snapshot