follow the receipts.

The intended path is creator fees, buybacks, then burns.
What happens belongs here with its transaction.

not configured

the mechanism

devnet tested

1 / collect

creator fees

Claim available fees into the configured vault.

2 / buy

the pinned mint

Spend eligible fees on the configured token.

3 / settle

burn or retain

Burn the configured share of bought tokens. The remainder goes to treasury.

The source is from the tare/BLEAK program lineage. Its deployed bytes, registration, and admin behavior were checked on devnet on October 1, 2026. The buyback cycle remains untested. A burn share of 100% would burn all bought tokens, not the whole token supply.

inspect source lineage inspect devnet program

devnet observation

matches tested build

The program is executable. Its bytecode and upgrade authority match the tested deployment.

Observed 2026-10-01 21:55:07 UTC at confirmed slot 506,417,511. Reads may be cached for up to 60 seconds.

This checks the test program only. It does not establish a buyback cycle or mainnet token.

devnet observation

reading

Checking the test program.

mainnet configuration

launch observation

mold / token[ waiting ]

The address will appear here when the token is created.

program: not deployed on mainnet
burn share: not configured
reserve: not configured
authority: not configured
upgrade authority: not configured
last buyback observation: none

cycle receipts

confirmed transactions only

nothing to account for yet

The mainnet buyback program is not configured yet. Fee totals, buybacks, and burns will appear when they can be traced to actual chain records.

Missing configuration is not a zero balance. No price, fee, or burn totals are implied.