When BEP-20 Metadata Changes, Treasury Records Need a Trail

A BEP-20 token’s name or symbol can change how it appears in treasury reports, so records need to identify the token by its chain and contract address too. Names and symbols help people read a report, but they are not unique identifiers. The BEP-20 specification defines functions for reading a token’s name, symbol and decimals; it does not define a standard function for changing them.

What does BEP-20 metadata tell a treasury team?

BEP-20 metadata describes how a token is labelled and displayed. The specification makes the symbol and decimals functions required, while the name function is optional. Decimals means the number of places used to display fractional units. For example, a token balance shown as 1.25 may be stored as a larger whole number that software divides according to the token’s decimals value.

A label can change in a contract that includes its own update feature, but that is outside the standard interface. A dashboard may then show a new name for the same contract, or a familiar name for a different one. Treasury staff comparing exports should keep the network and contract address beside each entry. If teams use token dashboards, Poocoin’s guide to choosing a token view covers the display question in more detail.

How should treasury records handle a metadata change?

Keep the original value and the new value with the date each was observed. Record the chain, contract address, name, symbol and decimals together. Keep token amounts in their raw on-chain units where possible, as well as the displayed amount. That makes it easier to check whether a difference comes from a changed label, a display setting or the underlying balance.

A dated record can include:

• Chain and contract address
• Name, symbol and decimals at the time of the report
• Observation date and source, such as a contract read or a block explorer
• The reporting period and balance, including units used

Do not overwrite old labels in archived reports. Keep each report as it was prepared, then note the later metadata separately. That leaves an audit trail for anyone reconciling past balances after a token’s display details change.

What should a reviewer check before reconciling?

First, compare the chain and contract address, not just the ticker. Then check decimals before comparing displayed quantities: a different value can change how the same raw balance is rendered. Finally, confirm when and where the metadata was read. A current contract value may not match an older export, and the BEP-20 standard does not require a metadata-change event that would explain when a custom update happened.

For treasury records, the practical rule is simple: treat labels as dated reference fields and the chain plus contract address as the asset identifier. That keeps a metadata change from silently rewriting the meaning of an earlier report.