V-Sum Eighteen
Tuesday, January 10, 2023
Technical Briefings
Alvaro Morales
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.
Nick Hynes
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.