Skip to main content
This page describes what we watch, not what we expect. We do not publish targets or forecasts, because a figure given before there is evidence behind it is only a hope. What we can commit to is how we measure, and how we report what we find.

The borrower journey

Each stage is a person doing something they were not doing before.
1

Hears about Writz

Through a conversation, a community or a partner. We note where they came from.
2

Understands it

They can say what Writz does and what happens if the price falls.
3

Tries it

They complete a Bitcoin lock and a borrow, first on testnet.
4

Finishes it

They repay the loan and their Bitcoin is released. This is the moment the promise is proven to them.
5

Comes back

They take another loan, or bring someone with them.

The lender journey

1

Hears about Writz

Through the Stellar community, or a product they already use.
2

Understands the risk

They can say where interest comes from and what could cause a loss.
3

Supplies USDC

First test USDC, then real USDC after launch.
4

Stays

They keep their supply in the pool through a full cycle of borrowing, and they withdraw when they choose to.

The builder journey

1

Discovers the tools

Through the docs, an event or another builder.
2

Makes a first call

Their code calls a Writz contract or the proof API.
3

Ships

They have something that real people can use.
4

Keeps it running

It is still in use after the event or bounty has ended.

The institution journey

1

First conversation

We understand their mandate and what they would need.
2

Technical evaluation

Their team reviews the design and the security model.
3

Written agreement

A signed document with a defined scope and next step.
4

Pilot

A test on testnet, with no real funds.
5

Live use

Limited use on mainnet, within the protocol’s limits.

One constraint at a time

At every point we name the single stage where most people drop out, and that stage is where the team’s effort goes. If people do not finish a loan, more reach only sends more people to the same problem. This keeps a small team from working on everything at once.

Rules for every figure we report

  • On-chain figures can be checked. Wallets, transactions and loans come from public contract data, so anyone can verify them.
  • Testnet is labelled as testnet. Activity with test coins shows that the system works. It is not demand for real loans.
  • Wallets are not people. We report wallets and accounts, and we say so.
  • Agreements are stated as they are. We say what was signed and at what stage, and we name an organization only with its consent.
  • Interviews are a signal, not a statistic. We state how many people we spoke with, and we do not turn a few conversations into a percentage of the market.
  • Dates come with numbers. Any figure we publish states when it was measured.
  • Interest is described, never promised. We explain how the rate works and do not forecast returns.

What would change this plan

This plan will change as we learn. A different first customer, a better channel or a lender design that does not work would each rewrite part of this section, and we will update it when that happens. The pages stay public, so that people can hold us to what we said and see why it changed.