GranEverest · ETH vault on Base
This page describes the GranEverest ETH vault on Base mainnet, how to use it as an end user, and how to integrate it as a developer. The design focuses on a narrow, transparent feature set, with clear risk boundaries and predictable on-chain behaviour.
GranEverest currently operates a single public vault contract on Base mainnet: GranVaultBaseETH. It is a single-asset borrowing vault where both collateral and debt are in the same token, WETH on Base. Through the app, users see and sign regular ETH transactions; wrapping and unwrapping between ETH and WETH is handled by the application layer.
The objective is to provide an ETH credit line without price-based liquidations or complex interest-rate models. Instead of a broad multi-asset money market, GranEverest keeps a tight, observable scope:
Canonical contract addresses, guardian details and auxiliary execution contracts are listed and kept up to date on the Trust page.
0x4200000000000000000000000000000000000006.swapExecutor contract (for example a DEX aggregator). Failures or excess price movement cause the entire transaction to revert, so the vault state does not change if execution cannot complete safely.Interacting with any smart contract on-chain involves risk. The points below highlight the main categories users should understand before using the vault. This section is informational only and does not constitute investment or legal advice.
Defects or vulnerabilities in the GranVaultBaseETH contract, the execution router or the external swap executor, as well as the surrounding infrastructure and dependencies, could result in loss of funds. The system is tested and monitored, but no smart contract can be guaranteed free of risk.
The owner/guardian can pause the vault and manage guarded parameters. The protocol is designed so that users can always repay, even while paused. As with any key-based governance model, there is residual risk related to key custody, potential compromise or operational mistakes.
The vault runs on Base. Network outages, sequencer issues, L1 congestion or censorship at the L2 or L1 level could delay or temporarily block interactions, including withdrawals.
The protocol does not liquidate positions based on ETH price. This avoids forced liquidations, but it also means users are responsible for deciding when to reduce exposure. If ETH moves sharply, the value of your collateral changes while your debt remains fixed in ETH terms.
If the GranEverest web app is unavailable, technically capable users can still interact directly with the contracts via BaseScan or their own scripts. This provides redundancy but requires care: interacting directly without the app's safeguards can increase the chance of user error.
GranEverest intentionally focuses on a single-asset vault rather than a general-purpose money market. Users should size positions conservatively, diversify across protocols and avoid depositing funds they cannot afford to lose.
Nothing in this documentation is an offer, solicitation or recommendation to use the protocol or to take any specific financial position. Each user is responsible for their own independent evaluation of risk.
GranEverest is implemented as a primary vault contract plus a small execution layer on Base mainnet. For the latest production addresses, roles and configuration parameters, always refer to the Trust page and the official GitHub repository.
0x0d1c77349E80F4c4AE47E318A3D0723D12159E2d (see Trust for confirmation).deposit() — records ETH/WETH collateral and applies the 0.25% protocol fee.borrow(uint256 amount, address account) — borrows on behalf of the given account, provided the resulting LTV is ≤ 70%.repay(uint256 amount, address account) — repays outstanding debt and returns any extra ETH sent by the user.withdraw(uint256 amount, address account, address to) — withdraws collateral, enforcing LTV and applying the withdrawal fee.swapExecutor contract (for example a DEX aggregator). If execution fails or the realised price exceeds the allowed slippage, the transaction reverts and the vault state is unchanged.import { createPublicClient, http } from "viem";
import { base } from "viem/chains";
import GranVaultBaseETH from "../src/abi/GranVaultBaseETH.json";
const VAULT_ADDRESS = "0x0d1c77349E80F4c4AE47E318A3D0723D12159E2d"; // see /trust for the latest address
const client = createPublicClient({
chain: base,
transport: http("https://mainnet.base.org"),
});
export async function getUserData(user: \`0x\${string}\`) {
const result = await client.readContract({
address: VAULT_ADDRESS,
abi: GranVaultBaseETH.abi ?? GranVaultBaseETH,
functionName: "getUserData",
args: [user],
});
console.log("User data", result);
return result;
}import { createWalletClient, http } from "viem";
import { privateKeyToAccount } from "viem/accounts";
import { base } from "viem/chains";
import GranVaultBaseETH from "../src/abi/GranVaultBaseETH.json";
const VAULT_ADDRESS = "0x0d1c77349E80F4c4AE47E318A3D0723D12159E2d"; // see /trust for the latest address
// In production, load private keys from a secure secret manager,
// never commit them to source control.
const account = privateKeyToAccount("0xYOUR_PRIVATE_KEY");
const client = createWalletClient({
account,
chain: base,
transport: http("https://mainnet.base.org"),
});
export async function borrow(amountWei: bigint, accountAddress: \`0x\${string}\`) {
const hash = await client.writeContract({
address: VAULT_ADDRESS,
abi: GranVaultBaseETH.abi ?? GranVaultBaseETH,
functionName: "borrow",
args: [amountWei, accountAddress],
});
console.log("Borrow tx hash:", hash);
return hash;
}The vault emits standard events for position changes, which can be indexed by off-chain services and analytics dashboards. Examples include events for deposits, borrows, repayments and withdrawals. Indexers can consume these events directly from Base to build history views or alerts around users' positions.
The code snippets above are illustrative only. Production systems should follow best practices for secret management, gas estimation, retry logic, logging and monitoring.
The GranEverest vault codebase is developed with a deliberately narrow scope, repeatable processes and multiple layers of testing and review:
GranVaultBaseETH, focused on LTV bounds, ETH conservation and debt behaviour under varied sequences of actions. The harness is maintained alongside the codebase and extended progressively; only the stable subset is part of the default passing test suite.rescueERC20 helpers and the router's low-level call to the configured swap executor. No critical or high-severity issues are known at this time.The vault and router source code are verified on BaseScan, and the public GitHub repository contains all configuration required to reproduce local tests and static analysis. Anyone can clone the codebase, run the same checks and form an independent view.
Independent external review and ongoing monitoring are part of the long-term roadmap. When additional audits or formal analyses are completed, references and reports will be linked from the Trust page.
Even with these measures, smart-contract risk cannot be eliminated. Users should size positions prudently, diversify across protocols and avoid depositing funds they cannot afford to lose.
Security researchers, integrators and advanced users are encouraged to review the contracts and the public GitHub repository. For potential vulnerabilities or high-impact issues, please follow a responsible disclosure process:
Formal bug bounty terms and dedicated bounty addresses will be published as the protocol matures and on-chain usage grows. Until then, disclosures are handled on a best-effort basis, with the goal of protecting users and the wider ecosystem.
The initial launch focuses on a single ETH vault on Base with predictable behaviour and a narrow risk surface. Future work is planned around expanding functionality while keeping clear separation of risk between components:
rescueERC20 before supporting materially higher TVL.These items are intentionally staged. GranEverest prioritises preserving principal and understanding risk before adding new features. New vaults or strategies will only be introduced once they can be tested, explained and monitored to the same standard as the current ETH vault.