Zero Point Zero
Position 0.0: The Garage on Emerson Street
The idea arrived at 3:14 a.m. on a Tuesday in March. Daniel Kao was twenty-nine years old, sitting on a folding chair in a Palo Alto garage that still smelled of the previous tenant's motor oil, staring at a Silicon Graphics O2 workstation he'd bought used from a liquidated startup on Page Mill Road. The screen cast blue light across his face and across the whiteboard behind him, where he'd drawn circles and arrows connecting the words DONORS, NONPROFITS, MATCHING, TRANSPARENCY, and TRUST in dry-erase marker that was running low on ink.
He wasn't thinking about money. He was thinking about the food bank in East Palo Alto where his mother had volunteered every Saturday morning for fourteen years, and about how the director there spent forty percent of her time filling out grant applications and donor reports instead of feeding people. He was thinking about the inefficiency of compassion, which seemed to him the most tragic inefficiency in the world. He was thinking that if you could build a platform that connected every dollar to every meal, every donor to every recipient, every intention to every outcome — if you could make charity as transparent and frictionless as a stock trade — you could unlock something enormous.
He called it CommonGround. The name came to him fully formed, as names sometimes do at 3:14 a.m. when the rational mind has clocked out and something older and more intuitive takes the keyboard.
The matching algorithm was the heart of it. Donors would pledge funds; nonprofits would post projects; CommonGround would algorithmically match pledges to projects based on donor preferences, geographic proximity, impact metrics, and a dozen other variables Daniel had dreamed up during those late-night sessions. The algorithm was beautiful. Elegant. It sorted and weighted and optimized, and in Daniel's early simulations it routed ninety-four percent of funds to their theoretically optimal destinations.
What he didn't notice then — what he couldn't have noticed, what no one noticed until it was far too late — was the six percent that didn't route anywhere. The gap. The ghost in the machine. A rounding error in the weighting function that, under very specific conditions, would redirect matched funds to an interstitial account labeled ADMINISTRATIVE RESERVE. The account was supposed to collect platform operating fees. Instead, under the right sequence of inputs, it became a siphon.
But that was years away. At 3:14 a.m., Daniel Kao was still at position 0.0: pure mission. He believed he was building a cathedral.
Position 0.14: Sand Hill Road, First Meeting
Roger McAllister was a partner at Kleiner Perkins Caufield & Byers, and he wore his venture capital uniform the way a general wears medals: chinos from the Menlo Park Brooks Brothers, a blue oxford shirt with the sleeves rolled precisely twice, a TAG Heuer dive watch he'd bought after the Netscape IPO. He listened to Daniel's pitch for eleven minutes before interrupting.
"Let me stop you," Roger said, tapping his PalmPilot with the stylus. Daniel noticed the gesture and filed it away as a data point: PalmPilot stylus tap means the VC is about to say something he thinks is profound. "You're telling me a nonprofit story. I don't invest in nonprofit stories. What's the revenue model?"
Daniel had prepared for this. He'd rehearsed in the garage, talking to the whiteboard. "Two percent transaction fee on matched donations. At scale, with the nonprofit sector moving four hundred billion dollars annually in the United States alone—"
"That's a for-profit model wrapped in a nonprofit mission." Roger leaned back. The leather chair made a sound like money. "I like it. But I need to know you can execute the for-profit side. The mission is the story you tell the press. The revenue is the story you tell me. Can you tell me that story?"
Daniel could. He told Roger about conversion funnels and customer acquisition costs and the compounding effects of donor-network growth. He used words like "monetizable empathy" and "philanthropic liquidity." He watched Roger's eyes and adjusted his pitch in real time, dialing up the business language, dialing down the cathedral talk. By the end of the meeting, Roger had committed to a two-million-dollar seed round.
Driving back to Palo Alto in his 1992 Honda Civic with the passenger window that wouldn't roll all the way up, Daniel felt something shift. He had told the revenue story so well that he'd almost believed it himself. The mission was still there — he could feel it, a warm coal in his chest — but it was now wrapped in layers of spreadsheet projections and term-sheet language.
He was at 0.14 on the vector. Still mostly mission. But the numbers had begun.
Position 0.31: Beta, and the Ghost
The vulnerability revealed itself on a Thursday in October, six weeks before the Series B close.
CommonGround was in closed beta, running on two Sun Microsystems servers in a colocation facility off Highway 101. Thirty-two nonprofits had been onboarded as test partners. Four hundred donors were in the beta pool. The matching algorithm was processing real money — small amounts, a few thousand dollars total — but real money, real routing.
Daniel was running a diagnostic query when he saw it: a $340 pledge to a literacy nonprofit in Oakland had been matched and routed, but $12.47 of the matched amount had gone to ADMINISTRATIVE RESERVE instead of the nonprofit. That wasn't supposed to happen. The platform fee was supposed to come from the transaction, not the matched funds.
He traced the error through seven hundred lines of Java code, his fingers moving across the keyboard in the rhythm of a man who had written every line himself and knew the architecture by heart. At 11:42 p.m., he found it: a floating-point rounding error in the weighting function. Under certain conditions — specifically, when a donor's stated preferences overlapped with three or more nonprofit categories in a weighted intersection of less than 0.015 — the algorithm would treat the matched amount as residual and route it to the reserve account.
The bug was subtle. It affected less than four percent of transactions. But Daniel, doing the math in his head with the speed of a man who had scored 800 on the math SAT, realized something chilling: if the platform scaled to the projected forty-seven million dollars in monthly transaction volume, the bug would siphon approximately one point eight million dollars per month into the administrative reserve.
One point eight million dollars per month. Twenty-two million per year. Money that donors believed was going to food banks and literacy programs and homeless shelters.
He sat in the server room until 4 a.m., the hum of the Sun machines filling his ears like the sound of the ocean. He could fix the bug. It would take maybe forty hours of work — a rewrite of the weighting function, regression testing, a database migration. But forty hours of work meant a minimum two-week delay in the public launch. And the public launch metrics were the foundation of the Series B presentation. Kleiner Perkins wanted to see user growth, transaction volume, nonprofit onboarding numbers. A two-week delay would push the launch past the Series B close date. Without the launch metrics, the term sheet was dead.
Daniel thought about the food bank in East Palo Alto. He thought about his mother's hands, sorting cans of soup. He thought about forty-seven million dollars in monthly volume and one point eight million in siphoned funds.
At 4:17 a.m., he closed the diagnostic window. He tagged the bug report as LOW PRIORITY — COSMETIC and pushed the launch code to production.
He was at 0.31 on the vector. The mission was still visible in the rearview mirror, but it was getting smaller.
Position 0.52: The Term Sheet
The Kleiner Perkins offices on Sand Hill Road had a courtyard with a koi pond and a single bonsai tree that cost more than Daniel's Honda Civic. He sat in a conference room with Roger McAllister and two other partners whose names he kept forgetting, and he watched Roger slide a document across the polished maple table.
"Series B," Roger said. "Twenty-two million at a one-hundred-eighty-million post-money valuation. You'll own thirty-one percent after dilution. Congratulations, Daniel. You're a paper millionaire twelve times over."
Daniel looked at the numbers on the page. Twelve million in stock, on paper. His parents had immigrated from Taipei in 1977 with eight hundred dollars and two suitcases. His father had worked as a janitor at Stanford Hospital for twenty-three years. Twelve million dollars.
"You'll need to hit the growth targets," Roger continued. "Monthly active donors doubling every quarter. Nonprofit onboarding at one hundred per month by Q3. Transaction volume north of forty million by year end. The standard stuff."
The standard stuff. Daniel nodded. He didn't mention the bug. He didn't mention the $12.47 that had gone missing in the beta test, or the extrapolation to one point eight million per month. He signed the term sheet with a Montblanc pen that Roger handed him, and when the pen scratched across the paper, it made a sound like a door closing.
That night, he drove to Fry's Electronics on Arques Avenue and bought a new monitor — a twenty-one-inch ViewSonic CRT that weighed forty-eight pounds — using his corporate AmEx. He told himself it was a business expense. He told himself he deserved it. He told himself that the bug was minor, that he'd fix it after the launch settled down, that the good CommonGround would do — the billions in efficiently routed charity, the transformed nonprofit sector, the cathedral — would outweigh forty hours of technical debt.
He was at 0.52 on the vector. The midpoint. The fulcrum. From here, the numbers tilted toward profit.
Position 0.71: The Launch Party
They held the launch party at the Stanford Park Hotel, because Roger said it was important to project success, and success meant valet parking and passed hors d'oeuvres and an open bar with top-shelf liquor. Daniel wore a blue suit with no tie, which was the Silicon Valley formal uniform in 1999 — dressed up enough for the investors, dressed down enough for the engineers. He stood near the bar and watched the room fill with people who wanted to touch the thing he had built.
A reporter from the San Jose Mercury News asked him about the mission. "What drew you to the nonprofit space?" she asked, holding a microcassette recorder.
Daniel gave her the cathedral answer. He talked about his mother, the food bank, the inefficiency of compassion. He used the word "democratizing" three times and the word "transparency" six times. The reporter smiled and wrote things down, and Daniel felt the warm coal in his chest glow brighter.
Then Roger appeared at his elbow and steered him toward a man in a gray suit. "Daniel, this is Howard Lindstrom from the Omidyar Network. Howard's interested in the revenue architecture."
Daniel gave Howard the revenue answer. He talked about transaction fees and scale economics and the compounding mathematics of donor networks. He used the word "monetization" without flinching. Howard nodded and asked about quarterly projections, and Daniel gave him numbers that were slightly higher than the internal forecasts but not so high as to be unbelievable.
He moved between the two conversations — mission and revenue, revenue and mission — the way a dolphin moves between water and air, breaching one world and then the other, never staying in either long enough to drown. By the end of the night, he had talked to seventeen people and given seventeen different versions of himself, each one calibrated to the listener.
The bug was still there. The $12.47 had become $340,000 in siphoned funds during the first month of public operation. Daniel had checked the dashboard that morning — a clean HTML interface rendered in Netscape Navigator 4.7 — and watched the ADMINISTRATIVE RESERVE line item climb past six figures. He had closed the browser window and changed into his suit.
He was at 0.71 on the vector. The cathedral was still visible, but it was now a distant landmark on the horizon, something you point to in interviews while your hands are busy counting money.
Position 0.86: The Dashboard, 2:47 a.m.
The numbers had gone wrong three days earlier, and Daniel had been watching them ever since.
He was in the office — a real office now, on University Avenue, with glass walls and Aeron chairs and a Nespresso machine that made a sound like a small animal being stepped on. The office was empty except for him and the cleaning crew, who vacuumed around his feet without making eye contact. He was staring at the admin dashboard, which now showed $18.7 million in the ADMINISTRATIVE RESERVE account.
Someone had found the bug. Not fixed it — weaponized it.
The pattern was unmistakable: a cluster of donor accounts, all created within a twenty-four-hour window, all pledging to nonprofits in overlapping categories with weighted intersection values below 0.015. The accounts were feeding the siphon deliberately, systematically. In seventy-two hours, they had routed $18.7 million through the exploit. At the current rate, the total would reach $47 million within two weeks.
Daniel traced the accounts through the database. Shell entities. Offshore registrations. The pattern was sophisticated — whoever was behind this understood not just the vulnerability but the exact mathematical conditions required to trigger it. They had reverse-engineered his algorithm. They had studied his bug.
The phone rang. It was the night security guard at the front desk. "Mr. Kao? There's a reporter here. Lucy Black from the Chronicle. She says it's urgent."
Daniel told the guard to send her away. He hung up the phone and looked at the dashboard. Eighteen point seven million dollars in the reserve account. The money was technically still there — the exploit had moved it into the reserve, but the attackers hadn't yet withdrawn it. He could freeze the account. He could report the exploit. He could kill the matching algorithm and revert to manual routing.
But any of those actions would generate a paper trail. A paper trail would generate questions. Questions would generate an investigation. An investigation would reveal that the bug had been tagged LOW PRIORITY — COSMETIC nine months ago, that Daniel had known about it before the Series B, that he had signed the Kleiner Perkins term sheet with the bug still in production, that he had told seventeen people seventeen different versions of CommonGround and none of them had included the truth about the siphon.
If he let the exploit run, the attackers would eventually drain the reserve and disappear. The losses could be attributed to a security breach — an external attack, no one's fault, these things happen. The board would demand better security. Daniel would promise to deliver it. The story would be a one-day item in the Mercury News and then everyone would move on.
If he stopped the exploit now, the story would be about him.
He closed the dashboard. He opened a new Netscape window and typed a URL into the address bar: www.escapeartist.com, a travel site that sold discount flights to destinations with no extradition treaties. He stared at the screen for a long time. The Nespresso machine cycled through its automatic cleaning routine, making its small-animal noise.
He was at 0.86 on the vector. The mission was a dot on the horizon. The numbers had filled the entire frame.
Position 0.97: The Confession
Lucy Black found him anyway.
She didn't come through the front desk this time. She waited outside the University Avenue office at 7 a.m., holding a paper cup of Peet's Coffee and wearing the expression of a woman who had already filed her story and just needed one more quote to bury someone.
"Mr. Kao," she said, falling into step beside him as he walked toward the entrance. "I've been looking at CommonGround's routing logs. Would you like to explain why eighteen million dollars in donor funds has been routed to an administrative account that doesn't appear in any of your public financials?"
Daniel stopped walking. The January morning was cold in the way that Palo Alto mornings are cold — fifty degrees and damp, a cold that surprises people who moved here expecting eternal California summer. He looked at Lucy Black and saw that she already knew. Not all of it, maybe, but enough.
"Let's talk inside," he said.
They sat in the conference room with the glass walls, and Lucy Black asked questions for forty-five minutes. Daniel answered some of them. On others, he said "no comment" in a voice that was a reasonable imitation of a man who had nothing to hide. Lucy wrote everything down in a spiral notebook with a blue Bic pen, and when she left, she said "I'm running this Sunday" in the tone of someone who wasn't asking for permission.
Daniel sat alone in the conference room. Through the glass walls, he could see the CommonGround office coming to life — engineers arriving with bike helmets and backpacks, the office manager refilling the snack bins with Trader Joe's trail mix, the marketing team gathering for their morning standup around a whiteboard covered in growth-hacking Post-it notes. None of them knew yet. They would know on Sunday.
He opened his laptop. He opened a text editor — BBEdit, the version that shipped on a CD-ROM — and began to type.
"My name is Daniel Kao, and I am the founder and CEO of CommonGround. In October of last year, during the beta testing period, I discovered a vulnerability in the platform's donation-matching algorithm that, under specific conditions, would redirect matched funds to an administrative reserve account. I classified this vulnerability as low priority and authorized the production launch without remediation. At the time of this writing, approximately $47 million in donor funds have been routed through this vulnerability, of which an estimated $31 million has been extracted by malicious actors who independently discovered the exploit."
He stopped typing. The words on the screen looked like they had been written by someone else — someone who had made a series of choices that Daniel Kao would never make. But they were his words. They were his choices. Each one had seemed small at the time: a bug report marked LOW PRIORITY, a term sheet signed, a launch party attended, a dashboard closed, a question deflected. Each small choice had moved him fractionally along the vector — 0.31, 0.52, 0.71, 0.86 — until he arrived here, at 0.97, where the mission was no longer even a memory and the numbers had consumed everything.
He saved the file as confession.txt on his desktop. He did not send it. Not yet.
Position 1.0: The Bourbon
His apartment was a one-bedroom on Alma Street, walking distance from the Caltrain station. He had leased it two years ago, before the Series B, before the term sheet, before the numbers. It had a balcony that overlooked the train tracks and a kitchen with a gas stove he had never used. He kept his liquor in the cabinet above the refrigerator: a bottle of Blanton's bourbon that Roger had given him as a congratulations gift after the Series B close.
He took down the bottle and a glass. He poured two fingers. He sat on the floor with his back against the sofa, because the sofa was too comfortable and he didn't feel he deserved comfort.
Through the sliding glass door, he could see the sky. It was a clear January night, and the sodium lights of Palo Alto turned the darkness orange. Somewhere above that orange glow were the tech campuses and the venture capital offices and the startup garages that had become startup offices that had become startup headquarters. Somewhere above that were the satellites and the orbital mirrors and all the other monuments to human ingenuity that had been built with the same mixture of vision and blindness that had built CommonGround.
The bourbon was warm in his throat. He thought about the email he hadn't sent — confession.txt, still sitting on his desktop, still unsent. He thought about Lucy Black's story, running on Sunday, and the board meeting on Monday, and the SEC investigation that would follow, and the class-action lawsuit from the donors whose money had been siphoned, and the nonprofits who had counted on matching funds that never arrived, and his mother, who was seventy-two and still volunteered at the food bank in East Palo Alto, and who would read about her son in the newspaper.
He thought about the moment at 3:14 a.m. in the garage on Emerson Street, when the idea had arrived fully formed and beautiful and pure. Position 0.0. He had been so sure, then. He had believed the mission was strong enough to carry him across any distance, through any compromise, past any temptation. He hadn't understood that the mission and the numbers pull in opposite directions, and that every step toward one is a step away from the other. He hadn't understood that the vector has no neutral position — you are always moving, always sliding, always choosing.
The bourbon bottle was half empty now. He didn't remember drinking that much. The sky through the sliding glass door was still orange, but it seemed to Daniel that the orange was getting brighter, spreading like a fire, consuming the darkness one degree at a time. He thought about the Sunfire mirrors — had there been a story about orbital mirrors? Something in Wired magazine? — and about what happens when you build something powerful and fragile and then let it slip out of your control.
He reached for the bottle and poured another glass. The computer on his desk was still on, the screen saver cycling through flying toasters. Confession.txt was still there, still unsent. In the morning, he would have to decide: send the confession, or let Lucy Black's story run without his side of it, or call a lawyer, or get on a plane to a country with no extradition treaty, or do nothing at all and let the vector carry him to wherever 1.0 led.
But morning was hours away. For now, there was only the bourbon and the orange sky and the knowledge that he had built something beautiful and then sold it, piece by piece, compromise by compromise, until there was nothing left but the numbers ticking upward on a dashboard he could no longer bear to look at.
He was at 1.0. Pure profit. Pure consequence. He had everything he had ever wanted, measured in dollars and valuation and term-sheet multiples, and he had nothing at all.
Based on the pending patent application document (202610351844.3), creationstamp.com has calculated the tensor feature encoding of this article:
OTMES-v2-UNKNOWN
- Art
- Causes
- Crafts
- Dance
- Drinks
- Film
- Fitness
- Food
- Giochi
- Gardening
- Health
- Home
- Literature
- Music
- Networking
- Altre informazioni
- Party
- Religion
- Shopping
- Sports
- Theater
- Wellness