feat(dashboard): Refactor Miner Status Dashboard to Separate Node and Protocol API Data Sources

[teslashibe]

Problem Statement

Miners currently lack visibility into their operational status on the Masa protocol. The existing dashboard at /status combines all data, making it difficult to maintain and scale. We need to separate miner status data (from nodes) from X/Twitter verification data (from Protocol API) to improve reliability and maintainability.

Proposed Solution

1. Create a new dedicated miner status dashboard at /miner-status
2. Split data sources:
   • Fetch miner status directly from nodeData
   • Create new Protocol API endpoint for X/Twitter verification data
3. Refactor existing /status to /miner-status endpoint to use the new data structure

Figma design is here: https://www.figma.com/design/8qqscJHEKjIhFW7vHvzDN1/Masa-Web-App-2.0?node-id=1630-118&t=0EM1IAyg7ybFBFiK-1

Technical Details

• Add new Protocol API endpoint for X/Twitter verification status: https://github.com/masa-finance/masa-protocol-api
• Implement separate data fetching for node status and X/Twitter data to get the nodes data from the API
• Refresh the data every 5 mins or when a user has clicked verify
• Update frontend to display combined data from both sources

Acceptance Criteria

• New /miner-status endpoint created and functional
• Miner status data successfully pulled from nodeData
• New Protocol API endpoint for X/Twitter verification implemented and integrated with the miner
• Dashboard displays:
  • Peer ID
  • Public key (wallet)
  • Online status
  • X/Twitter scraper status
  • Web scraper status
  • Telegram scraper status
  • Discord scraper status
  • Total peers
  • Staked status
  • X/Twitter verification data (accounts, last scraped, login status): total accounts, total scraped, plus the table
• Status updates every 5 minutes or when verify login button clicked
• Verify login buttons functional by sending a request only to the local node node remote workers to test the nodes login functionality

Out of Scope

• UI/UX improvements beyond basic functionality
• Historical data tracking
• Advanced analytics

Estimate

1 day implementation

Labels

feature api dashboard priority-high

[teslashibe]

@theMultitude to create SQL queries for getting the data for the table. Post them here to help the developer working on the API endpoints