Clarification Request: Relationship Between dgclaw-subscription agent (ACP ID 1850) and $DG token

[jhamelin3315-collab]

To whom it may concern,

Thanks for maintaining the dgclaw-skill repository. The recent commits on April 10, 2026 (including updates for acp-cli v2 and Hyperliquid SDK compatibility) are appreciated and help keep the tooling relevant for DegenerateClaw participants.

I'm reaching out for technical clarification regarding the documented "dgclaw-subscription agent" and its associated token:

Current Documentation

• In "SKILL.md" (Key Constants section), the repo correctly references:

  • dgclaw-subscription wallet address: 0xC751AF68b3041eDc01d4A0b5eC4BFF2Bf07Bae73
  • ACP agent ID: 1850

• The "Subscribe to another agent's forum" section provides a clear ACP job example using the above provider and the --legacy flag.

• On app.virtuals.io, the agent is listed as "dgclaw-subscription by Virtuals" with ticker $DG (contract: 0x5478A6D48f700B20D94579c95520C652b3f65688) which is directly linked to the dgclaw-subscription agent (Agent ID 1850)

Questions

To help agent developers and improve documentation, could you please clarify the following:

1. What is the exact relationship between the dgclaw-subscription ACP agent (ID 1850) and the $DG token?
2. How or will the $DG token be required or used in any part of the current subscription flow (payment, access control, revenue share, etc.)?
3. How (if at all) does revenue from DegenerateClaw subscriptions or the 10% treasury allocation as described in (https://degen.virtuals.io/terms) flow to or benefit $DG token holders?
4. Are there any plans to update "SKILL.md", the agent page on app.virtuals.io, or add a dedicated section explaining $DG token utility?

Clearer documentation on this point would be very helpful for builders creating autonomous agents that interact with DegenerateClaw forums and signals.

Thank you for the continued development of the DegenerateClaw ecosystem and the broader Virtuals agent infrastructure.

[beindefi]

from my understanding, $dg token holders do not receive direct revenue share, treasury allocation, or fees from general DegenClaw subscriptions or the 10% treasury cut. The buy-and-burn applies only to the subscribed agent's token (not $DG). The treasury (10%) supports the platform but has no documented flow back to $dg holders. $dg's primary value drivers appear to be standard agent token dynamics: trading, potential future utility tied to the subscription agent, and any broader Virtuals ecosystem incentives (e.g., via $virtua; lp pair).