MouseT 🫛 I JurisProtocol retweeted
I think a lot of people have a wrong idea about "L2s" meaning on-chain projects like @JurisProtocol & @LUNCSwapfun
They're not competing with $LUNC, but are decentralized protocols built on it
@BumeoCapital is just an Investor & participant in a decentral #TerraClassic network
MouseT 🫛 I JurisProtocol retweeted
🚨🚨🚨
BEWARE!
Misinformation is being spread about a "new chain" to lure delegators into believing that they would be missing out if they delegated with the supposedly "wrong" validators.
This is a classical fearmongering and FOMO scheme.
There is no new chain! And the technical possibilities to spin up a new chain based on an genesis export of the good old one is EXTREMELY limited and nearly impossible.
Redelegate and unfollow from the people that are spreading this kind of misinformation!
LunaClassic Community,
This is a lie, and it's built to scare you. ⚠️
🔹 There is no "new chain." Terra Classic is columbus-5, and it stays columbus-5. Every upgrade happens in place, on the same chain, with the same addresses and history.
🔹 Every validator runs the same chain. No validator is "migrating" and none is being "left behind." There is one network, and every validator in the active set is on it, all public on any explorer.
🔹 Your delegation lives in the chain's state. It carries through every upgrade automatically. You don't sign anything, move anything, or "migrate" anything.
So what is a post like this actually for? It
does two things. It scares delegators into moving their stake to a short list of "safe" validators, picked by the people spreading it. And it sets up holders for anyone who shows up next with a "migration" link to drain their wallets.
Your LUNC is safe exactly where it is. Anyone telling you to move it because of a "new chain" is lying to you. ⚡️
#LUNC #LunaClassic #TerraClassic #USTC #
MouseT 🫛 I JurisProtocol retweeted
Thank you for this fact based explanation 🙏
The first proposal involving @SolidProof_io was rejected because people said it was not following PPJ guidelines.
Now they got a PPJ - what they wanted.
But still they don't want it 🤣
Let's me wonder what the actual reasons were behind voting the first one down 😬
LunaClassic Community,
We've read the No with Veto memo on Proposal #12237, and we want to answer each point openly:
• "No advanced pay" This text vote moves no funds. The 40% only goes out through its own separate spend vote. Before that vote, SolidProof publishes a status note with the scope along hours of their work.
• If the work stops early, the hours actually worked are settled and any unearned part "is returned by the Auditor", back to the community pool.
• Paying 40% upfront is how independent audit firms work. They don't commit 568 hours of senior engineering time on credit. The 60% only comes after the findings are delivered, and that needs another vote too.
• "Conflict of interest" the proposers aren't paid by this audit. Every dollar goes to SolidProof, and the fixes are done by our own developers "at no cost to the community pool".
• "We explained this before" this isn't #12228. The provider, the payment terms and the safeguards were all rebuilt around the veto concerns raised on that proposal.
• "Following governance": this proposal is governance. A text vote comes first, then every payment gets its own vote. The community decides at every step.
Security isn't optional.
Market Module 2.0, USTC staking and v15 shouldn't go live on mainnet without an audit 👇
station.hexxagon.io/proposal…
MouseT 🫛 I JurisProtocol retweeted
MouseT 🫛 I JurisProtocol retweeted
Replying to @Szymansk_ii
Checkout @JurisProtocol and @LUNCSwapfun actively building and contributing to $LUNC and get in touch @Szymansk_ii 🫡
Jurisprotocol.com
MouseT 🫛 I JurisProtocol retweeted
Is there really much hope for $LUNC?
YES
🚨Is there really much hope for $LUNC ?
If I’m being honest, I think it’s way too early to entirely write it off…
While $LUNC has had a roller-coaster ride, there’s just one thing keeping it alive…
And that is its strong community. Despite having a difficult history, some holders still continue supporting the ecosystem in the hope for a brighter future…
For sure, rebuilding trust isn’t something that will happen overnight. It takes strategic development, adoption, and authentic progress….
As of now, it's one step at a time.
MouseT 🫛 I JurisProtocol retweeted
YWE
Hey #TerraClassic… since our voting process includes both no and no with veto (which is no longer used just for scam proposals, but for a little extra oomph) can we have YES, and YES WITH EXUBERANCE?
MouseT 🫛 I JurisProtocol retweeted
🙏 A huge THANK YOU to all #TerraClassic validators and community members who voted YES and supported us! ❤️
This approval finally allows us to deploy the long-awaited Juris migration to Injective USDC ($USDC.inj), alongside critical fixes for staking and governance. 🚀
Meanwhile, @frag_dude is actively working on a solution to address the underlying WASM vulnerability, with the goal of restoring permissionless code uploads ASAP.
Our goal has never been to restrict the chain. Quite the opposite.
Security without sacrificing decentralization. 🤝
We're grateful for the trust and excited to move forward with $JURIS and $LUNC! 🔥
MouseT 🫛 I JurisProtocol retweeted
🙏 A huge THANK YOU to all #TerraClassic validators and community members who voted YES and supported us! ❤️
This approval finally allows us to deploy the long-awaited Juris migration to Injective USDC ($USDC.inj), alongside critical fixes for staking and governance. 🚀
Meanwhile, @frag_dude is actively working on a solution to address the underlying WASM vulnerability, with the goal of restoring permissionless code uploads ASAP.
Our goal has never been to restrict the chain. Quite the opposite.
Security without sacrificing decentralization. 🤝
We're grateful for the trust and excited to move forward with $JURIS and $LUNC! 🔥
A proposal to allow two projects; Juris Protocol and LuncSwapfun; to directly upload their CosmWasm code onto the Terra Classic chain has been approved by the votes of $LUNC validators.
There was some unnecessary debate surrounding the proposal, but the Terra Classic community ultimately made the right choice. The Juris Protocol team is doing significant work for $LUNC and $USTC. It is worth remembering that Terra’s initial rise was driven by the Anchor Protocol; you can think of Juris Protocol as an advanced version of the Anchor Protocol.
#TerraClassic #LUNC #USTC #JurisProtocol
MouseT 🫛 I JurisProtocol retweeted
Tough Vote.
In the last hour JiL voted NO
Then he saw he wouldn't be able to sway the vote that way.
So he switched to NWV.
But that still did not suffice.
So he called his friend at LuncCommunity to NWV with him.
Guess what?
Still wasn't enough.
A strong community will b unimpressed by this kind of short sighted and erratic voting behavior.
Thank you for the trust and strong support.
👌🙏
MouseT 🫛 I JurisProtocol retweeted
Have you already voted on the two #LUNC governance proposals? If not, you can still do so.
Governance 12235 and 12236
$LUNC #USTC #TerraClassic #LuncCommunity #LuncFamily
Have a nice day Lunc's!
MouseT 🫛 I JurisProtocol retweeted
Replying to @_JCH01 @Yaman853397
These are the governance proposals I made in 2026:
12221: Software Upgrade v4.0.1
12225: Fund IBC Relaying
12226: Migrate USDC.n to USDC (Injective)
12227: Security Upgrade v4.0.1-patch.3
12233: Software Upgrade v4.1.1
12234: Restrict wasm code upload to governance
Behind every one of them is a lot of my own time and money: building and rolling out software upgrades, running infrastructure, managing community funds, security screening and incident response. None of it was paid.
12225 is the only one that paid out anything to me, and it only covered material costs: the servers that keep Terra Classic's IBC connections alive. My day job can't carry those costs. Not a single hour of my work running and maintaining the relayers was paid. For me personally it was net zero.
And I still voted ABSTAIN on it.
So, Yaman: explain how unpaid development hours, deployment work, managing community funds and security response for free benefited me personally.
If they didn't, there's no conflict of interest, and no reason for me to abstain on those proposals.
Every vote is on-chain. Check it.
MouseT 🫛 I JurisProtocol retweeted
The $ORBIT Token is now listed on LSF Exchange!
$ORBIT / $USDC pair is now available for trading.
Explore and follow the growth of the $LUNC ecosystem.
luncswap.fun/app/trade/luncs…
MouseT 🫛 I JurisProtocol retweeted
We appreciate your concerns, @HappyCatKripto, and genuinely respect your role as a watchdog for the Terra Classic ecosystem. 🤝
Let us be absolutely clear: We do NOT want to centralize $LUNC or permanently restrict permissionless CosmWasm deployments. Quite the opposite.
The security vulnerability is real, and the temporary restrictions were introduced for a reason.
However, we understand the concerns about transparency, centralization, and the potential implications for independent developers.
Therefore, we'd like to offer you the following:
1️⃣ Private technical demonstration: We invite you to a private call where we can demonstrate the actual attack in a controlled sandbox environment, without putting mainnet or user funds at risk.
2️⃣ A transparent remediation roadmap: Following verification of the vulnerability, we will present a proposed remediation roadmap, compatible with Terra Classic's Pay-Per-Job (PPJ) framework, with the ultimate goal of safely restoring permissionless WASM uploads.
3️⃣ Independent scrutiny: We welcome your questions, criticism, and input on appropriate safeguards throughout this process.
We do not expect the community to simply take our word for it. Security claims deserve scrutiny, and temporary restrictions must not become permanent privileges.
Our goal is to eliminate the vulnerability, not to eliminate decentralization.
Thank you for keeping a watchful eye on Terra Classic. We need people who ask difficult questions.
Let's work toward a solution together. 🤝
$LUNC | $JURIS | $LUNCPUMP
MouseT 🫛 I JurisProtocol retweeted
Replying to @_JCH01
@_JCH01 You keep telling people that your questions are going unanswered. Why not ask them publicly?
@luna_lover69 has already made it clear that the private line of communication is closed for several reasons, including your indirect support for and legitimization of GP's smear campaigns targeting his business and our brand.
If you have reasonable, legitimate questions or concerns, feel free to tag us publicly on X. We are happy to address them transparently, where everyone can follow the discussion.
You are not being denied answers. You are simply not entitled to special treatment or private access to our time.
The same communication standards apply to everyone.
$LUNC $JURIS $LUNCPUMP
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
MouseT 🫛 I JurisProtocol retweeted
I've always stood up for $LUNC and the community but am slightly upset that apparently we have to beg to be allowed to work on our own wasm contracts for @JurisProtocol and @LUNCSwapfun just to be accused of wanting to control the chain smh
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
MouseT 🫛 I JurisProtocol retweeted
Development will stall.
Security of @JurisProtocol is at stake - and with the safety of it's users - which are not only users of the product, but also users of the L1.
Vote YES on 12236 and thank you for your continued support 🙏🙏🙏
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
MouseT 🫛 I JurisProtocol retweeted
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




















