RottiLunc

Regarding Terra Classic Governance Proposal #12236 We are genuinely struggling to understand the reasoning behind the NO WITH VETO votes on our proposal. Let's clarify a few things. We are simply asking for permission to update our own smart contracts for Juris Protocol and LSF Exchange. These updates are necessary to address security issues, maintain our infrastructure, and migrate our liquidation engine. We are NOT requesting permission to execute arbitrary code on Terra Classic, nor are we asking for Community Pool funding or control over anyone else's contracts. In principle, we strongly believe that Terra Classic should have permissionless smart contract deployments. We do not want a permanently permissioned environment in which developers need governance approval just to maintain their applications. In fact, we supported the introduction of the current temporary restrictions ourselves. We did so because of serious security concerns and specific circumstances that we unfortunately cannot disclose further details about at this time. These restrictions were never intended to become permanent. They are a temporary, responsible precaution while the underlying security issues are being addressed. We stand by that decision. However, responsible security measures should not unnecessarily prevent legitimate builders from maintaining and securing their existing applications. We are simply asking to continue developing and maintaining our own products within the security framework that we ourselves supported. We fully respect the right of every validator to disagree with our proposal. But we would genuinely appreciate understanding what specifically justifies a NO WITH VETO rather than a regular NO vote in this case. We remain committed to building on Terra Classic, improving its DeFi infrastructure, and contributing to a safer, more sustainable ecosystem. 🤝 $JURIS | $LUNC 🔗 validator.info/terra-classic… #TerraClassic #LUNC #JurisProtocol #DeFi