feat (registration & scoring): Implement X Account Automation Verification for Miner Registration

[teslashibe]

Problem

Currently, there is no verification that miners registering on subnet 59 are properly declared as automated agents on X, which is a requirement per X's Terms of Service. This creates potential compliance issues and doesn't enforce proper agent identification.

Proposed Solution

Add X automation verification as a requirement for miner registration and scoring by:

1. Extending Masa Python SDK to include X profile verification functionality
2. Modifying validator registration interface to check automation status
3. Including automation verification in ongoing scoring criteria

Technical Implementation

1. API Endpoint Details

curl 'https://api.x.com/graphql/QGIw94L0abhuohrr76cSbw/UserByScreenName?variables=%7B%22screen_name%22%3A%22aion5100%22%7D' \
  -H 'authorization: Bearer AAAAAAAAAAAAAAAAAAAAANRILgAAAAAAnNwIzUejRCOuH5E6I8xnZz4puTs%3D1Zv7ttfk8LF81IUq16cHjhLTvJu4FA33AGWWjCpTnA' \
  -H 'x-guest-token: [TOKEN]'

2. Verification Logic

Check for automation flag in response:

{
  "data": {
    "user": {
      "result": {
        "affiliates_highlighted_label": {
          "label": {
            "description": "Automated",
            "userLabelType": "AutomatedLabel"
          }
        }
      }
    }
  }
}

3. Implementation Steps

• Add profile verification method to Masa SDK
• Extend registration interface to check automation status
• Add verification check to registration validation
• Include automation status in miner scoring criteria

Success Criteria

• All new miner registrations must have verified automated status on X
• Existing miners must verify automation status within grace period
• Scoring system includes automation verification in criteria

Technical Dependencies

• Access to X API (guest token generation)
• Masa SDK integration
• Validator registration interface modifications

Security Considerations

• API rate limiting handling
• Token refresh management
• Response validation and error handling

Timeline

• SDK Extension: 0.5 days
• Registration Interface: 0.5 days
• Testing & Integration: 0.5 day

[grantdfoster]

we are no longer using the SDK in SN59 so will look at how we can extend the protocol node to support this