Establish a Community-Run Decentralized Bridge Between GenesisL1 and Base
GenesisL1 proposal #131: Summary This proposal asks the GenesisL1 community to formally signal its agreement to establish and operate a decentralized bridge...
Yes
100%
No
0%
Abstain
0%
Veto
0%
Original Proposal Text
Summary This proposal asks the GenesisL1 community to formally signal its agreement to establish and operate a decentralized bridge connecting GenesisL1 (domain 29) and Base (domain 8453), built on the Hyperlane wL1 warp route. A YES vote signals that the community endorses bringing this bridge into being as a shared, community-owned piece of infrastructure — and that the community understands and accepts its experimental nature and the risks described below. What we are establishing A self-hostable cross-chain message route for the native L1 coin, wrapped as wL1 (ERC-20, 18 decimals) for transfer between chains. Native L1 is locked on GenesisL1, synthetic wL1 is minted on Base, and the reverse path burns on Base and unlocks on GenesisL1. The validator and relayer configurations, deployment scripts, and monitoring are public and reproducible: https://github.com/GenesisL1/genesisl1-base-hyperlane-bridge Decentralized means decentralized This is the core of the proposal. The bridge is not run by any single party, and not by any third party. Specifically: 1. The bridge is secured by a set of independent validators, not by one operator. 2. A cross-chain message is only honored when several validators agree — the security model requires a signing threshold to be met before a transfer is delivered. 3. The validator set itself is administered collectively by those validators, governed through a multisig. No single key, no single company, no external bridge provider controls it. 4. We are going big, and we are going by ourselves — no 3rd-party custodian, no outsourced trust. The current configuration starts with a small validator threshold and is actively seeking additional independent operators. Growing validator diversity is a community responsibility and a precondition for the bridge to be meaningfully decentralized over time. Mandatory: read the disclaimer Every voter, validator, relayer operator, and user must read and understand the DISCLAIMER before voting YES or interacting with the bridge: https://github.com/GenesisL1/genesisl1-base-hyperlane-bridge#%EF%B8%8F-read-this-first--disclaimermd In plain terms: this is open-source, decentralized, experimental software provided "AS-IS" with NO WARRANTY and NO LIABILITY. There are real financial, technical, and smart-contract risks. Bugs, key compromise, relayer failure, chain reorganizations, and total loss of bridged funds are all possible. By running any component or interacting with the bridge, you accept full responsibility for your funds, your infrastructure, and your users. Do not bridge more than you can afford to lose entirely. What a YES vote means 1. The community agrees to establish the GenesisL1 ↔ Base bridge as community-run infrastructure. 2. The community endorses the decentralized, multi-validator, multisig-administered governance model described above. 3. The community has read the DISCLAIMER and accepts the experimental nature and the absence of any warranty or liability. What a NO vote means The community does not wish to establish or endorse this bridge at this time.