Co-founder, Splits (0xSplits) | onchain payment infrastructure for teams on Ethereum | former SV Angel | the founder node on the $UM-Radar settlement-layer graph
Abram Dawson is a co-founder of Splits (0xSplits), the onchain payment infrastructure layer he has been building with Will Minshew since September 2021. In his own words on anabram.com, he is 'one of the founders of Splits, where we're building financial infrastructure for teams on Ethereum' — and before that he worked at SV Angel, with a self-built van project in between. Splits went live on Ethereum mainnet on 15 February 2022 and the project has since published over $400m in payment volume secured for businesses: that is cumulative distributed throughput, not a raise and not a valuation. He is the protocol-and-product half of a two-person founding pairing that publicly writes the code, and he has spoken on the design philosophy directly — why earlier splitter contracts underperformed, and how the hyperstructure framing (non-upgradable, permissionless, no protocol fee) was chosen so the primitive could run without maintenance. He co-authored the Liquid Splits work with Songcamp, which used NFTs to make ownership inside a split transferable, a pattern that has since become common in music deals. Publicly reachable as @abram on X and Farcaster, and at anabram.com. Public OSINT only — no invented net worth, no invented fund, no claim about his private holdings. He is not affiliated with UnicornsMap.com; this is an independent public dossier, and the graph edge to Splits is the sourced relationship.
Onchain payment infrastructure for teams: hyperstructure Splits on Ethereum mainnet since 15 February 2022, v2 with SplitsWarehouse + PullSplit/PushSplit, modules Split/Waterfall/Swapper, product tiers Treasury/Personal/Protocol. $400M+ payment volume published on splits.org.
He states on anabram.com that he worked at SV Angel before Splits.
NFT-transferable ownership inside a split, built with Songcamp for creative-industry royalty flows — a pattern that became common in music deals.
3 entities geo-pinned · toggle People / Institutions · 37.7749, -122.4194
🔍 Found by Aleksei Dolgikh @alexdolbun
Which of the two founding roles becomes the public face as Splits pushes agent tooling — protocol-first (Dawson) or commercial-first — and what that says about where the value accrues.
Whether the Songcamp-style Liquid Splits pattern (transferable ownership inside a split) returns as the mechanism for tokenised revenue shares in creator and agent economies.
HYPOTHESIS, not advice: a founder who chose an immutable, fee-free primitive over a rentable product is betting that being the substrate outlasts being the app.
🔭 WATCH: agent-side integration count · whether the rail survives its own token · rail volume, not follower count
🔍 Abram Dawson is carried at HIGH confidence on 5 filed sources. The horizon below is a hypothesis with a shelf life, not advice.
Paste the badge on a site, a README or an agent page. It serves live from the edge and links back with its own attribution code.
Machine form: GET /badge/abram-dawson.json
Paste a Base wallet and this record joins your watchlist. Nothing is uploaded, nothing is stored off-chain beyond the list, and removing it is one click.
Paste the badge on a post, a deck or a partner page. The image links home with ?ref=badge-abram-dawson, so every embed is attributed in the referral ledger and every reader lands on this record.
JSON twin: /badge/abram-dawson.json returns the same snippet for a generator.
Paste the badge on a post, a deck or a partner page. The image links home with ?ref=badge-abram-dawson, so every embed is attributed in the referral ledger and every reader lands on this record.
JSON twin: /badge/abram-dawson.json returns the same snippet for a generator.
Paste the badge on your own page. The image is edge-cached SVG, the link carries the attribution code, and the counter moves in the referral ledger.
The record is what it is: Co-founder, Splits (0xSplits) | onchain payment infrastructure for teams on Ethereum | former SV Angel | the founder node on the $UM-Radar settlement-layer graph. Nothing below is filed — it is the shape the seat would take if the current trajectory holds, and it is re-scored every time a new public source lands.
🔭 agent-side integration countExpect the mandate to widen before it deepens. Watch whether Splits (0xSplits) adds an adjacent function to the seat rather than a bigger title on the same one.
🔭 whether the rail survives its own tokenA second mandate is the normal move here — a board seat, a fund-side advisory role, or an operating chair next to the current one. The tell is a first public co-signature, not an announcement.
🔭 rail volume, not follower countFirst capital event window. Either a priced round behind Splits (0xSplits) or a personal vehicle appears. Watch rail volume, not follower count rather than the headline valuation.
🔭 which chain the settlement moves to nextJurisdictional switch is the highest-probability structural change from San Francisco, CA, USA. A second residence, a second entity, or a second currency book (USDC to a settlement unit) is the observable.
🔭 fee take-rate disclosureInstitutional shell forms: a holding vehicle, a family-office wrapper or a named co-investment club. Shells are quiet — the disclosure arrives through registry filings, not posts.
🔭 agent-side integration countDistribution becomes the constraint. At this horizon the question is who carries Splits (0xSplits)'s output and this seat's name, and on what terms. Watch which chain the settlement moves to next.
🔭 whether the rail survives its own tokenSuccession pressure. Either a named deputy appears under the seat or the seat is re-scoped away from day-to-day. Both read as the same signal from outside.
🔭 rail volume, not follower countSecond-order liquidity: secondary sales, a tender, or a strategic minority into Splits (0xSplits). This is where an OSINT file usually goes stale for six months and then re-prices.
🔭 which chain the settlement moves to nextRecord consolidation. By here the file should be readable as a single arc rather than a list of events, and the San Francisco, CA, USA base stops being the interesting part.
🔭 fee take-rate disclosureEnd-of-horizon check. Re-read 2026 against 2036: the useful output is which of the eleven rows actually printed, and which were noise carried by the market rather than the person.
🔭 agent-side integration count🔍 Deterministic horizon model: every row is derived from facts already on this record and re-scored when a new public source lands. No forecast value is asserted.
Buy without a browser: GET /oauth/protected-resource, then tools/call fetch_profile over MCP. Bulk and 402 retries are idempotent on the same slug.
Machine pack: /api/um-radar/agent-pack?slug=abram-dawsonBatch / dataset pricing on request
The dossier prose stays public. The space around it is for sale: locales, frames, video, links, the city slot, the verified badge. Holding $UM cuts the price at quote time - the balance is read from your wallet, nothing is self-declared.
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.
Public OSINT radar only. Not investment advice. Not a prediction engine.
Creator-fee revenue is onchain and verifiable.