Drift

Effortless Ethereum Development Across Web3 Libraries

Write cached Ethereum smart contract interactions once with Drift and run them anywhere. Seamlessly support multiple web3 libraries like viem, web3.js, and ethers—without getting locked into a single provider or rewriting code.

With built-in caching, type-safe contract APIs, and easy-to-use testing mocks, Drift lets you build efficient and reliable applications without worrying about call optimizations or juggling countless hooks. Focus on what matters: creating great features and user experiences.

Why Drift?

Building on Ethereum often means dealing with:

• Optimizing Network Calls: Manually caching calls and optimizing queries to minimize RPC requests slows down development.
• Managing Multiple Hooks: Each contract call often needs its own hook and query key to prevent redundant network requests.
• Complex Testing: Setting up mocks for contract interactions can be cumbersome and error-prone.
• Hard Dependency on a Specific Web3 Library: There are several competing options, like viem, web3.js, ethers.js. Tying your business logic to a specific one creates vendor lock-in and makes it harder to switch down the road.

Drift Solves These Problems

• ⚡ Optimized Performance: Automatically reduces redundant RPC calls with built-in caching. No need to manage hooks or query keys for each call.
• 🔒 Type Safety: Drift's type-checked APIs help catch errors at compile time.
• 🧪 Testing Made Easy: Built-in mocks simplify testing your contract interactions. Drift's testing mocks are also type-safe, ensuring your tests are always in sync with your contracts.
• 🌐 Multi-Library Support: Drift provides a unified interface compatible with multiple web3 libraries. Write your contract logic once and use it across different providers.
• 🔄 Extensibility: Designed to grow with your project's needs, Drift allows you to easily extend support to new web3 libraries by creating small adapter packages.

Table of Contents

• Installation
• Start Drifting
  • 1. Initialize Drift
  • 2. Interact with your Contracts
    • Read Operations with Caching
    • Write Operations
    • Contract Instances
• Example: Building Vault Clients
  • 1. Define core vault clients
  • 2. Use the clients in your application
    • Benefits of This Architecture
  • 3. Extend core clients for library-specific clients
  • 4. Test Your Clients with Drift's Built-in Mocks
    • Example: Testing Client Methods with Multiple RPC Calls
    • Benefits
• Simplifying React Hook Management
  • The Problem Without Drift
  • How Drift Helps
    • Example Using React Query
• Caching in Action
  • Cache Invalidation
  • Preloading Cache Data
• Advanced Usage
  • Custom Cache Implementation
  • Extending Drift for Your Needs
• Contributing
• License

Installation

Install Drift and an optional adapter for your preferred web3 library:

npm install @delvtech/drift

npm install @delvtech/drift-viem # Optional
npm install @delvtech/drift-web3 # Optional
npm install @delvtech/drift-ethers # Optional

[!TIP]

Drift includes a built-in adapter and can be used without installing any additional packages. However, adapters will reuse clients from their corresponding web3 library, which can improve performance depending on their configuration. For example, the publicClient from Viem can automatically batch requests via MultiCall.

Start Drifting

1. Initialize Drift

import { Drift } from "@delvtech/drift";

const drift = new Drift({
  rpcUrl: "[YOUR_RPC_URL]",
});

Viem adapter example:

import { Drift } from "@delvtech/drift";
import { viemAdapter } from "@delvtech/drift-viem";
import { createPublicClient, createWalletClient, http } from "viem";

const publicClient = createPublicClient({
  transport: http(),
});

// optionally create a wallet client
const walletClient = createWalletClient({
  transport: http(),
});

const drift = new Drift({
  adapter: viemAdapter({ publicClient, walletClient }),
});

2. Interact with your Contracts

Read Operations with Caching

import { VaultAbi } from "./abis/VaultAbi";

// No need to wrap in separate hooks; Drift handles caching internally
const balance = await drift.read({
  abi: VaultAbi,
  address: "0xYourVaultAddress",
  fn: "balanceOf",
  args: {
    account: "0xUserAddress",
  },
});

Write Operations

If Drift was initialized with a wallet client, you can perform write operations:

const txHash = await drift.write({
  abi: VaultAbi,
  address: "0xYourVaultAddress",
  fn: "deposit",
  args: {
    amount: BigInt(100e18),
    receiver: "0xReceiverAddress",
  },

  // Optionally wait for the transaction to be mined and invalidate cache
  onMined: () => {
    drift.cache.invalidateRead({
      abi: VaultAbi,
      address: "0xYourVaultAddress",
      fn: "balanceOf",
      args: {
        account: "0xReceiverAddress",
      },
    });
  },
});

Contract Instances

Create contract instances to write your options once and get a streamlined, type-safe API to re-use across your application.

const vault = drift.contract({
  abi: VaultAbi,
  address: "0xYourVaultAddress",
  // ...other options
});

const balance = await vault.read("balanceOf", { account });

const txHash = await vault.write(
  "deposit",
  {
    amount: BigInt(100e18),
    receiver: "0xReceiverAddress",
  },
  {
    onMined: () => {
      vault.invalidateRead("balanceOf", { account: "0xReceiverAddress" });
    },
  },
);

Example: Building Vault Clients

Let's build a simple library agnostic SDK with ReadVault and ReadWriteVault clients using Drift.

1. Define core vault clients

In your core SDK package, define the ReadVault and ReadWriteVault clients using Drift's ReadContract and ReadWriteContract abstractions.

// sdk-core/src/VaultClient.ts
import {
  ContractEvent,
  Drift,
  ReadContract,
  ReadWriteAdapter,
  ReadWriteContract,
} from "@delvtech/drift";
import { vaultAbi } from "./abis/VaultAbi";

type VaultAbi = typeof vaultAbi;

export class ReadVault {
  contract: ReadContract<VaultAbi>;

  constructor(address: string, drift: Drift<ReadAdapter> = new Drift()) {
    this.contract = drift.contract({
      abi: vaultAbi,
      address,
    });
  }

  // Read balance with internal caching
  async getBalance(account: string): Promise<bigint> {
    return this.contract.read("balanceOf", { account });
  }

  // Get all deposit events for an account with internal caching
  async getDeposits(
    account?: string,
  ): Promise<ContractEvent<VaultAbi, "Deposit">[]> {
    return this.contract.getEvents("Deposit", {
      filter: {
        depositor: account,
      },
    });
  }
}

export class ReadWriteVault extends ReadVault {
  declare contract: ReadWriteContract<VaultAbi>;

  constructor(address: string, drift?: Drift<ReadWriteAdapter>) {
    super(address, drift);
  }

  // Make a deposit
  async deposit(amount: bigint, recipient: string): Promise<string> {
    const txHash = await this.contract.write(
      "deposit",
      { amount, recipient },
      {
        // Optionally wait for the transaction to be mined and invalidate cache
        onMined: () => {
          this.contract.invalidateRead("balanceOf", { recipient });
        },
      },
    );

    return txHash;
  }
}

2. Use the clients in your application

Using an adapter, you can integrate Drift with your chosen web3 library. Here's an example using viem:

import { Drift } from "@delvtech/drift";
import { viemAdapter } from "@delvtech/drift-viem";
import { createPublicClient, http } from "viem";
import { ReadVault } from "sdk-core";

const publicClient = createPublicClient({
  transport: http(),
  // ...other options
});

const drift = new Drift({
  adapter: viemAdapter({ publicClient }),
});

// Instantiate the ReadVault client
const readVault = new ReadVault("0xYourVaultAddress", drift);

// Fetch user balance
const userBalance = await readVault.getBalance("0xUserAddress");

// Get deposit history
const deposits = await readVault.getDeposits("0xUserAddress");

Benefits of This Architecture

• Reusability: Write your business logic once and reuse it across different environments. Easily extend support to new web3 libraries by creating small adapter packages.
• Simplicity: Your application code stays clean and focused on business logic rather than on optimizing network calls or managing cache keys.
• Flexibility: Your core logic remains untouched when switching web3 libraries.

3. Extend core clients for library-specific clients

To provide library specific client packages, e.g., sdk-viem, extend the core clients and overwrite their constructors to accept viem clients.

// sdk-viem/src/VaultClient.ts
import {
  ReadVault as CoreReadVault,
  ReadWriteVault as CoreReadWriteVault,
} from "sdk-core";
import { Drift } from "@delvtech/drift";
import { viemAdapter } from "@delvtech/drift-viem";
import { PublicClient, WalletClient } from "viem";

export class ReadVault extends CoreReadVault {
  constructor(address: string, publicClient: PublicClient) {
    const drift = new Drift({
      adapter: viemAdapter({ publicClient }),
    });
    super(address, drift);
  }
}

export class ReadWriteVault extends CoreReadWriteVault {
  constructor(
    address: string,
    publicClient: PublicClient,
    walletClient: WalletClient,
  ) {
    const drift = new Drift({
      adapter: viemAdapter({ publicClient, walletClient }),
    });
    super(address, drift);
  }
}

Then, in your app:

import { ReadVault } from "sdk-viem";
import { createPublicClient, http } from "viem";

const publicClient = createPublicClient({
  transport: http(),
  // ...other options
});

// Instantiate the ReadVault client with viem directly
const readVault = new ReadVault("0xYourVaultAddress", publicClient);

4. Test Your Clients with Drift's Built-in Mocks

Testing smart contract interactions can be complex and time-consuming. Drift simplifies this process by providing built-in mocks that allow you to stub responses and focus on testing your application logic.

[!IMPORTANT]

Drift's testing mocks have a peer dependency on sinon. Make sure to install it before using the mocks.

npm install --save-dev sinon

Example: Testing Client Methods with Multiple RPC Calls

Suppose you have a method getAccountValue in your ReadVault client that get's the total asset value for an account by fetching their vault balance and converting it to assets. Under the hood, this method makes multiple RPC requests.

Here's how you can use Drift's mocks to stub contract calls and test your method:

// sdk-core/src/ReadVault.test.ts
import { MockDrift } from "@delvtech/drift/testing";
import { vaultAbi } from "./abis/VaultAbi";
import { ReadVault } from "./VaultClient";

test("getUserAssetValue should return the total asset value for a user", async () => {
  // Set up mocks
  const mockDrift = new MockDrift();
  const mockContract = mockDrift.contract({
    abi: vaultAbi,
    address: "0xVaultAddress",
  });

  // Stub the vault's return values
  mockContract.onRead("balanceOf", { account: "0xUserAddress" }).resolves(
    BigInt(100e18), // User has 100 vault shares
  );
  mockContract.onRead("convertToAssets", { shares: BigInt(100e18) }).resolves(
    BigInt(150e18), // 100 vault shares are worth 150 in assets
  );

  // Instantiate your client with the mocked Drift instance
  const readVault = new ReadVault("0xVaultAddress", mockDrift);

  // Call the method you want to test
  const accountAssetValue = await readVault.getAccountValue("0xUserAddress");

  // Assert the expected result
  expect(accountAssetValue).toEqual(BigInt(150e18));
});

Benefits

• No Network Calls: Tests run faster and more reliably without actual network interactions.
• Focus on Logic: Concentrate on testing your application's business logic.
• Easy Setup: Minimal configuration required to get started with testing.

Simplifying React Hook Management

The Problem Without Drift

In traditional setups, you might rely on data-fetching libraries like React Query. However, to prevent redundant network requests, each contract call would need:

• Its own hook (e.g., useBalanceOf, useTokenSymbol).
• Unique query keys for caching.

Composing multiple calls becomes cumbersome, as you have to manage each hook's result separately.

How Drift Helps

Drift's internal caching means you don't need to wrap every contract call in a separate hook. You can perform multiple contract interactions within a single function or hook without worrying about redundant requests.

Example Using React Query

import { useQuery } from "@tanstack/react-query";
import { ReadVault } from "sdk-core";

function useVaultData(readVault: ReadVault, userAddress: string) {
  return useQuery(["vaultData", userAddress], async () => {
    // Perform multiple reads without separate hooks or query keys
    const [balance, symbol, deposits] = await Promise.all([
      readVault.getBalance(userAddress),
      readVault.contract.read("symbol"),
      readVault.getDeposits(userAddress),
    ]);

    return { balance, symbol, deposits };
  });
}

No need to manage multiple hooks or query keys — Drift handles caching internally, simplifying your code and development process.

Caching in Action

Drift's caching mechanism ensures that repeated calls with the same parameters don't result in unnecessary network requests, even when composed within the same function.

// Both calls use the cache; only one network request is made
const balance1 = await contract.read("balanceOf", { account });
const balance2 = await contract.read("balanceOf", { account });

Cache Invalidation

// Invalidate the cache for a specific read
contract.invalidateRead("balanceOf", { account });

// Invalidate all reads matching partial arguments
contract.invalidateReadsMatching("balanceOf");

// Let it all go...
contract.cache.clear();

Preloading Cache Data

Data such as immutables from token lists can be preloaded into the cache to avoid network requests without changing how the data is accessed.

const drift = new Drift(/* ... */);
const contract = drift.contract({
  abi: erc20Abi,
  // ...
});

// Preloading read data //

// Drift
drift.cache.preloadRead({
  abi: erc20.abi,
  fn: "symbol",
  value: "DAI",
  // ...
});

// Contract
contract.preloadRead({ fn: "symbol", value: "DAI" });

// Preloading event data //

// Drift
drift.cache.preloadEvents({
  abi: erc20.abi,
  event: "Transfer",
  value: [],
  // ...
});

// Contract
contract.preloadEvents({
  event: "Transfer",
  value: [],
  // ...
});

[!IMPORTANT]

Preloading data affects all clients that share the same cache. Since Drift passes its own cache to the contracts it creates via Drift.contract() by default, they'll already be preloaded with the Drift instance's cache and any data preloaded with the contract will also be preloaded for the Drift instance.

Advanced Usage

Custom Cache Implementation

If you have specific caching needs, you can provide your own cache implementation:

import { LRUCache } from "lru-cache";

const customCache = new LRUCache({ max: 500 });
const drift = new Drift({
  cache: customCache,
});

Extending Drift for Your Needs

Drift is designed to be extensible. You can build additional abstractions or utilities on top of it to suit your project's requirements.

Contributing

Got ideas or found a bug? Check the Contributing Guide to get started.

License

Drift is open-source software licensed under the Apache 2.0.