Fherum (@Fherumfi) header
Fherum (@Fherumfi) profile picture

Confidential DeFi lending powered by FHE, with Aave V4-inspired architecture on Robinhood Chain.

Joined November 2026
Photo by Fherum (@Fherumfi)Photo by Fherum (@Fherumfi)Photo by Fherum (@Fherumfi)Photo by Fherum (@Fherumfi)Photo by Fherum (@Fherumfi)Photo by Fherum (@Fherumfi)Photo by Fherum (@Fherumfi)Photo by Fherum (@Fherumfi)Photo by Fherum (@Fherumfi)
What if DeFi lending could protect your positions without hiding the market? Introducing FHERUM, a confidential money market built around Fully Homomorphic Encryption (FHE). CA: 0x8665f6e7ce1df1abe042d4b044e681be98a62974 FHE brings a different approach to onchain privacy: computation over encrypted data, without exposing the underlying positions. Combined with an @aave V4-inspired modular architecture, FHERUM brings together confidential positions, curated lending markets, and transparent market-level risk.
32
8
4
60
8,313
Why connect FHERUM to @SentoraHQ ? Because our Risk Curator should be able to route capital beyond FHERUM-native markets. Sentora adds an external vault layer on Ethereum, giving the curator another venue for capital deployment and market selection. This makes FHERUM’s curated market architecture more modular, more flexible, and less dependent on a single liquidity environment. PYUSD is the first live flow.
2
6
324
We are back. And we’re coming back with something real. FHERUM is now officially connected to @SentoraHQ. Our curated market layer can now extend into Sentora vaults, giving the FHERUM Risk Curator access to external DeFi markets beyond our own lending infrastructure. The first PYUSD flow is already live on Ethereum.
2
2
7
561
Headless Lending × Fherum's Hearth Agentic Layer is now configured and working on Robinhood Chain Mainnet. We’ve created a Policy Vault, installed the Hearth Router hook, supplied USDG into a Headless Lending market, and assigned an agent executor. On-chain proof: Vault: robinhoodchain.blockscout.co… Create Vault: robinhoodchain.blockscout.co… Install HEARTH Router Hook: robinhoodchain.blockscout.co… Approve USDG: robinhoodchain.blockscout.co… Supply USDG: robinhoodchain.blockscout.co… Set Agent: robinhoodchain.blockscout.co… This is the foundation for autonomous lending on FHERUM. Developers can build their own lending applications and connect agents to monitor markets, manage positions, and execute lending strategies within user-defined policies. Headless Lending provides the infrastructure. Hearth provides the rules and execution boundaries. The goal is simple: let agents handle lending operations while users stay in control.
5
2
2
13
1,516
This is the direction we're working towards with FHERUM. Headless Lending provides the infrastructure, while Hearth adds the agentic layer on top. The goal is to let developers build lending applications where agents can monitor markets, manage positions, and execute lending strategies within user-defined policies. More than just automating transactions, it's about making lending programmable and autonomous while keeping users in control.
8
3
20
891
We're working on bringing autonomous lending to FHERUM. Inspired by @Morpho and their work on Morpho Agents, we're connecting Headless Lending with our Agentic Layer to let developers build custom lending apps where agents monitor markets, manage lending actions, and execute strategies within user-defined policies. Build your own lending experience. Let agents handle the execution, within your rules.
Introducing Morpho Agents in Beta Integrate Morpho with natural language and ship products in minutes using your preferred AI agents. Built for institutions, developers, and app builders.
4
2
1
10
879
We've been working on bringing a new approach to lending infrastructure into FHERUM. Introducing Headless Lending, now live. Based on the architectural approach behind ATLAS by @LayerZero_Core , we're adapting the headless infrastructure concept for lending and borrowing. Developers can build their own lending experience, with their own UI, brand, and users, while FHERUM handles the lending engine behind it. Start with an iframe, use our widgets, or build your own interface. Your app. Your experience. FHERUM's lending infrastructure. Live on Robinhood Chain.
2
2
12
610
Introducing Headless Lending, coming to FHERUM. Taking an architectural approach inspired by ATLAS from @LayerZero_Core , we're bringing the headless infrastructure concept to lending. The idea is simple: applications can build their own lending experiences without having to build the entire lending engine from scratch. FHERUM becomes more than a lending app. It becomes infrastructure others can build on. More details soon.
1
1
2
14
2,138
The website is back up, guys!
1
8
390
Been a little quiet on FHERUM lately, but we've been working on something behind the scenes. Still putting the pieces together. Should have something to share very soon. More soon 👀
4
1
2
13
1,450
Hearth Hooks are now working directly in FHERUM's web app on Robinhood Chain mainnet. We've tested the full flow: vault creation, installation of all 14 hooks, USDG deposit and supply, dust handling, withdrawal, and owner escape. This is no longer just an on-chain deployment. The hooks are integrated into FHERUM's lending workflow and working as intended. The walkthrough is attached. Every transaction below is publicly verifiable. Vault creation: robinhoodchain.blockscout.co… Install 14 hooks: robinhoodchain.blockscout.co… Deposit & approval: robinhoodchain.blockscout.co… Supply: robinhoodchain.blockscout.co… Dust handling: robinhoodchain.blockscout.co… Withdraw: robinhoodchain.blockscout.co… Owner escape: robinhoodchain.blockscout.co… Built to make FHERUM's lending and borrowing experience more configurable, without taking the focus away from the money market itself.
5
4
15
932
Hearth Hooks are now deployed and live on Robinhood Chain mainnet. This brings a new layer of user-defined execution policies to FHERUM's existing lending markets. The deployment includes the core infrastructure, Policy Router, Account Factory, Hook Factory, Session Oracle, and 14 individual hooks covering market access, utilization limits, liquidity buffers, position sizing, execution controls, and more. These aren't just agent-side preferences. The rules are designed to be enforced on-chain before HEARTH executes lending actions. FHERUM remains the money market. Hearth makes it more configurable, with users having greater control over how their positions are managed. Every contract is publicly verifiable on-chain. Deployment references below. This is a pretty big milestone for what we've been building.
2
3
15
641
We've shared quite a bit of the engineering behind HEARTH Hooks, so here's a closer look at what we're actually building. The core idea is to make FHERUM's existing lending markets more flexible to use. Users can define how HEARTH handles their USDG: which markets it can supply to, how much liquidity it can allocate, what utilization conditions it must respect, and when it should hold back or withdraw. Those rules are attached to the user's Policy Vault and enforced on-chain through a lending-specific hook system inspired by the Uniswap v4 architecture. The Circuit agent handles execution, but it doesn't get to decide the boundaries. And the lending itself stays where it belongs: in FHERUM's markets. We're bringing together the hook infrastructure, user configuration, execution receipts, and Circuit integration now. Next up is controlled mainnet validation, followed by the Hook Board rollout on FHERUM. The goal isn't to turn FHERUM into an AI agent project. It's to make the lending and borrowing experience more capable, configurable, and easier to manage.
1
3
1
10
851
I don't want users to need to understand every hook parameter before they can use HEARTH. That's why we're designing Hook Stacks alongside the individual implementations. Conservative, Steady, Session-Safe, and Active will provide starting configurations for how the agent interacts with FHERUM markets. Users can then adjust individual rules around market access, liquidity buffers, sizing, and timing. The presets don't replace the hooks. They simply make it easier to configure a set of on-chain policies for an existing lending workflow.
5
10
317
We're also building the hooks that determine when HEARTH should hold back instead of moving funds. DebtBlock prevents new parking while the vault has outstanding debt in the relevant market. PartialHold keeps partial withdrawal proceeds in the vault instead of triggering an unsuitable re-entry. PanicExit provides a controlled withdrawal path when utilization reaches a configured threshold, subject to the other applicable restrictions. The important distinction is that these hooks don't replace FHERUM's lending risk engine. They add another layer of user-defined conditions around how HEARTH interacts with the lending markets.
1
4
1
11
581
Another area we're working through is transaction sizing. Even when a market is allowed, that doesn't mean the agent should be able to move any amount it wants. TxSize defines per-transaction minimums and maximums. PortionCap limits how much of a market's available liquidity or vault equity can be allocated. WalletCap respects the protocol's market-level wallet cap and optional user-defined daily limits. These checks run as part of the supply and withdrawal execution path. Small controls, but they make a big difference when automation is managing real lending positions.
1
4
14
400
We've been focusing the first hook implementations on the decisions that matter most when parking USDG into FHERUM markets. IdleSweep handles eligible idle balances. FloorRate checks the minimum supply rate. UtilBand enforces a utilization range. CashBuffer protects available market liquidity. MarketAllow restricts which markets the agent can use. These are not separate lending products. They're configurable conditions around the existing supply and withdrawal flow. The point is to let users decide how their capital participates in FHERUM markets, rather than giving every user the same fixed strategy.
3
10
242
One important part of this design is keeping the agent separate from the user's funds. The HearthAccount acts as the Policy Vault. The user owns the vault, while the Circuit agent gets limited executor permissions. The agent doesn't get unrestricted access to call FHERUM Markets directly. It has to go through the Router, where the user's installed hooks are checked. We're also keeping the owner's escape path separate from normal agent execution. Automation should make lending easier to manage, not make users dependent on an agent to access their own funds.
4
9
368