Networks
Encumbra is launching on Base Sepolia. You integrate against one official deployment per network, once its address is published.
Each supported network will have a single official deployment. Your client talks to it through a JSON-RPC endpoint. No address is published yet, so there is nothing to connect to on a public network today.
On a public network you do not deploy a contract yourself. You point the SDK at the published address and build against it. On a local chain you can deploy your own copy with EncumbraClient.deploy to test the same calls.
- Your appagent, creditor, or owner code
- EncumbraClient (SDK)new EncumbraClient(chain, address)
- RpcChain (SDK)holds your keys, sends JSON-RPC
- EncumbraLien on Base Sepoliathe official deployment, once its address is published
Supported networks
Encumbra is launching on Base Sepolia first — Base's public testnet, chain id 84532. This is where the protocol will be validated end-to-end before any mainnet launch.
| Network | Status | Details |
|---|---|---|
| Base Sepolia (testnet) | Launching, testnet | Chain id 84532. The Encumbra contract address will be published here once the deployment is live. Until then there is no address to connect to on this network. |
| Mainnet | Not live | Not live yet. Encumbra is testnet-only at this stage; a mainnet deployment, with its own published address, will be announced when it is ready. |
Connecting the client
You connect by constructing an EncumbraClient with a chain and the contract address: new EncumbraClient(chain, address). The chain is any ChainLike transport. For a JSON-RPC network such as Base Sepolia it is RpcChain.rpc(url, privateKeys).
RpcChainsigns with the keys you pass. Every address that sends a transaction needs its key in that list, and every state-changing method takes that address as an argument.- For reads only, pass an empty key list. Reads need no signer.
@encumbra/sdkis not published. The SDK lives in the Encumbra repository (src/sdk.ts,src/rpc.ts) and you import it from there.
The same client code works on any chain; only the chain object and the address change. For a local chain use RpcChain.ganache(). The Quickstart walks through a full open, draw and repay.
import { RpcChain } from "./src/rpc.ts";
import { EncumbraClient } from "./src/sdk.ts";
const ENCUMBRA_ADDRESS = process.env.ENCUMBRA_ADDRESS!; // published here once the deployment is live
const RPC_URL = "https://sepolia.base.org";
// Reads only: no keys.
const reader = new EncumbraClient(await RpcChain.rpc(RPC_URL, []), ENCUMBRA_ADDRESS);
const lien = await reader.getLien(1n);
// Reads and writes: pass the key of every address that sends a transaction.
const chain = await RpcChain.rpc(RPC_URL, [process.env.OWNER_KEY!]);
const [owner] = chain.accounts; // the acting address
const encumbra = new EncumbraClient(chain, ENCUMBRA_ADDRESS);
// Every state-changing call names the acting address.
await encumbra.freeze(1n, owner); // the owner of lien 1 stops new chargesSettlement token per network
Each network has a settlement token that liens are denominated in: the token a creditor charges against and an owner repays with. On Base Sepolia this is Circle's testnet USDC.
| Token | Address | Decimals |
|---|---|---|
| Base Sepolia USDC (Circle testnet) | 0x036CbD538 | 6 |
- Verify the address against Circle's documentation before you rely on it.
- Amounts are expressed in the token's base units. With 6-decimal USDC, one dollar is
1_000_000n, so a $60 credit line is60n * 1_000_000n. - The owner approves this token to the Encumbra contract before
open, and whoever callsrepayapproves it before repaying.