LEASH v2 – Community Update: Vote Extension, Exchange Outreach, and Build Progress
The attacker (or former dev) keeps triggering rebases to make a point. From what it looks like, those who did vote favored Snapshot + Burn-to-Mint — so those attempts won’t work against the direction the community is choosing.
1) DAO vote: turnout + 24h extension
The first vote completed with lower turnout than expected. A few real factors likely contributed:
- Many holders keep LEASH on exchanges (can’t vote easily)
- Attention overload in the current crypto cycle
- Not localized into enough languages
- Our blog translator widget broke (we’re fixing it)
What’s new: we’ve created a new proposal with a 24-hour extension so you don’t need to bridge out of Shibarium or unstake veLeash to participate.
🔗 Vote here:
Note on veLeash: we’ve removed the penalty for withdrawing LEASH from veLeash, and it will remain removed until this issue is resolved.
2) Exchange outreach (critical path)
We’ve begun direct outreach to exchanges. Due to different timezones this is a slow process. If venues cooperate, migration can be seamless for their users (no action required). We’ll meet them and present all options. If a venue doesn’t cooperate, users can still withdraw and claim via the public portal.
3) Development update
Dev work for LEASH v2 has started. More technical details will follow after internal reviews.
4) Auditor selection
We’re in conversations with multiple independent auditors. Once we shortlist, we’ll share names and scope for community input. If you have strong references (with contacts), please ping us.
5) Advisor track
We’re also consulting with advisors on features and architecture to future-proof LEASH v2. Can’t say much yet — but think Zama.
If anything concrete comes out of these discussions, NO unilateral decisions will be made. We’ll publish a Design RFC with side-by-side options (pros/cons, security implications, complexity), feedback window, incorporate input, and then bring the final choices to the DAO for a binding vote. Before mainnet changes, we’ll run a public testnet, open a bug bounty, and complete independent audits. Otherwise we will stick to tried and tested simple ERC20 contract.
Closing
Thanks for the feedback and patience. We’ve extended the vote so more of you can be counted, we’re engaging exchanges, building, lining up auditors, and sharpening the design with advisors. Onward.