Token Stewards
A Token Steward is a community operator approved by Synthwav to maintain a token's Token Insight Profile when they do not control its on-chain Authority wallet. The system keeps community-run token information current while clearly separating profile maintenance from on-chain ownership or control.
Why Stewards Exist
Tokens can outlive their original teams, move to community leadership, or lose access to an original project wallet. In those cases, the active community may need to correct a description or update official links without claiming to be the token's on-chain Authority.
The Steward system provides a transparent, limited path for those updates. It does not transfer ownership, change the blockchain, or make a Steward the token creator or Authority.
Approval and Community Support
A Synthwav administrator creates a Steward grant for one canonical TIP token family. The grant records:
- the approved Steward wallet
- at least three distinct community-member X handles
- the approving administrator and relevant timestamps
- the grant's current status
X handles are stored and displayed to administrators exactly as entered. Duplicate checking ignores letter case and a leading @, so differently capitalized versions of the same handle cannot count as separate references.
These references are community attestations recorded by Synthwav, not wallet signatures or on-chain proofs from the referenced accounts. Their identities remain Admin-only. Public surfaces and the Synthwav Portal API disclose only that the active grant has the required community support.
Fewer than three references leaves a grant pending. Only an active grant permits Steward edits. Administrators can suspend, reactivate, or revoke a grant.
What a Steward Can Edit
An active Steward can update the same public TIP metadata fields available through the standard editor:
- description
- website
- X
- Telegram
- Discord
A Steward cannot change token identity, token-family relationships, the Authority wallet, supply, market data, the scoring methodology, the Token Score, or the TIP Grade directly. The Steward's allowed published metadata can affect the Profile-completeness factor under the same rules applied to every token profile.
Steward and Authority Precedence
The verified on-chain Authority always retains edit access. Steward authorization is checked only when the connected wallet is not the Authority.
Metadata changes apply per field. If a Steward updates a website and the Authority later changes that website, the Authority's newer value becomes current. Fields the Authority does not change remain untouched. Both updates remain in edit history with their original STEWARD or AUTHORITY role.
An Authority edit does not currently suspend or revoke the Steward grant automatically. While the grant remains active, the Steward can make a later update. Synthwav administrators can suspend or revoke the grant whenever exclusive Authority control is required.
What Users See
When a token has an active grant, its Token Score/TIP card shows a clickable Steward Managed notice. The notice explains:
This token is looked after by a verified Steward, with the support of at least 3 community members. The Steward helps keep this profile accurate and up to date, but does not act as its on-chain authority.
The public notice does not identify the community references. In the TIP editor, a connected Steward sees a STEWARD access badge on token families they are permitted to edit. Metadata history labels Steward edits so users can distinguish them from Authority and Admin changes.
Reliability and Revocation
Steward authorization fails closed. If Synthwav cannot load or validate the active grant, new Steward edits are temporarily denied instead of being allowed without verification. Existing metadata and edit history remain available.
Suspending or revoking a grant removes current Steward editing access and the active public notice. Historical edits retain their STEWARD label so the provenance record is not rewritten.
Portal API
The read-only Synthwav Portal API exposes an optional steward object on a full profile and verification.stewardActive in search results. The full object includes the Steward wallet, active status, verification date, and community-reference count, but never the reference identities.
Metadata maintained by a Steward uses verification: "steward". History requested with the appropriate scope uses actorRole: "steward" for direct Steward edits. These additions do not grant editing rights: Portal API keys and Steward authorization are separate systems.