₿m Babylon community,
SatLayer Labs values discourse on Babylon governance processes, a reflection of our collective commitment to success. We’re sharing rationale and context to help us all grow together:
- Cube BABY LST contracts were necessary prerequisites for the restaking flow to function. Otherwise the SatLayer core restaking vaults would have no assets to accept, especially as other LSTs were still testing and/or finalizing their canonical bridged assets on Babylon Genesis
- The above text proposal to launch Cube was submitted here on Babylon’s governance forum well ahead of onchain voting, with consistent community support and clear references to our main parameter change proposal to whitelist our deployer address for uploading smart contracts related to our core restaking protocol
- Our understanding at the time based on comms was that a separate on-chain signalling proposal for Cube would not be necessary, as we planned to use the same deployer address for both deployments, so long that the deployer address had been approved and relevant forum discussion had taken place, so we proceeded accordingly
To lead by example, SatLayer Labs will submit signalling proposals for any major new contract deployments or upgrades within our ecosystem (for Cube, core restaking, or future components) to ensure alignment with the latest governance guidelines and further transparency.
This can be a blueprint for how our pioneering ecosystem can best balance speed with consensus. Let’s keep building, faster.
Feel free to share feedback with me directly at any time.
Onwards,
Luke Xie and the SatLayer Labs team