# V-Sum — Long-form feed This is the machine-readable long-form feed of V-Sum content. It contains full summaries and timestamped chapter breakdowns for every technical briefing, plus interview summaries. Designed for single-fetch retrieval by AI agents. - Short index: https://v-sum.com/llms.txt - Public Data API (read-only JSON): https://api.v-sum.com · OpenAPI: https://api.v-sum.com/spec.json - MCP server: https://v-sum.com/mcp - Briefings: 67 · Events: 23 · Interviews: 0 - Last generated: 2026-05-19T21:18:22.542Z --- # Briefings ## V-Sum One — October 14, 2020 Event page: https://v-sum.com/events/one ### Nivelo — Nivelo Technical Briefing - Slug: `v-nivelo` - URL: https://v-sum.com/briefing/v-nivelo - Presenter: Eli Polanco (LinkedIn: https://www.linkedin.com/in/elipolanco/) - YouTube: https://www.youtube.com/watch?v=xlrwHjRaZ5s - Tags: payments, compliance Nivelo presents real-time ACH risk detection for payroll processors, ACH originators, and third-party senders. Instead of waiting the usual four-to-five-day ACH settlement window to find out a payment has failed, Nivelo's single API scores each debit and credit at the moment of origination — sub-second — combining identity, account, device, and behavioral signals into a machine-learned expected-loss score. The demo walks through a payroll processor flow (think ADP or Gusto) catching impersonation fraud at origination, triggering a real-time phone verification with the employee, and then exposing full score explainability in Nivelo's developer dashboard so ops teams can tune against false positives without a black-box model. Because Nivelo plugs in before the ACH batch file is built, it can act on richer payload data — payer/payee relationship, portal behavior, last account change — that the ACH network itself never sees. **Chapters:** - **[0:00] Introduction to Nivelo — real-time ACH risk** — https://www.youtube.com/watch?v=xlrwHjRaZ5s&t=0s Nivelo is an API company focused on real-time ACH risk detection, partnering with ACH processors, large originators, and third-party senders. The aim: bypass the 4-5 day ACH settlement wait by scoring each payment at origination. - **[1:00] Embedded in the payment flow, business-first** — https://www.youtube.com/watch?v=xlrwHjRaZ5s&t=60s Why Nivelo built API-first — so partners embed risk scoring into their existing origination flow — and why the first use cases target business payments rather than consumer. - **[1:30] Payroll as the first use case** — https://www.youtube.com/watch?v=xlrwHjRaZ5s&t=90s Payroll processors like ADP and Gusto manage both a debit side (funding from the employer) and a credit side (payout to employees) — Nivelo scores both in a single per-transaction call rather than a batch. - **[2:30] Origination-side payee registry and behavioral data** — https://www.youtube.com/watch?v=xlrwHjRaZ5s&t=150s At origination the payroll processor already has live employee data — names, account/routing numbers, contract type, and self-service portal behavior. Nivelo taps into all of it the moment a payment is initiated. - **[4:30] Sub-second ML scoring at origination** — https://www.youtube.com/watch?v=xlrwHjRaZ5s&t=270s Instead of micro-deposits or account-aggregator onboarding checks, Nivelo's API returns a sub-second expected-loss score per transaction — account validity, identity, fraud flow (synthetic identity, account takeover, business email compromise). - **[6:00] Real-time phone verification workflow** — https://www.youtube.com/watch?v=xlrwHjRaZ5s&t=360s Live demo of Nivelo flagging likely impersonation fraud on a payroll payment and prompting the originator to run phone verification with the employee before releasing funds — rather than hearing about the failure days later via an ACH return code. - **[8:00] Developer dashboard with score explainability** — https://www.youtube.com/watch?v=xlrwHjRaZ5s&t=480s The developer dashboard lets support staff drill into any flagged transaction, compare its score against others, and see exactly which signals drove the return — no black-box model. - **[9:30] Richer-than-ACH payload at origination** — https://www.youtube.com/watch?v=xlrwHjRaZ5s&t=570s Because Nivelo taps in before the ACH batch file is built, it can send extra data the ACH network never sees — payer/payee relationship, portal interaction history, last account change — and get an immediate risk ping back. ### Moov — Moov Technical Briefing - Slug: `v-moov` - URL: https://v-sum.com/briefing/v-moov - Presenter: Wade Arnold & Graham McBain - Company: https://moov.io - YouTube: https://www.youtube.com/watch?v=EhaPkqLRNk0 - Tags: payments, banking-as-a-service, developer-tools Wade Arnold (ex-Banno, Billgo) and Graham McBain present Moov — a thousand-strong open-source community that has shipped 37 low-level libraries covering the protocols that quietly move money through the US financial system: ACH, wires, image cash letter, Metro 2, IRS FIRE, ISO 20022, and ISO 8583. Wade walks through why none of this was open source before, how the libraries have been battle-tested against the full transaction volumes of Bank of America, PayPal, Square, and Visa, and why the community model beats every fintech writing its own parser from scratch (e.g., Square unifying seven different ACH implementations onto Moov). Graham then demos the Moov ACH library as a Docker image — curl a JSON payload in, get a NACHA-compliant ACH file back — and a WebAssembly-powered in-browser ACH parser that converts ACH to JSON without any data leaving your machine. **Chapters:** - **[0:00] Introduction to Moov — open-source payments plumbing** — https://www.youtube.com/watch?v=EhaPkqLRNk0&t=0s Wade Arnold introduces Moov. After successful exits with Banno (acquired by Jack Henry) and Billgo, Wade started angel-investing in fintechs and saw every founder spend half their funding round building the same low-level plumbing. - **[1:00] 37 open-source libraries covering the entire US payment stack** — https://www.youtube.com/watch?v=EhaPkqLRNk0&t=60s Moov has open-sourced 37 low-level libraries covering ACH, wire, image cash letter, Metro 2 credit reporting, IRS FIRE, ISO 20022, and ISO 8583 — the protocols that quietly move money through the US financial system. - **[1:30] Community validation at Bank of America scale** — https://www.youtube.com/watch?v=EhaPkqLRNk0&t=90s Moov's libraries have been battle-tested against full transaction volumes from Bank of America, PayPal, Square, and Visa — a thousand-strong community contributing fixes for edge cases like FIS using the wrong character return. - **[3:00] Making financial services less of a black box** — https://www.youtube.com/watch?v=EhaPkqLRNk0&t=180s Why financial services has historically been opaque — COBOL and RPG on mainframes — and why Moov believes reference implementations plus documentation are worth more than yet-another-proprietary-vendor. - **[4:00] Production use cases: ML on SWIFT, unifying ACH at Square** — https://www.youtube.com/watch?v=EhaPkqLRNk0&t=240s Real-world examples — machine-learning models trained on three years of SWIFT transactions via Moov libraries, and Square unifying seven different ACH implementations (collected through acquisitions) onto a single code base. - **[6:00] Watchman — community-maintained global watchlist** — https://www.youtube.com/watch?v=EhaPkqLRNk0&t=360s Graham McBain demos Moov's Watchman project: a global sanctions/watchlist service. When one company needed a list that wasn't included, they contributed it back, getting all the other lists as a bonus. - **[8:30] ACH file formats, character-limited from the punch-card era** — https://www.youtube.com/watch?v=EhaPkqLRNk0&t=510s A quick tour of the ACH file format — still character-limited, a living artifact of the punch-card era — and why a parser library beats every fintech writing it from scratch. - **[9:30] ACH library demo: Docker + curl + JSON** — https://www.youtube.com/watch?v=EhaPkqLRNk0&t=570s Live demo of Moov's ACH library running as a Docker container: POST customer data as JSON, get back a NACHA-compliant ACH file, or parse an existing ACH file into JSON for your web application. - **[11:30] WebAssembly in-browser ACH parser** — https://www.youtube.com/watch?v=EhaPkqLRNk0&t=690s A WebAssembly-compiled in-browser ACH parser — paste an ACH file in, get JSON out, without any data leaving your local machine. Same approach available for image cash letter and other projects. ### Modern Treasury — Modern Treasury Technical Briefing - Slug: `v-moderntreasury-one` - URL: https://v-sum.com/briefing/v-moderntreasury-one - Presenter: Matt Marcus - Company: https://www.moderntreasury.com/ - YouTube: https://www.youtube.com/watch?v=BQaZWWspuCo - Tags: payments, treasury, developer-tools Matt Marcus, co-founder of Modern Treasury, walks through the Modern Treasury payment operations platform and demos real-time payments (RTP) over The Clearing House's rails. Modern Treasury is a third-party service provider that deliberately stays out of the flow of funds — one API and dashboard connecting into roughly a dozen corporate banks from JPMorgan Chase and Wells Fargo down to niche partners, across ACH, wires, EFT in Canada, Bacs in the UK, and proprietary formats like Silvergate's SEN. The demo races a $1 RTP payment to Matt's Chase and Bank of America accounts via the Payment Orders API, walks through the Postman call (amounts in cents, JPMorgan Chase as the originating bank, credit-only, $100k cap, no returns, synchronous success or failure), and closes with the Modern Treasury "dollar demo," where every viewer can pay themselves a real $1 over RTP if their bank supports receiving it. **Chapters:** - **[0:00] Introduction to Modern Treasury** — https://www.youtube.com/watch?v=BQaZWWspuCo&t=0s Matt Marcus, co-founder of Modern Treasury, introduces the Modern Treasury payment operations platform — one API and dashboard for fintechs, neobanks, crypto exchanges, lenders, and online marketplaces that move money. - **[0:30] Origin story — LendingHome, reconciliation, fraud** — https://www.youtube.com/watch?v=BQaZWWspuCo&t=30s Why the founders built Modern Treasury after LendingHome — moving money is hard, but the work around money movement (fraud, reconciliation, accounting journal entries, "where's my money" support) is harder, and nothing off-the-shelf existed. - **[1:30] Not in the flow of funds** — https://www.youtube.com/watch?v=BQaZWWspuCo&t=90s Why Modern Treasury deliberately is not a BaaS — it's a third-party service provider connecting into ~12 corporate banks from JPMorgan Chase and Wells Fargo down to niche partners, not holding customer funds. - **[2:00] Payment types: ACH, wires, EFT, Bacs, SEN** — https://www.youtube.com/watch?v=BQaZWWspuCo&t=120s The full payment-type catalogue — ACH and wires in the US, EFT in Canada, Bacs in the UK, and proprietary bank formats like Silvergate's SEN for crypto. - **[2:30] Real-time payments via The Clearing House** — https://www.youtube.com/watch?v=BQaZWWspuCo&t=150s The focus of the demo: RTP on The Clearing House rails — live for a few years, 24/7/365 including bank holidays, used by PayPal and others to disburse funds instantly. - **[3:30] Payment Orders API — RTP Postman demo** — https://www.youtube.com/watch?v=BQaZWWspuCo&t=210s Walk-through of Modern Treasury's Payment Orders API sending two RTP payments — a race between Chase and Bank of America, originating from Modern Treasury's JPMorgan Chase account in cents. - **[6:00] RTP limits: $100k, credit-only, irreversible** — https://www.youtube.com/watch?v=BQaZWWspuCo&t=360s What makes RTP different from ACH: $100k cap per payment, credit-only (no debits — the protocol has a separate Request-for-Payment flow), synchronous success/failure, and irreversible once settled. - **[8:00] The dollar demo — audience pays itself $1 over RTP** — https://www.youtube.com/watch?v=BQaZWWspuCo&t=480s Audience participation: viewers enter their name, email, and bank details (Plaid-connected or manual routing/account) on modern-treasury.com/dd to receive a real $1 RTP payment. ## V-Sum Two — November 17, 2020 Event page: https://v-sum.com/events/two ### Paxos — Paxos Technical Briefing - Slug: `v-paxos-two` - URL: https://v-sum.com/briefing/v-paxos-two - Presenter: Zach Kwartler - Company: https://www.paxos.com - YouTube: https://www.youtube.com/watch?v=5xAvatzAeOE - Tags: stablecoins, crypto-infrastructure, compliance Zach Portler, product lead at Paxos, introduces Paxos as the regulated-custodian gateway between physical and digital assets, built for the multi-decade migration of $600T of assets from closed ledgers to public blockchains. Paxos is unusual in offering regulated custody and tokenization across four asset classes — crypto, cash, commodities, and securities — including USD-backed stablecoins (wire in, Paxos mints 1:1-redeemable tokens) and Pax Gold (PAXG), where tokenized gold balances on Ethereum are backed by physical gold in an unallocated account. This earlier briefing zooms in on the PayPal crypto partnership Paxos powers: the Paxos admin portal's signing ceremony for moving assets between banks and blockchains, and the four Paxos API endpoints PayPal uses under the hood (list-historical-prices for the chart, list-quotes to price a buy, create-quote-executions for the actual order, tickers for real-time holdings). **Chapters:** - **[0:00] Introduction to Paxos — regulated custodian gateway** — https://www.youtube.com/watch?v=5xAvatzAeOE&t=0s Zach Portler, product lead at Paxos, introduces Paxos — a regulated custodian acting as the gateway between physical and digital assets. The thesis: over the next two decades, a significant portion of the world's $600T of assets will migrate from closed ledgers to public blockchains. - **[1:00] Multi-asset custodian — crypto, cash, commodities, securities** — https://www.youtube.com/watch?v=5xAvatzAeOE&t=60s Paxos is unusual in that it offers regulated custody and tokenization across four asset classes — crypto, cash, commodities, securities. The goal is to be a one-stop shop for any digital asset a customer wants to hold, tokenize, or mobilize. - **[1:30] USD stablecoin mint and redeem flow** — https://www.youtube.com/watch?v=5xAvatzAeOE&t=90s Example flow: wire $1M to Paxos, Paxos mints USD-backed tokens on Ethereum and transfers them to your wallet. Anyone holding those tokens can return them to Paxos for 1:1 USD redemption — backed by the fact Paxos is regulated like a bank. - **[2:30] PayPal crypto partnership — the demo** — https://www.youtube.com/watch?v=5xAvatzAeOE&t=150s Paxos powers PayPal's crypto offering, which rolled out to US users in mid-October 2021 across web and mobile. The demo walks through buying $5 of Bitcoin directly in the PayPal app. - **[4:00] API walkthrough — historical prices endpoint** — https://www.youtube.com/watch?v=5xAvatzAeOE&t=240s The price chart in PayPal comes from /list-historical-prices with a BTC-USD pair and a requested data-point count — a time series ready for UI visualization. - **[5:00] Quotes endpoint — buy/sell price with expiration** — https://www.youtube.com/watch?v=5xAvatzAeOE&t=300s When a user requests a buy, PayPal hits Paxos's /list-quotes endpoint for BTC-USD. Paxos returns a quote with buy side, sell side, price, base and quote assets, and an expiration time. - **[5:30] Create quote execution — POST to buy** — https://www.youtube.com/watch?v=5xAvatzAeOE&t=330s Clicking Buy fires /create-quote-executions — the POST that actually orders the trade. The body references the quote ID and the USD amount; Paxos returns a report with the buy price, quantity, and USD debited. - **[6:30] Tickers endpoint for real-time holdings** — https://www.youtube.com/watch?v=5xAvatzAeOE&t=390s Returning to the PayPal holdings screen, PayPal calls Paxos's /tickers endpoint for best bid/ask to construct a real-time asset price — the visible UX, driven by a simple API. - **[7:00] Paxos signing ceremony — treasury operations** — https://www.youtube.com/watch?v=5xAvatzAeOE&t=420s A look inside the Paxos admin portal: the signing ceremony page operations uses multiple times a day to move assets between banks and blockchains. The network graph visualizes Paxos's holdings per chain. - **[7:30] PAXG (Pax Gold) — tokenized commodity** — https://www.youtube.com/watch?v=5xAvatzAeOE&t=450s Walk-through of PAXG, Paxos's tokenized gold: on-chain crypto addresses hold tokenized gold balances, while an unallocated gold account tracks the physical bars backing every token 1:1. ### DriveWealth — DriveWealth Technical Briefing - Slug: `v-drivewealth` - URL: https://v-sum.com/briefing/v-drivewealth - Presenter: John Shammas (LinkedIn: https://www.linkedin.com/in/jjshammas/) - Company: https://www.drivewealth.com - YouTube: https://www.youtube.com/watch?v=SPFMNNAr1oE - Tags: investing, capital-markets, embedded-finance John, product lead at DriveWealth, demos DriveWealth — the brokerage infrastructure behind Cash App investing in the US, Revolut in Europe, and a long list of wallets across Africa, South America, India, and Southeast Asia. The demo uses a sample banking app with an $845 balance to show how a customer goes from pure checking to buying $50 of Starbucks stock without leaving the app. Because the bank already holds identity data, DriveWealth\'s onboarding only collects brokerage-specific disclosures (SSN confirmation, broker/politician questions) — creating a tax-and-regulator-ready brokerage account in seconds. The account.managementType flag switches between self-directed and managed (robo-advisor) flows on the same API surface. DriveWealth was the first to offer real-time fractional shares: a $50 market order for Starbucks is recalculated against the live price so users never over- or under-spend. Shares are stored to ten decimal places (inspired by crypto UX), enabling pennies-of-Berkshire orders. Live P/L, cost basis, and market value surface in both the partner app and DriveWealth\'s admin portal. **Chapters:** - **[0:00] Introduction to DriveWealth** — https://www.youtube.com/watch?v=SPFMNNAr1oE&t=0s John introduces DriveWealth — the brokerage infrastructure behind investing features in Cash App in the US, Revolut in Europe, and many more wallets across Africa, South America, India, and Southeast Asia. - **[1:00] Banking app + investing demo setup** — https://www.youtube.com/watch?v=SPFMNNAr1oE&t=60s The demo app is a sample banking experience with a checking balance and recent spending. Partners have full control over the customer UI; DriveWealth powers the brokerage primitives underneath. - **[2:00] Rebundling of fintech — banking + investing** — https://www.youtube.com/watch?v=SPFMNNAr1oE&t=120s Modern wallets and neobanks are rebundling savings, lending, and investing under one app. The demo shows how an existing banking customer goes from holding cash to holding an equity position without leaving the app. - **[3:00] Onboarding in seconds with reused KYC** — https://www.youtube.com/watch?v=SPFMNNAr1oE&t=180s Because the banking partner already has name, address, tax ID, and contact info, DriveWealth only collects brokerage-specific questions (SSN confirmation, broker/politician disclosures). One tap opens a fully compliant brokerage account. - **[4:30] Self vs. managed accounts — APIs under the hood** — https://www.youtube.com/watch?v=SPFMNNAr1oE&t=270s The same API surface creates either a self-directed account (user picks trades) or a managed account (robo-advisor or human advisor directs trades). Setting account.managementType tells DriveWealth which tax and regulatory reporting applies. - **[6:30] Fractional shares and dollar-based investing** — https://www.youtube.com/watch?v=SPFMNNAr1oE&t=390s DriveWealth was the first company to offer real-time fractional-share trading. The demo buys $50 of Starbucks stock — no share quantity required — and explains why a $50 order that moves to $51 mid-market should never reject on a new investor. - **[8:00] Crypto-style granularity — Berkshire Hathaway A in pennies** — https://www.youtube.com/watch?v=SPFMNNAr1oE&t=480s Inspired by crypto-first investors, DriveWealth quotes shares out to ten decimal places and processes dollar-denominated orders as small as one cent of BRK.A — democratizing previously unreachable securities. - **[9:00] Live position and P/L** — https://www.youtube.com/watch?v=SPFMNNAr1oE&t=540s Immediately after execution, the user sees the new Starbucks position with live market value, cost basis, and profit/loss. The same data surfaces in DriveWealth's admin portal for partner operations staff. ### Phixius — Phixius Technical Briefing - Slug: `v-phixius` - URL: https://v-sum.com/briefing/v-phixius - Presenter: Peter Tapling & George Throckmorton (LinkedIn: https://www.linkedin.com/in/ptap/) - YouTube: https://www.youtube.com/watch?v=jpcorsL2Lag - Tags: data-infrastructure, compliance George (Nacha) and Peter demo Phixius — Nacha\'s business-focused data-services network for financial institutions, fintechs, and payment networks. Where consumer open banking addresses account holders, Phixius addresses the payment-provider side: exchanging data (ACH account validation, electronic payment information, etc.) between Credentialed Service Providers (CSPs) before a payment hits the rail. Phixius is point-to-point — no centralized storage, no give-to-get model. It combines standardized Nacha APIs with a blockchain/shared-ledger layer used for authentication, audit trail, and rule enforcement. Each request uses an authentication token that is effectively the address of a smart contract between the requesting CSP and responding CSP for that specific purpose. The demo runs two exchange services: an ACH account validation (routing + account → valid/invalid for Nacha), and an Electronic Payment Information exchange where Care-Free Catering at High-Rise Bank subscribes to payment info for Best Spreads at Low-Rise Credit Union — replacing the PDF-form email loop with an authoritative API exchange. A smart-contract subscription fires a notification when Best Spreads adds Zelle to their profile, proving the ongoing-update pattern. **Chapters:** - **[0:00] Introduction to Nacha and Phixius** — https://www.youtube.com/watch?v=jpcorsL2Lag&t=0s George introduces Nacha as the governance body for the US ACH network. Phixius is Nacha's newer utility — a business-focused data-services network (not consumer open banking) that enables financial institutions, fintechs, and payment networks to exchange data related to electronic payments. - **[1:30] Point-to-point architecture — no central storage** — https://www.youtube.com/watch?v=jpcorsL2Lag&t=90s Connected participants are payment providers (banks, fintechs, networks) — not end customers. Phixius does not move money and does not centrally store any exchanged data. It is a point-to-point network between Credentialed Service Providers (CSPs) using open APIs. - **[3:00] Standardized APIs over blockchain audit trail** — https://www.youtube.com/watch?v=jpcorsL2Lag&t=180s Peter explains the tech: standardized Nacha APIs define "exchange services" (single or collection of APIs for a use case). Blockchain/shared-ledger functionality replaces centralized storage — used for auditability, trust, and enforcing rules across CSPs. - **[4:30] ACH Account Validation exchange service** — https://www.youtube.com/watch?v=jpcorsL2Lag&t=270s The first demo: an ACH account-validation exchange service. A CSP submits a routing+account combination and the responding CSP confirms it's valid to accept Nacha requests — surfaced via a green toaster in the UI. - **[6:00] Smart-contract-based authentication tokens** — https://www.youtube.com/watch?v=jpcorsL2Lag&t=360s Each request requires an authentication token that is effectively the address of a smart contract between the requesting and responding CSPs for that specific purpose — providing both access control and the audit trail for dispute resolution. - **[7:30] Electronic Payment Information exchange service** — https://www.youtube.com/watch?v=jpcorsL2Lag&t=450s A second exchange service lets a buyer's bank (High-Rise) request payment info for a vendor (Best Spreads) whose financial institution is Low-Rise Credit Union — replacing the classic PDF-form email dance with a trusted API exchange. - **[8:30] Smart contract subscription — notify on profile change** — https://www.youtube.com/watch?v=jpcorsL2Lag&t=510s When Care-Free Catering subscribes to Best Spreads' EPI, a smart contract notifies them any time the vendor's payment profile changes — demoed by adding Zelle as a new payment method and seeing the subscriber get an "action required" update. ## V-Sum Three — January 19, 2021 Event page: https://v-sum.com/events/three ### Triple Blind — Triple Blind Technical Briefing - Slug: `v-tripleblind` - URL: https://v-sum.com/briefing/v-tripleblind - Presenter: Riddhiman Das (LinkedIn: https://www.linkedin.com/in/rdasxy/) - YouTube: https://www.youtube.com/watch?v=JhFSmaZQ4Sk - Tags: data-infrastructure, compliance TripleBlind demos a cryptographic platform for privacy-preserving data and algorithm exchange — an alternative to the status-quo model of decrypting and replicating third-party data (the Capital One / Experian problem). TripleBlind\'s novel one-way encryption is homomorphic-like but roughly a trillion times faster than full homomorphic encryption, and it works across text, voice, video, and images. The data can only be used for the purpose explicitly authorized, and algorithms themselves can also be encrypted — protecting IP and training data from reverse-engineering. The live demo uses Kaggle\'s customer-transaction-prediction dataset split across three mock organizations (Standard Chartered, JPMorgan Chase, BNP Paribas) running in three different browsers. Privacy-preserving EDA lets a data scientist see shape, distribution, and plots without seeing individual records. A feed-forward neural network (dense + ReLU layers) is trained across all three parties — each granting cryptographic consent with a justification — and produces a privacy-preserving PyTorch object that can be used for local inference or secure multi-party compute predictions (both algorithm and data stay hidden from each other). Training runs in minutes where FHE would take weeks, and the code is drop-in compatible with PyTorch, Pandas, TensorFlow, and XGBoost — GDPR, CCPA, and FDIC compliant. **Chapters:** - **[0:00] Introduction to TripleBlind** — https://www.youtube.com/watch?v=JhFSmaZQ4Sk&t=0s TripleBlind enforces privacy cryptographically across every data-and-algorithm exchange. Where Capital One today decrypts Experian credit files and creates replicas inside its own systems (creating GDPR and privacy risks), TripleBlind lets parties operate on data while it stays encrypted. - **[1:00] Novel one-way encryption — trillion× faster than FHE** — https://www.youtube.com/watch?v=JhFSmaZQ4Sk&t=60s TripleBlind has built a new kind of encryption that works on text, voice, video, or images — homomorphic-like in spirit but roughly a trillion times faster than full homomorphic encryption. Data can only ever be used for the purpose explicitly authorized. - **[1:30] Algorithms can also be encrypted** — https://www.youtube.com/watch?v=JhFSmaZQ4Sk&t=90s Not just the data — the algorithm itself can be encrypted, protecting the IP inside the model and the training data from reverse-engineering attacks. This is zero-trust for vendor/third-party data partnerships. - **[2:30] Kaggle-based customer transaction prediction** — https://www.youtube.com/watch?v=JhFSmaZQ4Sk&t=150s The demo uses a public Kaggle customer transaction prediction dataset. The problem: banks want to use each other's data to improve predictions, but sharing under CCPA/GDPR and competitive concerns forces most teams to use synthetic data — which loses accuracy. - **[4:00] Three-organization data fusion across browsers** — https://www.youtube.com/watch?v=JhFSmaZQ4Sk&t=240s Three browser windows (Edge, Brave, Chrome) represent three organizations. The demo shows bringing datasets together under TripleBlind — preserving privacy across all three parties while still training on real data. - **[4:30] Data discovery with privacy-preserving EDA** — https://www.youtube.com/watch?v=JhFSmaZQ4Sk&t=270s A data scientist can explore size, shape, layout, and distribution of a dataset via privacy-preserving EDA — viewing plots and descriptive statistics that never leak individual records in the clear. - **[6:30] Training a deep neural network across parties** — https://www.youtube.com/watch?v=JhFSmaZQ4Sk&t=390s A feed-forward neural network (dense + ReLU layers, loss function, target column) is trained across the three mocked banks (Standard Chartered, JPMorgan Chase, BNP Paribas). Each org grants cryptographic consent with a justification before the join occurs. - **[8:00] Trained PyTorch object — local and MPC inference** — https://www.youtube.com/watch?v=JhFSmaZQ4Sk&t=480s The output is a PyTorch-trained object that preserves privacy — no reverse engineering is possible. Predictions can run locally against data that never leaves the user, or via secure multi-party compute where both the algorithm and the data stay hidden from each other. - **[10:30] Speed, PyTorch compatibility, and compliance** — https://www.youtube.com/watch?v=JhFSmaZQ4Sk&t=630s The key differentiators: homomorphic-grade privacy in minutes (not weeks), drop-in compatibility with PyTorch / Pandas / TensorFlow / XGBoost, GDPR/CCPA/FDIC-compliant data sharing, and reduced bias by accessing data previously locked behind privacy concerns. ### Transparent Financial Systems — Transparent Financial Systems Technical Briefing - Slug: `v-transparent` - URL: https://v-sum.com/briefing/v-transparent - Presenter: Jeff Kramer (LinkedIn: https://www.linkedin.com/in/jeff-kramer-2518422/) - YouTube: https://www.youtube.com/watch?v=t4uNZLJ7CiQ - Tags: payments, banking-as-a-service Jeff Kramer, CTO of Transparent Financial Systems, demos Zand — a community-based B2B platform for real-time value transfers running 24/7/365. Zand networks are designed by and for their transactional community: forex and crypto OTC desks, networks of community and regional banks, and more. There is no central issuer, no new currency, no intermediaries — just programmable digital dollars under the community\'s control. Banks do not install new software; Zand only requires three APIs (balance check, transaction history, book transfer), and banks still choose who to bank. The live demo runs against two beta banks through both a wallet UI and Swagger docs: a creation request mints new digital dollars in two steps (request with a nonce, followed by the reserve transfer) — funds remain at the participating bank but move into the shared network reserve. A $10,000 peer-to-peer payment between wallets completes instantly on the Zand ledger with no bank API called; wallet IDs are publicly shareable without granting access. Finally, $1,000 and $100 redemptions destroy the claims and push underlying funds back to the member\'s chosen bank. Jeff positions Zand as a bank-agnostic dollar settlement rail for regional/community banks, a more equitable real-time payment system, and a BSA-compliant digital-dollar platform for fintechs and crypto businesses. **Chapters:** - **[0:00] Introduction to Transparent and Zand** — https://www.youtube.com/watch?v=t4uNZLJ7CiQ&t=0s Jeff Kramer, CTO of Transparent Financial Systems, introduces Zand — a community-based B2B platform for real-time value transfers available 24/7/365. Each Zand network is designed by and for its transactional community — forex, crypto OTC desks, or networks of community and regional banks. - **[0:30] No central issuer, no new currency — just digital dollars** — https://www.youtube.com/watch?v=t4uNZLJ7CiQ&t=30s Zand has no central issuer, no new currency, and no intermediaries — just digital dollars moving in real time. Networks are programmable to meet each community's settlement rules while remaining under community control, with equitable revenue and cost distribution. - **[1:30] Three-API integration at the bank** — https://www.youtube.com/watch?v=t4uNZLJ7CiQ&t=90s Banks don't install any new software to participate in a Zand network. Each bank exposes only three APIs — balance check, transaction history, and book transfer — which Transparent wraps. Banks still choose who to bank; all network members must be at a participating bank. - **[2:30] Creation request — minting backed digital dollars** — https://www.youtube.com/watch?v=t4uNZLJ7CiQ&t=150s Creation requests produce new digital dollars. Underlying funds remain at the participating bank but move into the shared reserve account for the network — each member controls creation, transfer, and redemption of its own dollars with no single issuer. - **[4:30] Two-step creation with nonce** — https://www.youtube.com/watch?v=t4uNZLJ7CiQ&t=270s Creation happens in two steps: an API call produces a request with a nonce, and a reserve transfer completes the backing. Once complete the source bank balance drops and the minted claims appear in the member's shared account. - **[5:30] Peer-to-peer payment — no bank touched** — https://www.youtube.com/watch?v=t4uNZLJ7CiQ&t=330s Payments between wallets happen entirely on the Zand ledger — bank APIs are not invoked. The demo sends $10,000 from Cool Inc to Awesome Co using the recipient's publicly shareable wallet ID, and the obligation is extinguished instantly. - **[7:30] Redemption — destroy claims, transfer to bank** — https://www.youtube.com/watch?v=t4uNZLJ7CiQ&t=450s Redemptions destroy digital-dollar claims and push the underlying funds back to the member's chosen bank account. The demo redeems $1,000 and $100 at different banks, showing the reserve balance adjust accordingly. - **[9:00] Bank-agnostic interface and regulatory framing** — https://www.youtube.com/watch?v=t4uNZLJ7CiQ&t=540s Zand wraps banking APIs so any compliant bank can be added with no on-premises install. Because any BSA-compliant business can use it within the US regulatory framework, Zand is positioned as a competitive rail for regional and community banks vs. tier-one banks. ### Digital Asset Holdings — Digital Asset Holdings Technical Briefing - Slug: `v-digitalasset` - URL: https://v-sum.com/briefing/v-digitalasset - Presenter: Eric Saraniecki - Company: https://www.digitalasset.com - YouTube: https://www.youtube.com/watch?v=tsq7y7u-Fog - Tags: blockchain, capital-markets Eric Sarnecki, co-founder of Digital Asset, demos DAML — Digital Asset\'s framework for building networks of systems of record. The pitch: the world already runs on distributed ledgers, but the consensus algorithm is reconciliation — expensive, slow, and the reason payments are slow, margin is expensive, and capital requirements are astronomical. DAML replaces this by putting authorization directly on the data, enabling privacy-preserving data integrity across organizations. Customers are using DAML to rebuild equity settlement (eliminating margining), re-architect repo markets, and tokenize new asset classes (peer-to-peer sports betting, securitized factoring receivables). The demo showcases Digital Asset\'s open-source "market in a box" — a 30-minute-deployable marketplace with investors, custodians, and an exchange running on Project Daimler (Digital Asset\'s devops-free cloud runtime) and integrated with partner Xberry\'s high-performance matching engine. A sample Bitcoin/Tesla trading pair shows DAML\'s ability to create, list, and settle any pair on the fly, with a live view of per-party database state, UUID-based privacy-preserving onboarding, and data-layer authorization that blocks wrong-party API calls at the ledger itself. **Chapters:** - **[0:00] Introduction to Digital Asset and DAML** — https://www.youtube.com/watch?v=tsq7y7u-Fog&t=0s Eric Sarnecki, co-founder of Digital Asset, introduces DAML — Digital Asset's development framework for building networks of systems of record. DAML lets businesses connect disparate core data systems across privacy boundaries, guaranteeing data integrity and enforcing authorization at the data layer itself. - **[1:00] Reconciliation as the worst consensus mechanism** — https://www.youtube.com/watch?v=tsq7y7u-Fog&t=60s Eric's thesis: the world has always run on distributed ledgers — but the consensus algorithm is reconciliation, which is expensive, slow, and error-prone. Reconciliation friction is why payments are slow, margin is expensive, and capital requirements are astronomical. - **[1:30] What customers are building on DAML** — https://www.youtube.com/watch?v=tsq7y7u-Fog&t=90s DAML customers build things like equity settlement systems that eliminate margining, repo-market re-architecture, peer-to-peer sports betting without counterparty risk, and financialization of previously illiquid asset classes (e.g. securitized factoring receivables). - **[2:30] Market-in-a-box starter app** — https://www.youtube.com/watch?v=tsq7y7u-Fog&t=150s A 30-minute deployable open-source starter app — the "market in a box" — shows what can be built on DAML. Any halfway-decent developer can modify it in a few days to fit their own marketplace use case. - **[3:30] Distributed marketplace — investors, custodians, exchange** — https://www.youtube.com/watch?v=tsq7y7u-Fog&t=210s The demo is a live open marketplace on Daimler with investors (Alice, Bob, Charlie), custodians, and an exchange — data segmented per participant with no central operator. Integrated with Xberry for cloud-native high-performance matching. - **[5:30] Listing Bitcoin/Tesla pair and aggregated order book** — https://www.youtube.com/watch?v=tsq7y7u-Fog&t=330s The exchange can create any pair on the fly — the demo lists a Bitcoin/Tesla pair (trading ~44 BTC) that no real exchange offers today. The order book aggregates per-participant bids and offers into a single view. - **[6:30] Wallet with holdings at a custodian** — https://www.youtube.com/watch?v=tsq7y7u-Fog&t=390s Eric's wallet holds Bitcoin, dollars, and Tesla shares at a custodian. The custodian can service and safe-keep the assets, but only the owner can instruct transfers or allocations — a clean separation DAML enforces at the data layer. - **[8:00] Project Daimler — devops-free deployment** — https://www.youtube.com/watch?v=tsq7y7u-Fog&t=480s Daimler is the live cloud runtime for DAML apps: download the DAML SDK, build, drag-and-drop to deploy. The live-data view shows every party's state segmented by UUID, with privacy-preserving onboarding so data is only replicated to authorized parties. - **[9:30] Data-centric authorization and segregation** — https://www.youtube.com/watch?v=tsq7y7u-Fog&t=570s DAML takes a data-centric view: authorization lives with the data, not in a layer above it. Asset-deposit contracts expose APIs (merge, split, set-observers) and the owner can see which parties are authorized to view or mutate. Wrong-party calls fail at the data layer. - **[11:30] External integrations — Xberry, Slack, Symphony, price feeds** — https://www.youtube.com/watch?v=tsq7y7u-Fog&t=690s Integrations (Xberry matching engine, Slack/Symphony notifications, price feeds) are tightly coupled to the cloud environment. Rather than building middleware, customers deploy integrations with credentials and interact with external APIs through DAML ledger transactions. ## V-Sum Four — March 2, 2021 Event page: https://v-sum.com/events/four ### YAP — YAP Technical Briefing - Slug: `v-yap` - URL: https://v-sum.com/briefing/v-yap - YouTube: https://www.youtube.com/watch?v=6g8JzsB8XqA - Tags: payments, cross-border, developer-tools YAP is an API platform that sits between banks and businesses across Asia — think Marqeta-adjacent, but covering processing plus full retail-bank orchestration across five to seven Asian markets (roughly 300 fintechs in India today). The briefing walks through YAP's granular API catalogue (wallet / card issuing, multi-currency travel, neo-banking primitives) and a real YAP-powered product: PaisaBazaar's Step-Up credit card, an Indian credit-builder card where customers book a fixed deposit and 80% of the FD becomes the starting credit limit. The demo covers Indian identity verification (PAN, Aadhaar share-code, UIDAI OTP), UPI penny-drop account verification, instant issuance of both virtual and physical cards, and the card-control API for toggling channels, setting limits, and delivering statements as PDF or JSON for custom branding. **Chapters:** - **[0:00] Introduction to YAP — API platform across Asia** — https://www.youtube.com/watch?v=6g8JzsB8XqA&t=0s YAP is an API platform that sits between banks and businesses in emerging markets. Think of YAP as something between Marqeta and a core-banking partner — YAP runs its own processing and extends it to fintechs launching cards, wallets, and neobanks. - **[0:30] Processing, bank orchestration, retail banking** — https://www.youtube.com/watch?v=6g8JzsB8XqA&t=30s YAP's capability set covers processing, card issuing (wallet, card, multi-currency travel), and full retail-bank orchestration. Today it powers roughly 300 fintechs in India across five to seven Asian markets. - **[1:30] API documentation — a worked credit card flow** — https://www.youtube.com/watch?v=6g8JzsB8XqA&t=90s Tour of YAP's documentation and APIs organized around a customer journey: onboarding, KYC, card registration. Instead of a monolithic endpoint, YAP exposes granular APIs that slot into whatever flow the fintech is already building. - **[3:00] PaisaBazaar Step-Up Credit Card — credit builder for India** — https://www.youtube.com/watch?v=6g8JzsB8XqA&t=180s A real YAP-powered product: PaisaBazaar's Step-Up card. Like a US credit-builder card, it targets users new to credit — you book a fixed deposit, and 80% of the FD is offered as a credit limit that the bank raises as your score grows. - **[3:30] Indian identity: PAN, Aadhaar, OTP verification** — https://www.youtube.com/watch?v=6g8JzsB8XqA&t=210s The onboarding flow tailored for India: PAN, mobile-number OTP verification, Aadhaar share-code flow (similar to SSN verification in the US), and UIDAI-issued OTP confirmation before any account is created. - **[6:00] Penny drop via UPI for account verification** — https://www.youtube.com/watch?v=6g8JzsB8XqA&t=360s YAP verifies bank account ownership via a penny-drop through UPI — collect IFSC code and account number, drop a single rupee, and confirm the UPI response matches what the user typed before issuing the card. - **[8:30] Card set: virtual and physical, real-time unveil** — https://www.youtube.com/watch?v=6g8JzsB8XqA&t=510s Once the FD is booked and KYC is complete, the YAP API issues both a virtual card (instantly usable in-app) and a physical one. End users can reveal virtual card details, toggle cards on/off, link add-on cards, and set preferences. - **[10:00] Programmable card controls and statements** — https://www.youtube.com/watch?v=6g8JzsB8XqA&t=600s Channel-level controls: disable contactless, block ATM withdrawals, set per-channel limits, set daily usage limits. Card statements are available as PDF or JSON — fintechs can wrap their own branding on the JSON response. ### CredoLab — CredoLab Technical Briefing - Slug: `v-credolab` - URL: https://v-sum.com/briefing/v-credolab - YouTube: https://www.youtube.com/watch?v=L7-XlLn7pxs - Tags: identity, compliance, lending Credolab is a Singapore-headquartered company building smartphone-based behavioral credit scoring for the financially underserved. The demo shows how Credolab\'s lender-embedded SDK (Android) captures behavioral metadata alongside the borrower\'s consent during a standard loan-application flow — with no PII ever leaving the phone (50,000 behavioral data points compressed into a 50 KB JSON). The borrower sees transparent Google-policy permission prompts (allow/deny per permission), Credolab reports coverage completeness (e.g. 83% if some permissions are denied), and the score plus metadata (record ID, device ID, timestamp, permissions) surfaces in the lender\'s dashboard in real time. The Credolab score focuses on intent to repay (behavioral patterns matched against known defaulter features via proprietary ML) rather than ability to repay — so it complements existing bureau data rather than replacing it. Use cases span emerging markets without credit bureaus (thin-file approvals on fair terms), developed markets (risk-based / relationship-based pricing), and instant-decision products like short-term loans, buy-now-pay-later, e-commerce, and e-wallets. Credolab has 86 clients across 26 countries. **Chapters:** - **[0:00] Introduction to Credolab** — https://www.youtube.com/watch?v=L7-XlLn7pxs&t=0s Credolab is a Singapore-headquartered company that builds a behavioral credit-scoring framework from smartphone usage patterns to predict the probability of default — designed to serve the financially excluded and underserved users that traditional credit bureaus can't reach. - **[1:30] Lender SDK — embedded in the loan app** — https://www.youtube.com/watch?v=L7-XlLn7pxs&t=90s Credolab is integrated by embedding the lender's SDK into their own mobile app, so the user experience stays seamless. When the borrower applies for a loan they simultaneously consent to Credolab collecting behavioral metadata for scoring. - **[2:30] Demo app with bank code and unique record ID** — https://www.youtube.com/watch?v=L7-XlLn7pxs&t=150s Because Credolab never touches PII, each applicant is identified only by a unique invite code known to the lender — no national ID, phone number, or name. A bank-code field routes the record to the correct lender tenant. - **[3:00] Transparent consent flow and Google permissions** — https://www.youtube.com/watch?v=L7-XlLn7pxs&t=180s Data privacy is a core pillar: the app explains what permissions are needed, why, and how. Android permission prompts follow Google's policy (explicitly allow or deny) and Credolab reports how complete the dataset is — 83% accessible if the user denies some permissions. - **[4:30] Score delivered to the lender dashboard in real time** — https://www.youtube.com/watch?v=L7-XlLn7pxs&t=270s On submission, the score and metadata (record ID, device ID, device type, permissions granted, timestamp) appear in the lender's Credolab dashboard in real time, ready to be fed into their own decisioning framework. - **[5:30] Intent to repay vs. ability to repay** — https://www.youtube.com/watch?v=L7-XlLn7pxs&t=330s The Credolab score is designed to complement — not replace — existing credit frameworks. Because it's built on behavioral data, it captures the borrower's intent to repay rather than their income or ability, making it complementary to traditional bureau data. - **[6:30] Use cases — emerging markets + risk-based pricing** — https://www.youtube.com/watch?v=L7-XlLn7pxs&t=390s In emerging economies without credit bureaus, Credolab opens credit to thin-file borrowers. In developed markets, it powers risk-based/relationship-based pricing — so lenders offer better rates to borrowers who show strong intent alongside strong ability. - **[7:30] Privacy architecture — 50,000 data points → 50 KB JSON** — https://www.youtube.com/watch?v=L7-XlLn7pxs&t=450s Credolab collects ~50,000 behavioral data points from the smartphone but outputs only a 50 KB JSON file — no actual content ever leaves the device. Metadata is processed on Azure and converted to millions of ML features for probability-of-default modeling. - **[9:00] Best-fit products and global footprint** — https://www.youtube.com/watch?v=L7-XlLn7pxs&t=540s The score fits instant-decision products — short-term loans, buy now pay later, e-commerce credit, e-wallets — rather than mortgages. Credolab serves 86 clients across 26 countries. ### Brankas — Brankas Technical Briefing - Slug: `v-brankas` - URL: https://v-sum.com/briefing/v-brankas - Company: https://brank.as - YouTube: https://www.youtube.com/watch?v=YPozXXzyI3Y - Tags: open-banking, payments Brankas is an open banking platform across Southeast Asia — Philippines, Indonesia, Thailand, Vietnam, Singapore. CPO Mike and Senior PM Luis demo Direct, the Brankas bank-transfer product that aggregates transfers across multiple banks via API with the end-user's explicit consent. Brankas never holds funds (no Stripe-style settlement); it exposes consent, authentication, and routing over open-banking rails. The demo walks through the two-endpoint Direct API (payment initiation, transaction retrieval), a live 100-peso payment from a BPI account in the Philippines through Brankas's IDP (identity provider) consent flow, per-bank authentication (username/password, TFA, OAuth 2 where banks support it), a biometric in-app authorization step on the BPI mobile app, and the final redirect + callback webhook that tell the integrator the payment settled. Production use cases include e-wallet top-up, lender collection, marketplace checkout, and bill payment. **Chapters:** - **[0:00] Introduction to Brankas — open banking across SEA** — https://www.youtube.com/watch?v=YPozXXzyI3Y&t=0s Mike, CPO of Brankas, introduces the company — an open banking startup across Southeast Asia with teams in Singapore, Manila, Indonesia, Thailand, and Vietnam. Brankas ships APIs between banks and businesses in markets where you cannot launch a fintech without bank partners. - **[0:30] Direct — bank transfer product** — https://www.youtube.com/watch?v=YPozXXzyI3Y&t=30s Luis, Senior PM on Direct, will demo the flagship bank-transfer product. In SEA, bank transfers still dominate transaction volume (Philippines, Indonesia, Thailand) — Direct aggregates transfers across banks via API, with the end-user's explicit consent. - **[1:00] Not a payment gateway — Brankas never holds funds** — https://www.youtube.com/watch?v=YPozXXzyI3Y&t=60s Brankas never settles into its own accounts — no Stripe-style holding, no Adyen-style settlement. The rails stay on the banks; Brankas exposes the consent, authentication, and routing over open banking APIs. - **[1:30] Use cases: e-wallet top-up, lending, marketplaces, bill pay** — https://www.youtube.com/watch?v=YPozXXzyI3Y&t=90s Production use cases for Direct: e-wallet top-up in Indonesia, lender collection in Indonesia and the Philippines, marketplace checkout on Lazada or Shopee, and bill-payment flows — all via consented bank transfers. - **[2:30] Payment initiation endpoint — one API across banks** — https://www.youtube.com/watch?v=YPozXXzyI3Y&t=150s Direct is two endpoints: payment initiation and transaction retrieval. Payment initiation takes a base set of fields (amount, destination account ID, reference, optional end-user info) — the rest of the complexity is hidden behind bank-specific adapters. - **[4:30] Brankas IDP — end-user consent flow** — https://www.youtube.com/watch?v=YPozXXzyI3Y&t=270s A successful initiate returns a redirect URI for the Brankas IDP, the secure end-user consent layer. The IDP walks the payer through explicit consent to Brankas' permissions, terms, and privacy policy before any bank credentials change hands. - **[5:30] Why emerging-market banks lack proper APIs** — https://www.youtube.com/watch?v=YPozXXzyI3Y&t=330s Banks in the region often have first-party-only APIs or none at all. Brankas partners with them to securely expose those APIs to third parties — accelerating digital banking rollout without each bank needing to build an OAuth 2 gateway. - **[6:30] Live PHP 100 payment into BPI** — https://www.youtube.com/watch?v=YPozXXzyI3Y&t=390s Luis kicks off a live 100-peso payment. The Brankas IDP renders a bank selector (a slice of integrated Philippine banks), selects BPI (second-largest bank in the Philippines), and routes the end user through bank-specific authentication. - **[9:30] Per-bank auth (username/password, TFA, OAuth2)** — https://www.youtube.com/watch?v=YPozXXzyI3Y&t=570s The IDP automatically adjusts to whatever authentication flow each bank requires — username/password for BPI, TFA for others, OAuth 2 where available. No third party sees credentials; Brankas just forwards them to the bank's own endpoints. - **[11:30] BPI biometric in-app authorization** — https://www.youtube.com/watch?v=YPozXXzyI3Y&t=690s Back on the IDP: transaction summary, confirm, and BPI prompts biometric in-app authorization on the mobile banking app. Once the bank responds, the IDP redirects to the integrator's return URL with the Brankas transaction ID and final status as query parameters. ## V-Sum Five — April 6, 2021 Event page: https://v-sum.com/events/five ### Apto Payments — Apto Payments Technical Briefing - Slug: `v-apto` - URL: https://v-sum.com/briefing/v-apto - Presenter: Meg Nakamura & Willis Jackson III (LinkedIn: https://www.linkedin.com/in/megnakamura/) - Company: https://aptopayments.com - YouTube: https://www.youtube.com/watch?v=9ByQFI_JXKM - Tags: payments, embedded-finance Meg Nakamura, Willis Jackson III, and Mike of Apto Payments demo Apto\'s self-service card issuance platform — the answer to years of customer complaints about how long and how expensive standing up a card program used to be. The new Apto is developer-first and fully self-service: design, build, launch, and scale a debit or prepaid card program without ever talking to a salesperson. The demo walks through real signup, API keys, a cardholder app delivered via TestFlight, KYC-backed cardholder onboarding, sandbox test transactions, and the production application (revenue split, KYB, UBO capture, off-the-shelf card designs, $500 collateral). Meg funds her card via ACH and a linked debit card, adds it to Apple Pay, and buys a Raygun t-shirt online — the transaction appears in both the Apto admin and the cardholder app within seconds. A closing demo fires an Apto API call to credit $20 to the cardholder wallet as a marketing incentive, and Willis covers the mobile SDK vs. white-label wrapper paths to shipping the cardholder app under your own brand. **Chapters:** - **[0:00] Introduction to Apto Payments — self-service card issuance** — https://www.youtube.com/watch?v=9ByQFI_JXKM&t=0s Meg Nakamura introduces Apto Payments' newest product. After hearing the same "time to market" pain from card-program customers, Apto built a developer-first, fully self-service issuance platform — design, build, launch, and scale a card program without ever talking to a salesperson. - **[1:00] Self-serve signup and API keys** — https://www.youtube.com/watch?v=9ByQFI_JXKM&t=60s Willis Jackson III walks through the real Apto signup, email verification, and grabbing an API key in the dashboard — plus team member invites, all from the browser in sandbox. - **[2:30] Cardholder sign-up via text message** — https://www.youtube.com/watch?v=9ByQFI_JXKM&t=150s Apto sends Meg a text with a TestFlight invite to the Apto cardholder app. Any issuer can bootstrap a compliant, bank-approved cardholder onboarding flow in a couple of taps — no mobile app build needed. - **[3:30] KYC-backed cardholder onboarding** — https://www.youtube.com/watch?v=9ByQFI_JXKM&t=210s The cardholder signup collects phone, personal details, and legal agreements, runs full KYC on the backend (compliant with the issuing bank), and issues a card — all in sandbox with fake data, but the same flow that runs in production. - **[5:30] Sandbox test transactions and card view** — https://www.youtube.com/watch?v=9ByQFI_JXKM&t=330s Back in the dashboard, Willis sees the cardholder and the just-issued card. Apto's sandbox supports test transactions across patterns so issuers can shake out webhooks, disputes, and spend controls before flipping to production. - **[6:00] Production application — revenue split and KYB** — https://www.youtube.com/watch?v=9ByQFI_JXKM&t=360s Moving to production involves accepting Apto's standard setup fees plus interchange and revenue split, running KYB on the issuing company, capturing UBOs, and verifying a company phone number. - **[8:00] Card design picker and $500 collateral** — https://www.youtube.com/watch?v=9ByQFI_JXKM&t=480s Pick an off-the-shelf card color (or upload a custom logo), sign the terms, and put up $500 of collateral. That's the last step before Apto's production application — and they're your card program. - **[9:00] Apple Pay purchase — live card in production** — https://www.youtube.com/watch?v=9ByQFI_JXKM&t=540s Meg opens her Apto cardholder app, funds the card via ACH in and debit card in, adds it to Apple Pay, and buys a Raygun t-shirt online. The transaction appears in both the dashboard and the app within seconds. - **[12:30] Funding endpoints for marketing incentives** — https://www.youtube.com/watch?v=9ByQFI_JXKM&t=750s A separate Apto API endpoint credits a cardholder wallet directly — useful for promotional spiffs like crediting $20 after a first purchase. Willis fires it from Postman and the balance updates in the cardholder app. - **[13:30] Mobile SDK or off-the-shelf wrapper app** — https://www.youtube.com/watch?v=9ByQFI_JXKM&t=810s Apto offers two paths to ship the cardholder experience: either the mobile SDK for teams building their own app, or Apto's off-the-shelf white-label app you wrap with a splash screen and publish under your brand. ### Dwolla — Dwolla Technical Briefing - Slug: `v-dwolla` - URL: https://v-sum.com/briefing/v-dwolla - Presenter: Skyler Nesheim & Ben Schmitt (LinkedIn: https://www.linkedin.com/in/skyler-nesheim/) - Company: https://www.dwolla.com - YouTube: https://www.youtube.com/watch?v=nqB22i-Fyko - Tags: payments, developer-tools Ben and Skyler Nesheim of Dwolla demo "programming the Fed and The Clearing House" — Dwolla\'s flexible ACH, same-day ACH, push-to-debit, and real-time payments (RTP) API that businesses use to program collections, disbursements, and stored-value flows. The demo opens on launch day for Dwolla RTP: already live in sandbox, newly live in production. A command-line "David Lightman" app walks through the full Dwolla payment stack — create a lightweight customer, upgrade to a verified customer with SSN and address, add a bank funding source, then fire four transfers back-to-back. Standard ACH requires only source URL, destination URL, currency, and amount. Same-day ACH adds a one-field "clearing object." Push-to-debit only changes the destination URL. RTP changes one line — the processing channel. Throughout the demo, Dwolla fires webhooks (customer completed, bank transfer completed, etc.) so applications can react in real time. **Chapters:** - **[0:00] Introduction to Dwolla — programming the Fed and The Clearing House** — https://www.youtube.com/watch?v=nqB22i-Fyko&t=0s Ben introduces Dwolla's demo on programming payments — "programming the Fed and The Clearing House." Dwolla connects businesses to banking infrastructure via a flexible API covering collections, disbursements, stored value, and every transfer type in between. - **[0:30] Live RTP launch + same-day ACH + push-to-debit** — https://www.youtube.com/watch?v=nqB22i-Fyko&t=30s Dwolla's real-time payments (RTP) feature went live on the production platform that morning. The demo programmatically fires a customer creation, verification, funding-source attach, and four payment types: standard ACH, same-day ACH, push-to-debit, and RTP — all on real sandbox rails. - **[2:30] Create a Dwolla customer via API** — https://www.youtube.com/watch?v=nqB22i-Fyko&t=150s Skyler walks through creating a Dwolla "customer" — the foundation for any payment. A few fields (first name, last name, email, IP) posted to the customers endpoint produces a lightweight Dwolla customer that can receive funds. - **[4:30] Upgrade to a verified customer** — https://www.youtube.com/watch?v=nqB22i-Fyko&t=270s Upgrading a customer to verified adds SSN-last-4, address, postal code, and date of birth — the yellow unverified badge flips to a green verified one. About 36 lines of Python total. - **[6:00] Add a funding source** — https://www.youtube.com/watch?v=nqB22i-Fyko&t=360s A funding source is a bank account (or debit card, or a few other types). The API takes routing number, account number, account type, and a nickname — it shows up in the Dwolla admin with the matching details. - **[7:00] Standard ACH transfer** — https://www.youtube.com/watch?v=nqB22i-Fyko&t=420s Program a standard ACH transfer: source URL (funding source to pull from), destination URL (where funds go), currency, amount. POST to /transfers and the transaction shows up in the Dwolla admin. - **[8:30] Same-day ACH with a clearing object** — https://www.youtube.com/watch?v=nqB22i-Fyko&t=510s Same-day ACH differs by one property — add a clearing object telling Dwolla to route the transfer into the next available clearing window. Everything else in the payment body stays identical. - **[9:00] Push-to-debit card** — https://www.youtube.com/watch?v=nqB22i-Fyko&t=540s For push-to-debit, the only change is the destination URL — point it at a debit-card funding source (a Visa test card in the demo) and the same /transfers endpoint moves funds to the card. - **[10:00] RTP — change processing channel** — https://www.youtube.com/watch?v=nqB22i-Fyko&t=600s Switching from ACH to real-time payments is about two lines of code — change the processing channel from ACH to real-time payments. The RTP rails settle in seconds on The Clearing House. - **[10:30] Webhooks for every event** — https://www.youtube.com/watch?v=nqB22i-Fyko&t=630s Throughout the demo, Dwolla fires webhooks to a catch-bin — customer created, customer completed, bank transfer completed, transaction created — so an application can drive UX and back-office logic off the Dwolla event stream. ### Atomic — Atomic Technical Briefing - Slug: `v-atomic` - URL: https://v-sum.com/briefing/v-atomic - Presenter: Lindsay Davis & Jeff Hendren (LinkedIn: https://www.linkedin.com/in/lindsay-crusan-davis/) - YouTube: https://www.youtube.com/watch?v=Bo_oLkVaLPo - Tags: open-banking, embedded-finance Lindsay Davis and Jeff Hoffer of Atomic demo Atomic's payroll-connectivity APIs — used by hundreds of thousands of consumers per month across challenger banks, neobanks, and online lenders to switch direct deposits, verify employment, and verify income. Atomic ships a standard SDK across iOS, Android, React Native, Flutter, and Kotlin that partners typically integrate in ~4 hours. The demo walks through launching Transact inside a partner app (passing a unique GUID and the destination account/routing number), distinguishing Deposit (write) flows from Identify/Verify (read) flows, and handling the employer-vs-payroll-provider selection. Atomic's conversion engineering is a differentiator: reverse-engineered in-modal password resets push authentication conversion to ~70%, and two-factor authentication (present in ~28% of logins) is handled inside the flow. Linked accounts enable periodic VOE/VOI refreshes without re-prompting the user. Partial direct-deposit switches power investing apps that want to route a percentage or dollar amount of each paycheck to a new destination without the user changing their primary bank. **Chapters:** - **[0:00] Introduction to Atomic — payroll APIs** — https://www.youtube.com/watch?v=Bo_oLkVaLPo&t=0s Lindsay opens the Atomic briefing with a question for the audience — "who pays you?" — to illustrate that roughly 20% of the hundreds of thousands of consumers who move through Atomic each month can identify their payroll provider by name. - **[1:00] Why payroll connectivity matters** — https://www.youtube.com/watch?v=Bo_oLkVaLPo&t=60s Mapping an end user to their payroll provider unlocks direct-deposit switching (full or partial), verification of employment, and verification of income — the data set behind most modern fintech onboarding and underwriting flows. - **[1:30] Atomic SDK — iOS, Android, React Native, Flutter** — https://www.youtube.com/watch?v=Bo_oLkVaLPo&t=90s Jeff walks through Atomic's standard SDK, with documentation and Postman collections. Atomic supports Kotlin, Swift, React Native, and Flutter natively, and partners typically get the standard SDK up and running in about four hours of development time. - **[2:30] Deposit, Identify, and Verify product flows** — https://www.youtube.com/watch?v=Bo_oLkVaLPo&t=150s The three Atomic flows — Deposit (full or partial direct-deposit switching), Identify (switch plus data), and Verify (income and employment). Used by challenger banks, neobanks, and online personal-lending and payday-lending apps. - **[3:30] Launching Transact from your app** — https://www.youtube.com/watch?v=Bo_oLkVaLPo&t=210s Initiating an API call into the Atomic SDK launches Transact inside the partner app or web view. Atomic is explicit about whether a flow is writing (direct-deposit switch) or reading (VOE/VOI) from the payroll system. - **[4:00] Unique GUID and destination account/routing** — https://www.youtube.com/watch?v=Bo_oLkVaLPo&t=240s For every user, the partner passes a unique GUID so Atomic can identify the transaction and route webhooks. For a direct-deposit switch, the partner also passes the new account and routing numbers Atomic will write into the payroll system. - **[4:30] Employer vs. payroll-provider selection** — https://www.youtube.com/watch?v=Bo_oLkVaLPo&t=270s Users can pick either their employer or payroll provider. Coverage and conversion are harder in payroll than in banking because the employer-to-payroll mapping changes — Atomic maintains that map and rebuilds per-payroll-provider quirks like Gusto's Google OAuth. - **[6:00] Partial direct-deposit switching for investing apps** — https://www.youtube.com/watch?v=Bo_oLkVaLPo&t=360s With partners like Home Depot, Atomic exposes the ability to switch only a portion of a paycheck — popular with investment and savings apps where a consumer wants a dollar amount or percentage routed to a new account, keeping the rest at the current bank. - **[6:30] Conversion tricks — password reset and 2FA** — https://www.youtube.com/watch?v=Bo_oLkVaLPo&t=390s Atomic reverse-engineered in-modal username and password resets, lifting authentication conversion to roughly 70%. Two-factor authentication is supported in-flow and appears in about 28% of logins, with linked-account credentials stored for periodic VOE/VOI refreshes. ## V-Sum Six — June 8, 2021 Event page: https://v-sum.com/events/six ### Casa — Casa Technical Briefing - Slug: `v-casa` - URL: https://v-sum.com/briefing/v-casa - Presenter: Nick Neuman & Michael Haley (LinkedIn: https://www.linkedin.com/in/nick-neuman-9586b822/) - Company: https://keys.casa - YouTube: https://www.youtube.com/watch?v=wbGiAXSSBrE - Tags: custody, wallets, crypto-infrastructure Casa demos its personal key-manager product for Bitcoin self-custody — a safe, visually-consumer-first way to hold Bitcoin private keys without falling off the "one key, one pool of coins" cliff that has already lost an estimated 4M of Bitcoin\'s 21M total supply. At Casa\'s highest security tier, five keys protect one Bitcoin pool (mobile phone, three hardware wallets, one emergency Casa-held key) under a 3-of-5 multi-sig — losing any one key doesn\'t risk your funds. A separate "checking account" uses a single mobile key for fast spending. The send flow shows the multi-sig in action: the phone signs first, Casa emails a prompt to plug in a Trezor or Ledger for the second signature, and a third hardware approval broadcasts the transaction to Bitcoin\'s network. QR-code-based signing on next-gen hardware wallets will eliminate the email step. Casa\'s replace-a-lost-key flow skips seed-phrase recovery entirely — mark the key compromised, add a new hardware device, and transfer funds with the remaining healthy keys. Premium service tiers offer concierge-style support for high-net-worth holders. **Chapters:** - **[0:00] Introduction to Casa** — https://www.youtube.com/watch?v=wbGiAXSSBrE&t=0s Nick introduces Casa as a safe and simple way to hold Bitcoin private keys. Of Bitcoin's 21M total supply, an estimated 4M coins have been lost in a decade — mostly to mistakes, not theft — blocking mass adoption for anyone unwilling to risk their savings. - **[1:00] The private-key tradeoff** — https://www.youtube.com/watch?v=wbGiAXSSBrE&t=60s Bitcoin private keys give you sole control of your money without needing a bank — but if you lose the key, you lose everything. The common workaround (leaving keys with Coinbase) trades control for security, which Casa is trying to unbundle. - **[1:30] Casa as a personal key manager** — https://www.youtube.com/watch?v=wbGiAXSSBrE&t=90s Casa is a new kind of product — a personal key manager that lets you safely manage your own Bitcoin private keys. Its core idea: instead of one key, use multiple keys to protect one pool of Bitcoin, so losing a key doesn't mean losing the money. - **[2:30] Casa's 5-of-3 multi-sig setup** — https://www.youtube.com/watch?v=wbGiAXSSBrE&t=150s At the highest security tier Casa holds five keys securing one Bitcoin pool: one on your phone, three on hardware wallets (Trezor/Ledger), and one emergency key held by Casa. Multi-sig means any three of five keys are enough to spend. - **[3:30] Checking account — single mobile key** — https://www.youtube.com/watch?v=wbGiAXSSBrE&t=210s For everyday spending, Casa offers a checking-style wallet with a single mobile key — easy one-tap sends from your phone without pulling out hardware devices, paired with the multi-sig vault for savings. - **[4:30] Sending 1 BTC — three signatures** — https://www.youtube.com/watch?v=wbGiAXSSBrE&t=270s Sending Bitcoin from the vault: the phone key adds the first signature, Casa emails a prompt to plug in your Trezor/Ledger for the second, and a third hardware signature finalizes the spend. Stolen phone alone cannot move funds. - **[5:30] QR-code signing on next-gen hardware** — https://www.youtube.com/watch?v=wbGiAXSSBrE&t=330s New hardware wallets with screens let Casa skip the email step entirely — sign by scanning a QR code into the hardware device and return the signature via QR, a major UX upgrade. - **[6:30] Replacing a lost key without a seed phrase** — https://www.youtube.com/watch?v=wbGiAXSSBrE&t=390s With multi-sig, losing one key doesn't require seed-phrase recovery. Mark the key as lost or compromised in-app, add a new hardware wallet, and transfer funds to a healthy new wallet using three of the remaining keys. - **[8:30] White-glove help for high-balance holders** — https://www.youtube.com/watch?v=wbGiAXSSBrE&t=510s Casa offers premium service tiers with concierge-style support — call a human for help — positioned as the opposite of Coinbase's days-long support queue, specifically for high-net-worth Bitcoin holders. ### ZenLedger — ZenLedger Technical Briefing - Slug: `v-zenledger` - URL: https://v-sum.com/briefing/v-zenledger - Presenter: Patrick Larsen & Dan Hannum (LinkedIn: https://www.linkedin.com/in/patlarsen1/) - Company: https://www.zenledger.io/ - YouTube: https://www.youtube.com/watch?v=NRqlypUK5sk - Tags: accounting, crypto-infrastructure ZenLedger presents crypto taxes and accounting at V-Sum Six. Presented by Patrick Larsen and Dan Hannum, covering portfolio tracking, taxable event reporting, tax loss harvesting, and full audit reports for cryptocurrency investors and tax professionals. **Chapters:** - **[0:00] Introduction to ZenLedger** — https://www.youtube.com/watch?v=NRqlypUK5sk&t=0s Patrick explains ZenLedger and how different countries are handling cryptocurrency — the coming accounting challenge as jurisdictions from El Salvador to Switzerland take different approaches. - **[2:20] ZenLedger app and data integration** — https://www.youtube.com/watch?v=NRqlypUK5sk&t=140s The ZenLedger platform — exchange API integration, daily portfolio tracking, and seeing all transactions whether on-exchange, on-wallet, on-chain, or off-chain in one place. - **[3:25] What is a taxable event** — https://www.youtube.com/watch?v=NRqlypUK5sk&t=205s Explanation of taxable events in crypto: buying crypto with USD is not taxable, but trading crypto-to-crypto or back to fiat creates a gain or loss that must be reported. - **[4:05] Exchange imports and lost Bitcoin** — https://www.youtube.com/watch?v=NRqlypUK5sk&t=245s Demo of importing from exchanges including Coinbase, and how to claim lost or stolen bitcoin accounted for at original cost basis. - **[4:50] CSV uploads and NFT income** — https://www.youtube.com/watch?v=NRqlypUK5sk&t=290s Uploading CSV files, importing on-chain transactions, and handling cryptocurrency income including NFTs — making, selling, buying, and trading NFTs all have different tax implications. - **[6:00] Tax forms and audit reports** — https://www.youtube.com/watch?v=NRqlypUK5sk&t=360s The Taxes tab — outputting to tax forms, full audit reports, tax loss harvesting reports, and error checking for missing wallets or non-taxable self-transfers. - **[6:50] Client types and use cases** — https://www.youtube.com/watch?v=NRqlypUK5sk&t=410s Who ZenLedger works with — ultra-high net worth practices, multinationals, single investors, crypto hedge funds, and private equity funds. - **[7:45] Wallet dashboard and recommendations** — https://www.youtube.com/watch?v=NRqlypUK5sk&t=465s Wallet view showing holdings per exchange, acquisition data, accounting methods, and recommendations on freeing up cash or capturing tax losses. - **[9:00] Full audit report example** — https://www.youtube.com/watch?v=NRqlypUK5sk&t=540s Spreadsheet walkthrough — all fiat/crypto movement, non-taxable self-transfers, current holdings, error checking, and taxable events organized by year for tax form generation. ### Hedera Hashgraph — Hedera Hashgraph Technical Briefing - Slug: `v-hedera` - URL: https://v-sum.com/briefing/v-hedera - Presenter: Greg Scullard & Lina Tran (LinkedIn: https://www.linkedin.com/in/greg-scullard/) - Company: https://hedera.com - YouTube: https://www.youtube.com/watch?v=pkctg86cjsU - Tags: blockchain, developer-tools Hedera Hashgraph walks through the Hedera public distributed ledger — a leaderless consensus network with thousands of TPS, 3–5 second latency at full finality, native multi-signature, and fees pegged to the US dollar for predictable business economics. The briefing demos the Hedera Token Service (HTS), which issues fungible and non-fungible tokens as native network operations (not smart contracts), with configurable keys for admin / supply / KYC / wipe / freeze so issuers can layer in compliance features selectively. The live demo creates a VSAN6 fungible token (two decimals, variable supply, KYC-gated), walks through token association (recipients must opt in — protecting users from unsolicited airdrops and the tax liability they can trigger in some jurisdictions), grants KYC to Alice and Bob, transfers 20,000 tokens to Alice, and closes with an atomic swap across three assets (VSAN6, demo-token-one, and HBAR) in a single Hedera transaction. **Chapters:** - **[0:00] Introduction to Hedera Hashgraph** — https://www.youtube.com/watch?v=pkctg86cjsU&t=0s Hedera Hashgraph introduces itself as a public distributed ledger with thousands of TPS, 3–5 second latency with 100% finality, leaderless consensus, USD-pegged fees, and native multi-signature — a different trade-off space from typical blockchain L1s. - **[1:00] HBAR micropayments and the crypto service** — https://www.youtube.com/watch?v=pkctg86cjsU&t=60s HBAR is Hedera's native coin. Fees are low enough to economically transfer a fraction of a cent, genuinely enabling micropayment use cases that most chains struggle with. - **[1:30] Hedera Token Service — native, not smart-contract** — https://www.youtube.com/watch?v=pkctg86cjsU&t=90s The Hedera Token Service (HTS) issues fungible and non-fungible tokens as native network operations — no smart contracts, as fast and cheap as HBAR itself — opening up token issuance use cases not seen on other chains. - **[2:00] Other Hedera services** — https://www.youtube.com/watch?v=pkctg86cjsU&t=120s Hedera's other services: Hedera Consensus Service exposes the underlying hashgraph consensus as an API for any app; scheduled transactions simplify multi-signature coordination; and EVM-compatible smart contracts plus mutable file storage round out the stack. - **[3:00] Create a fungible token via the token composer** — https://www.youtube.com/watch?v=pkctg86cjsU&t=180s Demo of Hedera's token composer UI: create a new fungible token (VSAN6), two decimals (dollar-like), variable supply starting at 500 whole tokens, with 3–5 second finality and no block confirmations required. - **[4:30] Mutable, KYC-gated, wipeable, freezable** — https://www.youtube.com/watch?v=pkctg86cjsU&t=270s Optional token controls: admin-key mutability, KYC key gating (mark which accounts have passed off-chain KYC), wipe key for reclaiming tokens from malicious holders, freeze key for temporarily blocking an account. Each control is its own key, enabling threshold-key governance. - **[7:30] Token association — opt-in receivers** — https://www.youtube.com/watch?v=pkctg86cjsU&t=450s Before an account can hold a token, it must associate with it. This protects high-profile users from unwanted airdrops showing up in their account (and from potential tax liability on those airdrops in some jurisdictions). - **[9:00] KYC grant and live transfers** — https://www.youtube.com/watch?v=pkctg86cjsU&t=540s The issuer grants Alice and Bob KYC (required because VSAN6 is KYC-gated), then transfers 20,000 tokens to Alice in a single transaction that settles in seconds with full finality. - **[10:00] Atomic swap across three assets** — https://www.youtube.com/watch?v=pkctg86cjsU&t=600s Alice atomically swaps 100 of demo-token-one for 10,000 VSAN6 and 5 HBAR with Bob — three asset movements in a single atomic transaction. Any insufficient balance would cause the whole thing to fail. ## V-Sum Seven — July 13, 2021 Event page: https://v-sum.com/events/seven ### Fabrica — Fabrica Technical Briefing - Slug: `v-fabrica` - URL: https://v-sum.com/briefing/v-fabrica - Presenter: Federico Pomi & Daniel Rollingher (LinkedIn: https://www.linkedin.com/in/fedepo/) - YouTube: https://www.youtube.com/watch?v=W1CVPTZ6s6E - Tags: blockchain, nft Federico, CEO and co-founder of Fabrica, presents Fabrica — a platform that makes real estate programmable by wrapping each property in a legal trust whose ownership is represented by a non-fungible token. The demo walks through a complete on-chain land transaction on the Fabrica platform: a buyer picks a plot, clears KYC, links a Plaid-connected Chase checking account, signs a transfer agreement, and the NFT plus bank transfer settle together in about three minutes — with a recorded county deed and land-tax-assessor appointment falling out of the same flow. Because Fabrica uses a standard NFT contract, each property shows up on OpenSea with full transaction history, priced in Sila USD. Federico closes with the broader vision — collateralize, borrow against, fractionalize, or earn DeFi-vault yield on real property — and Fabrica's state-by-state expansion in California, Arizona, New Mexico, and Colorado. **Chapters:** - **[0:00] Introduction to Fabrica — programmable real estate** — https://www.youtube.com/watch?v=W1CVPTZ6s6E&t=0s Federico, CEO and co-founder of Fabrica, introduces Fabrica — a platform that makes real estate programmable. The largest asset class in the world, still managed through paperwork, fingerprints, and notaries. - **[0:30] Trust + NFT — how a property becomes a token** — https://www.youtube.com/watch?v=W1CVPTZ6s6E&t=30s Federico explains the Fabrica architecture: each real property is wrapped in a legal trust that holds title, and ownership of the trust is represented as a non-fungible token. Transfer the NFT, transfer the property. - **[1:30] Demo: buying a plot of land in three minutes** — https://www.youtube.com/watch?v=W1CVPTZ6s6E&t=90s Live demo of the Fabrica buyer experience — browsing listed land plots, inspecting the coordinates, boundary, legal description, and transaction history, and clicking through to checkout at $28,000. - **[3:00] KYC + Plaid checkout** — https://www.youtube.com/watch?v=W1CVPTZ6s6E&t=180s Buyer-side KYC is already complete; linking a Plaid-connected Chase checking account verifies funds. The checkout resembles an Amazon flow — no blockchain jargon in front of the end buyer. - **[4:00] Transfer agreement + simultaneous NFT and bank transfer** — https://www.youtube.com/watch?v=W1CVPTZ6s6E&t=240s Signing the transfer agreement triggers a coordinated move — bank funds to the seller and NFT to the buyer — and the recorded deed and land-tax-assessor appointment fall out of the same flow. - **[5:30] Fabrica NFTs on OpenSea** — https://www.youtube.com/watch?v=W1CVPTZ6s6E&t=330s Because Fabrica uses a standard NFT contract, every property shows up on OpenSea with full transaction history, priced in Sila USD (the stablecoin Fabrica uses on-chain). - **[6:30] Formation document, recorded deed, and IPFS** — https://www.youtube.com/watch?v=W1CVPTZ6s6E&t=390s Every Fabrica token carries attached legal documents — a trust formation instrument (stored on IPFS) and a recorded county deed — proving the token holder owns the underlying real property. - **[9:30] Where programmable property goes next** — https://www.youtube.com/watch?v=W1CVPTZ6s6E&t=570s The broader vision: once real estate is an NFT, tap into any NFT-native primitive — collateralized on-chain mortgages that refinance in seconds, fractional ownership, DeFi vault yield on property you own. - **[10:00] State-by-state expansion** — https://www.youtube.com/watch?v=W1CVPTZ6s6E&t=600s Fabrica operates in California, Arizona, New Mexico, and Colorado — each state needs its own licensing and fine-tuned legal instrument, but the architecture is designed to expand to any jurisdiction, including abroad. ### Pinata — Pinata Technical Briefing - Slug: `v-pinata` - URL: https://v-sum.com/briefing/v-pinata - Presenter: Kyle Tut & Justin Hunter (LinkedIn: https://www.linkedin.com/in/kyletut/) - Company: https://www.pinata.cloud - YouTube: https://www.youtube.com/watch?v=iXpvhy9avLw - Tags: data-infrastructure, developer-tools Pinata manages off-chain data for blockchain applications — the infrastructure most NFT marketplaces (OpenSea, Rarible, and many others) quietly rely on. Kyle Tut, co-founder and CEO of Pinata, explains why on-chain storage is economically impractical (roughly $4M per GB on Ethereum) and how IPFS content identifiers (CIDs) give NFT creators tamper-proof references to their underlying files — you cannot silently swap out a CID the way you can a traditional Dropbox link. The demo covers Pinata's Dropbox-style upload UI, IPFS infrastructure run by Pinata to keep retrieval fast, dedicated per-customer gateways that serve IPFS content from your own domain (mypinata.cloud or your TLD) while preserving CID-level integrity, and Pinata's audit-trail approach for legitimately-updatable NFTs in gaming and interactive-art use cases. **Chapters:** - **[0:00] Introduction to Pinata — off-chain data for on-chain apps** — https://www.youtube.com/watch?v=iXpvhy9avLw&t=0s Kyle Tut, co-founder and CEO of Pinata, introduces Pinata — the off-chain data layer for blockchain applications. Justin Hunter (originally Pinata user #256) joins as co-presenter. - **[0:30] Why not store NFT data on-chain** — https://www.youtube.com/watch?v=iXpvhy9avLw&t=30s Blockchains are bad at storing lots of data — 1 GB on Ethereum would cost roughly $4M. Applications that want to prove their asset data is untampered without the on-chain storage cost need a different primitive. - **[1:30] IPFS content identifiers — tamper-proof references** — https://www.youtube.com/watch?v=iXpvhy9avLw&t=90s IPFS generates a content identifier (CID) from the bytes of a file. Embed the CID in an NFT and the data underneath cannot be silently swapped out — unlike a traditional URL or Dropbox link, where the content behind a link can change. - **[2:00] NFT marketplaces run on Pinata infrastructure** — https://www.youtube.com/watch?v=iXpvhy9avLw&t=120s Most major NFT marketplaces (OpenSea, Rarible, and many others) as well as individual creators rely on Pinata to serve IPFS content reliably. Pinata's API powers most of the integrations; the Dropbox-style UI covers the rest. - **[3:30] Pinata dashboard — upload and manage IPFS content** — https://www.youtube.com/watch?v=iXpvhy9avLw&t=210s Pinata's UI surfaces CIDs with a traditional Dropbox-like file manager, backed by Pinata-run IPFS infrastructure that keeps retrieval fast and predictable. - **[4:00] Dedicated gateways for custom branding** — https://www.youtube.com/watch?v=iXpvhy9avLw&t=240s Dedicated Pinata gateways (e.g. tutorial.mypinata.cloud, kyletut.com/ipfs) let creators and marketplaces serve IPFS content from their own domain instead of ipfs.io or Pinata's public gateway — while preserving CID-level content security. - **[5:30] Updating NFT content with audit trails** — https://www.youtube.com/watch?v=iXpvhy9avLw&t=330s Because NFTs increasingly want mutable data (game assets, living art), Pinata treats CIDs as a way to prove a version of the data — an audit trail of CID swaps gives you provable, traceable NFT updates without breaking the token. - **[6:00] Living NFTs in gaming** — https://www.youtube.com/watch?v=iXpvhy9avLw&t=360s The gaming and interactive-art use case: NFTs don't have to be immutable. Pinata is building tooling around CID history so developers can update the asset behind a token and keep a verifiable history of every change. ### Sardine — Sardine Technical Briefing - Slug: `v-sardine` - URL: https://v-sum.com/briefing/v-sardine - Presenter: Soups Ranjan & Aditya Goel (LinkedIn: https://www.linkedin.com/in/soupsranjan/) - Company: https://www.sardine.ai - YouTube: https://www.youtube.com/watch?v=6opRBJKHT-w - Tags: compliance, identity, payments Soups Ranjan, CEO and co-founder of Sardine, walks through the Sardine fraud and compliance API — a single endpoint for fintechs, crypto exchanges, challenger banks, and NFT platforms to prevent fraud, run KYC, monitor crypto transactions, and stay on top of AML and sanctions (PEP/SDN) screening. The demo shows how Sardine catches fraudsters running mobile emulators like BlueStacks, disposable phone numbers, and stolen dark-web identities — combining behavioral biometrics, device intelligence, and telco/social-graph enrichment with live Chainalysis and Coinbase Analytics calls. A no-code rule editor lets ops analysts chain dozens of fraud and AML typologies without writing code, and adverse-media signals cut AML false positives that plague traditional transaction-monitoring rules. **Chapters:** - **[0:00] Introduction to Sardine** — https://www.youtube.com/watch?v=6opRBJKHT-w&t=0s Soups Ranjan introduces Sardine — the fraud and compliance API-as-a-service for fintechs, crypto on-ramps, exchanges, NFT marketplaces, and cross-border commerce. - **[0:30] Stripe for high-risk merchants** — https://www.youtube.com/watch?v=6opRBJKHT-w&t=30s How Sardine positions itself as a single API for fraud prevention and AML compliance across the hardest merchant categories, with founding-team experience at Coinbase and Revolut. - **[1:30] The fraudster's mindset** — https://www.youtube.com/watch?v=6opRBJKHT-w&t=90s Live walk-through from the attacker's side — VPNs, mobile emulators like BlueStacks, stolen dark-web identities, disposable emails, and prepaid phone numbers used to open fintech and crypto accounts. - **[3:00] Behavioral biometrics at onboarding** — https://www.youtube.com/watch?v=6opRBJKHT-w&t=180s How Sardine captures typing, tapping, swiping, mouse movement and context switches — so long-term-memory fields like name, address, and SSN are scored differently for real customers vs. fraudsters copy-pasting dark-web data. - **[4:30] ML fraud scoring with Chainalysis and Coinbase Analytics** — https://www.youtube.com/watch?v=6opRBJKHT-w&t=270s Supervised and unsupervised ML models score each customer across a consortium of tens of millions of fintech and crypto consumers, with live calls to Chainalysis and Coinbase Analytics for crypto withdrawal risk. - **[5:30] KYC: sanctions, PEP and SDN screening** — https://www.youtube.com/watch?v=6opRBJKHT-w&t=330s Single-API KYC covering SSN verification, sanctions screening, politically-exposed-person checks, and suspected designated-nationals matching — all returned alongside the fraud score. - **[7:30] Identity correlation across telco, social, and bureau** — https://www.youtube.com/watch?v=6opRBJKHT-w&t=450s How Sardine correlates telco registration, social-media footprint, bureau identity, and document-KYC to flag mismatches — the dashboard surfaces all of them per user for analyst review. - **[9:00] No-code rule editor for fraud and AML typologies** — https://www.youtube.com/watch?v=6opRBJKHT-w&t=540s Dozens of built-in fraud and AML rule typologies (withdrawal to multiple high-risk crypto addresses, name mismatch vs bank account, high-risk carrier, low social graph) that ops analysts can chain without writing code. - **[10:30] Cutting AML false positives with adverse-media signals** — https://www.youtube.com/watch?v=6opRBJKHT-w&t=630s Why traditional AML rules (just transaction amount and count) produce too many false positives, and how Sardine combines adverse-media, crypto address risk, and device/behavior signals for a holistic AML picture. ## V-Sum Eight — September 28, 2021 Event page: https://v-sum.com/events/eight ### Astra — Astra Technical Briefing - Slug: `v-astra` - URL: https://v-sum.com/briefing/v-astra - Presenter: Gil Akos & Sam Morgan (LinkedIn: https://www.linkedin.com/in/gilakos/) - YouTube: https://www.youtube.com/watch?v=DW5eoDC8BMk - Tags: payments, developer-tools Gil Akos, co-founder and CEO of Astra, demos the Astra automation platform for money movement. Astra\'s thesis: ACH and AFP are fragile and archaic, but below the surface lies an iceberg of origination risk, returns, and entitlements that blocks fintechs from shipping money movement quickly. Astra wraps this complexity in a four-step integration: create a UserIntent, walk the user through a single OAuth 2.0 authorization screen (terms, SMS code, optional account linking, redirect), link bank accounts (managed Plaid, bring-your-own processor tokens, or manual account+routing), and create Routines — rule-driven automations like "when destination balance drops below $100, move $500 in." Routines run in the background, firing transfers automatically. The closing architecture segment contrasts origination (fintech → sponsor bank → one-way ACH debit) with Astra\'s orchestration model (fintech → Astra → debit source + credit sponsor bank) for higher settlement fidelity and faster speed, with the goal of enabling fintechs to eliminate origination risk and capture more recurring inbound deposits (typically ~$1,200 per user per month). **Chapters:** - **[0:00] Introduction to Astra — automation for money movement** — https://www.youtube.com/watch?v=DW5eoDC8BMk&t=0s Gil Akos, co-founder and CEO of Astra, frames Astra as an automation platform for money movement — when a user adds an account to their financial graph, there should be a layer that programmatically moves funds between accounts based on rules. - **[1:30] ACH and AFP are fragile — an iceberg problem** — https://www.youtube.com/watch?v=DW5eoDC8BMk&t=90s Existing rails (ACH, AFP) are "fragile and archaic." On the surface you need a UI and KYC; below the waterline lies the real work (origination risk, returns, entitlements) that blocks most fintechs from shipping money-movement features quickly. - **[2:30] Astra's ideal platform — fast, rule-driven, compliant** — https://www.youtube.com/watch?v=DW5eoDC8BMk&t=150s Astra's design principles: settlement fidelity across multiple speeds (not just next-day), automation by rule (balance below threshold → move $500), managed compliance so the integrator takes on less risk, and day-counted (not month-counted) go-live. - **[3:30] Astra developer dashboard and Postman** — https://www.youtube.com/watch?v=DW5eoDC8BMk&t=210s From the Astra developer dashboard, Gil creates a client, sets a redirect URI, and pulls up Astra's Postman collection with pre-built environment variables — then walks through the four-step integration to live money movement. - **[4:30] Step 1 — create a UserIntent** — https://www.youtube.com/watch?v=DW5eoDC8BMk&t=270s POST /user_intents pre-registers an end user in Astra's system. Astra returns an ID, and a subsequent GET /user_intents/{id} returns the record Gil will use in the authorization flow. - **[5:00] Step 2 — OAuth 2.0 user authorization** — https://www.youtube.com/watch?v=DW5eoDC8BMk&t=300s The single UI screen Astra requires: the end user accepts terms, confirms an SMS code, optionally links bank accounts, and is redirected back with an authorization code. The developer exchanges the code for an access token that scopes all subsequent calls. - **[6:00] Step 3 — link accounts (managed Plaid, processor tokens, manual)** — https://www.youtube.com/watch?v=DW5eoDC8BMk&t=360s Astra supports three account-linking paths: a managed Plaid instance (optionally white-labeled), a bring-your-own Plaid integration with processor tokens, and manual routing+account entry for accounts the developer already owns. - **[8:30] Step 4 — create routines** — https://www.youtube.com/watch?v=DW5eoDC8BMk&t=510s Routines are the "sexy part": pre-built rule templates like "when destination balance < $100, move $500 in" that run in the background, firing transfers automatically without the end user intervening each time. - **[9:30] Origination vs. orchestration payment architecture** — https://www.youtube.com/watch?v=DW5eoDC8BMk&t=570s Gil contrasts origination (fintech → sponsor bank → ACH debit, one-way pull) with Astra's orchestration model: fintech → Astra → ACH debit from source bank, then ACH credit into the sponsor bank — higher settlement fidelity and faster transfer speed. ### Alloy — Alloy Technical Briefing - Slug: `v-alloy` - URL: https://v-sum.com/briefing/v-alloy - Presenter: Jason Ioannides & Monica Murthy (LinkedIn: https://www.linkedin.com/in/jason-ioannides/) - Company: https://www.alloy.com - YouTube: https://www.youtube.com/watch?v=5oYltNVqY0g - Tags: identity, compliance Monica Murthy and Jason Ioannides of Alloy demo the Alloy identity decisioning platform — an "identity command center" financial institutions use to manage the customer lifecycle across fraud detection, KYC, AML, transaction monitoring, and (launching next month) credit underwriting. The briefing focuses on Alloy's onboarding product. At the core is the Alloy workflow — a visual no-code orchestration of 70+ third-party data sources (Iovation, LexisNexis, Socure, Ekata, ID Analytics, and more) that fan out from a single API call and return a consolidated approve/review/decline outcome. Compliance teams can edit rules in plain English (IF ID Analytics score ≥ 850 OR Socure Sigma Fraud ≥ 0.985), add entirely new data sources, and flip conditional-execution gates (skip KYC/AML on obvious frauds) — all from the UI, with version control, a change log, and role-based manual-review queues. Evaluation views expose every signal that fired and every raw data-source response for audit. **Chapters:** - **[0:00] Introduction to Alloy — identity command center** — https://www.youtube.com/watch?v=5oYltNVqY0g&t=0s Monica (partnerships lead) introduces Alloy — an identity command center for financial institutions. Alloy gives banks and fintechs a transparent, dynamic way to manage the customer lifecycle across fraud detection, KYC, AML, transaction monitoring, and credit underwriting. - **[1:30] Workflows — visual Alloy business logic** — https://www.youtube.com/watch?v=5oYltNVqY0g&t=90s Jason Ioannides (solutions consulting) walks through Alloy's "workflow" — a visual representation of the Alloy API's business logic. A workflow orchestrates calls to many third-party data sources (Iovation, LexisNexis, Socure, Ekata, ID Analytics, and 70+ others) and resolves their outputs into tags and a final outcome. - **[3:00] Individual onboarding best-practices workflow** — https://www.youtube.com/watch?v=5oYltNVqY0g&t=180s Tour of Alloy's "Best Practices for Individual Onboarding" starter workflow — a small cross-section of the 70+ integrated data sources, used for standard savings / DDA account onboarding by banks. - **[3:30] Rules as no-code conditional logic** — https://www.youtube.com/watch?v=5oYltNVqY0g&t=210s Clicking into the "Fraud Warning" tag reveals a plain-English if statement: if ID Analytics ID Score ≥ 850 OR Socure Sigma Fraud Score ≥ 0.985, apply the tag. Swap data attributes (ID Analytics → Socure synthetic fraud), comparison operators, and thresholds in-UI — no engineering lift. - **[4:30] Add a new data attribute with no code** — https://www.youtube.com/watch?v=5oYltNVqY0g&t=270s Adding an Ekata identity check score to the rule: select the Ekata node, connect it to the tag with OR, pick the identityCheckScore from the attribute dropdown, set the threshold. That's all the change management compliance teams need. - **[5:30] Conditional data-source execution saves money** — https://www.youtube.com/watch?v=5oYltNVqY0g&t=330s Alloy can gate downstream calls on upstream outcomes — if Denied Fraud is set, skip LexisNexis Instant ID and the KYC/AML stack entirely. Fewer data-source calls on obvious frauds = material cost savings at scale. - **[6:30] Outcomes — approve, manual review, decline** — https://www.youtube.com/watch?v=5oYltNVqY0g&t=390s Outcome logic: if denied_fraud is set, decline; else if the KYC checks pass, approve; else route to manual review. All editable in the same no-code UI. - **[7:00] Add an adverse-media data source in-UI** — https://www.youtube.com/watch?v=5oYltNVqY0g&t=420s Live addition of LexisNexis World Compliance as an adverse-media data source: pick the service, wire it into the workflow, add a threshold rule (adverse_media_confidence_score ≥ 0.99), and tag the evaluation. End-to-end in under a minute. - **[8:00] Version control and change log** — https://www.youtube.com/watch?v=5oYltNVqY0g&t=480s Saving a workflow produces a named new version (e.g. v325 → v337) with a human-readable change note and an auto-generated change log. Every historical version is browsable; saving does not auto-activate — flip the active flag manually. - **[9:30] Evaluation view — tag-by-tag breakdown** — https://www.youtube.com/watch?v=5oYltNVqY0g&t=570s The Evaluations view shows per-customer outcomes with a tag-by-tag breakdown of which data sources matched which attributes. In this demo, Todd Spencer fails KYC on name mismatch via LexisNexis — the workflow routes him to manual review with the exact reason surfaced. - **[11:30] Manual review queue with role-based saved searches** — https://www.youtube.com/watch?v=5oYltNVqY0g&t=690s Alloy's review queue supports saved searches (e.g. "KYC Reviews") that can be scoped to specific reviewer roles — KYC team sees KYC cases, loss-prevention team sees fraud cases. Individual reviews lock to a reviewer for 15 minutes and fire an outgoing webhook on status change. ### OpenNode — OpenNode Technical Briefing - Slug: `v-opennode` - URL: https://v-sum.com/briefing/v-opennode - Presenter: Rui Gomes & Julie Landrum (LinkedIn: https://www.linkedin.com/in/ruigomeseu/) - Company: https://www.opennode.com - YouTube: https://www.youtube.com/watch?v=Knwn-PiVY4E - Tags: payments, crypto-infrastructure OpenNode is a Bitcoin infrastructure provider focused on Bitcoin payments and payouts. The thesis: Bitcoin is the internet-native currency — global, decentralized, borderless, low-cost, and instantly final via the Lightning Network — and that makes it a better rail for online payments than legacy schemes. OpenNode powers Bitcoin payments for McDonald's El Salvador locations, Substack creator subscriptions, and Bitcoin-native companies like Fold. The demo walks through the OpenNode merchant dashboard (on-chain vs Lightning requests, live QR payment, USD auto-conversion so merchants have no volatility risk), payment buttons and invoicing, split settlement that keeps a configurable percentage in Bitcoin and the rest in fiat, and the OpenNode API for generating charges and paying out Bitcoin or Lightning without ever holding the coins. **Chapters:** - **[0:00] Introduction to OpenNode — Bitcoin payments infrastructure** — https://www.youtube.com/watch?v=Knwn-PiVY4E&t=0s OpenNode is a Bitcoin infrastructure provider focused on Bitcoin payments and payouts. The thesis: Bitcoin is the internet-native currency — global, decentralized, scalable, low-cost, instantly final, borderless — making it a better technology for online payments than the traditional rails. - **[1:00] Why Bitcoin and the Lightning Network** — https://www.youtube.com/watch?v=Knwn-PiVY4E&t=60s Why OpenNode is Bitcoin-only: strongest network effects, strongest security, clearest regulatory framework. Scaling comes from the Lightning Network, a permissionless trustless second layer that moves Bitcoin payments infinitely without involving a third party. - **[1:30] Customers: McDonald's El Salvador, Substack, Fold** — https://www.youtube.com/watch?v=Knwn-PiVY4E&t=90s OpenNode powers Bitcoin payments for McDonald's El Salvador locations and online, Substack creator Bitcoin subscriptions, and Bitcoin-native companies like Fold and Lastbit. - **[2:30] Merchant dashboard — on-chain and Lightning payments** — https://www.youtube.com/watch?v=Knwn-PiVY4E&t=150s The OpenNode merchant dashboard: create a payment request and the payer can settle on-chain (traditional Bitcoin) or via Lightning (instant, low cost). A Lightning wallet QR scan completes in seconds — full final settlement on Bitcoin mainnet. - **[3:30] Auto-convert to USD — no merchant volatility** — https://www.youtube.com/watch?v=Knwn-PiVY4E&t=210s Merchants can auto-convert incoming Bitcoin to USD (or other supported fiat) at the moment a payment request is created. OpenNode absorbs the volatility risk — create a $1 request, receive $1 minus fees. - **[4:30] Payment buttons, invoicing, and e-commerce integrations** — https://www.youtube.com/watch?v=Knwn-PiVY4E&t=270s OpenNode ships payment buttons (no website needed), PDF invoicing, and integrations with Shopify, BigCommerce, and major open-source e-commerce platforms. - **[5:30] Split settlement: 40% Bitcoin / 60% USD** — https://www.youtube.com/watch?v=Knwn-PiVY4E&t=330s Split settlement lets a merchant keep any percentage of incoming payments in Bitcoin while auto-converting the rest to fiat. Applies to all incoming payments — including internal transfers between OpenNode accounts. - **[7:30] OpenNode API — one parameter required** — https://www.youtube.com/watch?v=Knwn-PiVY4E&t=450s Tour of the OpenNode API: generate an API key, create a charge in either satoshis or USD (OpenNode locks the exchange rate), and get back a Bitcoin address, a Lightning invoice, and enough data to build a custom checkout — or just link to OpenNode's hosted checkout page. - **[10:00] Webhooks and payouts — paying Bitcoin without holding it** — https://www.youtube.com/watch?v=Knwn-PiVY4E&t=600s Webhooks fire the moment a payment settles. Payouts go from OpenNode-to-OpenNode or directly to any Bitcoin address or Lightning invoice — top up in fiat, send Bitcoin, never touch the coins yourself. ## V-Sum Nine — November 9, 2021 Event page: https://v-sum.com/events/nine ### Numary — Numary Technical Briefing - Slug: `v-numary` - URL: https://v-sum.com/briefing/v-numary - Presenter: Clément Salaün (LinkedIn: https://www.linkedin.com/in/clementsalaun/) - Company: https://numary.com - YouTube: https://www.youtube.com/watch?v=LSv9sXdGrnA - Tags: payments, developer-tools Clément of Numary demos Numary\'s open-source ledger and Numscript — a DSL purpose-built to model the hidden money-flow complexity of marketplaces and platforms (where customer payments, commission splits, and seller payouts quickly become an operational mess). The demo clones a DoorDash-style marketplace in Numscript: a "world" account injects funds, a coupon account funds a $15k FALL21 marketing campaign with a $10-per-redemption metadata value, an order\'s payment account pulls first from the user\'s wallet and falls back to world, and a single atomic Numscript splits the order payment four ways — 85% to the restaurant, a delivery amount to the rider, platform fees, and VAT-applicable taxes. Each step produces a transaction with clean source/destination postings in the Numary ledger, which the fintech later reconciles against Stripe, Wise, or their payment provider of record. The closing rider payout demonstrates the reconciliation handoff between Numary\'s internal ledger and the external payment system — the Numscript repo is open-sourced on GitHub at github.com/numary. **Chapters:** - **[0:00] Introduction to Numary and Numscript** — https://www.youtube.com/watch?v=LSv9sXdGrnA&t=0s Clément (Numary) demos Numary's open-source ledger and Numscript, the DSL designed to model complex money flows in marketplaces and platforms — where inflows, outflows, and commission splits quickly create a hidden mess in the back office. - **[1:30] Modeling the DoorDash money flow** — https://www.youtube.com/watch?v=LSv9sXdGrnA&t=90s The "blue part" of a marketplace flowchart — decoupling customer payments from seller payouts — is where ledgers become necessary. The demo clones DoorDash-style flows with riders, restaurants, a platform commission, and marketing coupons. - **[2:30] Numscript basics — world account and postings** — https://www.youtube.com/watch?v=LSv9sXdGrnA&t=150s Numscript moves assets between accounts. The "world" account is the only one allowed to spend money it doesn't have, letting developers inject funds into the ledger. A simple send from world → user_01 creates a single-posting transaction. - **[4:00] Multiple destinations with percentages** — https://www.youtube.com/watch?v=LSv9sXdGrnA&t=240s Numscript supports multiple destinations in one transaction — e.g. 10% to user_01 and the remainder to user_02 — producing a transaction with two postings. This is the primitive behind every split in the demo. - **[4:30] Funding marketing coupons** — https://www.youtube.com/watch?v=LSv9sXdGrnA&t=270s The first real Numscript models a coupon: $15k budget set aside for code "FALL21", with every redemption worth $10. The coupon is a first-class account in the ledger with metadata for per-use value — so the platform can never overspend the marketing budget. - **[7:30] Redeeming a coupon into a user wallet** — https://www.youtube.com/watch?v=LSv9sXdGrnA&t=450s When a user enters the coupon code, a Numscript reads the coupon's per-use value from metadata and credits the user's wallet. This produces a second transaction — 10 moved from the FALL21 coupon account to user_42's wallet. - **[9:30] Order payment — pull from wallet, then from world** — https://www.youtube.com/watch?v=LSv9sXdGrnA&t=570s Order payments use Numscript's source chaining: pull first from the user's wallet, then fall back to the world account to synthesize the remainder (reconciled later with Stripe). Two postings record both source flows into a single payment account per order. - **[11:30] Split an order across rider, restaurant, platform, taxes, fees** — https://www.youtube.com/watch?v=LSv9sXdGrnA&t=690s A final Numscript splits the payment account into four postings: restaurant (85%), delivery rider, platform (with 20% of that going to taxes on VAT-applicable items), and platform fees — all in one atomic transaction. - **[13:30] Paying out the rider** — https://www.youtube.com/watch?v=LSv9sXdGrnA&t=810s A closing Numscript registers the actual payout to the rider's external account — a transaction that would later be reconciled against the upstream payment system (Stripe, Wise, etc.). ### Basis Theory — Basis Theory Technical Briefing - Slug: `v-basistheory` - URL: https://v-sum.com/briefing/v-basistheory - Presenter: Brian Billingsley & James Armstead (LinkedIn: https://www.linkedin.com/in/bbillingsley/) - Company: https://basistheory.com - YouTube: https://www.youtube.com/watch?v=Wjo0o_bmbqM - Tags: data-infrastructure, developer-tools, compliance Brian, co-founder of Basis Theory, walks through the Basis Theory platform — a developer-first tokenization and encryption service for any sensitive value on the internet. The demo covers tenants (test/prod, sub-customer, or geo-split workspaces), Elements (drop-in UI that keeps you out of PCI scope for cards, bank accounts, SSNs, and driver's licenses), and server-to-server apps gated by PCI Level 1 attestation. Basis Theory tokenizes any serializable value — strings, documents, PII, cards, bank accounts — and returns a consistent token shape with type, fingerprint, and non-sensitive metadata so developers can dedupe without decryption. Customers can roll their own keypair (bring-your-own-key) so Basis Theory only sees ciphertext. The reactor system ships pre-built serverless templates (Stripe, Braintree, BIN analysis via Perapt) and private reactors for custom integrations, allowing partners to tokenize a card once and route to multiple processors without ever touching the raw PAN. **Chapters:** - **[0:00] Introduction to Basis Theory** — https://www.youtube.com/watch?v=Wjo0o_bmbqM&t=0s Brian, a co-founder of Basis Theory, introduces the product as a developer-first tokenization and encryption platform for the internet. Everything shown is dog-fooded on top of the Basis Theory APIs, SDKs, and Terraform module — build on the portal or on the APIs directly. - **[0:30] Tenants — test/prod, sub-customers, geo splits** — https://www.youtube.com/watch?v=Wjo0o_bmbqM&t=30s Basis Theory tenants let you split data by environment (test vs. prod), by sub-customer, or by geography. From the portal, Brian creates a new application and chooses from several application types depending on the job to be done. - **[1:30] Elements vs. server-to-server apps and PCI scope** — https://www.youtube.com/watch?v=Wjo0o_bmbqM&t=90s Elements drop into your UI so you can take in cards, bank accounts, or other PII (SSNs, driver's licenses) without ever touching the raw data — keeping you out of PCI scope. Server-to-server apps give you programmatic access, and PCI Level 1 attestation is required to decrypt card PANs. - **[2:00] Tokenize any serializable value** — https://www.youtube.com/watch?v=Wjo0o_bmbqM&t=120s In the sandbox, Brian tokenizes a simple string. Any serializable value (string, bool, document, card, bank account) can be tokenized and every response is the same shape: token, tenant id, type, creator, ISO timestamp, and optional child tokens. - **[2:30] PII tokens and bring-your-own keys** — https://www.youtube.com/watch?v=Wjo0o_bmbqM&t=150s For PII data, Basis Theory can either encrypt with its own keys (after reviewing your PCI/SOC2 due diligence) or let you roll your own keypair so Basis Theory only ever sees the ciphertext — only your private key can decrypt. - **[4:00] Card and bank account tokens with fingerprinting and metadata** — https://www.youtube.com/watch?v=Wjo0o_bmbqM&t=240s Tokenizing a card returns a masked PAN, a card-type tag, and a fingerprint you can use for dedupe without decryption. Bank accounts return tokenized account numbers (not routing numbers). Both accept attached non-sensitive metadata for analysis and lookup. - **[6:00] Reactors — pre-built serverless functions (Stripe, Braintree, BIN lookup)** — https://www.youtube.com/watch?v=Wjo0o_bmbqM&t=360s Reactors are pre-built serverless functions — e.g., a Stripe reactor using the Stripe SDK — that let you run partner SDKs against your Basis Theory tokens. Private reactors let you ship custom integrations from your own GitHub repo without exposing them publicly. - **[7:30] End-to-end: card element → Stripe / Braintree / BIN analysis** — https://www.youtube.com/watch?v=Wjo0o_bmbqM&t=450s A worked example: a user pastes a card into a Basis Theory element, gets a token back, and the token is then used to create a Stripe token, a Braintree token, and to run a BIN analysis (debit vs. credit, processor routing) via Perapt — all without touching the underlying PAN. ## V-Sum Ten — December 14, 2021 Event page: https://v-sum.com/events/ten ### Helium — Helium Technical Briefing - Slug: `v-helium` - URL: https://v-sum.com/briefing/v-helium - Presenter: Mark Phillips & Abhay Kumar (LinkedIn: https://www.linkedin.com/in/mark-phillips-255b757/) - Company: https://www.helium.com - YouTube: https://www.youtube.com/watch?v=1WfrU-Rra0M - Tags: blockchain, defi Helium walks through the largest wireless network in the world — an IoT network built on the Helium blockchain and powered by token incentives (HNT, trading ~$27.50 with a ~$3.2B market cap at time of demo). explore.helium.com visualizes the hotspots providing LoRaWAN coverage in cities like San Francisco. Helium hotspots (40+ approved manufacturers under the Decentralized Wireless Alliance) plug into power and internet at home, broadcasting a long-range IoT signal for sensors and soon handsets. The live demo uses a Dragino LDS-S01 door sensor: opening and closing the door sends 9-byte packets over the Helium network, picked up by the fittingly named "stable-rouge-puma" hotspot and routed to console.helium.com in real time. The packets flow onward via a Datacake integration into a dashboard — a full end-to-end application built with a cheap sensor and the public network. On the incentive side, the hotspot routing the demo traffic earned ~0.339 HNT over 7 days and ~1.3 HNT over 30 days from proof-of-coverage mining plus a small Data Credit reward for actually carrying the packets. **Chapters:** - **[0:00] Introduction to Helium** — https://www.youtube.com/watch?v=1WfrU-Rra0M&t=0s Helium has been building what is now the largest wireless network in the world for about three years, on the Helium blockchain. Unlike most crypto, Helium has a very direct utility: sending wireless data for IoT sensors — and soon handsets and computers. - **[1:00] Explore.helium.com — hotspots on the map** — https://www.youtube.com/watch?v=1WfrU-Rra0M&t=60s explore.helium.com shows the public blockchain data: a map of hotspots providing LoRaWAN coverage in hexagons. The HNT token trades around $27.50 with a ~$3.2B market cap at time of demo. - **[2:00] What a Helium hotspot is** — https://www.youtube.com/watch?v=1WfrU-Rra0M&t=120s A Helium hotspot is a wireless-AP-style device (~40 manufacturers approved by the Decentralized Wireless Alliance) that plugs into power and internet at home, providing LoRaWAN coverage for long-range IoT data. - **[3:00] HNT utility token and real applications** — https://www.youtube.com/watch?v=1WfrU-Rra0M&t=180s HNT is a layer-one utility token on the Helium blockchain. Thousands of companies and developers deploy applications on the network — e.g. air-quality monitoring and sensor tracking — with data routed from sensors through hotspots to cloud apps. - **[4:30] LDS-S01 door sensor live demo** — https://www.youtube.com/watch?v=1WfrU-Rra0M&t=270s The live demo uses a Dragino LDS-S01 door sensor. When the magnet separates, a packet is sent over the Helium network to tell an application the door is open or closed — a minimal end-to-end proof point. - **[5:30] console.helium.com packet feed** — https://www.youtube.com/watch?v=1WfrU-Rra0M&t=330s At console.helium.com, 9-byte packets from the door sensor appear live, with the hotspot that picked them up (named "stable-rouge-puma" from its public key) visible alongside RF and wireless stats. - **[7:00] Datacake dashboard integration** — https://www.youtube.com/watch?v=1WfrU-Rra0M&t=420s The console pipes packets to a Datacake dashboard — a partner in the Helium ecosystem — showing how developers wire sensors into full end-to-end applications. - **[7:30] Hotspot earnings — PoC + data credit rewards** — https://www.youtube.com/watch?v=1WfrU-Rra0M&t=450s The hotspot routing the door-sensor packets earned ~0.339 HNT over 7 days and ~1.3 HNT over 30 days. Rewards come from proof-of-coverage (PoC) mining plus small Data Credit rewards for actually routing packets. ### Rainbow — Rainbow Technical Briefing - Slug: `v-rainbow` - URL: https://v-sum.com/briefing/v-rainbow - Presenter: Mike Demarais (LinkedIn: https://www.linkedin.com/in/michael-demarais-73273736/) - Company: https://rainbow.me - YouTube: https://www.youtube.com/watch?v=Q8kAwMPv9Fg - Tags: wallets, defi Rainbow introduces itself as the most accessible Ethereum wallet — built to deserve a spot on your home screen rather than forcing a 30-word seed-phrase gauntlet on new users. The demo tours what makes Rainbow distinctive: auto-discovery of ERC-20 tokens across Ethereum mainnet, Arbitrum, and Optimism merged into a unified view (no chain-switching); a Savings section wired to Compound Finance that auto-swaps any deposited asset into DAI under the hood; Uniswap liquidity-pool positions surfaced with annualized fees; NFTs as first-class citizens including floor prices, trait-based search into OpenSea, a Showcase feature for favorites, and per-wallet public web profiles like rainbowwallet.eth; a swap UI that takes any-to-any input and exposes EIP-1559 custom gas tipping; and WalletConnect as Rainbow's deliberate answer to an in-app dApp browser — connect Rainbow to any web dApp via mobile Safari and bounce back to Rainbow for action approvals. **Chapters:** - **[0:00] Introduction to Rainbow — the most accessible Ethereum wallet** — https://www.youtube.com/watch?v=Q8kAwMPv9Fg&t=0s Rainbow introduces itself as an Ethereum wallet built to deserve a spot on your phone's home screen. The thesis: Ethereum wallets are a new product category and, before long, any "finance app" people keep on their home screen will first and foremost be an Ethereum wallet. - **[1:00] Onboarding without the 30-word seed gauntlet** — https://www.youtube.com/watch?v=Q8kAwMPv9Fg&t=60s Rainbow skips the usual "write down 30 words" first experience — it drops users straight in, with an Apple Pay on-ramp for fast funding and a smoother unwrapping experience rolling out through 2022. - **[2:00] Auto-discover tokens across L1 and L2s** — https://www.youtube.com/watch?v=Q8kAwMPv9Fg&t=120s Rainbow automatically discovers ERC-20 tokens held by an address — including tokens on Arbitrum and Optimism — and merges them into a single unified token view. No chain switching like other wallets require. - **[3:00] Rainbow vs MetaMask** — https://www.youtube.com/watch?v=Q8kAwMPv9Fg&t=180s Why Rainbow pursues a richer UX than the incumbent (MetaMask) — price charts, native visualization, a real "single app" experience instead of add-custom-token-by-hand friction. - **[3:30] Savings section — Compound Finance** — https://www.youtube.com/watch?v=Q8kAwMPv9Fg&t=210s Rainbow's Savings tab is wired to Compound. Deposit any asset — even meme coins like Shiba — and Rainbow auto-swaps the deposit into DAI under the hood before routing into Compound, so the user never sees the intermediate step. - **[5:00] Uniswap pool positions, contextualized** — https://www.youtube.com/watch?v=Q8kAwMPv9Fg&t=300s Rainbow surfaces Uniswap liquidity positions with annualized fees, contextualized alongside your other holdings — turning DeFi positions into a product surface rather than a raw pair of token balances. - **[5:30] NFTs as first-class citizens** — https://www.youtube.com/watch?v=Q8kAwMPv9Fg&t=330s NFTs have been first-class in Rainbow since day one. Clicking into an NFT shows floor price for the category, image, trait-based search hooks to OpenSea, save-to-photos for using the artwork as a Twitter avatar, and a Showcase feature for favorites. - **[8:00] Web profile — rainbowwallet.eth** — https://www.youtube.com/watch?v=Q8kAwMPv9Fg&t=480s Every Rainbow wallet with an ENS name gets a public web profile at rainbow.me — visit rainbowwallet.eth to see that wallet's showcase and NFTs. A natural social layer on top of Ethereum. - **[9:30] Swap between any two assets, EIP-1559 tip control** — https://www.youtube.com/watch?v=Q8kAwMPv9Fg&t=570s The Rainbow swap UI takes any-to-any inputs — type in a source amount, destination amount, or USD value and the others auto-calculate. The view-details sheet surfaces the execution rate, and the EIP-1559 gas UI lets power users tip the miner a custom amount. - **[12:30] WalletConnect instead of an in-app dApp browser** — https://www.youtube.com/watch?v=Q8kAwMPv9Fg&t=750s Rainbow deliberately skips an in-app dApp browser in favor of WalletConnect for long-tail web experiences. The demo connects Rainbow to Uniswap in mobile Safari, logs in as rainbowwallet.eth, and starts interacting with the dApp — action approvals bounce back to Rainbow. ### Stacks — Stacks Technical Briefing - Slug: `v-stacks` - URL: https://v-sum.com/briefing/v-stacks - Presenter: Marvin Janssen & Friedger Müffke - Company: https://www.stacks.co - YouTube: https://www.youtube.com/watch?v=2PBp58RYrbA - Tags: blockchain, nft, developer-tools Marvin Janssen, technical lead at the Stacks Foundation, gives a hands-on tour of Stacks — a Bitcoin L2 blockchain that anchors every block to the Bitcoin chain via proof-of-transfer, inheriting Bitcoin's security while adding smart-contract capability. The briefing centers on writing a SIP-009 NFT in Clarity, Stacks' non-Turing-complete Lisp-based smart-contract language. Marvin uses Clarinet — the Stacks analogue of Truffle plus Ganache — to scaffold the project, opens the Clarinet console for a REPL tour of Clarity (strongly typed, with distinct signed vs unsigned integer literals), then implements the SIP-009 NFT trait (Stacks' ERC-721 equivalent) using NFT primitives baked into the language (nft-mint, nft-burn, nft-transfer) — the correct balance-sheet semantics come for free. The ownership model is user-defined: Marvin asserts that sender equals tx-sender (Clarity's msg.sender) before transferring. A closing clarinet-console session mints two NFTs, checks owners, and transfers one between principals in the local Clarity VM. **Chapters:** - **[0:00] Introduction to Stacks** — https://www.youtube.com/watch?v=2PBp58RYrbA&t=0s Marvin Janssen, technical lead at the Stacks Foundation, introduces Stacks — a Bitcoin L2 blockchain that anchors every block to the Bitcoin chain via proof-of-transfer, inheriting Bitcoin's security and exposing smart-contract capability that Bitcoin itself lacks. - **[1:00] Clarinet — local Stacks development toolkit** — https://www.youtube.com/watch?v=2PBp58RYrbA&t=60s Clarinet is the Stacks analogue of Truffle + Ganache: it scaffolds projects, runs a local Clarity VM, and supports writing, testing, and debugging smart contracts without ever hitting a real node. One command (clarinet new) creates the starter project structure. - **[1:30] Clarity — non-Turing-complete, Lisp-based, strongly typed** — https://www.youtube.com/watch?v=2PBp58RYrbA&t=90s Clarity is Stacks' smart-contract language. Deliberately non-Turing-complete (so you can reason about contracts statically) and Lisp-based, with strong typing — walk-through of the unsigned vs. signed integer distinction in a live REPL. - **[4:00] NFT primitives built into Clarity** — https://www.youtube.com/watch?v=2PBp58RYrbA&t=240s Unlike Solidity, Clarity has native NFT primitives — nft-mint, nft-burn, nft-transfer, and the matching balance-sheet plumbing — baked into the language. No standard-template copy-paste; the correct semantics come for free. - **[5:00] The SIP-009 NFT trait** — https://www.youtube.com/watch?v=2PBp58RYrbA&t=300s SIP-009 is Stacks' NFT standard (analogous to ERC-721). Clarity traits define a contract's public interface; implement the trait and you have an NFT that works with the rest of the ecosystem. - **[6:30] Implementing the SIP-009 trait** — https://www.youtube.com/watch?v=2PBp58RYrbA&t=390s Walk-through of clarinet check catching missing trait functions, then pasting a reference SIP-009 NFT implementation: get-last-token-id, get-token-uri, get-owner, transfer, and a convenience mint. - **[10:00] Principals and the tx-sender ownership check** — https://www.youtube.com/watch?v=2PBp58RYrbA&t=600s Clarity's "principal" primitive captures both standard addresses and contract addresses. The transfer function asserts that the sender argument equals tx-sender (Clarity's equivalent of msg.sender) — without that check, anyone could transfer anyone's NFT. - **[12:30] Clarinet console — local VM REPL** — https://www.youtube.com/watch?v=2PBp58RYrbA&t=750s clarinet console opens an in-process Clarity VM REPL. Deployed contracts are introspectable, standard wallets are pre-funded, and calls like contract-call? ... mint, get-owner, and transfer fire instantly and emit events just like mainnet would. ## V-Sum Eleven — January 18, 2022 Event page: https://v-sum.com/events/eleven ### Phantom — Phantom Wallet Technical Briefing - Slug: `v-phantom` - URL: https://v-sum.com/briefing/v-phantom - Presenter: Brandon Millman (LinkedIn: https://www.linkedin.com/in/brandon-millman-b093a022/) - Company: https://phantom.app/ - YouTube: https://www.youtube.com/watch?v=XRmY5PqrwGs - Tags: wallets, crypto-infrastructure Phantom presents their Solana wallet at V-Sum Eleven. Presented by co-founder Brandon Millman, covering token swaps, staking, NFT management, transaction simulation, and phishing protection. **Chapters:** - **[0:00] Introduction to Phantom** — https://www.youtube.com/watch?v=XRmY5PqrwGs&t=0s Brandon Millman introduces Phantom — the leading Solana wallet, approaching 2 million users at time of presentation. - **[1:56] Wallet features and NFT management** — https://www.youtube.com/watch?v=XRmY5PqrwGs&t=116s Walkthrough of Phantom's core wallet — token management, NFT collections, built-in token swaps, and Web3 app interaction from the browser extension. - **[4:50] Transaction simulation and security** — https://www.youtube.com/watch?v=XRmY5PqrwGs&t=290s Phantom's transaction simulation — showing users exactly what will happen before they sign. How Phantom documents and records transaction details. - **[6:55] Anti-phishing and scam protection** — https://www.youtube.com/watch?v=XRmY5PqrwGs&t=415s How Phantom combats phishing with website blocking, malicious site flagging, and API integrations to protect users from known scam addresses. - **[9:22] Key management and wallet recovery** — https://www.youtube.com/watch?v=XRmY5PqrwGs&t=562s Secret recovery phrase system — secure backup and restoration, plus managing multiple wallets and identities within a single Phantom installation. - **[11:50] Developer experience and Web3 integration** — https://www.youtube.com/watch?v=XRmY5PqrwGs&t=710s Building Web3 applications that integrate with Phantom — API overview, connection handling, and transaction signing for Solana developers. ### NFTfi — NFTfi Technical Briefing - Slug: `v-nftfi` - URL: https://v-sum.com/briefing/v-nftfi - Presenter: Stephen Young (LinkedIn: https://www.linkedin.com/in/stephen101/) - Company: https://www.nftfi.com/ - YouTube: https://www.youtube.com/watch?v=zA6GtHOcWxc - Tags: nft, defi, lending NFTfi presents their peer-to-peer NFT-backed lending marketplace at V-Sum Eleven. Presented by Stephen Young, walking through the borrower experience — listing NFTs as collateral, receiving offers, and managing loans. **Chapters:** - **[0:00] Introduction to NFTfi** — https://www.youtube.com/watch?v=zA6GtHOcWxc&t=0s Stephen Young introduces NFTfi — a peer-to-peer marketplace where users borrow crypto against NFT collateral. - **[0:33] Borrower experience and collateral listing** — https://www.youtube.com/watch?v=zA6GtHOcWxc&t=33s Demo of the borrower workflow — listing an NFT as collateral, setting loan terms (7, 14, 30, or 90 days), and signing via MetaMask. - **[2:29] Lender view and making offers** — https://www.youtube.com/watch?v=zA6GtHOcWxc&t=149s The lender side — browsing listed NFT collateral, evaluating assets, and making loan offers in the peer-to-peer marketplace. - **[3:37] Loan execution and repayment** — https://www.youtube.com/watch?v=zA6GtHOcWxc&t=217s End-to-end loan lifecycle — offer acceptance through repayment. NFTfi takes a 5% cut on interest. Borrower defaults mean the lender keeps the NFT. ### Goldfinch Finance — Goldfinch Finance Technical Briefing - Slug: `v-goldfinch` - URL: https://v-sum.com/briefing/v-goldfinch - Presenter: Mike Sall (LinkedIn: https://www.linkedin.com/in/michaelsall/) - Company: https://goldfinch.finance/ - YouTube: https://www.youtube.com/watch?v=4UDGZKLmmU0 - Tags: defi, lending, capital-markets Goldfinch Finance presents their decentralized credit protocol at V-Sum Eleven. Presented by co-founder Mike Sall, covering how Goldfinch enables crypto lending to real-world businesses through Backer and Senior Pool mechanics. **Chapters:** - **[0:00] Introduction to Goldfinch Finance** — https://www.youtube.com/watch?v=4UDGZKLmmU0&t=0s Mike Sall introduces Goldfinch — a decentralized credit protocol enabling crypto lending to real-world businesses without requiring crypto collateral. - **[0:38] Borrower pools and capital supply** — https://www.youtube.com/watch?v=4UDGZKLmmU0&t=38s Demo of the protocol — how capital flows into the Senior Pool and Borrower Pools (Almavest, Aspire, QuickCheck) reaching businesses globally. - **[1:31] Backers and liquidity providers** — https://www.youtube.com/watch?v=4UDGZKLmmU0&t=91s Goldfinch's two-sided model — Backers evaluate and fund specific borrower pools while Liquidity Providers supply capital to the Senior Pool for automated allocation. - **[4:01] Senior Pool mechanics** — https://www.youtube.com/watch?v=4UDGZKLmmU0&t=241s Deep dive into the Senior Pool — capital allocation across borrower pools, contributing and withdrawing funds, automatic diversification. - **[6:00] Borrower operations and repayment** — https://www.youtube.com/watch?v=4UDGZKLmmU0&t=360s The borrower perspective — how businesses draw down loans and make repayments that automatically flow back to capital providers on-chain. - **[6:57] GFI token and governance** — https://www.youtube.com/watch?v=4UDGZKLmmU0&t=417s GFI token distribution — staking rewards, governance rights, and the unlock schedule for community-distributed tokens. ## V-Sum Twelve — February 22, 2022 Event page: https://v-sum.com/events/twelve ### Swarm Markets — Swarm Markets Technical Briefing - Slug: `v-swarmmarkets` - URL: https://v-sum.com/briefing/v-swarmmarkets - Presenter: Philip Pieper & Sam Stone (LinkedIn: https://www.linkedin.com/in/philipppieper/) - Company: https://swarm.markets/ - YouTube: https://www.youtube.com/watch?v=Ju1fe8T-Htc - Tags: defi, capital-markets, compliance Swarm Markets presents their BaFin-licensed DeFi exchange at V-Sum Twelve. Presented by Philip Pieper, covering regulated token swaps, the dOTC peer-to-peer trading service, SX1411 token standard, and their Passport compliance system. **Chapters:** - **[0:00] Introduction to Swarm Markets** — https://www.youtube.com/watch?v=Ju1fe8T-Htc&t=0s Philip Pieper introduces Swarm Markets — the first BaFin-licensed DeFi platform, bringing regulated decentralized trading to tokenized real-world and digital assets on Ethereum and Polygon. - **[0:43] From tokenization to regulated DeFi** — https://www.youtube.com/watch?v=Ju1fe8T-Htc&t=43s Swarm's journey from building tokenization technology to leveraging the 2020 amendment of the German banking act to build a regulated DeFi trading platform. - **[4:22] Swarm trading interface and swaps** — https://www.youtube.com/watch?v=Ju1fe8T-Htc&t=262s Live demo of Swarm's DEX built on a Balancer-like architecture. Token swaps, pool scenarios, and the trading experience across SMT, DAI, and multiple asset pairs. - **[4:58] Passport: compliant on-chain identity** — https://www.youtube.com/watch?v=Ju1fe8T-Htc&t=298s Swarm's Passport system — a centralized onboarding service that writes a non-transferable NFT to users' wallets, enabling compliant interaction with regulated smart contracts. - **[6:52] dOTC trading and new features** — https://www.youtube.com/watch?v=Ju1fe8T-Htc&t=412s Demo of Swarm's dOTC (decentralized over-the-counter) trading service — peer-to-peer offers with partial fills, private offers, and expiration dates. Plus the SX1411 token standard. - **[10:52] NFTs as off-chain asset representations** — https://www.youtube.com/watch?v=Ju1fe8T-Htc&t=652s How Swarm uses NFTs to represent off-chain assets on-chain — bridging traditional finance assets into the DeFi ecosystem under regulatory compliance. ### Zero Hash — Zero Hash Technical Briefing - Slug: `v-zerohash` - URL: https://v-sum.com/briefing/v-zerohash - Presenter: Max Howenstine (LinkedIn: https://www.linkedin.com/in/maxhowenstine/) - Company: https://zerohash.com/ - YouTube: https://www.youtube.com/watch?v=1yMuKu1ReFk - Tags: crypto-infrastructure, embedded-finance, defi Zero Hash presents their crypto-as-a-service API at V-Sum Twelve. Presented by Max Howenstine, with a live demo of crypto-back credit card rewards built with Deserve — three API calls to go to market. **Chapters:** - **[0:00] Introduction to Zero Hash** — https://www.youtube.com/watch?v=1yMuKu1ReFk&t=0s Max Howenstine introduces Zero Hash — a modular, API-first crypto-as-a-service platform for companies that want to offer crypto products to their customers. - **[0:38] Platform partners and neobank integrations** — https://www.youtube.com/watch?v=1yMuKu1ReFk&t=38s Overview of Zero Hash's partner ecosystem including Tastyworks and challenger banks. How financial platforms integrate Zero Hash to offer crypto trading. - **[1:43] Crypto-back credit card rewards** — https://www.youtube.com/watch?v=1yMuKu1ReFk&t=103s Technical demo of a crypto-backed credit card reward system built with Deserve — replacing traditional cashback with cryptocurrency rewards. - **[3:42] API integration and code examples** — https://www.youtube.com/watch?v=1yMuKu1ReFk&t=222s Walkthrough of the actual API calls needed to implement crypto rewards — three simple API calls to go to market with embedded crypto services. - **[5:43] Withdrawal and cash-out services** — https://www.youtube.com/watch?v=1yMuKu1ReFk&t=343s How Zero Hash enables crypto reward withdrawal and fiat cash-out, handling the fiat disbursement for any platform offering crypto services. ### TreasureFI — TreasureFI Technical Briefing - Slug: `v-treasurefi` - URL: https://v-sum.com/briefing/v-treasurefi - Presenter: Ben Verscheure & Matt Clower (LinkedIn: https://www.linkedin.com/in/benjamin-verschuere-66106116/) - Company: https://www.treasurefi.com/ - YouTube: https://www.youtube.com/watch?v=O0a4Vysb7wg - Tags: defi, yield, treasury TreasureFI presents their corporate cash management platform at V-Sum Twelve. Presented by Ben Verscheure, covering Treasure Cash (FDIC-insured) and Treasure High Yield — tools for businesses to optimize idle cash across money market funds and T-bills. **Chapters:** - **[0:00] Introduction to TreasureFI** — https://www.youtube.com/watch?v=O0a4Vysb7wg&t=0s Ben Verscheure introduces TreasureFI — Treasure Cash (FDIC-insured, zero market risk) and Treasure High Yield (low-risk corporate bond fund) for optimizing business idle cash. - **[0:43] Treasure Cash and High Yield products** — https://www.youtube.com/watch?v=O0a4Vysb7wg&t=43s Breakdown of both offerings — Treasure Cash provides FDIC insurance up to $2.5M across partner banks. Treasure High Yield offers a SIPC-insured corporate bond mutual fund. - **[2:46] Account setup and KYC process** — https://www.youtube.com/watch?v=O0a4Vysb7wg&t=166s Walkthrough of TreasureFI onboarding — KYC data collection for business accounts, owner/officer verification, and custodian (APEX) account creation. - **[5:25] Dashboard and bank account management** — https://www.youtube.com/watch?v=O0a4Vysb7wg&t=325s Demo of the Treasure Dashboard — connecting business bank accounts via Plaid, viewing cash positions, and transferring funds. Supports transfers up to $500K via Plaid and wires for larger amounts. - **[7:31] Cash allocation and yield optimization** — https://www.youtube.com/watch?v=O0a4Vysb7wg&t=451s How TreasureFI distributes customer funds across partner banks to maximize FDIC coverage and yield. - **[8:53] Business analytics and CFO tools** — https://www.youtube.com/watch?v=O0a4Vysb7wg&t=533s Cash flow analytics — real-time visibility into business account trends, spending patterns, and financial forecasting tools for CFOs. ## V-Sum Thirteen — March 29, 2022 Event page: https://v-sum.com/events/thirteen ### Unit — Unit Technical Briefing - Slug: `v-unit` - URL: https://v-sum.com/briefing/v-unit - Presenter: Leah Staniorski (LinkedIn: https://www.linkedin.com/in/leah-staniorski-9b212540/) - Company: https://www.unit.co/ - YouTube: https://www.youtube.com/watch?v=mGLSXqoL0tY - Tags: banking-as-a-service, embedded-finance Leah, a client engineer at Unit, walks through the Unit banking-as-a-service platform — the three-part challenge of building banking into a fintech (compliance, technology, bank relationships) and how Unit handles all three so product teams can focus on acquisition and differentiation. The demo covers Unit's two build environments (Sandbox for unbounded prototyping, Pilot for real production with minor limits), generating an API token, submitting a business application through the KYB flow, Unit's optional white-label application form, subscribing to webhooks for real-time events, and issuing a deposit account plus virtual debit card in two API calls. Leah then reveals the full card details using Unit's VGS-backed sensitive-details service and buys a webcam cover on Amazon, closing the loop with the settled-transaction webhook firing back into the dashboard. **Chapters:** - **[0:00] Introduction to Unit — banking-as-a-service** — https://www.youtube.com/watch?v=mGLSXqoL0tY&t=0s Leah, a client engineer at Unit, introduces Unit — a banking-as-a-service platform founded on the idea that building banking into a fintech product shouldn't take 18 months and a seven-figure investment. Unit covers the three faceted challenge: compliance, technology, and banking relationships. - **[1:00] Unit's ecosystem: Lance and Abound** — https://www.youtube.com/watch?v=mGLSXqoL0tY&t=60s A preview of two Unit customers on the day's agenda — Lance, one of Unit's earliest clients building a banking experience for freelancers, and Abound, a Unit partner offering tax and benefits automation that several Unit clients embed to help freelancers manage taxes. - **[1:30] Sandbox vs Pilot environments** — https://www.youtube.com/watch?v=mGLSXqoL0tY&t=90s Unit offers two build surfaces: a Sandbox with test data for unbounded prototyping, and Pilot, a limited production environment with real accounts, cards, and live funds so teams can ship a functional MVP after just a few API calls. - **[2:30] Creating an API token in Pilot** — https://www.youtube.com/watch?v=mGLSXqoL0tY&t=150s Walk-through of the Pilot signup flow and generating a Unit API token — scoping, expiration, source-IP restrictions — ready to drop into Postman for the rest of the demo. - **[4:00] Create a business application and KYB** — https://www.youtube.com/watch?v=mGLSXqoL0tY&t=240s Submitting a business application via Unit's API kicks off the KYB flow — some applications auto-approve, others require document uploads or manual review. Unit also offers a white-label application form so fintechs don't need to build their own. - **[5:30] Webhooks for real-time events** — https://www.youtube.com/watch?v=mGLSXqoL0tY&t=330s Unit uses webhooks to push real-time events like application approved or documents awaiting, so client apps can chain actions (e.g. auto-create an account the moment a customer is created) without polling. - **[7:00] Create a deposit account and virtual debit card** — https://www.youtube.com/watch?v=mGLSXqoL0tY&t=420s Two API calls: one to create a deposit account linked to the customer, a second to issue a virtual business debit card that's active the moment it's created. - **[8:30] VGS for PCI-safe sensitive card details** — https://www.youtube.com/watch?v=mGLSXqoL0tY&t=510s Unit's sensitive-card-details service uses Very Good Security (VGS) so fintechs can reveal full PAN and CVV to a cardholder without ever touching PCI data themselves — the sample HTML ships in the docs. - **[9:30] Live Amazon purchase** — https://www.youtube.com/watch?v=mGLSXqoL0tY&t=570s End-to-end test: Leah swipes the freshly-issued Unit virtual debit card through Amazon checkout to buy a webcam cover, and the resulting authorization and settled transaction flow back through the webhook feed. ### Lance — Lance Technical Briefing - Slug: `v-lance` - URL: https://v-sum.com/briefing/v-lance - Presenter: Oona Rokyta (LinkedIn: https://www.linkedin.com/in/orokyta/) - Company: https://www.lance.app/ - YouTube: https://www.youtube.com/watch?v=7QsgTYVNiNo - Tags: freelance-finance, banking-as-a-service Lance is a banking app for the 68M independent workers in the US — sole entrepreneurs ranging from Instacart/Uber/Lyft drivers to lawyers, teachers, and NFT creators. Built on Unit for banking-as-a-service and Abound for tax intelligence, Lance tackles the three hardest parts of freelance finance: setting aside taxes, opting into benefits, and building a cash-flow footprint. Onboarding collects standard KYC/KYB plus filer type, state of residence, and a ballpark annual-income estimate — then recommends an allocation across "stacks" (salary, taxes, main expenses, goals). Stacks are Unit-powered sub-accounts delivered to the freelancer from day one instead of year five. Abound dynamically withholds the right tax from each deposit. On the first payment from a new client or marketplace, Lance prompts the user to classify it as 1099, W-2, or personal, so every subsequent payment from that source is taxed (or not) correctly. Virtual and physical cards drop into Apple Wallet, invoices go out in a few taps, and the home screen shows month-over-month income vs. expenses vs. taxes — plus an Abound-generated Schedule C. Crypto investing and a debt-payoff stack are on the near-term roadmap. **Chapters:** - **[0:00] Introduction to Lance — banking for independents** — https://www.youtube.com/watch?v=7QsgTYVNiNo&t=0s Lance powers financial independence for the 68M solo entrepreneurs in the US — from Instacart/Uber/Lyft drivers to lawyers, teachers, and NFT creators. Built on Unit for banking infrastructure and Abound for tax intelligence. - **[1:00] The freelancer problem — taxes, benefits, cash flow** — https://www.youtube.com/watch?v=7QsgTYVNiNo&t=60s Freelancers struggle with the jobs traditionally handled by a corporate back-office: setting aside taxes, opting into benefits, and tracking a coherent financial footprint. Lance is a banking account that actively partners with the user on all three. - **[2:30] Onboarding — KYC/KYB + income estimate** — https://www.youtube.com/watch?v=7QsgTYVNiNo&t=150s Lance runs standard KYC/KYB plus tax-specific questions (filer type, state of residence). It also asks for a ballpark annual income estimate — so Lance can compute the user's tax liability and recommend an allocation across savings, main expenses, and goals. - **[3:30] Stacks — salary, taxes, expenses, goals** — https://www.youtube.com/watch?v=7QsgTYVNiNo&t=210s The main screen shows the total balance and its distribution across "stacks" — sub-accounts for salary, taxes, main expenses, and custom goals. Stacks are powered by Unit's banking-as-a-service sub-account primitives, which Lance delivers from day one instead of year five. - **[4:30] Automated salary and tax withholding** — https://www.youtube.com/watch?v=7QsgTYVNiNo&t=270s The salary stack supports an automated every-other-week payout; the tax stack (Abound-powered) dynamically sets aside the right amount of every deposit based on its source. Users can also add manual tax-deductible expenses from other cards. - **[5:30] Main account, search, and transaction notes** — https://www.youtube.com/watch?v=7QsgTYVNiNo&t=330s The main account holds the spendable business-expense balance — shifting freelancers from reactive bill-paying to knowing exactly how much they can spend while still hitting automated allocations. Transactions are searchable, categorized, and can be marked reimbursed with receipts. - **[6:30] 1099 vs. W-2 classification per client** — https://www.youtube.com/watch?v=7QsgTYVNiNo&t=390s On the first payment from a new client or marketplace, Lance prompts the user to tag the source as 1099, W-2, or personal. From then on, every deposit from that source is automatically taxed or not — critical as the workforce mixes contract, seasonal, and freelance income. - **[7:30] Fund, invoice, and move between stacks** — https://www.youtube.com/watch?v=7QsgTYVNiNo&t=450s The action screen lets users fund from direct deposit or a payment platform, send a simple invoice, and dynamically re-allocate funds across stacks. Virtual and physical cards drop straight into Apple Wallet with one tap. - **[8:30] Business insights and Abound Schedule C** — https://www.youtube.com/watch?v=7QsgTYVNiNo&t=510s Lance shows month-over-month income vs. expenses vs. withheld taxes, and a richer tax menu (Abound-generated Schedule C reports, allocation settings, tutorial videos, chat support). Crypto investing and a debt-payoff stack are on the near-term roadmap. ### Abound — Abound Technical Briefing - Slug: `v-abound` - URL: https://v-sum.com/briefing/v-abound - Presenter: Alex Cram (LinkedIn: https://www.linkedin.com/in/alexcram/) - Company: https://www.withabound.com/ - YouTube: https://www.youtube.com/watch?v=DUhkqhy14so - Tags: insurance, embedded-finance Abound demos the tax-automation APIs behind freelancer banking apps like Lance — built on the thesis of "what if the IRS shipped a REST API." Four core products cover the self-employed tax stack: year-to-date federal/state/self-employment tax calculation, tax payments with 100% federal/state/DC coverage, transaction prediction (personal vs. business, deduction category), and end-of-year form generation (1099, Schedule C). The demo shows how Abound sits on top of Unit BaaS: when a Lance user opens a Unit account, Abound automatically registers them on its tax ledger using Unit\'s KYC data and auto-creates a payment method from the Unit account and routing numbers. Every debit and credit on the Unit ledger flows to Abound, which recalculates taxes in real time — income marked 1099 adds to the marginal/effective rate breakdown; business expenses categorized as commission deduct accordingly; a personal Apple Store purchase is flagged by the prediction engine as non-deductible. Abound returns a "smart tax rate" that Lance uses to set aside taxes from every deposit, and the tax-payment API remits $887 to the IRS on April 15 with a full created → pending → done lifecycle. **Chapters:** - **[0:00] Introduction to Abound — tax automation for freelancers** — https://www.youtube.com/watch?v=DUhkqhy14so&t=0s Abound demos the tax automation layer behind freelancer banking apps like Lance. Where W-2 employees live in net income (taxes, healthcare, 401k withheld automatically), self-employed people live in gross income — Abound handles that tax back office over banking-as-a-service providers like Unit. - **[1:30] Developer dashboard, Postman, SDKs, recipes** — https://www.youtube.com/watch?v=DUhkqhy14so&t=90s Abound's developer dashboard ships API keys, guides, a full Postman collection, SDKs, and recipes authored by the team. The tone is very "what if the IRS built an API" — four main products cover everything a freelancer bank needs. - **[2:00] Four Abound products — calculate, pay, predict, file** — https://www.youtube.com/watch?v=DUhkqhy14so&t=120s Tax calculation (year-to-date federal, state, and self-employment tax), tax payment (the only API with 100% coverage of federal, state, and DC estimated tax payments over REST), transaction prediction (personal vs. business split, deduction categories), and form generation (1099s and Schedule C). - **[3:30] User registration via the Unit integration** — https://www.youtube.com/watch?v=DUhkqhy14so&t=210s When a user opens a Lance account on Unit, Abound automatically registers them on the Abound tax ledger using Unit's KYC data. Fintechs don't re-collect identity data; Abound receives SSN, name, and address directly from Unit's webhooks. - **[4:30] Real-time tax calculation on every debit/credit** — https://www.youtube.com/watch?v=DUhkqhy14so&t=270s As debits and credits flow across the Unit ledger, Unit forwards them to Abound which recalculates taxes on the fly. A sample $1,500 Lyft cashout or client invoice shows marginal + effective rates, Medicare breakdown, and total taxes including any W-2 side income. - **[6:30] Expense categorization and transaction prediction** — https://www.youtube.com/watch?v=DUhkqhy14so&t=390s Expenses sent to Abound get a tax_category (e.g. "commission"). The prediction engine flags personal-looking purchases (Apple Store) as non-deductible and reshapes the tax breakdown as deductions accumulate. - **[7:30] Smart tax rate — how much to set aside per paycheck** — https://www.youtube.com/watch?v=DUhkqhy14so&t=450s Abound returns a "smart tax rate" per user. Lance multiplies each incoming payment by this rate and uses Unit to move funds from the main account to a tax-withholding sub-account — mimicking what ADP/Gusto do for W-2 employees. - **[8:30] Quarterly remittance via the tax payment API** — https://www.youtube.com/watch?v=DUhkqhy14so&t=510s The tax payment API creates an $887 Q1 IRS payment using the auto-created Unit-Abound payment method. Payments move through created → pending → done; sandbox supports forcing statuses (222 → done, 111 → pending) and surfaces common errors like name/SSN mismatches. ## V-Sum Fourteen — April 26, 2022 Event page: https://v-sum.com/events/fourteen ### Rehive — Rehive Technical Briefing - Slug: `v-rehive` - URL: https://v-sum.com/briefing/v-rehive - Presenter: Helghardt Avenant (LinkedIn: https://www.linkedin.com/in/helghardt/) - Company: https://rehive.com/ - YouTube: https://www.youtube.com/watch?v=flm-70828Mc - Tags: wallets, embedded-finance Helgaard of Rehive demos Rehive — a no-code fintech app builder that sits on top of the application layer of the fintech stack (above Plaid, Synapse, Wyre). For marketplaces (Fiverr, Upwork, Uber-style) looking to bring banking into their ecosystem, Rehive ships a pre-integrated ledger, user management, and an extensions framework — plus three UI surfaces (iOS, Android, web, admin dashboard, merchant portal). The demo walks through a US-oriented project using Rehive\'s Wyre integration for on/off-ramps, fiat and crypto custody, and KYC — producing a production-ready PayPal-like app in 5–10 business days. From the admin dashboard, operators define currencies (each backed by Wyre or their own custodial license), add account types, and manage transactions. A mass-send extension uploads a CSV of recipients and triggers a bulk payout through the Rehive API — paying users into their own branded wallet instead of PayPal. The consumer mobile app includes peer-to-peer transfers, QR scan-to-pay, a rewards/cashback engine, a lightweight in-app merchant marketplace, and a Wyre-backed crypto buy flow. Merchants get their own portal to list products, send invoices, and integrate POS — Rehive ends with a white-label option that hands over the source code for further customization. **Chapters:** - **[0:00] Introduction to Rehive — no-code fintech app builder** — https://www.youtube.com/watch?v=flm-70828Mc&t=0s Helgaard introduces Rehive as a no-code fintech app builder that sits on top of the application layer of the fintech stack. Target customers: marketplaces bringing finance into their ecosystem (Fiverr, Upwork, Uber-style) and new fintechs getting started quickly. - **[0:30] Rehive on the fintech stack** — https://www.youtube.com/watch?v=flm-70828Mc&t=30s Plaid, Synapse, and Wyre supply APIs that move real funds. Rehive sits on top of that layer with a pre-integrated application — a ledger, user management, and an extensions framework that consumes those rails without needing custom integration work. - **[1:30] Three user roles — admin, business, end user** — https://www.youtube.com/watch?v=flm-70828Mc&t=90s Rehive's product structure: a platform (ledger + user management), an extensions framework, and three UI layers — admin dashboard, merchant business interface, and end-user iOS/Android/web apps. - **[2:00] Wyre integration for US banking and crypto rails** — https://www.youtube.com/watch?v=flm-70828Mc&t=120s For US projects, Rehive integrates with Wyre for on/off-ramps, custody of fiat and crypto, and KYC — so a marketplace can stand up a production PayPal-like app in 5–10 business days after opening Wyre, Plaid, and Rehive accounts. - **[3:30] Admin dashboard — ledger and user management** — https://www.youtube.com/watch?v=flm-70828Mc&t=210s From the admin dashboard: add as many currencies as you like (each backed by Wyre or your own custodial licensing), define user vs. standalone accounts, and filter/export transactions from the ledger. - **[4:30] Mass-send extension for programmatic payouts** — https://www.youtube.com/watch?v=flm-70828Mc&t=270s The mass-send extension uploads a CSV of recipients and amounts to run a bulk payout through the Rehive APIs — instead of sending to PayPal, the marketplace pays users into their own branded wallet. - **[5:30] Consumer mobile app — branded wallet UX** — https://www.youtube.com/watch?v=flm-70828Mc&t=330s The end-user mobile app ships with peer-to-peer payments, QR-code scan-to-pay, portfolio balance, rewards/cashback campaigns, and a lightweight marketplace where merchants list products — all under the customer's brand. - **[7:30] Crypto buy flow via Wyre** — https://www.youtube.com/watch?v=flm-70828Mc&t=450s The mobile app also supports crypto purchases: pick a coin, get a quote from Wyre, execute the buy, and the funds move via Wyre's rails in the background — opening up an app's Gen-Z-friendly crypto features without separate integrations. - **[8:00] Merchant interface — invoices, POS, scan-to-pay** — https://www.youtube.com/watch?v=flm-70828Mc&t=480s The merchant-facing interface lets businesses in the marketplace list products, send invoices, and integrate POS. A demo walks through a scan-to-pay invoice flow between a buyer's mobile app and the merchant's invoice link. ### MoonPay — MoonPay Technical Briefing - Slug: `v-moonpay` - URL: https://v-sum.com/briefing/v-moonpay - Presenter: Victor Faramond (LinkedIn: https://www.linkedin.com/in/victorfaramond/) - Company: https://www.moonpay.com/ - YouTube: https://www.youtube.com/watch?v=_P-3i0ZAmbw - Tags: crypto-infrastructure, payments MoonPay is the on-ramp that lets anyone with a crypto wallet top up in a couple of clicks — or, increasingly, buy an NFT with a credit card without ever touching crypto. The demo opens with the common workflow (found an NFT on OpenSea, not enough ETH on Polygon to buy it), walks through a $30 ETH-on-Polygon top-up with 3D Secure via a UK banking app, and tours buy.moonpay.com — MoonPay supports 100+ cryptocurrencies, 40+ fiat currencies, SEPA across Europe and the UK, and a limited US ACH rollout. For developers, MoonPay ships a configurable widget (iframe or URL) with pre-fillable currency, amount, wallet address, email, language, and brand colors, plus an API key per partner. The closing demo buys an NFT on OpenSea with the MoonPay iframe filter enabled — one saved-card click, 3D Secure, and the NFT is minted to the buyer's wallet with no bridging or gas-fee juggling required. **Chapters:** - **[0:00] Introduction to MoonPay** — https://www.youtube.com/watch?v=_P-3i0ZAmbw&t=0s MoonPay's demo opens with a common problem: you found an NFT on OpenSea but don't have enough ETH on Polygon to buy it. MoonPay is designed for people who already have a crypto wallet and just need to top it up fast. - **[0:30] Top up $30 of ETH on Polygon** — https://www.youtube.com/watch?v=_P-3i0ZAmbw&t=30s Live demo: choose ETH on Polygon, enter $30, switch currency if needed (the minimum is $30). MoonPay detects MetaMask in the browser and pre-fills the destination address. - **[1:00] Logged-in flow — saved cards, saved wallet** — https://www.youtube.com/watch?v=_P-3i0ZAmbw&t=60s For returning MoonPay users, card, wallet, and personal info are all saved — buy crypto in a couple of clicks. The presenter approves the transaction on their UK banking app via 3D Secure. - **[1:30] buy.moonpay.com — 100+ crypto, 40+ fiat** — https://www.youtube.com/watch?v=_P-3i0ZAmbw&t=90s Anyone can paste a wallet address at buy.moonpay.com and top up. MoonPay supports more than 100 cryptocurrencies and 40 fiat currencies, with SEPA bank transfers in Europe and UK, and a limited ACH rollout in the US. - **[2:00] MoonPay Widget — iframe or URL** — https://www.youtube.com/watch?v=_P-3i0ZAmbw&t=120s Developers generate an API key, load the MoonPay widget URL, and embed it as an iframe or open it in a web view. This is how MoonPay powers wallets and mobile apps across the ecosystem. - **[2:30] Widget customization** — https://www.youtube.com/watch?v=_P-3i0ZAmbw&t=150s Pre-fill currency, amount, wallet address, email, language, and brand color so users skip unnecessary steps. MoonPay supports more advanced configuration via the developer docs. - **[3:30] Buying an NFT on OpenSea with a credit card** — https://www.youtube.com/watch?v=_P-3i0ZAmbw&t=210s On OpenSea's "Tiny Faces" collection, MoonPay enables a "buy with card" filter. One click, 3D Secure, and the NFT is purchased without ever touching crypto — no bridging, no gas management, no separate ETH top-up. - **[5:30] One-click NFT delivery** — https://www.youtube.com/watch?v=_P-3i0ZAmbw&t=330s The MoonPay widget is embedded as an iframe on OpenSea. MoonPay purchases the NFT on the user's behalf, the wallet calls the OpenSea smart contract, and the NFT shows up in the wallet once the transaction is mined. ### Composer — Composer Technical Briefing - Slug: `v-composer` - URL: https://v-sum.com/briefing/v-composer - Presenter: Ben Rollert (LinkedIn: https://www.linkedin.com/in/benrollert/) - Company: https://www.composer.trade/ - YouTube: https://www.youtube.com/watch?v=8t7LU03Dicc - Tags: investing, capital-markets Ben Rollert, CEO and co-founder of Composer, demos Composer — a trading app that gives retail investors access to systematic investing. Strategies are called "Symphonies" — containers for trading logic and the assets they operate on, much like an ETF is a container for a basket. The demo walks through the strategy library (featured, community, classic), Symphony fact sheets with backtests that actually model slippage and fees (rare in retail products), the visual conditional-logic editor and natural-language descriptions, live editing of conditions and benchmarks, swapping underlying assets, and Composer's fundamental building blocks (weight blocks, assets, filters, conditions) used Lego-style to build recursively nested multi-strategy portfolios like the Dragon Portfolio. Composer supports threshold rebalancing (rebalance only on drift, not calendar) and deploys to real brokerage accounts via Alpaca with fractional market orders. **Chapters:** - **[0:00] Introduction to Composer — systematic investing for retail** — https://www.youtube.com/watch?v=8t7LU03Dicc&t=0s Ben Rollert, CEO and co-founder of Composer, introduces Composer — a trading app that gives retail investors access to the power of systematic investing. Rather than picking individual stocks, the product is centered on trading strategies ("Symphonies") and funded like any brokerage account. - **[0:30] Symphonies — the strategy library** — https://www.youtube.com/watch?v=8t7LU03Dicc&t=30s Each tile in Composer's library is a Symphony — a container for trading logic and the assets it operates on, like an ETF is a container for a basket. Featured strategies, community strategies built by influencers, and themed classics are available out of the box. - **[1:50] Fact sheets, backtests with real slippage and fees** — https://www.youtube.com/watch?v=8t7LU03Dicc&t=110s Every Symphony has a fact sheet with a backtest. Composer is one of the few retail products that actually models slippage and transaction fees in backtests — most retail backtests ignore spreads and look unrealistically rosy. - **[3:00] Visual logic + natural-language descriptions** — https://www.youtube.com/watch?v=8t7LU03Dicc&t=180s Symphonies surface as a visual tree of conditional logic plus a natural-language description ("every month ask whether SPY's 60-day cumulative return is above TLT's"), with the currently-active branch highlighted live. - **[3:30] Symphony editor — edit conditions and rerun backtests** — https://www.youtube.com/watch?v=8t7LU03Dicc&t=210s Clicking Edit a Copy opens the Composer Symphony editor. Change the lookback window (60-day to 30-day), swap TLT for QQQ, rerun the backtest on demand, compare historical allocations — all against the original benchmark. - **[5:00] Compare any Symphony as a benchmark** — https://www.youtube.com/watch?v=8t7LU03Dicc&t=300s Any Symphony can be used as a benchmark against any other — so you can stack this strategy against the classic big-tech momentum Symphony and get the Sharpe, max-drawdown, and annualized-return comparison table in place. - **[6:30] Building blocks — weight blocks, assets, filters, conditions** — https://www.youtube.com/watch?v=8t7LU03Dicc&t=390s The fundamental Composer primitives — weight blocks, assets, filter blocks for momentum, conditions for switching. Compose them like Lego to build anything from an equal-weighted SPY+bonds blend to fully nested multi-strategy portfolios. - **[8:00] The Dragon Portfolio — nested sub-strategies** — https://www.youtube.com/watch?v=8t7LU03Dicc&t=480s A real example: the Dragon Portfolio, composed of five nested sub-strategies (long-vol, trended-momentum, fiat alternatives, cyclical growth assets) each made up of further Lego blocks. No other retail product lets you compose this recursively. - **[9:30] Threshold vs calendar rebalancing** — https://www.youtube.com/watch?v=8t7LU03Dicc&t=570s Composer supports threshold rebalancing — rebalance only when allocation drift exceeds a target, instead of on a fixed calendar — which saves meaningfully on trading costs without a research desk. - **[11:30] Deploy to a real brokerage account via Alpaca** — https://www.youtube.com/watch?v=8t7LU03Dicc&t=690s Every Symphony deploys to a funded brokerage account. Composer executes fractional market orders near market close via Alpaca on the backend; the user only sees a single Composer account, and strategies can be shared publicly with a link. ## V-Sum Fifteen — June 14, 2022 Event page: https://v-sum.com/events/fifteen ### Crescent — Crescent Technical Briefing - Slug: `v-crescent` - URL: https://v-sum.com/briefing/v-crescent - Presenter: Grant Roscoe (LinkedIn: https://www.linkedin.com/in/grantroscoe/) - Company: https://www.crescent.app/ - YouTube: https://www.youtube.com/watch?v=lCyBc05Hkbs - Tags: treasury, yield, stablecoins Crescent demos a high-yield treasury product for businesses — live in production V1, newly serving its first publicly traded customer, backed by USDC over-collateralized lending desks with zero exposure to Terra/Luna or Celsius and $30B of originations through its partners. The dashboard compounds interest every second, breaks earnings down by lifetime/year/month, and exposes admin controls for teams (plus easy switching between accredited individual and multiple business accounts, appealing to investment advisors). Because Crescent bridges fiat to USDC to lending desks, it natively supports wire and USDC deposits (ACH via Plaid coming soon) — the demo wires USDC from MetaMask into a Crescent account. Yield is accrued fungibly 1:1 in USDC/dollars at a ~4% sustainable rate. Despite looking like fixed income, Crescent accounts are fully liquid: next-day withdrawals initiate a wire, with Crescent pulling from fully-liquid lending pools, converting USDC to cash, and using bank credit lines to guarantee next-day settlement at zero fees. The roadmap is a yield marketplace: traditional cash sweeps, Treasury/mutual-fund products, and crypto yields — Crescent as the composable middle layer between businesses and yield sources. **Chapters:** - **[0:00] Introduction to Crescent — high-yield treasury product** — https://www.youtube.com/watch?v=lCyBc05Hkbs&t=0s Crescent is a high-yield treasury product for businesses, bridging cash into alternative yields — anywhere from cash management to USDC-based over-collateralized lending through the largest crypto lending desks (with zero exposure to Terra/Luna or Celsius, no defaults, and $30B of originations through their partners). - **[0:30] Live V1 dashboard — balance accrues by the second** — https://www.youtube.com/watch?v=lCyBc05Hkbs&t=30s The V1 dashboard is intentionally minimal: total balance, earnings compounded every second, transactions, and a clean statement UI. Crescent serves everything from startups to a newly-onboarded publicly traded company. - **[1:00] Admin controls and multi-account switching** — https://www.youtube.com/watch?v=lCyBc05Hkbs&t=60s Admin controls let enterprise customers define who can move funds. Users can switch between accredited-individual accounts and multiple business accounts — appealing to investment advisors managing funds on behalf of many business or accredited clients. - **[1:30] USDC deposit from MetaMask** — https://www.youtube.com/watch?v=lCyBc05Hkbs&t=90s Crescent bridges fiat on/off-ramps and crypto rails. A live USDC deposit from a MetaMask wallet shows the USDC-based on-ramp — built specifically for crypto treasuries and DAO treasuries depositing from their operating wallets. - **[2:30] Yield accrued 1:1 in USDC / dollars** — https://www.youtube.com/watch?v=lCyBc05Hkbs&t=150s Deposit rails today include wire and USDC, with ACH via Plaid launching soon. All yield is accrued fungibly 1:1 in USDC / dollars at a 4% sustainable rate arrived at with the over-collateralized lending partners. - **[3:30] Fully liquid next-day withdrawals** — https://www.youtube.com/watch?v=lCyBc05Hkbs&t=210s Despite looking like a fixed-income instrument, the account is fully liquid — next-day in and out. Withdrawals initiate a wire; on the back end Crescent pulls from fully-liquid lending pools, converts USDC back to cash, and uses credit lines to guarantee next-day timing with zero fees. - **[4:30] Yield marketplace — composable yield platform** — https://www.youtube.com/watch?v=lCyBc05Hkbs&t=270s The roadmap: a yield marketplace where customers self-direct across traditional cash sweeps, mid-risk Treasury/mutual fund products, and crypto yields — positioning Crescent as the composable middle layer between businesses and yield sources. ### Modern Treasury — Modern Treasury Technical Briefing - Slug: `v-moderntreasury` - URL: https://v-sum.com/briefing/v-moderntreasury - Presenter: Koji Murase (LinkedIn: https://www.linkedin.com/in/kojiro-murase/) - Company: https://www.moderntreasury.com/ - YouTube: https://www.youtube.com/watch?v=QvpJ0Nr5Kd0 - Tags: payments, treasury, developer-tools Koji, PM at Modern Treasury, walks through Modern Treasury Ledgers — a managed double-entry ledger API for fintechs like Revolut and Marqeta, marketplaces like ClassPass and Outdoorsy, and anyone building money-movement apps. The demo builds out "BillFold," a sample digital wallet, and walks through the patterns Modern Treasury has seen in production: custom ISO currencies (including USDC with a six-digit exponent for stablecoin-native apps), pending-vs-posted states for in-flight payments, immutable pending transactions with full audit trails, combined payment-plus-ledger API calls, and optimistic locking for just-in-time card funding flows alongside card issuers like Lithic and Marqeta. The closing pattern — purely in-ledger transactions between user accounts — makes user-to-user transfers essentially instant without ever touching an external rail. **Chapters:** - **[0:00] Introduction to Modern Treasury Ledgers** — https://www.youtube.com/watch?v=QvpJ0Nr5Kd0&t=0s Koji, PM at Modern Treasury, introduces the Modern Treasury Ledgers API — a managed double-entry ledger for fintechs like Revolut and Marqeta, marketplaces like ClassPass and Outdoorsy, and anyone building money-movement apps. - **[1:00] Creating a ledger object (custom USDC currency)** — https://www.youtube.com/watch?v=QvpJ0Nr5Kd0&t=60s Live walk-through of creating a Modern Treasury ledger in the dashboard (and the public API docs), including a custom USDC currency with a six-digit exponent for stablecoin-native apps. - **[2:00] The BillFold demo wallet — accounts and balances** — https://www.youtube.com/watch?v=QvpJ0Nr5Kd0&t=120s A sample wallet app called BillFold is used to show core ledger objects — user ledger accounts, a cash account, and a card settlement account — and the posted vs pending balances tracked on each. - **[2:30] Double-entry ledger transactions** — https://www.youtube.com/watch?v=QvpJ0Nr5Kd0&t=150s Why every money movement in the ledger has matching credits and debits — the pattern good fintechs use, whether the movement happens inside the app (user-to-user) or across external rails. - **[3:30] Pending vs posted — modelling money in flight** — https://www.youtube.com/watch?v=QvpJ0Nr5Kd0&t=210s How Modern Treasury models payments as pending before they settle and posted after, so ACH in-transit or card authorizations are tracked accurately before they clear. - **[4:30] Combined payment-and-ledger API call** — https://www.youtube.com/watch?v=QvpJ0Nr5Kd0&t=270s A Postman walk-through of payment orders: Jane deposits money into BillFold. One API call moves funds between bank accounts and writes the matching ledger entries, with an external_id for idempotency. - **[5:30] Immutable pending transactions + audit trail** — https://www.youtube.com/watch?v=QvpJ0Nr5Kd0&t=330s Pending Modern Treasury ledger transactions are immutable with a full audit trail — so card-authorization amount changes are captured as edits rather than overwrites and the full history is reconstructable. - **[6:30] Just-in-time card funding with Lithic / Marqeta** — https://www.youtube.com/watch?v=QvpJ0Nr5Kd0&t=390s The common pattern of using Modern Treasury Ledgers to manage card balances in real time alongside card issuers like Lithic and Marqeta — authorizing swipes against the ledger, then posting once the card network confirms. - **[7:30] Optimistic locking for card race conditions** — https://www.youtube.com/watch?v=QvpJ0Nr5Kd0&t=450s How the ledger avoids race conditions on high-throughput card flows: each account read returns a locked version, which the subsequent transaction must reference; the write only succeeds if the version hasn't moved. ### FinGoal — FinGoal Technical Briefing - Slug: `v-fingoal` - URL: https://v-sum.com/briefing/v-fingoal - Presenter: Jack Ryan (LinkedIn: https://www.linkedin.com/in/john-dixon-ryan/) - Company: https://fingoal.com/ - YouTube: https://www.youtube.com/watch?v=iOELscx3NUY - Tags: open-banking, data-infrastructure Jack Ryan of FinGoal demos the FinGoal Switch Kit — a wrapper around Plaid, MX Link Money, Yodlee, and other aggregators that normalizes the account and transaction shape so you can swap aggregators in minutes instead of months. The live demo starts with a Next.js app running a Plaid link against Wells Fargo, then swaps the token endpoint and frontend portal to MX Link Money — which authenticates via open banking directly in the Wells Fargo app. The migration philosophy is not a big-bang swap: FinGoal recommends leaving existing Plaid connections alone and re-linking users through the new aggregator only when a connection breaks, so net-new users and natural re-auths silently migrate without churn. The Switch Kit\'s payoff is that the success page digests the callback event string from Link Money and renders the new accounts and /transactions/get output alongside pre-existing Plaid data — same schema, same categories, same fields — with only three files changed across the entire app. The thesis: developers should not be locked into an aggregator by migration cost. **Chapters:** - **[0:00] Introduction to FinGoal and the Switch Kit** — https://www.youtube.com/watch?v=iOELscx3NUY&t=0s Jack Ryan of FinGoal introduces the FinGoal aggregator Switch Kit — a wrapper that lets you rip out an existing Plaid integration and swap in a new aggregator (like MX Link Money) in minutes instead of months. - **[0:30] Why aggregator switches take months** — https://www.youtube.com/watch?v=iOELscx3NUY&t=30s Plaid, Yodlee, and MX all aggregate bank accounts and transactions, but their APIs and models are not interchangeable. A raw swap can put a fintech's roadmap at risk for months; the Switch Kit standardizes the data shape so only a thin wrapper changes. - **[1:00] Three windows — code, docs, browser** — https://www.youtube.com/watch?v=iOELscx3NUY&t=60s Jack opens the Next.js repo, the FinGoal Switch Kit quickstart guide, and a browser running a live Plaid link that pulls Wells Fargo accounts and transactions into a success page. The mission: swap Plaid for Link Money in one pass. - **[2:00] Step 1 — generate a user access token** — https://www.youtube.com/watch?v=iOELscx3NUY&t=120s Paste the Switch Kit access-token boilerplate into the existing index.js controller. Both Plaid and Link Money need an item ID and user ID at different stages, and the Switch Kit standardizes the token shape across both. - **[3:30] Step 2 — open the Link Money portal with a redirect** — https://www.youtube.com/watch?v=iOELscx3NUY&t=210s On the frontend, Jack removes the Plaid Link handler and replaces it with a call that opens the Link Money portal in a new tab, passing the JWT for authentication and a redirect URL pointing back to the success page. - **[5:30] Open banking login through the bank's own app** — https://www.youtube.com/watch?v=iOELscx3NUY&t=330s The Link Money portal authenticates Wells Fargo via open banking — redirecting the user straight into the Wells Fargo app for approval and 2FA, instead of asking for credentials in a third-party modal. - **[6:30] Supplementing, not ripping out, existing Plaid data** — https://www.youtube.com/watch?v=iOELscx3NUY&t=390s FinGoal's recommendation: don't force a big-bang migration. As existing Plaid connections break, re-link users through the new aggregator — net-new users and re-auths silently move to Link Money with no churn event. - **[7:30] Digest events and render accounts** — https://www.youtube.com/watch?v=iOELscx3NUY&t=450s On the success page, Jack adds a digestEvents method that parses the callback query string Link Money appends on exit — and the three Link Money accounts render alongside the pre-existing Plaid accounts with no template changes at all. - **[8:30] Transactions — same endpoint, same schema** — https://www.youtube.com/watch?v=iOELscx3NUY&t=510s Same trick for transactions: a 30-day bracket, a GET /transactions/get call to Link Money production, and the new transactions load in with Plaid-compatible shapes and categories. The only clue they loaded is a scrollbar shift. - **[11:00] Why the Switch Kit exists** — https://www.youtube.com/watch?v=iOELscx3NUY&t=660s FinGoal's thesis: the best data should win. Companies shouldn't be locked into a single aggregator by migration cost. The Switch Kit makes it cheap to pick the aggregator that fits each data need. ## V-Sum Sixteen — September 20, 2022 Event page: https://v-sum.com/events/sixteen ### Arc — Arc Technical Briefing - Slug: `v-arc` - URL: https://v-sum.com/briefing/v-arc - Presenter: Raven Jiang (LinkedIn: https://www.linkedin.com/in/ravenjiang/) - Company: https://www.arc.tech/ - YouTube: https://www.youtube.com/watch?v=J2zRnoUjRk0 - Tags: data-infrastructure, lending, capital-markets Arc is a B2B financing platform for software companies, pairing Arc Advance (revenue-based financing) with Arc Treasury (a deposit account for the same customer profile). This briefing walks through the Arc customer onboarding flow — NDA, API credentials for banking, accounting, and billing — and the unified data model Arc has built across all three. Live demos connect Capital One via Plaid sandbox, accounting data via Codat, and billing via Stripe, with each sync landing in Arc's GraphQL backend as canonical data events. Behind the scenes, Arc normalizes data across multiple aggregators per domain using virtual SQL views, preserves raw provider data for traceability, and optimizes connector selection for long-term stable recurring connections — because Arc re-syncs this data continuously to monitor risk on outstanding balances and surface upsell opportunities. **Chapters:** - **[0:00] Introduction to Arc — B2B financing for software companies** — https://www.youtube.com/watch?v=J2zRnoUjRk0&t=0s Arc is a B2B financing platform for software companies. The team started with Arc Advance (revenue-based financing) last year and recently launched Arc Treasury (a deposit account for the same customer profile) to create an integrated financing plus banking experience. - **[1:30] Customer onboarding — NDA and API credentials** — https://www.youtube.com/watch?v=J2zRnoUjRk0&t=90s The Arc signup flow: sign an NDA so customers feel safe sharing financials, then request API credentials for banking, accounting, and billing providers — three independent data domains Arc needs to underwrite. - **[2:30] Multiple aggregators per data domain** — https://www.youtube.com/watch?v=J2zRnoUjRk0&t=150s Arc connects to multiple providers per data type — banking is the most mature aggregator space, accounting is growing, and billing / subscription providers (Stripe, Recurly) are the newest frontier. Arc picks the best connector per customer's bank. - **[3:00] Plaid sandbox — Capital One OAuth** — https://www.youtube.com/watch?v=J2zRnoUjRk0&t=180s Live demo connecting a Capital One account through the Plaid sandbox. Behind the scenes Arc's GraphQL backend records the bank connection, company, and user and receives asynchronous Plaid webhooks as transactions sync. - **[4:30] Codat for accounting, Stripe for billing** — https://www.youtube.com/watch?v=J2zRnoUjRk0&t=270s Same pattern applied to accounting (Codat sandbox on a medium US company syncs balance sheet and P&L updates) and billing (a Stripe test key connects in one step, with invoice history syncing over a longer window). - **[7:00] Underwriting decision and financing offer** — https://www.youtube.com/watch?v=J2zRnoUjRk0&t=420s After data syncs, Arc's dashboard surfaces a financing offer with cost and maximum limit. Customers can fund into their existing bank account (ACH delay) or Arc Treasury (instant upon approval, no onboarding re-KYC if already set up). - **[9:00] Unified data model over banking, accounting, and billing** — https://www.youtube.com/watch?v=J2zRnoUjRk0&t=540s Arc normalizes data from every connector into a canonical schema — ARN-style unique IDs, merchant cleanup, shared data events — so the backend services operate on a single model while raw provider data is preserved for traceability. - **[11:00] Continuous sync, risk monitoring, and upsell** — https://www.youtube.com/watch?v=J2zRnoUjRk0&t=660s Because Arc carries outstanding balances, it selects connectors optimised for long-term stable recurring connections (webhook-driven updates), not just one-off underwriting. The same data powers risk monitoring and future-opportunity discovery. - **[13:00] Virtual SQL views and the unified architecture** — https://www.youtube.com/watch?v=J2zRnoUjRk0&t=780s Arc unifies data using virtual SQL views (chosen for tooling compatibility across their TypeScript ORM and Luca analytics stack) with a plan to move to materialized tables for performance as volume grows. ### Nium — Nium Technical Briefing - Slug: `v-nium` - URL: https://v-sum.com/briefing/v-nium - Presenter: Geoff Greenberg (LinkedIn: https://www.linkedin.com/in/geoffgreenberg/) - Company: https://www.nium.com/ - YouTube: https://www.youtube.com/watch?v=Wl0pfcApFv4 - Tags: payments, cross-border Nium is a B2B money-movement platform supporting 190 currencies and moving into crypto rails including Stellar, Polygon, Ethereum mainnet, the Lightning Network, and Bitcoin. The demo focuses on Nium\'s Stellar integration for stablecoin (USDC) payouts. Login uses Stellar\'s sign-a-secret flow (challenge → wallet signature → JWT) so there are no usernames or passwords. Nium creates a second participant on Stellar testnet, validates the destination routing number (the same validation used for fiat rails), and sends $0.20 USDC — recording the transaction on Nium\'s side, broadcasting to Stellar, and reflecting the debited balance in seconds. The product positioning: Nium is the pipes connecting fiat and digital-asset rails, giving people more control over what/when/how/where their money moves. **Chapters:** - **[0:00] Introduction to Nium** — https://www.youtube.com/watch?v=Wl0pfcApFv4&t=0s Nium is a B2B money-movement platform supporting 190 currencies and increasingly moving into crypto. The demo focuses on Nium's integration with the Stellar network for stablecoin (USDC) payments. - **[0:30] Chains supported — Stellar, Polygon, Ethereum, Lightning, Bitcoin** — https://www.youtube.com/watch?v=Wl0pfcApFv4&t=30s Nium is integrated with Stellar, Polygon, Ethereum mainnet, the Lightning Network, and Bitcoin, among others. Today's demo runs on the Stellar testnet with 3.90 USDC in the sending wallet. - **[1:00] Stellar-native login — sign-a-secret for a JWT** — https://www.youtube.com/watch?v=Wl0pfcApFv4&t=60s Logging in uses Stellar's sign-a-secret flow: the server issues a challenge, the wallet signs it, and the user gets a JWT — no username or password. Nium exposes this as a simple API. - **[1:30] Create a participant on Stellar** — https://www.youtube.com/watch?v=Wl0pfcApFv4&t=90s Nium creates a second participant on the Stellar testnet, pushing the same data from the UI into the network and accepting the new wallet before any funds can be sent. - **[2:30] Routing-number validation** — https://www.youtube.com/watch?v=Wl0pfcApFv4&t=150s Even for crypto rails, Nium enforces the same validation used for fiat — the routing number is looked up and validated before the transaction is created on Nium's side. - **[3:00] Send $0.20 USDC — Nium creates, Stellar settles** — https://www.youtube.com/watch?v=Wl0pfcApFv4&t=180s Nium records the transaction on its side, pushes it to Stellar for settlement, and debits the sender for $0.20 USDC — leaving the sender with $3.70. The live wallet balance reflects the Stellar-settled transfer in seconds. ### Routable — Routable Technical Briefing - Slug: `v-routable` - URL: https://v-sum.com/briefing/v-routable - Presenter: Omri Mor (LinkedIn: https://www.linkedin.com/in/omrimor/) - Company: https://www.routable.com - YouTube: https://www.youtube.com/watch?v=qv7_W8PfBgw - Tags: payments, developer-tools Routable is a B2B payments platform — a successor to the painful experience of building B2B payment infrastructure in-house at marketplaces, where a thousand to a million payouts per month have to move alongside tax-document management, ERP logging, and appease finance, ops, and engineering simultaneously. This briefing demos an international payout to a Canadian delivery driver with Routable co-querying NetSuite in the same flow, attaches files and FX conversion to the transaction, exposes Routable's approval rules, and walks through the magic-link payee experience (branded in the payer's name, no signup required). Closing demos cover bank-error recovery, retroactive payment-method updates on pending payables, the Object Field Mapping UI developers use to align with NetSuite/QuickBooks object IDs, and RTP-enabled domestic payouts. **Chapters:** - **[0:00] Introduction to Routable — B2B payments platform** — https://www.youtube.com/watch?v=qv7_W8PfBgw&t=0s Routable is a B2B payments platform. Both co-founders previously built B2B payment infrastructure in-house at marketplaces — a terrible experience involving 1k–1M payouts/month, tax-document management, ERP logging, and simultaneous appeal to finance, ops, and engineering. - **[1:30] International payout demo: Canadian delivery driver** — https://www.youtube.com/watch?v=qv7_W8PfBgw&t=90s Live demo of sending an international payout — paying a Canadian delivery driver — with Routable querying NetSuite alongside its own data in a single flow, checking outstanding liabilities, and rendering the full NetSuite-required payment form. - **[2:30] NetSuite posting period, memo, required fields** — https://www.youtube.com/watch?v=qv7_W8PfBgw&t=150s Every field in Routable's payment form maps to a NetSuite-required or optional attribute per vendor type. Attach files, attach addresses, trigger FX conversion at the right rate — all of it syncs back to NetSuite so accounting stays clean. - **[4:00] Approval rules** — https://www.youtube.com/watch?v=qv7_W8PfBgw&t=240s Approval rules (e.g. payouts over $3,000 require explicit approval; smaller payments auto-send) run on the Routable platform before any funds move. - **[5:00] Magic-link payee experience** — https://www.youtube.com/watch?v=qv7_W8PfBgw&t=300s Payees receive a Routable email branded in the payer's name (e.g. "Michelle from Dunkin Donuts"). Magic links let payees view payment status and history without a signup — or the payer can build their own payee UI against the Routable API. - **[6:30] Bank-error recovery and payment method updates** — https://www.youtube.com/watch?v=qv7_W8PfBgw&t=390s If a payment fails on bad banking instructions, Routable lets the payee update their payment method and offers a control in Advanced Options to retroactively apply the new method to pending payables so the fix cascades. - **[7:30] Object Field Mapping for developers** — https://www.youtube.com/watch?v=qv7_W8PfBgw&t=450s A dashboard-level Object Field Mapping UI lets finance teams hand developers the NetSuite / QuickBooks object IDs they need to fire payments programmatically — the cheat sheet that usually burns hours of Slack back-and-forth. - **[9:00] RTP-enabled domestic vendors** — https://www.youtube.com/watch?v=qv7_W8PfBgw&t=540s For domestic vendors whose bank supports real-time payments, Routable surfaces an "RTP enabled" badge on the payout screen — one click to route a payment over RTP instead of ACH or check. ## V-Sum Seventeen — November 15, 2022 Event page: https://v-sum.com/events/seventeen ### Prime Trust — Prime Trust Technical Briefing - Slug: `v-primetrust` - URL: https://v-sum.com/briefing/v-primetrust - Company: https://www.primetrust.com - YouTube: https://www.youtube.com/watch?v=Mzjcyk0rMm8 - Tags: custody, crypto-infrastructure, compliance Antonio Georgalis, principal solution engineer at Prime Trust, demos the Prime Trust regulated custody and liquidity platform — the API-driven back-end infrastructure that connects crypto to the US dollar financial system for fintechs. The platform covers KYC-gated account creation (/v2/accounts), settlement, cash and asset transfers, and a liquidity API (/v2/quotes) that converts between dollars and roughly eight to ten supported digital assets via a request-for-quote flow. Money-in rails include ACH pull, wire, debit card, and Signet; money-out covers ACH and wire disbursements. The demo walks through the liquidity quote lifecycle end-to-end: RFQ with a price and expiration, execute, and check settlement status. Prime Trust runs two settlement modes — instant (settle asynchronously within milliseconds of execution, default) and scheduled (execute first, move funds in later, settle end-of-day, similar to T+2 in traditional markets) — plus a hot vs. warm balance distinction for automated vs. operations-reviewed disbursements. **Chapters:** - **[0:00] Introduction to Prime Trust — regulated crypto custody** — https://www.youtube.com/watch?v=Mzjcyk0rMm8&t=0s Antonio Georgalis, principal solution engineer at Prime Trust, introduces Prime Trust — a regulated trust company acting as custodian to fintechs in the crypto industry. The API-driven platform connects crypto to the US dollar financial system for fully compliant money movement. - **[0:30] API overview — accounts, settlement, transfers, liquidity** — https://www.youtube.com/watch?v=Mzjcyk0rMm8&t=30s Tour of the Prime Trust API surface: /v2/accounts for KYC-gated account creation, an internal settlement API for buying and selling trades between accounts, cash and asset transfer APIs, and the liquidity API at /v2/quotes for converting between USD and crypto. - **[2:30] On-ramps and off-ramps** — https://www.youtube.com/watch?v=Mzjcyk0rMm8&t=150s Money and asset movement in and out of Prime Trust custodial accounts: external wallet deposits and withdrawals, ACH pull / wire / Signet / debit card for cash-in, and ACH / wire disbursements for cash-out. Plus direct-deposit instructions for payroll. - **[3:00] Demo app — buy and sell interface** — https://www.youtube.com/watch?v=Mzjcyk0rMm8&t=180s Walk-through of a Prime Trust demo app built on the liquidity API — a dollar amount and a ticker produce an RFQ (request-for-quote) with a price, quantity, and expiration timer. Miss the window and the button disables. - **[4:30] Liquidity API in Postman — /v2/quotes** — https://www.youtube.com/watch?v=Mzjcyk0rMm8&t=270s The /v2/quotes endpoint returns a quote ID; a follow-up call executes it. /v2/assets returns the list of supported asset IDs. The hot/warm flag controls whether a subsequent disbursement from the account requires operations review. - **[5:30] Warm vs hot balances — human-in-the-loop** — https://www.youtube.com/watch?v=Mzjcyk0rMm8&t=330s Warm is the default — Prime Trust ops reviews every disbursement before it moves, on top of the standard account-owner email confirmation. Hot balances auto-disburse after owner confirmation, intended for stablecoin-in-the-loop flows. - **[6:30] Execute a quote and settlement status** — https://www.youtube.com/watch?v=Mzjcyk0rMm8&t=390s POSTing to /v2/quotes/.../execute returns "executed pending settlement" — under Prime Trust's instant settlement (the default), the trade is actually settled within milliseconds in an asynchronous post-trade process with timestamps for created/executed/settled. - **[7:30] Specify base amount or target asset quantity** — https://www.youtube.com/watch?v=Mzjcyk0rMm8&t=450s Quotes accept either a USD amount or an explicit asset quantity (Bitcoin to 8 decimals). Handy for "fill my payment in BTC" flows vs. "sell everything I have" flows. - **[8:30] Scheduled settlement for post-trade flows** — https://www.youtube.com/watch?v=Mzjcyk0rMm8&t=510s Scheduled settlement works like T+2 in traditional markets — execute the quote first, move funds in afterwards during the day, settlement completes at end-of-day. Useful when a customer is wiring funds in and wants to lock a price before the wire clears. ### DFNS — DFNS Technical Briefing - Slug: `v-dfns` - URL: https://v-sum.com/briefing/v-dfns - Presenter: Clarisse Hagege & Josh Siegel (LinkedIn: https://www.linkedin.com/in/clarissehagege/) - Company: https://www.dfns.co/ - YouTube: https://www.youtube.com/watch?v=UP6BZ537eCQ - Tags: wallets, custody, developer-tools Clarisse (co-founder, CEO) and Josh (product) of Dfns introduce Dfns — a developer-first wallet-as-a-service platform that separates the security of the private key from the governance of the assets. Dfns operates a decentralized MPC signer network in secure enclaves so private keys never materialize in memory or on disk — no single point of failure like seed-phrase or multi-sig-HSM setups. The API is chain-agnostic (25 blockchains, 9,000 tokens, new chains in ~3 weeks, new tokens in ~half a day) and built to scale to millions of segregated wallets per customer. A customer demo with Nilos (treasury management) shows how a user signs in and gets a fully functioning EVM wallet in seconds via createAssetAccount (distributed key generation) and initiatePayment, with every transaction subject to Dfns's programmable, API-first policy engine — including 2-of-3-style approvals defined in code rather than in a vendor UI. Pricing is unusual for the custody space: Dfns charges per wallet, per authorized signer, and per policy-engine access — never on AUM or AUC. **Chapters:** - **[0:00] Introduction to Dfns** — https://www.youtube.com/watch?v=UP6BZ537eCQ&t=0s Clarisse, co-founder of Dfns, introduces the company — 30 people across Europe and the US, $14M seed, founded more than two years ago. Leadership combines experience from BitGo (security), Google (product), and Robinhood (research) to build wallet infrastructure for developers. - **[1:30] Contrarian view of digital custody** — https://www.youtube.com/watch?v=UP6BZ537eCQ&t=90s Dfns separates the security of the private key from the governance of the assets, operating a decentralized MPC signer network that signs transactions in response to authenticated API calls — so no single party ever holds the full key. - **[3:00] Developer-first API — 25 chains, 9,000 tokens** — https://www.youtube.com/watch?v=UP6BZ537eCQ&t=180s Dfns ships an API-first wallet infrastructure. Chain-agnostic integration: new blockchains in ~3 weeks, new tokens in ~half a day — today 25 blockchains and 9,000 tokens. Built to scale to millions of segregated wallets, not just derived addresses from a single keypair. - **[4:30] Programmable policy engine and compliance** — https://www.youtube.com/watch?v=UP6BZ537eCQ&t=270s Dfns is the only wallet API that lets developers define compliance policies at the API level, down to assigning specific smart-contract details. 60% of use cases are crypto (wallets, exchanges, staking apps), 40% are NFTs, with security tokens an emerging segment. - **[5:00] Pricing — per wallet, per signer, not per AUC** — https://www.youtube.com/watch?v=UP6BZ537eCQ&t=300s Unlike Fireblocks and most custody vendors, Dfns does not price based on AUM or AUC. The monthly fee is based on the number of wallets created, the number of authorized signers, and policy-engine access — an annual commitment that decouples cost from asset growth. - **[6:00] Customer demo — Nilos treasury platform** — https://www.youtube.com/watch?v=UP6BZ537eCQ&t=360s Josh walks through Nilos, a treasury management platform. Instead of the 30-step MetaMask seed-phrase flow, a user signs in and gets a Nilos wallet — a Dfns wallet on the back end — with Ethereum and Polygon support ready to go. - **[7:30] createAssetAccount → distributed key generation** — https://www.youtube.com/watch?v=UP6BZ537eCQ&t=450s When the user clicks create, Nilos calls Dfns' createAssetAccount with MATIC for Polygon. Dfns' signer network runs a distributed key-generation ceremony inside secure enclaves — the private key never materializes in memory or on disk, eliminating a single point of failure. - **[9:30] High-level API — initiatePayment and transaction status** — https://www.youtube.com/watch?v=UP6BZ537eCQ&t=570s Nilos uses Dfns' high-level API to get balances and initiate payments — posting an origin asset-account ID, symbol, amount, and receiver (any arbitrary blockchain address or Dfns wallet). Dfns returns a payment ID, signs, broadcasts, and hands back a transaction hash. - **[11:30] Policy engine and API-first approvals** — https://www.youtube.com/watch?v=UP6BZ537eCQ&t=690s All transactions are subject to Dfns' programmable policy engine. Because the engine is fully exposed via API (unlike Fireblocks' app-driven approvals), customers can build their own approval UX on top — including multi-sig-style "2-of-3" approvals on individual transactions. - **[12:30] Levels of abstraction — raw signing → smart-contract ABI → NFTs** — https://www.youtube.com/watch?v=UP6BZ537eCQ&t=750s Dfns offers a raw signing API (create key, ECDSA/EdDSA, sign as HSM), a smart-contract API (import ABI, call function with parameters, Dfns encodes and broadcasts), and a high-level NFT API with ERC-721 metadata built in — all governed by the same policy engine. ### Paxos — Paxos Technical Briefing - Slug: `v-paxos` - URL: https://v-sum.com/briefing/v-paxos - Presenter: Jordan Valentine & Davis Hart (LinkedIn: https://www.linkedin.com/in/jordan-valentine/) - Company: https://www.paxos.com - YouTube: https://www.youtube.com/watch?v=16ReoYTDXk8 - Tags: stablecoins, crypto-infrastructure, compliance Davis Hart and Jordan of Paxos walk through the regulated crypto infrastructure Paxos provides to financial institutions — including PayPal, Paxos's first crypto brokerage customer from 2020. This briefing focuses on the June 2022 transfers launch: the ability for Paxos customers to enable their end users to deposit and withdraw crypto directly into their wallets without a fiat round-trip. The demo covers the PayPal web UI receive/send flows, Paxos's guaranteed network fees, and the Postman walkthrough of the three-endpoint withdrawal API: create a crypto-withdrawal fee quote (rate locked for minutes so retail users have time to review), submit the withdrawal with amount-vs-total and fee-asset-selection UX tools for developers, and track the transfer to completion with compliance checks and block confirmations. A final deposit-address walkthrough shows how Paxos issues one address per blockchain per end-user — covering Bitcoin, Bitcoin Cash, Ethereum, and the rest of the asset list. **Chapters:** - **[0:00] Introduction to Paxos — regulated crypto infrastructure** — https://www.youtube.com/watch?v=16ReoYTDXk8&t=0s Davis Hart, on the product team at Paxos, introduces Paxos — a regulated crypto services company (New York state trust) providing crypto infrastructure to financial institutions. Most of Paxos's surface area is API; customers like PayPal and Mercado Libre build the consumer UX on top. - **[0:30] The PayPal crypto partnership** — https://www.youtube.com/watch?v=16ReoYTDXk8&t=30s PayPal was Paxos's first crypto brokerage customer in 2020, launching buy/sell/hold. This briefing demos the June 2022 follow-up GA: the ability for Paxos customers to enable crypto deposits and withdrawals directly into and out of the PayPal wallet — no round-trip through fiat rails. - **[1:30] Why transfers matter — P2P, asset acquisition, payments primitives** — https://www.youtube.com/watch?v=16ReoYTDXk8&t=90s Transfers unlock P2P crypto sending between friends and family (natural follow-on to PayPal's core P2P product), a new asset-acquisition channel for PayPal (customers can move crypto in from a competitor), and the primitive underneath future payments in web3. - **[2:30] The invisible compliance layer** — https://www.youtube.com/watch?v=16ReoYTDXk8&t=150s Under the hood Paxos handles full compliance monitoring, travel rule compliance, treasury management, and signing — at PayPal scale. The simple UX is backed by a lot of regulated plumbing. - **[3:00] PayPal receive Bitcoin — unique per-user address** — https://www.youtube.com/watch?v=16ReoYTDXk8&t=180s The PayPal web UI renders a transfer button for Bitcoin. Receive generates a unique Bitcoin address mapped to the PayPal account — send from any wallet or exchange and funds show up in PayPal. - **[4:30] Guaranteed network fees** — https://www.youtube.com/watch?v=16ReoYTDXk8&t=270s PayPal presents the amount, network fee, and delivery time before sending. A signature Paxos feature: the network fee is guaranteed for about five minutes — whatever Paxos ends up paying on-chain, the user pays the quoted fee. - **[6:30] API walkthrough — fee quotation, withdrawal, tracking** — https://www.youtube.com/watch?v=16ReoYTDXk8&t=390s Jordan walks through the three-endpoint withdrawal integration in Postman: create a crypto-withdrawal fee quote, submit the withdrawal, and track it to completion. - **[7:00] Fee quotation API with locked rate** — https://www.youtube.com/watch?v=16ReoYTDXk8&t=420s The /crypto-withdrawals/fees endpoint quotes a guaranteed fee rate that Paxos holds for a period of time — giving retail users breathing room to review a transaction before committing. - **[8:30] Amount vs total, fee asset selection** — https://www.youtube.com/watch?v=16ReoYTDXk8&t=510s Integrators can request "send exactly 0.01 ETH" (put the fee on top) or "send all I have" (take the fee out of total). Fee asset is settable — send LINK and deduct the fee in LINK even though Paxos pays ETH gas under the hood. - **[10:00] Execute withdrawal and track** — https://www.youtube.com/watch?v=16ReoYTDXk8&t=600s With a fee ID, the crypto-withdrawal endpoint locks in the rate and debits the user's Paxos profile. List Transfers shows the withdrawal in pending — Paxos runs compliance checks and waits for block confirmations before flipping to completed with an on-chain transaction hash. - **[13:00] Deposit addresses — one per blockchain per user** — https://www.youtube.com/watch?v=16ReoYTDXk8&t=780s The create-deposit-address endpoint returns a per-user-per-network address. Every Paxos end user has at least one deposit address per supported blockchain — Bitcoin, Bitcoin Cash, Ethereum, and the rest. ### Plaid — Plaid Technical Briefing - Slug: `v-plaid` - URL: https://v-sum.com/briefing/v-plaid - Presenter: Clay Allsopp (LinkedIn: https://www.linkedin.com/in/clayallsopp/) - Company: https://www.plaid.com - YouTube: https://www.youtube.com/watch?v=ZYglck-zkno - Tags: open-banking, identity, developer-tools Plaid introduces Wallet Onboard — a Plaid product for crypto developers that brings the familiar Plaid "connect" experience to self-custody crypto wallets. Where Plaid has always linked bank accounts to fintechs, Wallet Onboard normalizes the fragmentation across hundreds of crypto wallets, multiple connection protocols, and the UX differences between MetaMask, Coinbase Wallet, Rainbow, Ledger, and WalletConnect-compatible wallets. The demo shows auto-detection of installed extensions, per-wallet optimized flows (QR for mobile-only wallets, desktop app handoff for hardware), direct wallet-to-app data flow with no Plaid intermediary on wallet addresses, and a drop-in vanilla JavaScript SDK that takes roughly an hour to integrate — plus auto-updates for new wallets and protocols delivered via cdn.plaid.com. Use cases span token gating, NFT mint, holdings tracking, payouts, and message-signature-based authentication. **Chapters:** - **[0:00] Introduction to Plaid — from bank connect to crypto** — https://www.youtube.com/watch?v=ZYglck-zkno&t=0s Plaid traditionally links bank accounts to fintech apps — Venmo, Robinhood, and thousands of others. With crypto exchanges and self-custody tools emerging as major Plaid customers, the team looked at what a Plaid-native primitive for crypto developers would look like. - **[1:00] Parallels between banks and crypto wallets** — https://www.youtube.com/watch?v=ZYglck-zkno&t=60s Just as there are thousands of financial institutions, there are hundreds of different crypto wallets, many protocols, and lots of normalization and UX work — all problems Plaid has already solved once for banking. - **[1:30] Wallet Onboard — Plaid for self-custody crypto wallets** — https://www.youtube.com/watch?v=ZYglck-zkno&t=90s Plaid announced Wallet Onboard, a product that helps crypto developers connect self-custody wallets with the same familiar Plaid feel — no wallet addresses collected, no intermediary sitting between the app and the wallet. - **[2:30] Per-wallet optimized connection flows** — https://www.youtube.com/watch?v=ZYglck-zkno&t=150s Wallet Onboard detects if MetaMask is installed locally, shows a QR scan for MetaMask mobile, jumps straight to a QR code for mobile-only wallets like Rainbow, and hands off to a desktop app for hardware wallets like Ledger. - **[4:00] Wallet data straight from the wallet — no Plaid intermediary** — https://www.youtube.com/watch?v=ZYglck-zkno&t=240s Once connected, address, chain, and balance data come directly from the wallet over an in-browser connection. Plaid is not in the data path; apps can request transaction signatures, mint NFTs, or token-gate using the wallet address directly. - **[5:00] Pain of rolling your own wallet connect** — https://www.youtube.com/watch?v=ZYglck-zkno&t=300s Live code comparison: the window.ethereum approach handles only browser-extension wallets, leaves you to manage chain IDs and hex-vs-decimal quirks, and doesn't work for mobile, Coinbase Wallet, or WalletConnect. Plaid's SDK smooths over all of it. - **[6:00] Drop-in JavaScript SDK** — https://www.youtube.com/watch?v=ZYglck-zkno&t=360s Wallet Onboard is a vanilla JS script tag — no React required. Drop it in, configure chain and RPC URL, pass callbacks, and call open() to launch the flow. A checkForExistingConnection() API lets apps rehydrate connections silently. - **[7:30] Auto-updates as new wallets come online** — https://www.youtube.com/watch?v=ZYglck-zkno&t=450s Because the SDK is served from cdn.plaid.com, Wallet Onboard auto-updates whenever a new wallet ships — Trust Wallet's new extension, new mobile protocols, new conversion optimizations — without app bumps. - **[8:30] Use cases: token gating, NFT mint, payouts, auth** — https://www.youtube.com/watch?v=ZYglck-zkno&t=510s Production use cases seen on Wallet Onboard: token gating (Clubhouse), NFT minting, holdings tracking for finance-management apps, payout address capture, and wallet-backed user authentication via message signatures. ## V-Sum Eighteen — January 10, 2023 Event page: https://v-sum.com/events/eighteen ### Orb — Orb Technical Briefing - Slug: `v-orb` - URL: https://v-sum.com/briefing/v-orb - Presenter: Alvaro Morales (LinkedIn: https://www.linkedin.com/in/alvaro-morales/) - Company: https://www.withorb.com/ - YouTube: https://www.youtube.com/watch?v=cmwQus1DPv8 - Tags: payments, developer-tools Alvaro, co-founder and CEO of Orb, demos Orb — billing and invoicing built for the hybrid usage-based pricing models common in fintech, cloud infrastructure, and developer platforms. Orb\'s primitive is the event: API calls, sessions, or any product action, ingested via direct API push or warehouse sync from Snowflake/Redshift/S3 with a name and a payload of tags and values. From events, operators define metrics — simple filters and aggregations (count of API calls at a balance endpoint) or full custom SQL for more sophisticated MAU or dimensional cases. Plans compose any number of fixed fees (e.g. a $100k annual platform-access fee) and usage-based fees (flat rate per call, tiered volume discounts, dimensional pricing tagged into event properties), with out-of-the-box support for minimums, discounts, trials, and "phases" that stage fee schedules over a customer\'s onboarding ramp. The payoff: billing becomes a real-time process instead of a month-end batch — live next-invoice previews, transparent customer invoices tied to underlying usage, webhook alerts on cost/usage thresholds (upsell banners, CSM alerts, Zapier/Slack), and a Salesforce integration that syncs usage into opportunity pages for sales reps experimenting with consumption-based pricing. **Chapters:** - **[0:00] Introduction to Orb — billing for usage-based pricing** — https://www.youtube.com/watch?v=cmwQus1DPv8&t=0s Alvaro, co-founder and CEO of Orb, introduces the product as "what billing and invoicing would look like if it got created for today's hybrid usage-based pricing models" — targeted at fintech, cloud infrastructure, data, and developer platforms. - **[0:30] Events as the billing primitive** — https://www.youtube.com/watch?v=cmwQus1DPv8&t=30s Orb is built around events — API calls, sessions, or any product action. Events flow into Orb via direct API push or warehouse sync (Snowflake, Redshift, S3) with a name and a payload of tags and values for the dimensions that matter to billing. - **[2:00] Metrics — filter, aggregate, and full SQL** — https://www.youtube.com/watch?v=cmwQus1DPv8&t=120s From ingested events, Orb lets operators define metrics with filters and aggregations (e.g. count of API calls at a balance endpoint). Complex metrics drop into full SQL — so even sophisticated MAU or dimensional aggregations can be expressed without changing the event pipeline. - **[4:00] Pricing plans — fixed fees + usage fees + tiers** — https://www.youtube.com/watch?v=cmwQus1DPv8&t=240s Plans compose any number of fixed fees (e.g. $100k platform-access fee) and usage-based fees (flat rate per API call, tiered volume discounts, dimensional pricing tagged into event properties). - **[4:30] Minimums, discounts, trials, and onboarding phases** — https://www.youtube.com/watch?v=cmwQus1DPv8&t=270s Out-of-the-box pricing levers: minimums, discounts, trials. For API products with integration ramps, Orb's phases feature lets you stage fee schedules (e.g. 3 months at a subset of fees) so invoicing stays automatic as a contract matures. - **[5:30] Real-time invoice preview and transparent customer invoices** — https://www.youtube.com/watch?v=cmwQus1DPv8&t=330s Orb turns billing from a month-end batch into a real-time view: at any moment you see next invoice detail per dimension. Invoices sent to customers tie line items directly back to the underlying usage data, building trust on surprise bills. - **[7:30] Cost and usage alerts + webhooks** — https://www.youtube.com/watch?v=cmwQus1DPv8&t=450s Because Orb tracks invoices in real time, it can fire webhooks when cost or usage thresholds are met — drive in-app upsell banners, alert CSMs, or route to Zapier/Slack for internal workflows. - **[8:30] Salesforce integration for sales visibility** — https://www.youtube.com/watch?v=cmwQus1DPv8&t=510s Orb syncs into Salesforce opportunity pages, giving sales reps full visibility into customer usage patterns — critical for any business adopting or experimenting with consumption-based pricing. ### Oasis Labs — Oasis Labs Technical Briefing - Slug: `v-oasis` - URL: https://v-sum.com/briefing/v-oasis - Presenter: Nick Hynes (LinkedIn: https://www.linkedin.com/in/nhynes-/) - Company: https://www.oasislabs.com/ - YouTube: https://www.youtube.com/watch?v=WMNcAaIBi4c - Tags: blockchain, data-infrastructure, identity Oasis Labs demos on-chain verifiable credentials and selective disclosure on the Oasis confidential EVM. The thesis: put KYC/KYB data on-chain once with a trusted issuer (Equifax-rooted in this demo), then reuse it across web3 protocols without re-doing verification per counterparty — while giving users revocable, selective control over exactly what each verifier sees. The demo walks end-to-end through requesting a credential via identity.oasislabs.com, receiving both an NFT credential on the non-confidential Emerald chain and the full identity data stored confidentially on Sapphire (Oasis's confidential EVM, backed by trusted hardware), granting a demo website access to just the "is over 18" property, calling the isOver18 view from an Express backend, and revoking access afterwards. Broader use cases: credit score disclosure, zip-code mortgage / insurance quoting, and any flow that needs a derived fact rather than raw PII. **Chapters:** - **[0:00] Introduction to Oasis Labs — on-chain verifiable credentials** — https://www.youtube.com/watch?v=WMNcAaIBi4c&t=0s Oasis Labs demos on-chain verifiable credentials and selective disclosure. The thesis: put your identity information on-chain once with a trusted issuer, then reuse it across any web3 protocol — without re-doing KYC/KYB per counterparty. - **[1:00] Benefits to users, verifiers, and issuers** — https://www.youtube.com/watch?v=WMNcAaIBi4c&t=60s Users approve and revoke access per verifier. Verifiers reduce their attack surface because they no longer store sensitive data. Issuers (credit unions, Equifax) amortize KYC cost across many verifiers and get a web3 distribution path. - **[2:00] Demo: over-18 age verification against a website** — https://www.youtube.com/watch?v=WMNcAaIBi4c&t=120s End-to-end walk-through: request a credential from an Equifax-rooted issuer, receive it on a confidential EVM, grant a "dirty website" access to the "is over 18" property only, access the site, then revoke. - **[3:30] NFT credential + confidential identity on Sapphire** — https://www.youtube.com/watch?v=WMNcAaIBi4c&t=210s Two artifacts come back: an NFT on the non-confidential Emerald chain saying "this person passed KYC" (a one-bit credential), plus the full identity data stored confidentially on Sapphire, Oasis's confidential EVM. - **[4:30] Sapphire — confidentiality via trusted hardware** — https://www.youtube.com/watch?v=WMNcAaIBi4c&t=270s Sapphire gives confidentiality via trusted hardware: only the smart contract itself can read blockchain state and incoming transactions. On-chain transactions look like opaque encrypted blobs to third parties. - **[5:30] Identity registry smart contract — selective disclosure** — https://www.youtube.com/watch?v=WMNcAaIBi4c&t=330s Walk-through of the Identity Registry V1 Solidity contract. grantAccess(...) toggles an access-list entry; isOver18() checks the birth timestamp only within the enclave and returns a single boolean — never leaking the date. - **[7:00] Express backend reads "isOver18" from the contract** — https://www.youtube.com/watch?v=WMNcAaIBi4c&t=420s The "dirty website's" Express backend just calls isOver18() on the Oasis contract. No blockchain node, no storage unit, and no other website can see the underlying age — only the approved site gets the single bit. - **[9:30] Revoking access and broader use cases** — https://www.youtube.com/watch?v=WMNcAaIBi4c&t=570s Revocation is a single transaction. Beyond age verification, Oasis sees use cases in credit score disclosure, zip-code-based mortgage and insurance quoting, and any flow where a site needs a derived fact rather than the raw PII. ## V-Sum Nineteen — March 7, 2023 Event page: https://v-sum.com/events/nineteen ### Ansible Labs — Ansible Labs Technical Briefing - Slug: `v-ansible` - URL: https://v-sum.com/briefing/v-ansible - YouTube: https://www.youtube.com/watch?v=U4Y0IWcQh2o - Tags: crypto-infrastructure, defi, payments Ansible Labs co-founder Dan demos Beam, the team's crypto-to-cash off-ramp, at V-Sum Nineteen. The briefing covers wallet-connect onboarding, blockchain risk screening (TRM Labs / Chainalysis / Elliptic) on both the enrolled wallet and the source-of-funds address, Persona KYC, and a unique 1:1 smart-contract Beam address tied to a user + bank-account pair. A live production $15 off-ramp lands in a Bank of America account via RTP in minutes, with ACH, RTP, and push-to-card (Visa Direct / Mastercard Send) on the payout roadmap. **Chapters:** - **[0:00] Off-ramp as the missing piece** — https://www.youtube.com/watch?v=U4Y0IWcQh2o&t=0s Dan, ex-Visa, introduces Ansible Labs' thesis that crypto needs a much smoother off-ramp back to USD. The current flow — self-custody wallet → Coinbase → manual wire — is a blocker on wider adoption of DeFi, NFTs, and DAOs. - **[0:53] Beam overview and live milestones** — https://www.youtube.com/watch?v=U4Y0IWcQh2o&t=53s Beam is Ansible's web app for user enrollment and transfer capabilities. Bank-partner approval was secured two weeks before the briefing, and the demo switches between dev and production environments throughout. - **[1:46] Wallet-connect login and email verification** — https://www.youtube.com/watch?v=U4Y0IWcQh2o&t=106s Connect-wallet login (reusable on return visits), access-code gating in dev, acceptance of T&Cs for both Beam and its custodian + liquidity provider, and a one-time email verification. - **[3:04] Wallet screening and KYC with Persona** — https://www.youtube.com/watch?v=U4Y0IWcQh2o&t=184s Initial address screening using a blockchain risk analytics provider (TRM Labs / Chainalysis / Elliptic) — severe scores block onboarding, high scores trigger manual review. Persona then runs traditional KYC on name, DOB, SSN, and address. - **[5:16] Payout credential: ACH, RTP, and push-to-card** — https://www.youtube.com/watch?v=U4Y0IWcQh2o&t=316s ACH and RTP payouts live today. Visa Direct / Mastercard Send push-to-card workflow and Plaid account linking are on the roadmap — debit card payout gives near-instant deposit to the linked checking account. - **[6:35] Unique smart-contract off-ramp address** — https://www.youtube.com/watch?v=U4Y0IWcQh2o&t=395s Each user + bank-account pair maps 1:1 to a unique smart-contract address on the custodian's platform. Sending ETH or USDC there from MetaMask (or any wallet) triggers automated liquidation and fiat payout. - **[7:27] Source-of-funds screening** — https://www.youtube.com/watch?v=U4Y0IWcQh2o&t=447s In addition to screening the enrolled wallet, Beam screens the sending address against the blockchain-risk provider to ensure funds never originate from sanctioned counterparties such as Tornado Cash. - **[8:18] Live production off-ramp** — https://www.youtube.com/watch?v=U4Y0IWcQh2o&t=498s Switching to production: fetching a live Beam address, sending $15 from MetaMask with ~$4.70 gas, and waiting for block confirmation before the custodian liquidates the crypto and triggers the fiat payout. - **[10:02] RTP settlement to Bank of America** — https://www.youtube.com/watch?v=U4Y0IWcQh2o&t=602s How Beam settles from custodian bank to payments bank, then delivers to the user's RTP-capable Bank of America account in near-real time — typically three to five minutes end-to-end. ### Fairplay — Fairplay Technical Briefing - Slug: `v-fairplay` - URL: https://v-sum.com/briefing/v-fairplay - Presenter: Kareem Saleh - YouTube: https://www.youtube.com/watch?v=J1qHNdlOi7o - Tags: compliance, lending Fairplay founder and CEO Kareem Saleh walks through "fairness as a service" for any algorithm making high-stakes decisions. The briefing demos customer composition and demographic imputation, proxy detection on a bias-vs-predictive-power matrix, fair lending analysis across women, Black, Hispanic, API, and American Indian applicants with Shapley-based driver attribution, census-tract-level geographic maps, a Fairness Optimizer that adds $1M of profit while closing Black-applicant approval gaps, SR 11-7 model risk documentation, and second-look models that surface thousands of additional approvals from declined applications. **Chapters:** - **[0:00] Fairness as a service** — https://www.youtube.com/watch?v=J1qHNdlOi7o&t=0s Kareem Saleh introduces Fairplay, "the world's first fairness-as-a-service company." Tools for any high-stakes decision algorithm to answer five questions: is it fair, why not, can it be fairer, what's the economic impact, and did we reconsider declines. Customers include Figure, Octane, Happy Money, Splash Financial, and LendingPoint. - **[1:18] Getting started and data upload** — https://www.youtube.com/watch?v=J1qHNdlOi7o&t=78s fairplay.ai login with GCP, Azure, or AWS integrations (or direct accounts). Upload a non-mortgage, mortgage, or marketing dataset — inputs, outputs, and outcomes — to unlock five product functions on the dashboard. - **[2:35] Customer composition and demographic imputation** — https://www.youtube.com/watch?v=J1qHNdlOi7o&t=155s Using first name, last name, and street address to approximate race, gender, and age for every applicant — replacing "fairness through blindness" with actual measurement. A top-10 bank took nine months to build this internally; Fairplay exposes it as a one-click function. - **[3:27] Proxy detection: bias vs predictive power** — https://www.youtube.com/watch?v=J1qHNdlOi7o&t=207s Every variable in the algorithm plotted on a 2D matrix — bias (predictiveness of protected status) on the x-axis, predictive power on the y-axis. Credit score is highly predictive of default but also of being Black or Hispanic; lower-bias substitutes are surfaced. - **[6:04] Fair lending analysis** — https://www.youtube.com/watch?v=J1qHNdlOi7o&t=364s Evaluating fairness of underwriting (or pricing, line assignment, fraud, marketing) decisions. Summary cards per protected group show adverse-impact ratios against current, previous, and credit-score-only baselines — with notes on the different fairness definitions preferred by CFPB, OCC, and FDIC. - **[7:22] Protected groups and Shapley-based drivers** — https://www.youtube.com/watch?v=J1qHNdlOi7o&t=442s Per-group views for women, Black, Hispanic, API, and American Indian applicants. "Drivers of disparity" uses Shapley values — e.g. FICO explains 18%, borrower income vs MSA median 12%, and co-applicant Vantage score 8% of the disparity exhibited by Black applicants. - **[9:07] Geographic fairness mapping** — https://www.youtube.com/watch?v=J1qHNdlOi7o&t=547s Census-tract-level maps of mortgage fairness for every U.S. originator. Example: Wells Fargo in Miami-Dade census tract 114.01 is approving Black applicants at 43% the rate of white applicants. - **[10:28] Executive presentations and Fairness Optimizer** — https://www.youtube.com/watch?v=J1qHNdlOi7o&t=628s Downloadable executive reports designed by Seth Feaster (ex-NYT data viz lead), almost all visual. Fairness Optimizer plots alternative models on a profitability-vs-fairness chart — finds an algorithm that approves more Black applicants and adds $1M in profit while holding the loan book constant. - **[13:07] SR 11-7 model risk documentation** — https://www.youtube.com/watch?v=J1qHNdlOi7o&t=787s In-time and out-of-time stress tests, modeling technique, and variables-used reports — the full SR 11-7-style model risk management documentation required by federal financial regulators, generated with one click. - **[13:33] Second-look models** — https://www.youtube.com/watch?v=J1qHNdlOi7o&t=813s Re-underwriting declined applications with a fairness-tuned second-look model. Accepting a 3% accuracy diminution surfaces ~5,000 additional loans, grows the book by $100M, and lifts profitability ~11% — with population-characteristics views revealing higher-DTI, lower-FICO, higher-LTV applicants the incumbent missed. ## V-Sum Twenty — May 16, 2023 Event page: https://v-sum.com/events/twenty ### Sila — Sila Technical Briefing - Slug: `v-sila` - URL: https://v-sum.com/briefing/v-sila - Presenter: Shamir Kharkel - Company: https://silamoney.com - YouTube: https://www.youtube.com/watch?v=eDvvEokYlvE - Tags: payments, banking-as-a-service, developer-tools Shamir Karkal, co-founder of Sila and previously Simple and BBVA\'s API platforms, demos the Sila money API — a developer-first platform built around three primitives (users, wallets, transactions) that lets any builder onboard users, run KYC, link bank accounts, and move ACH. The demo app at demo.silamoney.com onboards both individuals and businesses via unique alphanumeric handles; KYC runs asynchronously through Socure/LexisNexis (3–15 seconds typical) with document-upload fallback for IDs or formation docs. Every user gets one wallet by default but can own many (one-to-many), enabling segregated-account patterns. Sila supports three ways to link bank accounts: raw routing+account entry, your own Plaid integration via processor tokens, or Sila\'s managed Plaid instance (Plaid sandbox user_good/pass_good). Same-day ACH pulls $1,234 into the wallet in roughly five minutes in sandbox — deliberately slow so developers don\'t build code expecting real-time settlement. Wallet-to-wallet transfers settle on Sila\'s ledger in seconds; external redeems push ACH out to any linked bank account. **Chapters:** - **[0:00] Introduction to Sila** — https://www.youtube.com/watch?v=eDvvEokYlvE&t=0s Shamir Karkal, co-founder of Sila and previously Simple and BBVA's API platforms, introduces Sila — a developer-first API to onboard users, verify identity, hold money, and move ACH payments in the US. - **[1:30] Sila demo app and API console** — https://www.youtube.com/watch?v=eDvvEokYlvE&t=90s The demo uses demo.silamoney.com, where Shamir has dropped in API keys from the Sila Console. Sila's model is built around three entities: users, wallets, and transactions — with all responses surfaced on the right panel for inspection. - **[2:00] Individual vs. business entities** — https://www.youtube.com/watch?v=eDvvEokYlvE&t=120s Sila onboards both individuals and businesses via the /register endpoint. Each entity gets a unique alphanumeric handle — Shamir picks one that isn't taken — and then selects a KYC path from several supported flows. - **[3:00] KYC with document upload fallback** — https://www.youtube.com/watch?v=eDvvEokYlvE&t=180s KYC is asynchronous (3–15 seconds typical) and delivered via webhook. If Socure or LexisNexis flags a field (SSN, address), Sila supports document upload — IDs for individuals, formation docs for businesses — to complete verification. - **[5:00] Wallets — pockets of cash, one-to-many** — https://www.youtube.com/watch?v=eDvvEokYlvE&t=300s Wallets are just balance-holding pockets — every user gets one by default, but customers can create as many as they want and name them anything. The wallet-to-user relationship is one-to-many, which enables segregated account patterns. - **[5:30] Link bank accounts — routing+account, Plaid, Plaid-via-Sila** — https://www.youtube.com/watch?v=eDvvEokYlvE&t=330s Sila supports linking external bank accounts via raw routing+account entry, your own Plaid integration with processor tokens, or Sila's managed Plaid flow — Shamir uses the last option with Plaid's sandbox credentials (user_good/pass_good). - **[7:30] Same-day ACH and realistic sandbox timing** — https://www.youtube.com/watch?v=eDvvEokYlvE&t=450s Sila pulls $1,234 in via same-day ACH. Amounts are denominated in "Sila" (1 cent). The sandbox deliberately takes ~5 minutes to complete ACH transactions so developers don't build code expecting real-time settlement. - **[9:00] ACH transfers between users and external redeems** — https://www.youtube.com/watch?v=eDvvEokYlvE&t=540s Transfers between Sila wallets settle on Sila's internal ledger in seconds. Redeem transactions push funds out to an external linked bank account via ACH. Both flows are exposed as dedicated endpoints that chain cleanly from KYC → wallet → transaction. ### Nval — Nval Technical Briefing - Slug: `v-nval` - URL: https://v-sum.com/briefing/v-nval - Company: https://nval.com - YouTube: https://www.youtube.com/watch?v=6JPj_jppp48 - Tags: capital-markets, investing, nft NVAL demos pricing infrastructure for illiquid assets, starting with NFTs. Using AI and on-chain data feeds, NVAL produces fair market values for NFTs in near real time — foundational for any financial workflow (lending, borrowing, insuring, trading) on non-fungible assets that have no spot price. NVAL sits as an analytics layer between blockchains (L1s, L2s, cross-chain) and the industries building on top (gaming, sports, trade finance, accounting, lending). Mark (CTO) walks through the REST API documented with OpenAPI: a "try it out" docs UI, a Postman collection, and a CLI all return the same price prediction for a specific NFT (the demo values a Doodle at 3.3 ETH with 96% confidence, sitting between the listed price of 4.2 ETH and the highest offer of 2.8 ETH). A Chrome extension surfaces NVAL prices on OpenSea pages, and the NVAL web app shows floor price, listed price, and price history against actual trade prints. The price-history endpoint returns 52 weekly data points across a year (configurable daily). Feature importance breaks down what drives price — 96% market action for a Doodle, 72% market action + 30% accessory-trait for a CryptoPunk — giving traders a way to understand why NVAL priced an NFT where it did. **Chapters:** - **[0:00] Introduction to NVAL** — https://www.youtube.com/watch?v=6JPj_jppp48&t=0s NVAL is the pricing infrastructure for illiquid assets — starting with NFTs. Using AI and on-chain data feeds, NVAL produces fair market values in near real time — foundational for lending, borrowing, insuring, and trading non-fungible assets where there is no spot price. - **[1:00] Layer between blockchains and industries** — https://www.youtube.com/watch?v=6JPj_jppp48&t=60s NVAL sits as an analytics layer between the raw blockchain data (L1s, L2s, cross-chain) and the industries building on top (gaming, sports, trade finance, lending, accounting) — turning access to data into usable market information. - **[2:30] REST API and developer docs** — https://www.youtube.com/watch?v=6JPj_jppp48&t=150s Mark, CTO, demos the NVAL REST API documented with the OpenAPI standard. Authenticated B2B customers hit a docs-site "try it out" UI or use an API key + secret in Postman/CLI to fetch price predictions for specific network+collection+NFT-ID combinations. - **[3:30] Live doodle price prediction — 3.3 ETH with 96% confidence** — https://www.youtube.com/watch?v=6JPj_jppp48&t=210s The demo prices a specific Doodle at 3.3 ETH with 96% confidence. The NFT is listed on OpenSea at 4.2 ETH with offers around 2.8 — NVAL's prediction lands in between, showing both where the market is mispricing and where the owner is over-asking. - **[5:00] Chrome extension and web app insights** — https://www.youtube.com/watch?v=6JPj_jppp48&t=300s NVAL's Chrome extension surfaces prices on OpenSea pages. The web app goes deeper: market price, current listed price, floor price, and a time-series price history with predictions overlaid against actual trade prints. - **[6:30] Price history — daily or weekly granularity** — https://www.youtube.com/watch?v=6JPj_jppp48&t=390s The price-history endpoint returns weekly prices for a specific NFT over the last year (52 data points) — configurable down to daily granularity or extended back to mint. Same contract address, same token ID, same shape via Postman. - **[8:30] Feature importance — market action vs. traits** — https://www.youtube.com/watch?v=6JPj_jppp48&t=510s Feature importance breaks down which signals drive the price. For a Doodle, 96% is market action and very little is trait-based. For a CryptoPunk, ~72% is market action and 30% is accessory/trait — so traits matter significantly for collectibles with strong art. - **[11:30] Graphing feature importance over time windows** — https://www.youtube.com/watch?v=6JPj_jppp48&t=690s Feeding the feature-importance response into Google Sheets produces pie charts showing the dominant inputs (one-day window) vs. secondary (two-day window, accessories). Different collections produce strikingly different weightings. ### Ntropy — Ntropy Technical Briefing - Slug: `v-ntropy` - URL: https://v-sum.com/briefing/v-ntropy - Company: https://ntropy.com - YouTube: https://www.youtube.com/watch?v=jhymM6Zy_GA - Tags: data-infrastructure, developer-tools Amelia Niemi, co-founder and CTO of Ntropy, walks through the Ntropy transaction enrichment and categorization API. Raw bank transactions go in, structured data comes out — category, merchant identity, logo, location, website, recurrence pattern, active and cancelled subscriptions, and detected income sources. A live Python quickstart shows four lines of code enriching a 1,500-row CSV (roughly 12–18 months of transaction history); the Ntropy app then surfaces the same data in a PFM-style UI. Amelia walks through Ntropy's benchmarks against GPT-4 — about 2,000× cheaper per transaction, 150× faster, and 15× more accurate on the hardest cases — before ML engineer Robin demos "Ntropy Cookie," a Discord chatbot that lets end users ask natural-language questions about their own spending: essentials vs non-essentials, savings opportunities, bank fees. **Chapters:** - **[0:00] Introduction to Ntropy** — https://www.youtube.com/watch?v=jhymM6Zy_GA&t=0s Amelia Niemi, co-founder and CTO of Ntropy, introduces the Ntropy transaction enrichment and categorization API — raw bank transactions in, structured merchant data out. - **[1:00] API overview: income, recurrence, categories** — https://www.youtube.com/watch?v=jhymM6Zy_GA&t=60s The Ntropy API ingests raw bank transactions and returns enriched data — categories, merchant identity, recurrence patterns, income source detection, and all the bells and whistles fintechs need for PFM, underwriting, and personalization. - **[2:30] Python quickstart — five lines to enrich a CSV** — https://www.youtube.com/watch?v=jhymM6Zy_GA&t=150s Live quickstart from the Ntropy docs: initialize the SDK with your API key, point it at a CSV of 1,500 transactions (~12-18 months of history), and save the enriched output. Four or five lines of Python. - **[4:30] Enriched transactions in the app UI** — https://www.youtube.com/watch?v=jhymM6Zy_GA&t=270s Uploading the same CSV into app.ntropy.com shows labels, merchant logos, locations, website URLs, and merchant IDs — the same API output rendered in a PFM-style interface. - **[5:30] Subscriptions, recurring payments, and income detection** — https://www.youtube.com/watch?v=jhymM6Zy_GA&t=330s Out of the box the app surfaces active and inactive subscriptions, recurring payments (including monthly Spotify), and detected income sources like salary — useful primitives for personalization and underwriting. - **[7:00] Ntropy vs GPT-4 benchmarks** — https://www.youtube.com/watch?v=jhymM6Zy_GA&t=420s Amelia walks through benchmark numbers for Ntropy's specialized transaction enrichment vs GPT-4: roughly 2,000× cheaper per transaction, 150× faster latency, and 15× more accurate on the hardest cases. - **[8:30] Ntropy Cookie — chat over your transactions** — https://www.youtube.com/watch?v=jhymM6Zy_GA&t=510s Robin demos "Ntropy Cookie," a Discord-hosted chatbot built on top of the enrichment API — users ask "how much did I spend on fast food last month?" and an LLM reads enriched Ntropy output to answer. - **[11:30] Pre-made prompts: essentials, savings opportunities, bank fees** — https://www.youtube.com/watch?v=jhymM6Zy_GA&t=690s Shipped prompts show essentials-vs-non-essentials breakdowns (correctable by the user), savings opportunities, bank-fee audits, and a tongue-in-cheek "roast me based on my transactions" command. ## V-Sum TwentyOne — June 27, 2023 Event page: https://v-sum.com/events/twentyone ### Stride — Stride Technical Briefing - Slug: `v-stride` - URL: https://v-sum.com/briefing/v-stride - YouTube: https://www.youtube.com/watch?v=ZAPeHt8fURs - Tags: identity, compliance, developer-tools Stride.ai co-founder Virajendra Daita walks through the company's unified AI platform for financial institutions — Doc AI for multi-language document processing, Web AI for no-code scraping of regulator and market sources, and an NLU layer for entity extraction and semantic search. The briefing covers an enterprise KYC orchestration that cuts corporate onboarding from ~29 days to ~1 day (saving €2M+/year), an 80,000-docs-per-day remittance processor, and live demos of KYC screening via Refinitiv and structured + unstructured document extraction. **Chapters:** - **[0:00] Introduction to Stride** — https://www.youtube.com/watch?v=ZAPeHt8fURs&t=0s Virajendra "VJ" Daita introduces Stride.ai — "NextGen AI for Enterprises" — focused on financial institutions and occasional pharma customers, with a unified platform for intelligent automation. - **[0:26] Platform components: Doc AI, Web AI, NLU** — https://www.youtube.com/watch?v=ZAPeHt8fURs&t=26s Three pillars of the platform: Doc AI for multi-language and multi-format document processing, Web AI for programmatically tracking regulator registries and markets without code, and NLU for check analysis, entity extraction, and semantic search. - **[2:13] Workflow editor and pre-built integrations** — https://www.youtube.com/watch?v=ZAPeHt8fURs&t=133s The no-code build layer with UI and API connectors, intelligent annotation, and pre-built integrations — configuration-first development from requirements gathering through deployed solution. - **[3:30] Low-resource learning differentiator** — https://www.youtube.com/watch?v=ZAPeHt8fURs&t=210s Stride's 2019 Dexter paper (dexter.stride.ai) on learning from less data — the entry-barrier-breaker for financial services, alongside on-prem deploy, security and compliance, and tunable customization. - **[4:48] Enterprise KYC orchestration case study** — https://www.youtube.com/watch?v=ZAPeHt8fURs&t=288s Corporate KYC reduced from roughly 29 working days to about 1 day using Doc AI, Web AI, and multilingual capabilities. Ubiquitous UX across otherwise fragmented bank tooling, full audit trail, and €2M+ of annual savings. - **[6:57] Remittance processing at scale** — https://www.youtube.com/watch?v=ZAPeHt8fURs&t=417s 80,000 scanned remittance documents per day processed via pattern recognition. Data-entry and quality-check effort cut by 80%, with seamless integration into existing downstream systems. - **[7:49] Wedding analyst form standardizer** — https://www.youtube.com/watch?v=ZAPeHt8fURs&t=469s A simpler case study: a standardized "Wedding Analyst" form captured at >99.9% accuracy, already being integrated into the customer's existing KYC system. - **[9:06] Live KYC demo** — https://www.youtube.com/watch?v=ZAPeHt8fURs&t=546s Walkthrough of the KYC orchestration product: pulling screening data from Refinitiv (formerly World-Check), validating against the customer's preferred data sources, then running entity screening in seconds with drill-down into match strength. - **[11:20] Document processing demo** — https://www.youtube.com/watch?v=ZAPeHt8fURs&t=680s Live upload of a scanned remittance document. Processed in about 30 seconds with extracted fields rendered alongside the original image, editable to match the back-end schema exactly. - **[14:02] Unstructured extraction** — https://www.youtube.com/watch?v=ZAPeHt8fURs&t=842s Final demo showing the linguistic models handling documents with no specific structure, using the core models built over eight years — works for structured, semi-structured, and fully unstructured inputs. ## V-Sum TwentyTwo — April 14, 2026 Event page: https://v-sum.com/events/twentytwo ### Compass Labs — Compass Labs Technical Briefing - Slug: `compass-labs-technical-briefing` - URL: https://v-sum.com/briefing/compass-labs-technical-briefing - Presenter: Elisabeth Duijnstee - Company: https://compasslabs.ai - YouTube: https://www.youtube.com/watch?v=lN5PjPoTFG4 - Tags: Compass Labs, DeFi, Stablecoin Compass Labs CEO Elisabeth Duijnstee walks through how fintechs and neobanks can embed DeFi products — stablecoin yield, crypto-backed loans, and tokenized stocks — through a single non-custodial API. The briefing includes a live build in Compass Studio of a white-label USDC savings account on Base, a $5 deposit into a Gauntlet USDC Prime vault, and a tour of position reporting, segregated sub-accounts for crypto-backed credit, and an LLM-friendly docs surface designed for coding agents like Claude Code. **Chapters:** - **[0:00] Introduction to Compass Labs** — https://www.youtube.com/watch?v=lN5PjPoTFG4&t=0s Elisabeth Duijnstee introduces Compass Labs — the DeFi layer for fintechs and neobanks. One API for stablecoin yield, crypto-backed loans, and tokenized stocks, so platforms can ship DeFi products in a day instead of building protocol-by-protocol integrations. - **[0:49] From physics to DeFi infrastructure** — https://www.youtube.com/watch?v=lN5PjPoTFG4&t=49s Background: a PhD in physics at Oxford, a London fund role, and the move into crypto trading. The thesis: better finance runs on crypto rails, but building on-chain is painful — protocols are integrated one by one, and shipping a second product tends to break the first. - **[1:51] Compass Studio and the product suite** — https://www.youtube.com/watch?v=lN5PjPoTFG4&t=111s Tour of studio.compasslabs.ai and the API catalog at api.compasslabs.ai. Four product lines: DeFi savings, portfolio management, credit (crypto-backed loans), and public markets (tokenized stocks), all behind a single set of endpoints. - **[2:54] Configuring a DeFi savings account** — https://www.youtube.com/watch?v=lN5PjPoTFG4&t=174s Live build of a white-label yield product on Base. Select chains and tokens, then filter the ERC-4626 vault universe (Morpho, Pendle, and more) by minimum TVL and asset to curate the markets surfaced to end users — including a fixed-rate Pendle option. - **[4:16] First deposit into a Gauntlet USDC vault** — https://www.youtube.com/watch?v=lN5PjPoTFG4&t=256s A non-custodial $5 deposit into the Gauntlet USDC Prime vault, confirmed on BaseScan. Compass returns transaction payloads — custody stays with the integrator's wallet layer (any wallet, embedded or otherwise). - **[5:06] Positions, reporting, and swap-and-deposit** — https://www.youtube.com/watch?v=lN5PjPoTFG4&t=306s Read balances, positions, realized and unrealized P&L, and transaction history via the Compass API — useful for end-user reporting. ETH is swapped and deposited into a USDC-denominated market in a single call. - **[5:56] White-label UI and copy-paste shipping** — https://www.youtube.com/watch?v=lN5PjPoTFG4&t=356s Theme the widget for dark or light mode, pick brand colors, and copy-paste the generated code into your app. Gas sponsorship, monetization, and bridging are abstracted behind the API rather than re-implemented per integrator. - **[7:15] Segregated accounts and crypto-backed loans** — https://www.youtube.com/watch?v=lN5PjPoTFG4&t=435s Per-product sub-accounts keep fund flows isolated across savings, credit, and markets without intermingling balances. Quick look at the credit product: deposit BTC, borrow USDC, inspect the net interest rate, and ship. - **[8:03] LLM docs and a DeFi risk dashboard** — https://www.youtube.com/watch?v=lN5PjPoTFG4&t=483s Compass exposes LLM-oriented docs that pair well with Claude Code and other coding assistants. Demo of a risk dashboard built that way — showing per-wallet exposure across underlying markets and overlap between Morpho and Pendle vaults. - **[9:24] Free API key and call to action** — https://www.youtube.com/watch?v=lN5PjPoTFG4&t=564s Free API keys at api.compasslabs.ai with generous limits for building an MVP, plus hands-on support from the Compass team for integrators shipping DeFi products. ### Ideem — Ideem Technical Briefing - Slug: `ideem-technical-briefing` - URL: https://v-sum.com/briefing/ideem-technical-briefing - Presenter: Toby Rush (LinkedIn: https://www.linkedin.com/in/tobiasrush) - Company: https://www.useideem.com/ - YouTube: https://www.youtube.com/watch?v=Gn_UgtuufI8 - Tags: ideem, wallet Ideem CEO Toby Rush walks through how modern cryptography can deliver invisible possession-factor authentication for banks, neobanks, and agentic-commerce flows. The briefing covers Ideem's FIDO + multi-party-computation "chip in software" model, device-plus-passkey binding on the same challenge, and a live Android demo of app-to-app bridging where a merchant webview verifies trust with a previously enrolled Yes Bank app via a silent push and an encrypted local channel — with no human in the loop. **Chapters:** - **[0:00] Introduction to Ideem** — https://www.youtube.com/watch?v=Gn_UgtuufI8&t=0s Toby Rush introduces Ideem's work with a large global bank on modern cryptography for possession-factor authentication. The three factors — something you know, are, and have — and why generative AI weakens all three except hardware-bound "have". - **[1:03] The chip-in-software thesis** — https://www.youtube.com/watch?v=Gn_UgtuufI8&t=63s How credit-card EMV chips drove card-present fraud toward zero via a private key in the chip. Ideem puts the equivalent inside software — native apps on iOS/Android, browsers, embedded webviews — using the FIDO protocol with a multi-party-computation key split between device and server. - **[2:11] Invisible MPC authentication** — https://www.youtube.com/watch?v=Gn_UgtuufI8&t=131s The runtime flow: Ideem's SDK pulls a challenge from the relying party, signs it via MPC on the device, and returns it for validation. Two simple calls — authenticate and validate — with no public-key infrastructure required on the integrator. - **[3:03] First-time device enrollment** — https://www.youtube.com/watch?v=Gn_UgtuufI8&t=183s Enrolling a device into the "zero-trust secure module" on a browser (works identically on native apps). Post-enrollment, signing a long one-time passcode takes ~500ms with no user interaction. - **[4:21] Device + user binding with passkeys** — https://www.youtube.com/watch?v=Gn_UgtuufI8&t=261s Layering a FIDO passkey (biometric) on top of the device key so both the device and the user are verified. The two FIDO keys sign the same challenge and are cryptographically linked — fully auditable by regulators. - **[6:05] Bridging across apps on one phone** — https://www.youtube.com/watch?v=Gn_UgtuufI8&t=365s Solving first-time-on-device trust: an embedded webview in a merchant app asks the trusted bank app "am I on a trusted device?" via a silent push, the native app wakes, signs a FIDO challenge, and opens a local port for an encrypted app-to-app bridge. - **[7:49] Android demo: Yes Bank to merchant** — https://www.youtube.com/watch?v=Gn_UgtuufI8&t=469s Enrolling "Yes Bank" with Ideem's SDK, then paying inside a separate merchant app. The webview bridges to the native bank app (port 60766 in the log), proving same-device origin with PKI and no user interaction beyond tapping pay. - **[9:35] Agentic commerce implications** — https://www.youtube.com/watch?v=Gn_UgtuufI8&t=575s Every agent-commerce proposal — Visa, Mastercard, Stripe, Google, OpenAI — reduces to public/private keys for user identification, consent signing, and downstream auditable authorization. Ideem's primitives map directly onto that control plane. ### Tempo — Tempo Technical Briefing - Slug: `tempo-technical-briefing` - URL: https://v-sum.com/briefing/tempo-technical-briefing - Presenter: Brendan Ryan - Company: https://tempo.xyz - YouTube: https://www.youtube.com/watch?v=Ph8z2SjV3F0 - Tags: Tempo, Stripe Tempo's Brendan Ryan introduces the Machine Payments Protocol (MPP), designed with Stripe as the payment form for AI agents. The briefing shows how MPP rides natively on HTTP request/response flows so agents can make paid API calls without preconfigured API keys or billing relationships, with live demos paying Parallel for web data and unlocking a payment-gated article via HTTP 402 — across Tempo, Stripe, Solana, Bitcoin payment methods, and Visa cards from day one. **Chapters:** - **[0:00] Launching the Machine Payments Protocol** — https://www.youtube.com/watch?v=Ph8z2SjV3F0&t=0s Tempo's Machine Payments Protocol (MPP), designed with Stripe, positioned as the payment form for agents in the broader stablecoin and agentic-commerce wave. - **[0:52] Why payments matter for AI workflows** — https://www.youtube.com/watch?v=Ph8z2SjV3F0&t=52s Stablecoins improve cross-border, payroll, and netting efficiency. AI creates value that needs to be captured, but the classic payment form is full of friction and fights 20+ years of bot-protection headwinds. - **[1:46] Designing the payment form for agents** — https://www.youtube.com/watch?v=Ph8z2SjV3F0&t=106s First-principles redesign: MPP works natively in the HTTP request/response flow. An agent can make a paid API call with no API key and no formal billing relationship — the 402 response carries the payment terms. - **[2:40] Paying Parallel for web data on demand** — https://www.youtube.com/watch?v=Ph8z2SjV3F0&t=160s Live demo calling Parallel's LLM-search and web-scraping API in cents per request using a Tempo wallet, with no API key provisioned in advance, to retrieve structured data on the fly. - **[3:56] 10+ payment methods on day one** — https://www.youtube.com/watch?v=Ph8z2SjV3F0&t=236s MPP ships with support for Tempo, Stripe, Solana, Bitcoin payment methods, and Visa cards via a spec extension — multi-method and multi-interface by design rather than protocol-specific. - **[4:48] HTTP 402 and payment-gated articles** — https://www.youtube.com/watch?v=Ph8z2SjV3F0&t=288s Classic paywall UX rebuilt on MPP: load a page, receive a 402 with price and accepted methods, confirm payment with a vaulted Stripe card (or Tempo, or any stablecoin), and the page returns 200 — same programmatic flow across rails. ## Day Zero 06 — May 5, 2026 Event page: https://v-sum.com/events/day-zero-06 ### Para — Para Technical Briefing - Slug: `para-technical-briefing` - URL: https://v-sum.com/briefing/para-technical-briefing - Presenter: Nitya Subramanian - Company: https://www.getpara.com/ - YouTube: https://www.youtube.com/watch?v=bemopJ-zFfk - Tags: wallets, agentic-payments, permissions, Para, Day Zero 06 Para's Nitya Subramanian demos Para's wallet infrastructure for agentic commerce at Day Zero 06, framed around three problems with agentic payments today: hard wallet UX, plain-text private keys, and missing guardrails. Paramodal turns email verification into a fully functional wallet in seconds. The REST API provisions agent wallets with IP allowlists so a wallet for an OpenWebUI agent on a single Mac mini can only be exercised from that exact IP, then signs messages and raw transactions across Solana, Stellar, EVM, and Cosmos. Para's permissions feature enforces app-wide policies — scopes for transfers and signing, conditions like 'transaction amount < 1', plus distinct bypass and autonomous-with-policy modes for agents — at the MPC cryptography layer rather than in app code. Modular Para clients can be wrapped with x402 or MPP forwarders to slot directly into agent-payment flows. **Chapters:** - **[0:00] Para — wallet infrastructure for agentic commerce** — https://www.youtube.com/watch?v=bemopJ-zFfk&t=0s Nitya Subramanian opens with Para's pitch: wallet infrastructure that abstracts away the complexity of authentication and on-chain interaction so any company can offer wallets to users (or agents) without building it from scratch. - **[0:30] Modular wallets wrapped by x402 / MPP forwarders** — https://www.youtube.com/watch?v=bemopJ-zFfk&t=30s Para's clients are modular by design — you can wrap them with x402 or MPP-compatible forwarders to slot directly into agentic-payment flows like the ones James (Stellar) and Jeff (Stable Coin Company) demoed earlier in the session. - **[0:50] Three problems with agentic commerce** — https://www.youtube.com/watch?v=bemopJ-zFfk&t=50s Wallets are hard to use, agents often need access to private keys in plain text, and once an agent is loose there are no guardrails. Para has three product surfaces that address each problem. - **[1:20] Paramodal — email-to-wallet in seconds** — https://www.youtube.com/watch?v=bemopJ-zFfk&t=80s Live Paramodal demo: enter an email, verify, and a fully functional wallet appears with an address, top-up, and asset list. The "log into a website" UX replaces seed phrases for end users. - **[2:00] REST API for agent wallets — IP allowlists** — https://www.youtube.com/watch?v=bemopJ-zFfk&t=120s For agents, the REST API creates wallets without OAuth or email credentials. IP allowlisting means a wallet provisioned for an OpenWebUI agent on a Mac mini can only be exercised from that exact IP — sharply limits compromise blast radius. - **[2:40] Create a wallet via API key** — https://www.youtube.com/watch?v=bemopJ-zFfk&t=160s Live: a one-time developer-portal API key creates a new wallet, picks the wallet type, returns a wallet ID and address. The same API wallet can later be upgraded to an authenticated user wallet seamlessly. - **[4:00] Sign a message — multi-chain signature** — https://www.youtube.com/watch?v=bemopJ-zFfk&t=240s "hello day zero" gets signed via the same API key path. The returned signature is valid for Solana, Stellar, EVM, Cosmos — and a sign-raw capability lets agents sign just about any transaction shape. - **[5:00] Guardrails — recent multi-million-dollar agent rug** — https://www.youtube.com/watch?v=bemopJ-zFfk&t=300s A trading bot recently accumulated 7–8 figures in PnL and then shipped the entire balance to an unknown address. Cautionary tale that motivates Para's permissions feature. - **[5:30] Permissions — app-wide policies with scopes** — https://www.youtube.com/watch?v=bemopJ-zFfk&t=330s Permissions are app- or project-wide policies built from scopes (think OAuth-style permission requests). Each scope groups granular sub-capabilities and supports lists of conditions that must all evaluate true for a transaction to pass. - **[6:30] Bypass vs autonomous-with-policy** — https://www.youtube.com/watch?v=bemopJ-zFfk&t=390s Two agent capabilities: one-time human bypass for a specific transaction outside the policy, or autonomous-with-policy where the agent transacts freely inside the policy envelope. Enforced at the MPC layer, not in app code. - **[7:00] Permissions builder — transfers + signing scopes** — https://www.youtube.com/watch?v=bemopJ-zFfk&t=420s Live walk-through of the permissions builder as Acme Corp: select Ethereum and Polygon, add a transfers scope with a "transaction amount < 1" condition, then add a signing scope for messages. Final policy applies to every wallet under the project. ### Radius — Radius Technical Briefing - Slug: `radius-technical-briefing` - URL: https://v-sum.com/briefing/radius-technical-briefing - Presenter: Tyler Frederick - Company: https://www.radiustech.xyz/ - YouTube: https://www.youtube.com/watch?v=uzRGT62QUMY - Tags: stablecoins, microtransactions, x402, Radius, agentic-payments, Day Zero 06 Radius's Tyler Frederick walks through Radius — stablecoin infrastructure aimed at millions of transactions per second to power agentic microtransactions like sub-penny purchases of data, inference, or compute — at Day Zero 06. The demo uses a fictional security/risk-assessment API called EdgeMeter, which currently blocks the ~50% of web traffic that is bots with 403s. Flip on x402 with per-request sub-penny pricing and the same bot traffic becomes monetized agent demand: live MetaMask-driven traffic settles in real time on Radius mainnet with revenue accruing per call. The deploy story is just as fast — a Claude session uses the open-source Radius x402 skill to ship a Cloudflare Worker endpoint, and a parallel buyer agent provisions a wallet, hits the Radius mainnet faucet for a 1-cent SBC drip (which funds 100 transactions at Radius's 1/100¢ per tx), then completes a paid call end-to-end in under five minutes. **Chapters:** - **[0:00] Radius — millions of TPS for stablecoin infra** — https://www.youtube.com/watch?v=uzRGT62QUMY&t=0s Tyler Frederick introduces Radius: massively scalable stablecoin infrastructure aiming at processing transactions in the millions of TPS, in service of agentic commerce use cases that legacy L1s and L2s can't fit. - **[0:30] Why agentic commerce needs that much bandwidth** — https://www.youtube.com/watch?v=uzRGT62QUMY&t=30s Other interpretations of agentic commerce ("Claude, find me running shoes under $100") are well-served by existing rails. Radius targets the harder regime: paying for a bit of data, inference, or compute — sub-penny microtransactions agents will run by the millions. - **[1:30] EdgeMeter — fake company, real demo** — https://www.youtube.com/watch?v=uzRGT62QUMY&t=90s A hypothetical company called EdgeMeter sells security and risk-assessment endpoints (threat intel, bot scoring) and gates access via subscriptions. Its bot-traffic problem mirrors most real APIs. - **[2:00] ~50% of web traffic is bots** — https://www.youtube.com/watch?v=uzRGT62QUMY&t=120s Cloudflare's number: roughly half of web traffic is now bots, and that share will keep climbing as developers lean on Claude Code and similar tools. EdgeMeter's 403-block-bots policy is leaving real revenue on the table. - **[2:30] Flip on x402 — per-request sub-penny pricing** — https://www.youtube.com/watch?v=uzRGT62QUMY&t=150s EdgeMeter turns on x402 with per-request pricing under one cent. Every endpoint now has a per-call price tag, and the dashboard sits idle waiting for settlement events. - **[3:00] Mainnet swarm — real settlements on Radius** — https://www.youtube.com/watch?v=uzRGT62QUMY&t=180s A traffic generator fires real transactions through MetaMask. The dashboard shows revenue accruing per request in real time on the Radius mainnet — bots monetized instead of blocked. - **[4:30] Buyer side — agent, wallet, funds** — https://www.youtube.com/watch?v=uzRGT62QUMY&t=270s Walking back to the start: making this agent-native means agents need wallets, funds, and an x402-aware client. Radius publishes open-source x402 skills so any harness (Claude, Codex, Hermes) can plug in. - **[5:30] Live deploy — Claude builds the seller side** — https://www.youtube.com/watch?v=uzRGT62QUMY&t=330s Tyler pastes a prompt into Claude that uses the Radius x402 skill to deploy a dummy x402-gated endpoint to a Cloudflare worker. (Brief Claude login wobble, recovered live.) - **[6:30] Buyer agent — wallet + Radius mainnet faucet** — https://www.youtube.com/watch?v=uzRGT62QUMY&t=390s In a parallel Claude window, a buyer agent creates a wallet and hits the Radius mainnet faucet for a 1-cent SBC drip. At Radius's 1/100¢ per transaction, that funds 100 calls. - **[7:30] Endpoint deployed and verified live** — https://www.youtube.com/watch?v=uzRGT62QUMY&t=450s Cloudflare worker comes up; the dummy x402 endpoint is live and verified. Buyer wallet is funded. Time elapsed so far: a few minutes. - **[9:00] Buyer pays + receives premium content** — https://www.youtube.com/watch?v=uzRGT62QUMY&t=540s Buyer agent calls /api/dummy via the Radius x402 skill: 402 challenge, payment, receipt of the secret payload ("the cake is a lie"). End-to-end agent purchase on Radius mainnet, deploy + buy in under five minutes. - **[10:30] Why the TPS target is real** — https://www.youtube.com/watch?v=uzRGT62QUMY&t=630s One transaction is the small case. Microtransactions hitting any meaningful adoption climb past hundreds of thousands per second into the millions. Sub-penny services need an underlying chain that can carry that load — that's the Radius bet. ### Stellar — Stellar Technical Briefing - Slug: `stellar-technical-briefing` - URL: https://v-sum.com/briefing/stellar-technical-briefing - Presenter: James Bachini - YouTube: https://www.youtube.com/watch?v=i1JUfrHg3_A - Tags: Stellar, x402, USDC, MCP, agentic-payments, Day Zero 06 Stellar's James Bachini ships a complete x402 server in 30 lines of code at Day Zero 06: a single Node.js file that gates a "secret number" behind a 0.01 USDC payment on Stellar Pubnet (Stellar's mainnet). The server uses the OpenZeppelin x402 facilitator as a relayer that sponsors transaction fees — agents move USDC at near-zero cost, a new paradigm for agentic systems transacting at scale. Important Stellar gotcha: a recipient wallet must establish a USDC trustline before it can receive payments; James recommends sending a 0.1 USDC test first to verify. On the buyer side, an open-source MCP server is registered into Codex via 'codex mcp add x42-stellar', backed by a hot wallet whose Stellar secret key lives in a .env variable. Codex loads the MCP, recognizes the x402 challenge on a fetch, signs and submits the payment, and returns the secret content — all visible end-to-end on a Stellar block explorer. Server + buyer + first paid microtransaction in under ten minutes. **Chapters:** - **[0:00] x402 in 30 lines on Stellar** — https://www.youtube.com/watch?v=i1JUfrHg3_A&t=0s James Bachini opens with the goal: a complete x402 server in 30 lines that lets agentic AI systems buy services on Stellar with USDC. Live, end-to-end, on Stellar Pubnet. - **[0:30] Server config — secret URL, 0.01 USDC price** — https://www.youtube.com/watch?v=i1JUfrHg3_A&t=30s The server runs locally and gates a "secret number" behind a 0.01 USDC payment. Default asset is USDC; network is Stellar Pubnet (Stellar's mainnet). - **[1:00] Stellar trustlines — USDC inbound gotcha** — https://www.youtube.com/watch?v=i1JUfrHg3_A&t=60s A wallet on Stellar must explicitly establish a trustline before it can receive USDC. Best practice: send a 0.1 USDC test from a known wallet first to confirm the trustline before opening the endpoint to live agent buyers. - **[1:30] OpenZeppelin facilitator — sponsored gas** — https://www.youtube.com/watch?v=i1JUfrHg3_A&t=90s The OpenZeppelin x402 facilitator acts as a relayer that sponsors transaction fees, so agents can move USDC at near-zero cost. A new paradigm: agents transacting at scale without paying gas themselves. - **[2:00] x402 middleware — refuse, then collect** — https://www.youtube.com/watch?v=i1JUfrHg3_A&t=120s How x402 works: the middleware refuses the initial unauthenticated request with HTTP 402, advertises payment terms, and only delivers the protected content after a valid payment is presented. - **[2:30] Run the server — node + open-source repo** — https://www.youtube.com/watch?v=i1JUfrHg3_A&t=150s James starts the server with a single node command. Code is open-source on GitHub. Browser hits localhost → 402 paywall page (which can be styled for human buyers; here it's machine-only). - **[3:30] Client side — MCP server for Codex** — https://www.youtube.com/watch?v=i1JUfrHg3_A&t=210s Buyer side uses MCP — the Anthropic-originated, now-cross-vendor standard for bolting tools into agent harnesses. James clones his open-source MCP server, runs npm install, and registers it with Codex via "codex mcp add x42-stellar". - **[4:30] Hot wallet via .env secret key** — https://www.youtube.com/watch?v=i1JUfrHg3_A&t=270s For agent payments to flow, the agent needs a key. The MCP server reads a Stellar secret key from a .env environment variable — convenient for demos, not the most secure for production. - **[5:30] Codex MCP inventory — x42-stellar ready** — https://www.youtube.com/watch?v=i1JUfrHg3_A&t=330s Codex loads the MCP inventory; the x42-stellar tool appears alongside other registered tools. The agent now has the capability to make x402 payments on Stellar autonomously. - **[6:00] Autonomous purchase — fetch the secret number** — https://www.youtube.com/watch?v=i1JUfrHg3_A&t=360s Codex is asked to fetch the protected URL using the x42-stellar MCP server. It receives a 402, sends a payment, and returns the secret number — without any per-call human approval. - **[6:30] Verify the payment on a Stellar block explorer** — https://www.youtube.com/watch?v=i1JUfrHg3_A&t=390s The transaction ID returned by the MCP shows up on a Stellar block explorer: 0.01 USDC moves from the agent's wallet to the server's payment address (the GA4D... account configured in the 30-line server). - **[7:00] Closing — full loop in under 10 minutes** — https://www.youtube.com/watch?v=i1JUfrHg3_A&t=420s End-to-end: 30-line x402 server + Codex MCP buyer agent + Stellar settlement, all live in under ten minutes. Clean foundation for x402 services on Stellar with USDC. ### The Stable Coin Company — Stable Coin Technical Briefing - Slug: `stable-coin-technical-briefing` - URL: https://v-sum.com/briefing/stable-coin-technical-briefing - Presenter: Jeff Milewski - Company: https://stablecoin.xyz - YouTube: https://www.youtube.com/watch?v=VzTmIEYbr_g - Tags: stablecoins, x402, agentic-payments, Stable Coin Company, Day Zero 06 The Stable Coin Company's Jeff Milewski demos agents.stablecoin.xyz at Day Zero 06 — an agent-payments platform built on Para wallet infrastructure and Brale webhooks that wraps any API endpoint as an x402-monetized resource on the Radius network. Seller side: a local Express CPI mock API gets x402 middleware (1/10¢ per call, SBC on Radius) auto-implemented by Claude Code from a generated integration prompt; the gated 402 response advertises the wallet address, asset, and price. Buyer side: a "Day Zero demo" agent on Para uses preconfigured policies (per-transaction limits, dollar caps, seller allow lists) and abstracts its private key behind an API key. The buyer wallet is funded by bridging SBC from Base to Radius via Brale-powered webhooks. A public GitHub template deployed on Pinata Cloud as an OpenWebUI instance auto-loads the SBC agent ID + API key, so the agent retrieves the gated CPI data through an x402 micro-payment with no further setup — closing the seller-to-buyer loop in a single live demo. **Chapters:** - **[0:00] Agent payments platform at agents.stablecoin.xyz** — https://www.youtube.com/watch?v=VzTmIEYbr_g&t=0s Jeff Milewski introduces The Stable Coin Company's agent-payments platform. Built on Para wallet infrastructure and Brale webhooks — the audience just saw both in earlier briefings — it ships preconfigured wallets for both buyer and seller agents. - **[0:30] Seller side — monetize a mock CPI API endpoint** — https://www.youtube.com/watch?v=VzTmIEYbr_g&t=30s The demo monetizes a mock CPI API: a local Express server with public time-series data is wrapped in x402 middleware so every call requires payment. - **[1:30] Configure the seller wallet on Radius SBC** — https://www.youtube.com/watch?v=VzTmIEYbr_g&t=90s On the platform: pick a custom wallet or the built-in Para wallet, set price (1/10 of a penny), select Radius as the network with SBC as the native stablecoin, and choose protocol (MPP or x402 — x402 here). - **[2:00] Generate API key and integration prompt** — https://www.youtube.com/watch?v=VzTmIEYbr_g&t=120s Naming the endpoint, generating an API key tied to the wallet (so analytics flow), and copying an x402 integration prompt sized for the chosen framework — Express in this case. - **[3:00] Claude Code implements the x402 middleware** — https://www.youtube.com/watch?v=VzTmIEYbr_g&t=180s Paste the prompt into Claude Code running against the Express repo. Claude plans, edits files, and wires x402 + middleware in a single pass. - **[4:00] Endpoint gated — 402 with full payment terms** — https://www.youtube.com/watch?v=VzTmIEYbr_g&t=240s Hit port 8000 → 402 response with x402 v2 payload: scheme exact, network radius, price 1/10¢, pay-to wallet address, asset SBC on Radius. ngrok exposes the URL publicly for the buyer side. - **[4:30] Buyer side — preconfigured Para wallet on Radius** — https://www.youtube.com/watch?v=VzTmIEYbr_g&t=270s Switch to the buyer side. Add a "day zero demo" agent on Para mainnet wallets, configure spending policies — dollar limit, per-transaction limit, seller allow lists. API key abstracts the private key away from the agent. - **[5:30] Bridge SBC from Base to Radius via Brale webhooks** — https://www.youtube.com/watch?v=VzTmIEYbr_g&t=330s Fund the buyer wallet by bridging SBC from Base to Radius. The bridge runs on Brale webhooks under the hood — a preview of the Brale integration that powers the platform. - **[7:00] Pinata-hosted OpenWebUI template wired to SBC** — https://www.youtube.com/watch?v=VzTmIEYbr_g&t=420s Open the public GitHub template "stablecoin wallet agent" and deploy it to Pinata Cloud as an OpenWebUI instance. The template auto-loads the SBC agent ID and API key, so the agent is x402-spend-ready immediately. - **[9:30] Agent retrieves the gated CPI data** — https://www.youtube.com/watch?v=VzTmIEYbr_g&t=570s Send the Pinata-hosted agent the ngrok URL and ask for a summary. It hits 402, pays via the SBC platform wallet, retrieves the CPI series, and returns a clean monthly + trend summary — closing the loop end-to-end. - **[10:30] Closing — a monetizable agent-native internet** — https://www.youtube.com/watch?v=VzTmIEYbr_g&t=630s Jeff frames the platform as one piece of a broader move toward an internet where gated content and services are monetizable directly through agent-driven micro-payments tied to the actual value being created. ### Brale — Brale Technical Briefing - Slug: `brale-technical-briefing` - URL: https://v-sum.com/briefing/brale-technical-briefing - Presenter: Chase Merlin - Company: https://brale.xyz - YouTube: https://www.youtube.com/watch?v=4R-xQ0TwCig - Tags: stablecoins, webhooks, Brale, Day Zero 06 Brale's Chase Merlin walks through Brale's new webhook product at Day Zero 06 — webhooks that publish signed lifecycle events as transfers settle, eliminating the need for clients to poll for status. The reference neobank app, built on the Brale stablecoin operating system, receives a transfer-completion event in roughly 18 seconds after a Solana transfer, then again on Spark, with signature verification, dedupe, and live balance + activity updates baked in. A single flexible transfer-request endpoint handles on-chain, off-chain, mint, RTP off-ramp, and cross-chain flows — and webhooks fire on the same event model for every variant. Closing pointer to a same-day blog post measuring a ~20% latency reduction versus polling-based integrations. **Chapters:** - **[0:00] Webhooks for real-time stablecoin events — kill the polling loop** — https://www.youtube.com/watch?v=4R-xQ0TwCig&t=0s Brale's Chase Merlin opens with the thesis: no more polling. A reference neobank app, built on Brale's API, will receive signed webhook events as transfers settle on-chain — driving live customer experiences without aggressive client-side polling. - **[0:30] Brale stack — issuance, custodial balances, on/off ramps, fiat rails** — https://www.youtube.com/watch?v=4R-xQ0TwCig&t=30s Quick tour of Brale's stablecoin operating system: SBC issuance (or your own stablecoin), custodial balances across chains starting with Solana, on/off ramps on 20+ chains, and fiat rails on the same primitives. - **[1:00] Three reasons webhooks matter** — https://www.youtube.com/watch?v=4R-xQ0TwCig&t=60s User experience (live balances and activity), reconciliation (events keep your system synced with the chain), and complexity reduction (polling adds edge cases and load that webhooks eliminate). - **[1:30] Live Solana transfer kicks off** — https://www.youtube.com/watch?v=4R-xQ0TwCig&t=90s A vendor-payout-shaped transfer fires on Solana. The on-chain transaction settles, Brale waits for finalization, then publishes a completion event — no aggressive polling required on the client side. - **[2:00] Webhook received in ~18s — signature, dedupe, balance update** — https://www.youtube.com/watch?v=4R-xQ0TwCig&t=120s The completion webhook arrives in roughly 18 seconds. The reference app verifies the signature, deduplicates, runs eligibility checks, then updates balances and activity in real time. Snappy settlement UX with zero polling. - **[2:30] Single flexible transfer-request endpoint** — https://www.youtube.com/watch?v=4R-xQ0TwCig&t=150s All transfer flavors run through one endpoint with flexible value-type and transfer-type fields — on-chain, off-chain, conversions to wire/RTP, and cross-chain. Webhooks track the lifecycle of every transfer-request. - **[3:30] Spark transfer demo — Brale rides fast underlying networks** — https://www.youtube.com/watch?v=4R-xQ0TwCig&t=210s A Spark transfer fires and settles via webhook. Networks like Spark and Radius (referencing Tyler's prior demo) are already fast — Brale layers webhooks on top instead of adding polling delay, keeping events near-real-time. - **[4:00] Downstream consumers — treasury, APIs, agents** — https://www.youtube.com/watch?v=4R-xQ0TwCig&t=240s Webhooks notify treasury teams, downstream APIs, and agents the moment transfers complete. Far more robust than polling for any system reacting to settlement events. Works across mints and RTP off-ramps too — the transfer endpoint is the single source of truth. - **[4:30] Reference app, quickstart, ngrok in Brock** — https://www.youtube.com/watch?v=4R-xQ0TwCig&t=270s The reference app and quickstart guide ship in the docs. Chase runs the demo locally with ngrok in Brock — same code path you'd ship to production. - **[5:00] New webhooks blog post — ~20% latency reduction** — https://www.youtube.com/watch?v=4R-xQ0TwCig&t=300s Closing pointer to a same-day Brale blog post on the motivation behind webhooks, including a measured ~20% latency reduction versus polling-based integrations. --- For structured queries against this archive, use the MCP server at https://v-sum.com/mcp or the read-only HTTP API at https://api.v-sum.com (see https://api.v-sum.com/spec.json). For visible pages, start at https://v-sum.com/demos (briefings), https://v-sum.com/events, https://v-sum.com/interviews.