#LowLevelDev

The goal is bigger than launching another Terra Classic app. We want to make $LUNC accessible again — to retail, builders, investors and the wider crypto industry. From day one, @JurisProtocol will be fully integrated and accessible directly from the new @LUNCSwapfun app. 😍 From one familiar interface, users will be able to: 🌀 Trade $JURIS 🏦 Borrow & earn through @JurisProtocol 💧 Deploy liquidity to DEX 🌐 Access Terra Classic applications 💵 Deposit and withdraw USDC directly from/to Ethereum using a single @keplrwallet connection No juggling several wallets. No hunting for obscure bridges. No requirement to understand the entire Cosmos ecosystem before you can even get started. Connect Keplr → bring USDC from Ethereum into Terra Classic → use the ecosystem → move it back out when you want. That kind of simplicity is essential if we actually want people outside our existing community to use $LUNC again. SEPTEMBER: CONNECTING THE ECOSYSTEM 🌀 Throughout September, the team will gradually roll out additional features while preparing the deeper integration of @LUNCSwapfun — including Juris Protocol — natively into @LUNCDash. We will also work on mobile wallet connectivity for @hexxagon_io and @keplrwallet. And after the initial launch, we intend to progressively integrate additional Terra Classic venues and applications into both our web app and the native LUNCDash experience. This includes, but is absolutely not limited to: 🔹 @Terraport — full platform integration 🔹 @garuda_defi — full platform integration 🔹 @WESOWorld — full platform integration 🔹 @LUNCDash — tools, analytics, wallet connectivity & discovery The list should continuously expand as the ecosystem grows. We also intend to create a dedicated directory for useful and widely used Terra Classic applications, tokens, media outlets, infrastructure providers, builders and known ecosystem contacts. Prominent placement. Easy discovery. Marketing exposure through our apps and social channels. Because the objective is not to create another walled garden. The objective is to build a front door into Terra Classic. AND THEN WE TAKE IT OUTSIDE THE $LUNC BUBBLE. 🌍 Founder @luna_lover69 will attend multiple major crypto events this year representing Juris Protocol and the broader Terra Classic ecosystem. One of the most important stops: TOKEN2049. And @frag_dude will be there with him. But we don't intend to show up with nothing more than a presentation about what Terra Classic could become. We intend to arrive with working products. 📱 A native @LUNCDash mobile wallet in our pockets — at minimum as a working developer preview. 🌀 The @LUNCSwapfun web application fully ready. 💵 Direct USDC access from/to Ethereum through one Keplr wallet connection. 🏦 @JurisProtocol demonstrating BTC + $LUNC basket collateral with USDC loans. This year, people at TOKEN2049 should be able to experience Terra Classic themselves. Not hear another pitch about 2022. Not read another governance proposal. Not be told to imagine what could theoretically be built. Open the app. Connect the wallet. Bring in capital. Trade. Borrow. Earn. Deploy liquidity. Explore the ecosystem. Retail users should be able to discover the new Terra Classic within minutes. THE EXPOSURE SHOULD BENEFIT EVERYONE. Our recent $JURIS listing on @WEEX_Official is not supposed to create exposure for Juris alone. The exchange partnership, marketing campaigns, events, industry meetings and introductions should create another entry point into the entire $LUNC ecosystem. Someone discovers $JURIS through WEEX. They discover @LUNCSwapfun. From there they discover @LUNCDash. Then @Terraport. @garuda_defi. @WESOWorld. Other tokens. Other applications. Other builders. Other communities. One project's growth should create opportunities for the others. That is the positive feedback loop we want. More users → more liquidity. More liquidity → better products. Better products → more attention. More attention → more users, builders and capital. And every successful independent project strengthens the network around it. No single company, validator or protocol should ever be Terra Classic. A healthy ecosystem needs independent teams, competition, different ideas and different communities. What we can do is connect them. Make them discoverable. Reduce friction between them. And use whatever exposure we generate to help put the wider ecosystem back in front of the crypto industry. That is Project Flywheel in practice. Integrate everything. Connect everything. Make it accessible. Grow #TerraClassic. 🌀🚀 ━━━━━━━━━━━━━━━━━━ 🔥 TRADE & SUPPORT THE ECOSYSTEM 🌀 Trade $JURIS on LUNCSwapFun: 📈 Trade $JURIS/USDT on WEEX: 🔥 Join the WEEX × $LUNC Burn Campaign: VIP CODE: LUNCBURN Trade. Build. Burn. Grow $LUNC. 🔥

From day one, @LUNCSwapfun is designed to make entering Terra Classic dramatically easier for new users. 🌀 Trade $JURIS & other tokens 🏦 Earn through @JurisProtocol lending & $LUNC staking 🪙 Use $LUNC as collateral to borrow (BTC & GOLD on roadmap) 💧 Deploy liquidity to DEX 🌐 Access #TerraClassic applications from one interface 💵 Deposit and withdraw USDC directly from/to Ethereum — using a single @keplrwallet connection No juggling multiple wallets. No hunting for obscure bridges. No need to already understand the entire Cosmos ecosystem before you can get started. Connect Keplr, bring USDC from Ethereum into Terra Classic, use the ecosystem — and move it back out when you want. This is the kind of UX we want people to experience when we put the new Terra Classic in front of retail users at @token2049 and other major events this year. Make $LUNC accessible again.

@JurisProtocol @LUNCSwapfun If say.... Hardcore any errors to say... "Damn.... Error 667..... #blameFrag" with a way to click to report the issue that spams Frags inbox to fix his mistake or he loses his wooden chair in the office. #LowLevelDev

Drama King and #lowleveldev Strath did some #LUNC #aimusic again during the past week to vent 😅

Dear #LUNCcommunity, a message from your friendly #lowleveldev Strath. It really seems that many don't understand the implications of their behavior and the consequences for chain security. I did not bring this up before end of the SubDao vote as I, contrary to obviously common habits, don't like to use dirty tricks and fear-mongering to sway votes. The SubDao approach would have offered a promising way to provide the chain with something it is lacking badly: *governance-approved points of contact*. These are *especially* relevant for chain security. And I'll explain why. #TerraClassic relies on upstream code like wasm, Cosmos SDK, CometBft and others. Those code releases can contain security issues. The normal procedure for (especially high-severity) fixes is to notify chain points of contact *before* making the issue and patch public. This is to prevent making potentially bad actors aware of the issue and give chains the opportunity to upgrade early. Fact is: We as a chain do NOT receive these notifications anymore. Why? Because of the public bickering and discrediting, and the missing (approved) point of contact. So what does that mean? People (voluntarily) need to actively track all upstream repositories for security advisories (which normally anyway are only published *after* private disclosure). So to give you a more concrete example: I stumbled upon a message from Antier Solutions in a casual group about their SDK upgrade proposal few days ago (they posted it earlier already). They hinted to a Security Advisory with "critical" severity which had already been publicly disclosed in February. After assessing the impact, Frag decided to implement the fix on chain. During the work we realized that other upstream code also released high-severity patches, already publicly announced since a while and had gone unnoticed. A dedicated *governance-approved* security group would have provided a transparent and efficient point of contact and a way to efficiently coordinate with devs (and validators if necessary) on these matters. The same applies to the other fields that the DAOs were meant to handle communication in. But that's a different story. People do not understand that there is no "make everything public" in security. Not even in a decentralized environment. Demanding this and blocking efforts to streamline this part of the chain is *actively and intentionally* putting the chain at risk. And this is absolutely no exaggeration. After all, we all are lucky that this chain did not run into unplanned chain halts or more severe problems due to security issues that could not be fixed as quickly as it was the case a longer while ago. Meanwhile, some are trying their best to discredit all those who step in voluntarily in these situations, and that have done more for the chain than they would and could ever do … of course again and again with false claims, half-truths and populism. Bravo. Think about this when supporting and cheering those playing "guardians of decentralization". Those using fear-mongering, false claims, deflection and threats. Well, good luck to us all with that mindset. Cheers. P.S.: Thank you, @frag_dude for stepping in. Once again. Although parts of this community absolutely do not deserve it. And according to their talks, don't need it. #blamefrag (and maybe myself) for going outside of governance to apply various important security patches to the chain and coordinate the upgrade procedure through a governance proposal. #LUNC #chainsecurity

Challenge: Build my own simple malloc to understand C memory New to C, learning via Dan Luu’s tutorial: Surprise: stack & heap share the same virtual address space (see thread)! Any tips while building? #CProgramming #LowLevelDev .----. | o_o |

Let's educate GP a bit. IBC relaying is a crucial infrastructure expense for a Cosmos chain. The central entity around the chain would pay it as a part of their business budget - However, if there is no entity, big validators like GP can pay it from their commissions. 1/x

But from what I can see GP is just doing nothing for the chain... That's why I was so kind to correct his failure and pay for it in advance. GP, you are still open to pay for the IBC relayers. But I guess you don't even have an idea what that is and how much volume goes over it

And yes. I am a terrible #lowleveldev. But you know what? The people love me for it 😘

I literally worked 8hrs to get this message... PS: @ColeStrathclyde

@frag_dude #lowleveldev #bridgehero

Touching grass?

@frag_dude If you're touching grass, who's doing the low-level development 😂😂

@LuncGuardian I heard @luna_lover69 is #lowleveldev as well...

“Maybe it’s just me but learning C first makes learning other programming languages a lot easier” absolutely!

@isharduld Now I know why I am a #lowleveldev. It's because Pascal was my first language 😂

$juris #lowleveldev is cookin' on the bitch-beach 🤪🙃🤓

@frag_dude Der Bro hat sogar an USDT gedacht 🙈

@luna_lover69 #lowleveldev eben

We officially announce that $juris #lowleveldev @frag_dude does not have permission to ape $peas. Be advised that any engagement with the @Peastoken06_09 twitter account will result in a permanent ban from all #JurisProtocol related activities. WE REPEAT: DO NOT APE $PEAS 🚨

@frag_dude No, do not buy GeenPeas $PEAS. Do NOT have fun! Get back to work #lowlevevdev

GM $lunc, I am happy that @Allnodes supported our proposal to compensate @frag_dude 🙏 This was a controversial one but I am happy that we got enough support to make things alright. Our $juris #lowleveldev deserves it 🤠 Stake with @JurisLuncVal to support @JurisProtocol ❤️

Optimizing some code w/hand written ARM (64) code. Not done this in years, having some fun with it. #lowleveldev

Bad actor frag relayed more than $2M worth of assets. He should go directly to prison without collecting salary. He is a scammer leeching CP money. Don't stake with @luncgoblins. Educate yourself. Boycott the #lowleveldev.