Onchain payment infrastructure for teams | $400M+ payment volume secured | non-upgradable permissionless hyperstructure on Ethereum | 13+ EVM chains | the settlement layer under the $UM-Radar hot path



Splits — originally 0xSplits — is onchain payment infrastructure for teams, launched on Ethereum mainnet on 15 February 2022 by co-founders Abram Dawson and Will Minshew. The design is deliberately a hyperstructure: non-upgradable, permissionless, no external maintenance, no intermediary. A canonical SplitMain contract plus one deterministic proxy address per Split route incoming ETH and ERC-20 revenue to preset recipients, so any contract, NFT royalty feed or wallet can pay a Split without an SDK. Splits v2 decouples splitter logic from token storage behind SplitsWarehouse — an immutable ERC-6909 wrapper deployed at the same address across chains — with PullSplit and PushSplit implementations (audited by Zach Obront). The public product surface is now tiered (Treasury / Personal / Protocol) with modules Split, Waterfall and Swapper, an explorer and an app at splits.org and app.splits.org, SDKs under @0xsplits/splits-sdk, and agent-facing tooling (CLI + MCP server + llms.txt) for programmatic transfers with memo and properties. Sends supports private transfers routed through NEAR Confidential Intents, which hides the payer-to-recipient link on-chain while the team still sees recipient and amount in the Splits UI. IMPORTANT READING OF THE NUMBER: the company homepage states 'Over $400m in payment volume secured for businesses'. That is cumulative DISTRIBUTED PAYMENT THROUGHPUT — not a seed round, not a valuation, not revenue, and not profit. Third-party directories recorded lower public floors at earlier dates (>$100M distributed to 50,000+ users; >$250M+ across networks), consistent with a rising throughput curve we have not independently re-measured on-chain this wave. Where Splits sits in the $UM-Radar architecture: it is the SETTLEMENT LAYER, not a radar competitor. The radar hot path is Cloudflare Workers + x402; Splits is the onchain distribution primitive that a payments product would settle through. Public OSINT only — no invented figures, no impersonation of the Splits team, no claim of any partnership with UnicornsMap.com.
| Metrik | Nilai | Dasar |
|---|---|---|
| Payment volume secured (as published) | $400M+ | splits.org homepage, read 2026-09-16 — 'Over $400m in payment volume secured for businesses'. Cumulative distributed throughput, NOT a seed round or valuation. |
| Earlier public floors (context) | >$100M / >$250M+ | Third-party project directories at earlier dates (>$100M distributed to 50,000+ users; >$250M+ across networks) — consistent with a rising curve, not independently re-measured on-chain. |
| Protocol fee (v1 design) | None | Original 0xSplits framing: free to use, no protocol fee, non-upgradable hyperstructure. Current commercial tiers are priced separately on splits.org. |
| Mainnet launch | 2022-02-15 | Launch coverage and project history — Ethereum mainnet. |
| Chain coverage | 13+ EVM chains | Public project directory listing (Ethereum, Arbitrum, Optimism, Polygon, Base, Zora and others). |
| Position in the $UM-Radar stack | Settlement layer | Architecture note, not a measured metric: the radar hot path is Cloudflare Workers + x402; Splits is the onchain distribution primitive a payments flow would settle through. No partnership is claimed. |
🔍 Owner-circulated framing confirmed here: ~$400M protocol throughput is NOT seed capital. The distinction matters because a throughput number is often misread as a raise.
Publicly introduced by Splits as one of the two founders; builds protocol and product. Public X handle @abram.
Publicly described as co-founder and co-CEO alongside Dawson; both write code. Public X handle @wminshew.
Publicly described as a small distributed team (single-digit headcount in 2022 coverage; US + Peru). No headcount figure is claimed for 2026 — we did not source one this wave.
Multi-sig-style treasury workflows for teams: collect revenue into an onchain account and distribute it on rules, with no paperwork and no company required to receive funds.
Individual onchain payment account surface on the same infrastructure.
Integration surface for builders: use the contracts, SDK and modules directly rather than the hosted app.
The single canonical 0xSplits SplitMain contract, deployed across EVM chains; each Split gets its own deterministic proxy address for composability.
Generic immutable ERC-6909 token wrapper that can hold any native or ERC-20 token for any recipient, deployed at the same address across chains.
PullSplit keeps funds in the Warehouse for pull-flow distribution with built-in accounting; PushSplit pushes to recipients with a generous gas limit and Warehouse fallback on failed transfers.
Swapper converts any incoming token into a single output token (oracle starts at Uniswap v3 TWAP, Chainlink planned); Diversifier stacks a Split in front of one or more Swappers so a share of income routes into a different token. Publicly framed as a way to automate tax withholding or salaries.
Send tokens to addresses, ENS names, Farcaster usernames, saved contacts or a connected bank account; multisend to up to 100 recipients with CSV upload, batched under one signature, plus Schedules for recurring payroll-like flows. Private transfers route through NEAR Confidential Intents and hide the payer-recipient link on-chain.
Programmatic API/CLI/MCP access for automated transfers with optional memo and properties, plus llms.txt files so AI agents can read the docs surface.
2 geo-pins — live operational-market GIS network on the $UM-Radar vector map
🔍 Found by Aleksei Dolgikh @alexdolbun
Whether private Sends over NEAR Confidential Intents becomes the default payments path for teams that previously only used transparent Splits — privacy as the funnel, distribution as the durable layer.
Agent tooling (CLI + MCP + llms.txt) as a distribution wedge: if AI agents pick Splits as the payout primitive, throughput compounds without a human in the loop.
HYPOTHESIS, not advice: deterministic per-recipient accounts on immutable contracts either become standing financial infrastructure for teams, or get abstracted away by the smart-account layer above them. Both outcomes are live at the 2036 horizon.
This node belongs to the public Base / Anti Fund builder graph the radar maps. $UM-Radar runs on Base: read the graph, take the next signal, unlock any dossier per-call in USDC.
🤖 AI agents — one call: GET /api/radar/conductor.json
🔍 Public OSINT only. Not investment advice. Not a prediction engine. $UM is a Base token — nothing here is a return projection.
Hanya radar OSINT publik. Bukan nasihat investasi. Bukan mesin prediksi.