---
title: "Shared eng team wallets"
date: "2026-07-16"
canonical: "https://splits.org/blog/shared-eng-team-wallets/"
---

# Shared eng team wallets

An engineer needs ETH on an L2 to test a deployment. Today that means bridging and swapping across multiple apps, or a Slack message to whoever holds the treasury (who then bridges and swaps across multiple apps).

Getting engineers funds—where and how they need them—is hard. Bridging, swapping, gas, approvals, accounting. So teams work around it: engineers spend from personal wallets and file reimbursements; company assets sit in accounts owned by individuals; people share private keys and scramble to rotate when someone leaves. They're all bad.

The goal: keep engineers unblocked without screwing up opsec or creating future accounting headaches.

A shared engineering account is a common pattern we're seeing at Splits. Think Ramp or Brex for onchain spend: a pre-funded account engineers pull from, where you can always see who spent what, when, and why. Here's what we’ve seen works well.

## The setup

Folks typically use either a subaccount inside an existing workspace, or a separate workspace just for eng. The litmus test is whether engineers should see the treasury, since right now everyone in a workspace sees every account, balance, and transaction.

![](https://storage.ghost.io/c/ec/10/ec1004a4-54fe-4879-9efd-9a3fe755a821/content/images/2026/07/image.png)

_Switching between workspaces_

If you're small and flat and visibility isn't a concern, use a subaccount. If you're bigger and don't want everyone seeing everything, give eng its own dedicated workspace and switch between workspaces as needed.

## The account

Most often we see folks using a 1-of-N shared account so that any signer can pull funds as needed. That shared account maintains a small balance that gets topped up periodically from a treasury or operating account (often M-of-N).

With this setup, approvals happen at the account layer (since the budget is pre-approved), making the balance the blast radius.

![](https://storage.ghost.io/c/ec/10/ec1004a4-54fe-4879-9efd-9a3fe755a821/content/images/2026/07/image-1.png)

_Account details, showing each signer_

As a workspace admin, you can require memos on outgoing transactions, forcing the engineer to communicate each transaction's purpose. This friction—setting a memo at the time of transaction—saves time when closing your books at the end of the month.

Adding and removing signers as engineers join and depart is easy. Add their email and set them as a signer on the shared account, and remove them when they leave. Signers stay in sync across all networks, so you're not updating a multisig on five chains every time—it's just a single transaction.

## One balance

The shared eng account typically holds one balance, usually a stablecoin. Crosschain swaps turn it into whatever token is needed, on whatever network, in a single transaction. The paymaster account covers gas, so nobody's hunting for ETH or dealing with dust.

![](https://storage.ghost.io/c/ec/10/ec1004a4-54fe-4879-9efd-9a3fe755a821/content/images/2026/07/image-2.png)

_Sending SOL on Solana from USDC on Base_

## Browser extension

The [browser extension](https://chromewebstore.google.com/detail/splits/ghfacfafnbcgkielpaeifdpoggfeakif) connects the shared wallet to any third-party app so no personal EOA needs to hold company assets. Transactions are simulated before signing, and memos and transaction history sync back to the dashboard, so you still see who did what and why.

![](https://storage.ghost.io/c/ec/10/ec1004a4-54fe-4879-9efd-9a3fe755a821/content/images/2026/07/image-3.png)

_Connect shared wallets to third party apps_

## Cleaner books

Accounting becomes easier when all your transactions have corresponding memos. You can export, categorize, and reconcile into QuickBooks or Xero. Or better yet, add your accountant as a read-only member so they can do this for you.

You can also set rules so every outflow from the eng wallet is coded as R&D, and every top-up from your treasury or operating account is booked as an internal transfer with cost basis intact.

## Why we're excited

We're excited about this simple use case for a few reasons. First, it hints at a bigger problem: delegating in an irreversible, adversarial setting—a public blockchain—is hard. One mistake can mean permanent loss of funds or a compromised account. This is why many CTOs still do their team's onchain ops. This use case demonstrates that our account structure—a series of nested crosschain multisigs that work together beneath an isolated root account and roll up to a single dashboard—is a great solution that remains _entirely_ self-custodial. Seizure-proof self-custody.

Second, we believe this is a preview of how financial accounts will work for agents. An agent is just another engineer pulling from a scoped subaccount. The horrible human-ergonomics of blockchains are what enables them to serve agents better than tradfi ever can. We anticipate tradfi having a very hard time keeping up with agents, since you can't hold agents accountable.