RADIANT

Creator Playbook

Register Influence Tokens

Step-by-step guide for creators to emit FIP-2 context, bind their token to the registry, and verify graph data.

1. Prerequisites

  • Deployed InfluenceToken contract (ERC-20 compatible).
  • Creator wallet with permission to mint/attest.
  • SDK installed: npm install @influence-protocol/sdk.

2. Emit Canonical Attestation

Call buildMintInfluenceTx with includeAttestation enabled. The payload must reference your creator metadata via FIP-2.

const tx = buildMintInfluenceTx({
  tokenAddress: creatorToken,
  to: creatorWallet,
  amount: 0n,
  request: {
    attestor: creatorWallet,
    includeAttestation: true,
    captureContext: true,
    snapshotData: '0x',
    payload: {
      workId: creatorToken,
      attestationUri: 'ipfs://creator-manifest',
      lens: 'creator_bootstrap',
      schemaId: schemaAddress,
      isPublic: true,
      fip2Target: encodeFip2Target({ kind: 'castId', fid, hash }),
    },
  },
});

Broadcast the transaction through your signer of choice. This binds the token + payload in VisualizationAssembler.

3. Verify Registry Entry

Use RelationalClient to confirm the attestation is discoverable:

const creatorGraph = await client.getCreatorTopology(creatorWallet);

The response should include primaryToken, attestationCount, and participant metrics. Share this endpoint with AI agents for health checks.

4. Optional: Distribute Radiant

Reward early attestations via buildIlluminateTx or the permit workflow.

Agent Notes

  • Validate that creatorToken matches the primaryToken in topology responses.
  • Store the attestation URI and schema for reference; these power downstream visualizations.
  • Subgraph adapter (coming soon) will mirror the same topology data for faster reads.

Machine-readable workflow: /agents/workflows/creator_onboard