Pinned Tweet
That’s my new account, since the other one got attacked and restricted by some 🫛 Lovers and Co 🤣🤦♂️
I’m gonna continue to speak about my Crypto Journey and what I’m enthusiastic about here from now on ✌️
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
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
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
@_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
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
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
MouseT 🫛 I JurisProtocol retweeted
🚀 NEW LISTING ON LSF EXCHANGE! 🪐
Welcome $ORBIT from OrbitWire to #TerraClassic DeFi! 🔥
The ORBIT/USDC market is now LIVE on @luncswapfun! 💧
✅ Trade $ORBIT against USDC
💰 Provide liquidity & earn 2/3 of pool trading fees
⚡️ Explore arbitrage opportunities as liquidity and trading activity grow
🌐 Help expand the Terra Classic DeFi ecosystem!
Every new listing brings more assets, more markets and new opportunities for traders and liquidity providers.
🔥 Who wants to see more projects join LSF Exchange?
👇 Trade & provide liquidity:
luncswap.fun/app/trade/luncs…
#ORBIT #OrbitWire #LSFExchange #LUNC #DeFi $JURIS $LUNCPUMP
MouseT 🫛 I JurisProtocol retweeted
🚨 BIG NEWS FOR $INJ and $LUNC! 🥷🔥
Nasdaq has approved the listing of Canary Capital's Staked Injective ETF ($INJC)! Institutional adoption meets DeFi! 🚀
Did you know $INJ is already trading against $USDC on LSF Exchange on #TerraClassic?
💧 Liquidity Providers: Earn 2/3 of pool trading fees by providing INJ + USDC liquidity!
⚡ Arbitrage Traders: Explore price differences between LSF and other $INJ markets, helping align prices and drive trading volume.
📈 More trading volume = more potential LP fee revenue for $JURIS stakers!
🔥 Don't just watch the $INJ ecosystem grow. Help build its liquidity!
👉 luncswap.fun/app/trade/luncs…
@injective @luncswapfun
#Injective #LSFExchange #LUNC #DeFi
BREAKING: The NASDAQ has officially approved the listing of the first-ever INJ Staked ETF.
The ETF will bring unprecedented exposure to $INJ and will target staking 90% of its institutional holdings in the U.S.
The ticker is INJC.
MouseT 🫛 I JurisProtocol retweeted
Imagine being in crypto and not having a $LUNC moon bag.
Opened a nice degenerate long position to celebrate the mid terms 😉
MouseT 🫛 I JurisProtocol retweeted
Thank you @BInodes_ for helping @JurisProtocol to maintain its security operations 🙏🙏🙏
MouseT 🫛 I JurisProtocol retweeted
Time to send $LUNC much higher 🫡
How to earn trading fees on LSF Exchange 🙏
Even in a bear market, there are several ways to make some revenue/money 👇
$LUNC $JURIS $LUNCPUMP
💧 HOW TO EARN TRADING FEES ON LSF EXCHANGE 🚀
Did you know you can earn 2/3 of all pool trading fees by providing liquidity on @luncswapfun and 1/3 of fees go to $JURIS stakers during the promo period? 🔥
Let's use our $INJ / $USDC pool on #TerraClassic as an example! 👇
💰 Add INJ + USDC to the liquidity pool
🔄 Traders swap between both assets
📈 2/3 of trading fees go to liquidity providers, proportional to their pool share
💎 Earn fees as trading activity grows!
Our INJ/USDC pool currently shows:
💧 Liquidity: ~$4,038
📊 7D LP APR: 3.11%
How to participate:
1️⃣ Visit luncswap.fun
2️⃣ Connect your wallet
3️⃣ Select INJ/USDC → Liquidity
4️⃣ Click Provide and deposit both assets
5️⃣ Start earning your share of pool trading fees!
🌐 More liquidity = deeper markets, better trading conditions & a stronger #TerraClassic DeFi ecosystem.
⚠️ LP positions involve impermanent loss and smart contract risks. APR is variable, not guaranteed.
Trade. Provide. Earn. Build. 🐦
#LSFExchange #Injective #USDC #LUNC #DeFi
MouseT 🫛 I JurisProtocol retweeted
💧 HOW TO EARN TRADING FEES ON LSF EXCHANGE 🚀
Did you know you can earn 2/3 of all pool trading fees by providing liquidity on @luncswapfun and 1/3 of fees go to $JURIS stakers during the promo period? 🔥
Let's use our $INJ / $USDC pool on #TerraClassic as an example! 👇
💰 Add INJ + USDC to the liquidity pool
🔄 Traders swap between both assets
📈 2/3 of trading fees go to liquidity providers, proportional to their pool share
💎 Earn fees as trading activity grows!
Our INJ/USDC pool currently shows:
💧 Liquidity: ~$4,038
📊 7D LP APR: 3.11%
How to participate:
1️⃣ Visit luncswap.fun
2️⃣ Connect your wallet
3️⃣ Select INJ/USDC → Liquidity
4️⃣ Click Provide and deposit both assets
5️⃣ Start earning your share of pool trading fees!
🌐 More liquidity = deeper markets, better trading conditions & a stronger #TerraClassic DeFi ecosystem.
⚠️ LP positions involve impermanent loss and smart contract risks. APR is variable, not guaranteed.
Trade. Provide. Earn. Build. 🐦
#LSFExchange #Injective #USDC #LUNC #DeFi