All field notes

Leadership · Retrospective

Deciding to stop our own chain's block rewards: the Trivechain 3.0 plan

A faucet turned off with a blue handle above a glass block, one last bead under the spout.
Concept illustration · AI-generated

On 24 March I published Trivechain 3.0 on our Medium, in English and Chinese, as lead developer of Trivechain Protocol. It sets out a six-point plan; the four parts that matter here are:

  • move TRVC to Binance Smart Chain;
  • fork the current chain into Trivechain Legacy, with a block reward of zero;
  • open staking contracts on BSC for TRVC-BNB liquidity, TRVC-BUSD liquidity and single-asset TRVC;
  • begin development of T3, an EVM-compatible proof-of-stake protocol, after the migration.

It also records TRVC's exchange listings from 2018 to 2020.

This post is about the decision inside the fork, because it is the one that cannot be walked back.

What a block reward pays for

Every Trivechain block creates new TRVC. The subsidy is split between the miner, the masternode paid for that block, and the governance budget that funds proposals. It is how the chain pays for its own security and upkeep, and every holder pays for it through dilution.

That bargain makes sense while the chain is where holders keep and use their coins. It makes less sense once the plan is for TRVC's activity to move to a chain where contracts, pools and wallets are cheap to use. Continuing to issue on the old chain would mean diluting holders to secure a ledger they are being asked to leave. Setting the reward to zero stops that, and keeps the chain's history in place as Trivechain Legacy rather than switching it off.

The options in front of a chain like ours

A small proof-of-work chain in 2021 has a few honest options.

It can carry on: keep the rewards, keep miners and masternodes paid, and hope that use grows into the issuance. It can build its own smart-contract platform first, and ask holders to wait on an empty new chain while that happens. Or it can move the coin to where holders can already trade and stake it, and treat new protocol work as something that comes after.

The 3.0 plan takes the third route, and the order of its steps is the point. The migration comes first, staking on BSC comes with it, and T3 is planned work that starts after the migration. Holders get a usable home first; the next chain is not something they have to wait for.

Who this lands on

A reward change is not something only developers notice. On Trivechain it reaches:

  • miners and pool operators, who would no longer be paid in new coins;
  • masternode operators, who lock 10,000 TRVC as collateral and are paid from the same subsidy;
  • proposal owners, whose funding comes from the governance budget;
  • exchanges, which run nodes and credit deposits from them;
  • holders, who will have to move their coins.

I built and ran Trivechain's mining pool before I became its lead developer, so I know what a change like this means to the people keeping blocks coming. A plan that reaches all of them should be public before any step of it happens.

What an announcement like this owes people

A plan that ends a chain's rewards owes the people who depend on that chain a few things.

  • The sequence, stated plainly: what happens to the chain, where the coin goes, and what comes after.
  • What stays: the old chain's history remains readable as Trivechain Legacy.
  • Which parts are plans: T3 is development that begins after the migration, not something already built, and it should be described that way.
  • Where to look for instructions, because any migration attracts people who will pretend to run it.

It can state the emission rate the staking contracts will pay; it should not translate that into a yield or a price, or promise a launch date for a chain that has not been written.

Proposing the end of what you maintain

It is an odd position for a maintainer. The easy course is to keep shipping releases and keep the chain running as it is. But the job is to look after the people who hold and run the chain, not the chain for its own sake. If their coins are better served somewhere else, the useful thing I can do is make the move understandable and checkable, and write the code that does it carefully.

The plan is public now. What it leaves for the coming months is the release that ends the reward and the route that moves holders across.