← Protocols
Coinshift
DAO / Governance·EVM

Coinshift

01Description

Treasury management dashboard built on top of Safe (formerly Gnosis Safe). Multi-Safe portfolio view, mass payouts, accounting/reporting, csUSDL/csUSDC yield assets, and integrations with CoW Swap, 1inch, AAVE, and Superfluid. Targets DAOs and onchain orgs.

02Best for
  • 01Safe-based treasury operations
  • 02multi-safe consolidation
  • 03mass / recurring payouts
  • 04treasury accounting + reporting
  • 05yield on idle stablecoins (csUSDL/csUSDC)
03Install
  • pnpm add @safe-global/safe-core-sdk @safe-global/api-kit viem
04Environment variables
VariableScopeDescription
COINSHIFT_ORG_IDClientCoinshift organization slug used to deep-link into the dashboard.
SAFE_ADDRESSClientAddress of the Safe being managed in Coinshift (the underlying multisig).
05Prompt snippet
Coinshift is a UI/operations layer on top of Safe — there is no public write API. For programmatic flows, build Safe transactions with `@safe-global/safe-core-sdk` + `@safe-global/api-kit` (Safe Transaction Service), then have signers approve them inside the Coinshift dashboard, which renders the same Safe queue. Deep-link users with `https://app.coinshift.xyz/<orgId>/safe/<safeAddress>`. For mass payouts, generate a CSV (recipient, token, amount) and import it via Coinshift's bulk-payout flow, or build the equivalent multi-send Safe tx yourself with `MultiSendCallOnly`. csUSDL and csUSDC are ERC-20 yield-bearing wrappers — treat them like any ERC-4626-style asset for accounting.
06Gotchas
  • There is no public Coinshift SDK — automation must go through the Safe Transaction Service (api-kit) and surface in Coinshift's UI for human signers.
  • Coinshift requires an org-level invite/access; running flows for an external user means they must already be added to the org, not just a Safe owner.
  • Multi-chain Safes are tracked separately — a Safe at the same address on Ethereum and Base shows as two entries; reconcile by `chainId + address`, not address alone.
  • csUSDL/csUSDC are not USDC — bridges, oracles, and accounting tools must be configured for the wrapper token; treating them as native USDC will misprice the treasury.
  • Recurring payouts in Coinshift v2 still require a signer to approve each scheduled tx in the Safe — they are not autonomous (no module is installed by default).
  • Coinshift integrations (CoW, 1inch, Superfluid) are surfaced inside the dashboard; building parallel direct-protocol flows can create duplicate pending Safe txs in the queue.
07Alternatives