Smart contracts.

The Housd protocol consists of several core components working together.

Core Contracts

• Vault Contract
• Share Token
• Treasury
• Access Control
• Liquidity Module
• Loan Management System (Offchain)
• NAV Engine

Investor interactions—including deposits, withdrawals, share issuance, and redemptions—are executed through the vault contracts.

Portfolio data is synchronized from the Loan Management System into the vault accounting layer.

Each Housd vault operates independently.

Every vault maintains its own:

• Asset allocation
• Share supply
• NAV
• Liquidity policy
• Fee configuration
• Originator relationships

This architecture allows multiple investment strategies to coexist while remaining isolated from one another.

Where appropriate, Housd vaults follow the ERC-4626 tokenized vault standard.

This enables integrations with wallets, aggregators, lending markets, and DeFi protocols using a standardized vault interface.

Core functionality includes:

• Deposit assets
• Mint vault shares
• Redeem shares
• Withdraw assets
• Preview vault operations

Additional functionality may extend beyond the standard to support NAV-based accounting and institutional liquidity mechanisms.

Investors deposit supported stablecoins into an approved Housd vault.

The vault:

1. 1Receives the deposit.
2. 2Calculates the current Net Asset Value (NAV).
3. 3Mints vault shares proportional to the investor's ownership.
4. 4Allocates capital according to the vault strategy.

All deposits are recorded onchain.

Withdrawals follow the liquidity policy defined for each vault.

Depending on available liquidity, withdrawals may occur through:

• Standard redemption
• ODL liquidity
• Secondary transfers
• AMM liquidity (where available)

Redeemed shares are burned upon settlement.

The Housd Loan Management System serves as the primary source of truth for portfolio data.

Portfolio metrics—including outstanding principal, accrued interest, repayments, and realized losses—are continuously synchronized with the vault accounting system.

As Housd expands its DeFi integrations, verified Net Asset Value (NAV) data may be published through supported oracle infrastructure, enabling external protocols to reference trusted vault pricing.

Security is a core design principle of the Housd protocol.

Before deployment, all production smart contracts undergo independent security reviews and formal auditing.

Audit reports, findings, and remediation summaries will be published alongside each production release.

Where applicable, upgrades are subject to governance and internal security review procedures.

Official contract addresses for every supported network will be published below.

Mainnet

• Residential Transition Loan Vault — To be published
• Liquidity Vault — To be published
• Leveraged Vault — To be published
• Treasury — To be published
• Vault Factory — To be published
• Access Control — To be published

Testnet

Development and testing deployments are maintained separately from production contracts.

Only addresses published through Housd's official documentation should be considered authentic.

Housd believes transparency extends beyond portfolio reporting.

Core smart contracts, interfaces, and integration examples will be publicly available where appropriate to support ecosystem integrations, independent review, and developer adoption.

Developers building on Housd are encouraged to reference the published interfaces and SDKs for the latest implementation guidance.