# An Introduction to an Introduction

*The awkward business of selling legitimacy to the technology that could replace you.*

By [zoz.eth](https://paragraph.com/@0xzoz) · 2026-10-02

---

  

By the time we finally got on the call, several weeks had passed, the people had changed, and somebody had taken over coordination of a relationship that had yet to begin. The main representative admitted he had no idea why we were there.

We explained that they had contacted us.

  

Recently, I had the pleasure of speaking to representatives of UNDP.

An intern had made the connection. We ran a grants programme; they had an accelerator for projects ready to deploy. It sounded reasonable, and the name on the email carried weight(it was LinkedIn - after all). Someone sent a portfolio. Someone else suggested a meeting. My colleague couldn’t make the time, so I put it in my calendar.

The person who suggested the meeting declined the invitatio. Sometimes I wonder if its the dead interet theory or the disconnect between irl and online to think that something like that is ok socially. Two other people accepted. Then someone wrote to explain that she and a colleague would be taking over coordination and getting up to speed on the earlier conversations.

  

We had not yet had a conversation.....

  

At this stage I thought I might be getting set up for a North Korean hacking attempt. Imagining a please download our chat platform as our teams doesnt work message while looking at some seemingly confused AI representations of suits. My colleague and I were trying to establish who was coming to a call that was then cancelled. More dates followed. Someone was away. Something conflicted. We were looking more than a month beyond the first approach.

We kept trying. Important institution. Doors might open. I was god damn participating in the same thing I am about to complain about.

When we eventually made it, two men joined. It was late in Europe, so one was out and listening in. Once we had established who had contacted whom, the main representative gave us a monologue. Great, because I had nothing to say, they started this interaction, I kinda didnt know why were here either. It was well versed, only the kind of description of an org that had been done over and over and over again.

There were teams across offices that spoke with teams across offices across continents and relationships with some of the world’s largest organisations(no names but GOVERNMENTS AND POLITICAL ORGS - The ones that make decisions, they assured us). An extensive blockchain and emerging ventures operation. Then we got to the accelerator, the reason for the call, which we _fortunately had the opportunity_ and could sponsor for the small fee of fifty thousand benjamins.

As I understood the proposition, we would bring the money and access to teams we had already sourced. They would bring the accelerator and the relationships. Something, something, important people, doors opening. I understood our contribution considerably better than I understood what would happen to the projects. Ideally what we would have been looking for is the sourcing aspect. The one thing about the industry is that $$$ are not the scarce resource, talent is. More appropriately, individuals or teams who deeply understand the important time we are in and the tools that exist to build the tomorrow we long for.

We described our programme. This was fairly brief. We assess projects, fund work and follow what happens. The decisions can be difficult. The explanation does not require a tour of the planet.

It turned out they had already been speaking with several organisations in our ecosystem. Some conversations had lasted years, through employees who had come and gone. Then, as it became clear we were unlikely to be the golden goose, we heard about the calibre of the projects they would be _willing_ to consider. An air of superiority entered the room.

We could supply the funding and the teams, then find out whether our teams were good enough to be introduced to somebody else. After the effort required to establish why we were on the call, this was quite something.

My colleague, who comes from a nonprofit background, appreciated the conversation. These relationships were more familiar. I arrived in this work through luck, resourcefulness and enough decisions going the right way. I was trying to strip the language down to what we would actually be buying.

What I could identify was permission to be taken seriously by the next person.

The approach looked backwards. Product-market fit changes who wants a meeting with whom. People keep using the thing because it solves a problem. A customer has a reason to pay, a distributor has a reason to sell it, and an institution has a reason to put its name beside it. You still have selling to do, but now you have something to negotiate with. Buy the name first and you still have to find out whether anybody wants the product.

For public goods, the people using it and the people funding it might be different people. Somebody still needs to want the result enough to keep it going - R.I.P public goods of yester year mimicking beurocratic orgs like the one we are discussing. Another organisation agreeing that the idea sounds important does not get you there. In fact, it depletes resources so you never see PMF.

The pitch, as it reached us, put prestige before that discovery. Pay for the relationship, put the projects through the process, and hope the relationships produce the demand. We would finance the uncertainty while the accelerator could collect revenue from arranging it.

Perhaps it understood its market perfectly. An ecosystem with money, projects and a desire for recognition is a perfectly serviceable customer. The builders and the people they intend to help can remain somewhere further down the chain.

The fifty thousand was only the visible part of the cost.

Behind the projects were people who had already spent time building them. Behind our ability to bring those projects were applications, reviews, funding decisions and follow-up. The proposition arrived after all that work and asked us to contribute it to another process, alongside the money.

Then there were the years of conversations they described having across our ecosystem. Each organisation would see its own handful of calls. A new employee could inherit the relationship, ask for the background and begin another round. The collective bill would be spread across budgets and calendars, with no single person necessarily seeing it.

The fifty thousand was the part that would make it onto an invoice. Everyone else’s time was scattered across the ecosystem. Six people sitting through eight one-hour calls, with as much time spent preparing and following up, have used 96 working hours. At an assumed $100 an hour, that is $9,600; ten parallel versions cost $96,000. Those are hypothetical inputs, not their accounts. The history they described ran across years.

Somewhere in the ecosystem, a builder is trying to stretch a small grant long enough to find users. Their time has an obvious limit. A promising institutional relationship seems able to remain promising for a remarkable length of time.

UNDP’s own report on its 2025 accelerator describes more than 120 external partners, 46 solutions ready for piloting or implementation, and twelve entering real-world testing. I would like to see the whole bill for that. Though we never will, much like the foundations that run a blockchain.

Stellar and Cardano fit comfortably into this picture. UNDP announced the Stellar Development Foundation as an accelerator partner in August 2025 and identifies Cardano treasury funding, through Project Catalyst, as a source of support.

Look around that funding machinery and you can see the appetite for the same transaction. A separate Catalyst proposal requested 60,000 ADA for a summit offering Cardano projects access to UN and NGO decision-makers. Its success metrics included at least a hundred senior ecosystem stakeholders in “Random Matchmaking.” That proposal was not approved. The offer itself is still revealing: assemble important people, put the ecosystem in front of them, count the resulting activity.

There is a market for being near somebody who might become a customer.

Stellar’s funding model is explicit. Its foundation says it sells XLM on public exchanges and through direct sales to meet operating expenses and support its mandate, which includes promoting and developing the ecosystem. Token inventory can be turned into money to fund the organisation and its work.

Ripple offers a particularly clear historical example of how institutional adoption can be purchased. In 2017, it announced a **$300 million** RippleNet accelerator funded from its XRP holdings. Institutions meeting integration and volume milestones could receive rebates covering 50 to 300 per cent of integration fees and first-year licence fees. Ripple also offered to match eligible spending on marketing its products. That was a separate Ripple programme, not the UNDP accelerator.

Up to three times the specified costs. When an impressive institution adopts something on those terms, I would like to know how much it wants the product once the incentive runs out.

Subsidies can get a useful network started. The revealing part comes when they stop. Until then, a partnership announcement leaves a fairly consequential question unanswered: which side was the customer?

This is why the machinery around Stellar, Cardano and Ripple makes me so sceptical. The blockchains can function while the organisations around them become extremely effective at turning expectations into spending. A treasury finances a relationship. The relationship produces a prestigious association. The association becomes evidence in the story about the ecosystem’s future. Meanwhile, the people arranging it have already been paid.

I see an extraction mechanism in that loop whenever the money reliably reaches the people selling access while the promised usefulness is carried into the next funding round. Token-funded development can produce valuable infrastructure. It can also support an elaborate business of continually announcing that valuable infrastructure is about to become important.

The badge is a very convenient product for that business. The institution gets funding and relevance. The ecosystem gets legitimacy. Neither has to wait for an ordinary user to come back a second time before announcing the partnership.

That is the part I wish had sat at the centre of the call. Which teams already have users? What are those users doing? Where is demand being held back by something we could actually fix? If a particular institutional relationship solves that problem, pay for the work it takes to establish it. There should be a connection between the door and the thing on the other side of it.

I asked these... with vague answers that didnt answer the questions.

Instead, I came away with a much clearer understanding of the price of admission than the demand for the projects.

The people involved seemed sincere. I don’t think sincerity fixes the incentives. An organisation has to fund its continued existence now. The social value it hopes to create may arrive much later. Finding a sponsor keeps people employed and the programme running. After enough repetitions, the work of preserving the programme can become almost indistinguishable from its mission.

  

Yet this is where I see the Trojan horse.

  

The institution thinks it is lending credibility to a strange new technology. The ecosystem accepts the ceremony because the institution has access to governments, budgets and people who won’t take a meeting without its name on the invitation. Everyone thinks they understand their role. A sponsor pays. A programme convenes. A pilot gets announced.

But realistically, they are a small piece in helping normalize the technology that superseeds them.

Eventually it brings the uncomfortable questions in a world where an impressive name can stand in for an answer. The intivtive talk within my mind gets asked and there is no where to hide when an alternative exists

UNDP says 82 per cent of participating country offices were getting their first direct experience with blockchain or similar technologies. That exposure matters. Some staff will encounter real problems, and some builders will reach people they could never have reached alone. Somewhere inside all that ceremony, the technology may cross from institutional colonisation into infection: replicating through actual use until the host begins reorganising itself around it.

Once people need the tool, it stops behaving like a pilot. They keep using it. They ask for changes. Another office copies the first. The builder no longer needs an accelerator to explain who might care, because the users are doing the introductions themselves.

That is the leap from exposure to infection. The technology begins replicating through use, and the host starts reorganising around it.

This does not make every institution obsolete. It does make every part of the institution prove why it is there. The meeting that produced another meeting. The introduction to the person who makes introductions. The fee attached to the logo. The actual work, still being done somewhere else.

The institution believes it is hosting a pilot. In reality, it may be culturing a system that makes much of its own ceremony unnecessary.

  

That is the Trojan horse.

  

Blockchain enters wearing a lanyard, carrying a sponsor’s cheque and asking permission to sit at the serious table. The institution welcomes it because it looks modern. But once the technology becomes useful enough to spread without the badge, the uncomfortable questions arrive with it.

  

Why did this require six intermediaries?

  

Why did the introduction cost more than the work?

  

What, exactly, was the programme doing that the users and builders could not do directly?

  

I still cannot see why we should pay fifty thousand dollars for the privilege of entering that chain. But I can see why institutions keep inviting the technology inside.

  

They think it will make their programmes look current.

  

They may be introducing the thing that finally makes their programmes legible.

---

*Originally published on [zoz.eth](https://paragraph.com/@0xzoz/an-introduction-to-an-introduction)*
