Season points look like a claim. A dashboard ticks up a score and a wallet treats that score as tokens already owed. The score is the first story. The conversion rule is not.
Points can record who showed up. They can also sit in a private table with no mint path. I read a points page the way a stamp card is read: the stamps are marks. They are not the prize until a rule says how many stamps buy what.
- A score is the first reading
- A private table is not a ledger
- A season without a rate
- Card I kept for a season called TALLY
- A score that is actually owed
- Read the conversion rule before you treat the score as a claim
A score is the first reading
The problem is easy to name. A campaign prints points each week. The first reading treats the total as a share of a future token. Many campaigns never publish a rate. Many keep the table off-chain. A later season can change the weight of the last one.
Is the first reading always false? No. Some programs name a pool, a date, and a formula that maps points to units, then execute that formula on chain. The first reading fails when “points will convert” is the whole sentence, when the table can be edited by one admin, or when two seasons are added together with no published weights.
My claim is narrow. Points are a score in a campaign. A claim is a later fact: a contract will pay a named unit to a named address by a named rule. Mixing them turns a stamp card into a coupon.
Opinion, not a law for every season: the leaderboard is a costume. The conversion page is the room.
A private table is not a ledger
If the score lives in a database the team can rewrite, it is a note. A note can be honest. It can also drop a row. An on-chain snapshot or a published Merkle root is a different object.
Question I keep on the page: can a reader verify their score against a public root? If not, write “table,” not “ledger.”
Exception: a live contract that mints points as tokens is not a season score. It is already a unit. Call it that.
A season without a rate
A claim needs a rate, even a rough one: this many points, that many units, from this pool. Without a rate, the score only ranks wallets against each other.
Observation from public pages: I have lined a points total next to a blog post that said “token later” and found no pool size. That pairing is a fact on two pages. It is not a verdict on every campaign.
Condition: if a later post names a pool but not a date, the rate is still open. Write what is missing. Do not fill the hole with a guess.
Card I kept for a season called TALLY
I keep a card for a made-up season I call TALLY. Six weeks. My row: 12,000 points. Docs: “points convert at season end.” No pool. No rate. No root. A dashboard called the 12,000 a balance.
Question in the margin: a balance of what? Answer I could defend: a rank in a table. Not 12,000 units. Not a share of a named pile.
Was I looking at a live book? No. TALLY is a page. The experience was asking for the rate and finding a slogan. A reader can repeat that ask on any public season page without taking a position.
Exception I left beside the card: if TALLY later publishes a root and a pool, the 12,000 becomes an input to a formula. Until that post exists, the word balance is early.
A score that is actually owed
The first reading works when the score is snapshot on chain or under a public root, when a pool and a rate exist, and when the pay path is a contract a reader can open. It works for that season.
It fails when a ticking number is treated as tokens already due. It fails when a second season is added to the first as if both already shared a formula.
I do not treat a missing rate as a command to leave. I treat it as a reason to keep the score and the claim on two lines.
Read the conversion rule before you treat the score as a claim
The solution that holds under the conditions above is a short read, not a slogan.
Write where the score is stored. Write whether a public root exists. Write the pool, the rate, and the date. If a page will not show those, the “already owed” sentence is not ready to stand.
If the dashboard and the announcement disagree, say so and stop before the coupon becomes certain.
The spare thought on the desk is small. A score can be a real count of who showed up. The prize can still be unnamed. I read the conversion rule first. I do not call the stamps a claim because the first reading stopped at the ticking number.
The articles on this site are not investment recommendations or financial advice. They are structural analysis based on on-chain data and project documents.
Comments
Post a Comment