Aeredium Launches Loveh Lending Protocol On Testnet With Aerx Rewards

13 min read
3 views
Nov 17, 2026

Aeredium just dropped an ownerless lending protocol on testnet and put real AERX rewards on the table for anyone who can break it. Fixed fees, no admin keys, and a public challenge that could change how people think about risk in DeFi. The details are wilder than they first appear.

Financial market analysis from 17/11/2026. Market conditions may have changed since publication.

I still remember the first time a gas spike wiped out a position that should have been perfectly safe. Watching the liquidation bot eat collateral simply because the network got congested felt less like finance and more like a bad joke. That memory is exactly why the latest move from Aeredium caught my attention so hard. They just put an entirely ownerless lending protocol called Loveh onto their public testnet and, instead of the usual quiet launch, they attached a real incentive for people to try and break it.

What Makes Loveh Different From Everyday DeFi Lending

Loveh is a lending market built directly on the Aeredium Layer 1. Lenders deposit assets and earn interest. Borrowers lock collateral and take out loans. If the collateral value drops too far, anyone can step in, repay the debt, and claim the collateral at a discount. So far that sounds familiar. The part that stands out is everything the protocol deliberately refuses to include.

There is no owner. There are no admin keys. There is no governance module waiting to vote on parameter changes. Once the contracts are live, not even the original developers can pause them, upgrade them, or redirect funds. The assets sit only inside the smart contracts themselves. Aeredium wrote the code and published it, but after deployment the protocol runs on pure rules.

I’ve watched too many projects keep a quiet back door “just in case.” Loveh throws that option away on purpose. That decision forces a different kind of confidence, the kind that has to come from the code holding up under pressure rather than from a team promising to behave.

Fixed Gas Fees And Why They Matter More Than Most People Think

Most chains let transaction costs float with demand. When markets go wild, gas can jump high enough that liquidations become expensive or even impossible for smaller positions. Loveh sits on a network that publishes a fixed gas price: sixty dollars per megabyte of transaction data. That number does not climb during volatility.

The practical result is simple. A loan should never get liquidated just because the network suddenly became too expensive to interact with. Collateral ratio rules still apply, of course. If the value of the locked assets falls below the required threshold, liquidation remains fair game. What disappears is the extra tax that network congestion used to charge.

In my view this is one of the cleaner attempts at removing a known failure mode. Borrowers and lenders both gain a clearer picture of costs. The uncertainty that used to sit on top of every leveraged position shrinks a little.

The Security Challenge That Comes With The Launch

Because the contracts cannot be changed later, Aeredium is treating the testnet phase as an open stress test. The foundation is offering ten thousand AERX in airdrop points for every confirmed vulnerability that meets specific criteria. The issues that count are the serious ones: anything that would let someone move funds without permission, lock legitimate deposits, or break the documented rules of the protocol.

Examples they listed include accounting mismatches, fees flowing to the wrong address, or liquidations that fire even when collateral is still above the safety line. Style complaints, documentation gaps, and pure gas-cost observations do not qualify. If two people report the same bug, the first valid submission takes the reward. All outcomes get published so the community can see what was found and what was rejected.

The source code sits in a public repository. The contracts are already deployed on the Aeredium test network under Chain ID 2237. Anyone can spin up a new lending market through the factory contract and start poking at the edges. Reports go in privately with a clear description and reproducible steps.

When a protocol cannot be upgraded, the only honest path is to let the entire internet try to break it before real capital arrives.

That attitude feels healthier than the usual quiet audit followed by a soft launch. It also raises the bar for anyone who later decides to deposit actual value. At least the code will have taken some public punches first.

How The Interest Rate Model Was Built

Loveh does not invent its rate curve in isolation. At deployment the parameters were set using the average rates of the three largest USDC lending pools on Ethereum. The numbers came straight from those contracts and were cross-checked by two independent sources that had to agree. The goal was to start with rates that already felt familiar to active DeFi users rather than something experimental that might scare capital away.

Of course averages change. Because the protocol itself cannot be upgraded, the initial calibration becomes part of the permanent design. Future markets created through the factory will inherit the same logic unless someone finds a way to open a market with different parameters that the factory still accepts. That constraint is both a limitation and a feature. Predictability has a price.

The Practical Pieces Available Right Now

Three contract addresses are already public on the testnet. One receives foundation fees. One holds the interest rate formula. One is the market factory that lets anyone create a new lending market. Together they form the working skeleton of the system. Developers can read the code, deploy their own test markets, and start looking for edge cases while the incentive window is open.

I spent some time reading through the published material and the overall design feels deliberate. There is no attempt to hide complexity behind a friendly frontend promise. The rules are the rules. If you understand collateral ratios, interest accrual, and liquidation thresholds, you already understand the core of Loveh.

Why An Ownerless Design Still Makes People Nervous

Plenty of users like the idea of immutability until something goes wrong. Then the same people start asking who can fix it. Loveh answers that question in advance: nobody. That honesty is refreshing and also a little uncomfortable. It forces participants to treat the code as final rather than as a beta that will be patched later.

In practice this means the testnet phase carries extra weight. Every confirmed bug that gets fixed before mainnet reduces the chance of a permanent flaw. Every bug that slips through becomes a permanent feature of the system. The ten-thousand-AERX bounty is not marketing fluff. It is the cost of buying extra eyes while the window still exists.

I’ve seen projects claim they are decentralized while still holding upgrade keys “for emergencies.” Loveh simply removes the emergency option. Whether that choice ages well depends entirely on how thoroughly the current challenge is taken up by researchers.

Fixed Costs Change The Risk Math For Borrowers

On most networks a borrower has to keep extra buffer not only for price moves but also for the possibility that gas will spike at the worst moment. That buffer is capital that could have been used elsewhere. A fixed fee structure removes one of those variables. The remaining risk is still real, but it is cleaner.

Lenders benefit too. Liquidations that fail because nobody wants to pay the gas leave bad debt sitting in the system. When the cost of liquidating is predictable, more participants are willing to act as liquidators. Healthier liquidation markets usually mean healthier lending markets overall.

Of course fixed fees only help if the network itself stays reliable. Aeredium’s proof-of-attestation model is still relatively new. The combination of machine validation and human verification is an interesting bet, but it will need to prove itself under sustained load before the fixed-fee promise feels fully bankable.

What The Broader DeFi Crowd Should Watch

Loveh is not trying to reinvent every piece of lending. It is trying to remove two specific pain points: administrative control and unpredictable transaction costs. If the testnet phase produces clean results and real capital later follows, other chains may feel pressure to offer similar guarantees.

The open bug-bounty style of launch also sets a tone. Instead of a polished marketing campaign followed by a quiet audit report, the team is saying “here is the code, here is the money, try to break it.” That approach will not suit every project, but it fits a protocol that has already decided it will never be able to issue patches.

I keep coming back to the gas-fee piece. In a market where every basis point of cost and every minute of uncertainty gets priced in, a protocol that can honestly say “your liquidation will never be blocked by network congestion” has a real story. Whether the rest of the design holds up is exactly what the current challenge is meant to discover.

A Closer Look At The Collateral And Liquidation Rules

The liquidation mechanism itself is standard in concept. When collateral value falls below the required ratio, the position becomes eligible. Anyone can repay the debt and receive the collateral at a discount. That discount is the incentive that keeps the system solvent. Because the gas cost is known in advance, the profitability calculation for liquidators becomes more reliable.

What is less common is the absence of any pause function. In many protocols a sudden market crash can trigger a temporary freeze while parameters are adjusted. Loveh has no such freeze. The rules keep running even if prices gap hard. That design choice puts more weight on conservative initial parameters and on the quality of the price feeds the markets will eventually use.

During the testnet phase those price feeds and edge cases around rapid moves are exactly the kinds of situations researchers should be hammering. A vulnerability that only appears under extreme volatility is still a vulnerability if the protocol cannot be upgraded later.

The Airdrop Point Structure And What It Signals

Rewards arrive as airdrop points rather than immediate tokens. Those points convert according to the terms of the larger Aeredium airdrop program. The structure encourages serious, well-documented reports instead of a flood of low-effort submissions. Publishing every outcome also creates a public record that future depositors can review.

In an industry that still struggles with trust, transparent handling of security findings is useful. People can see which classes of bugs were found, which were dismissed, and how quickly the process moved. That visibility is rare and, in my experience, more valuable than another glossy audit PDF that nobody outside the core team ever reads in detail.

How Developers Can Actually Participate

The path is straightforward. Read the public code. Deploy interactions against the testnet contracts. Try to create markets, supply liquidity, borrow, repay, and liquidate under as many edge conditions as possible. When something looks wrong, document the steps so someone else can reproduce them. Submit the report through the designated private channel.

No special permission is required to start. The factory is open. The test network is public. The incentive is sitting there for anyone who finds a qualifying issue. That combination of open access and real reward is still uncommon enough to be worth noticing.

I expect most of the early activity will come from people who already live in DeFi security circles. The hope is that the size of the bounty also pulls in some newer researchers who might otherwise overlook a testnet launch.

Potential Weak Spots Worth Stressing Early

Even without access to the full bytecode analysis, certain areas always deserve extra attention in lending protocols. Interest accrual math over long periods can hide rounding errors that accumulate. Liquidation incentives need to stay profitable after fees. Factory contracts that let anyone create markets introduce the risk that a poorly configured market could somehow affect shared components.

Price oracle manipulation remains a classic vector. If the eventual mainnet version relies on external feeds, the quality and freshness of those feeds become part of the security surface. Because Loveh cannot be paused, a compromised oracle would keep feeding bad data until the market somehow resolves itself or runs dry.

These are not accusations. They are the ordinary places any careful reviewer would start. The fact that Aeredium is paying for confirmed findings suggests they want those places examined thoroughly while the cost of a mistake is still measured in test tokens rather than real capital.

Comparing The Philosophy To More Common Approaches

Most large lending platforms retain some form of governance or emergency control. The argument is always the same: the world changes, bugs appear, and users expect someone to be able to respond. Loveh rejects that argument. The counter-argument is that the ability to change the rules eventually becomes the ability to change them for the benefit of a small group.

Neither side has a perfect track record. Protocols with admin keys have been drained through compromised keys. Protocols without them have suffered permanent losses from unfixable bugs. Loveh is simply choosing one side of the trade-off and then trying to reduce the downside by maximizing the number of people looking for problems before launch.

I find the clarity refreshing. Too many projects try to sit in the middle and end up with the worst of both worlds: enough control to create centralization risk and not enough control to actually fix serious issues quickly.

The Role Of Predictable Costs In A Volatile Market

Crypto markets still swing hard. When they do, network activity spikes and variable-fee chains become expensive. Strategies that rely on frequent adjustments suddenly cost more than expected. Strategies that need to liquidate or rebalance can stall. A fixed fee removes one of those moving parts.

That predictability is especially useful for automated systems and for smaller participants who cannot absorb sudden cost increases. It does not eliminate market risk, but it does make the operational risk more transparent. In a sector that already carries plenty of uncertainty, every reduction in hidden variables helps.

Whether sixty dollars per megabyte turns out to be the right long-term number is a separate question. The important design decision is that the number is published and stable rather than floating with every surge in demand.

What Success Would Actually Look Like

A successful testnet phase would produce a short list of confirmed issues that get addressed before any mainnet deployment, followed by a period of quiet operation with real deposits and no major incidents. The more interesting success metric is whether other teams start copying the combination of immutable contracts and fixed network fees.

If the model works, it could push the industry toward clearer guarantees. Users would know in advance whether a protocol can be upgraded or paused. They would know whether their liquidations can be blocked by gas spikes. Those two pieces of information alone would make risk assessment simpler.

Of course success is not guaranteed. The code could contain a subtle flaw that only appears under mainnet conditions. The fixed fee could prove too high or too low once real volume arrives. The proof-of-attestation consensus could face challenges that variable-fee chains handle differently. All of those outcomes remain possible. The current public challenge is simply the best available tool for reducing the first of those risks.

A Personal Take On Timing And Incentives

Launching a serious security challenge at the same moment as the testnet deployment feels well timed. Attention is highest right at the announcement. Researchers who might ignore a quiet repository are more likely to look when there is both novelty and a clear payout. Waiting until after a mainnet launch would have left the immutable contracts exposed with real money already inside.

The size of the reward per bug is large enough to matter to independent researchers yet not so large that it attracts only the noisiest submissions. Publishing every outcome further disciplines the process. In an industry that still sees too many silent fixes and quiet disclosures, that level of transparency is welcome.

I plan to keep an eye on the public list of findings as it grows. The quality and quantity of reports will say more about the readiness of the protocol than any official statement could.

Broader Implications For Layer 1 Design

Most Layer 1 conversations still revolve around throughput, finality, and developer tooling. Loveh highlights a different axis: the predictability of costs and the permanence of application rules. A chain that can offer stable fees and host truly immutable applications may attract a specific class of users who value those properties over raw speed.

Whether that class is large enough to matter remains to be seen. But the experiment is worth running. If enough capital prefers the combination of fixed costs and no admin keys, other networks will have to respond. If the experiment fails, the industry will have clearer data on how much users actually value those guarantees when real money is at stake.

Either outcome improves the information available to the next team that sits down to design a lending protocol.

Practical Advice For Anyone Considering Early Involvement

If you write smart contracts or hunt bugs for a living, the current window is straightforward. The code is public, the network is open, and the reward criteria are published. Treat it like any other bug-bounty program: focus on fund-moving issues, document everything, and submit clean reports.

If you are a potential future user, the best action right now is simply to watch. Read the findings as they appear. Notice which classes of problems surface and how they are handled. That public record will be more informative than any amount of marketing language once the protocol eventually moves toward real deposits.

And if you are building on other chains, it is worth asking whether your own users would value fixed fees or stronger immutability guarantees. Loveh is testing those preferences in public. The results will be useful far beyond one project.

Final Thoughts On An Unusually Clear Experiment

Most protocol launches try to look finished. Loveh is launching while still explicitly unfinished and is paying people to prove it. That posture is rarer than it should be. Combined with the decision to abandon admin keys and to lock in a fixed fee schedule, the whole package feels like a coherent bet rather than a collection of trendy features.

Whether the bet pays off will depend on the quality of the scrutiny it receives over the coming weeks and on the behavior of the system once real value arrives. For now the invitation is open, the code is readable, and the incentive is real. In a space that often hides risk behind complexity, that level of openness is worth paying attention to.

I’ll be watching the public reports and the eventual transition from testnet to whatever comes next. The combination of ownerless contracts and predictable costs is interesting enough that even a partial success would move the conversation forward. And if the researchers find serious issues, those findings will be public too. Either way, the process itself is already more transparent than most of what the industry usually offers.

The next few months should tell us whether immutability plus fixed fees is a niche preference or a feature set that can attract meaningful capital. Until then, the testnet remains the place where the real work is happening.

❝
Wealth consists not in having great possessions, but in having few wants.
— Epictetus
Author

Steven Soarez passionately shares his financial expertise to help everyone better understand and master investing. Contact us for collaboration opportunities or sponsored article inquiries.

Related Articles

?>