6.2: Test X/Twitter scraping

Let’s start by making sure our miner node is in local mode.

If you are following the guide step by step, you should not have added a bootnode to the .env file yet. Meaning your miner node should be running in local mode.

If you previously connected to the testnet by adding a bootnode to your .env file, you will need to comment it out to run in local mode.

To ensure the miner node is in local mode, check the .env file for any bootnode entries. If you find any, comment them out to run in local mode.

Verify that your X/Twitter scaper is working and returning data

Execute a curl request to the node running in local mode to ensure it retrieves X/Twitter data:

curl -X 'POST' \
'http://localhost:8080/api/v1/data/twitter/tweets/recent' \
-H 'accept: application/json' \
-H 'Content-Type: application/json' \
-d '{
"query": "$Masa AI",
"count": 1
}'

You should receive a response similar to this:

{
  "data": [
    {
      "Error": null,
      "Tweet": {
        "ConversationID": "1828797710385942907",
        "GIFs": null,
        "HTML": "<a href=\"https://twitter.com/CryptoGodJohn\">@CryptoGodJohn</a> $MASA the leading token for <a href=\"https://twitter.com/hashtag/AI\">#AI</a> and <a href=\"https://twitter.com/hashtag/Data\">#Data</a> <br><a href=\"https://twitter.com/gesepolia Masafi\">@gesepolia Masafi</a>",
        "Hashtags": ["AI", "Data"],
        "ID": "1828900558452797478"
        // ... (other Tweet fields)
      }
    }
  ],
  "workerPeerId": "16Uiu2HAmSCQMh22Xmo1GMxXB73qRx3YaVqqL1UwTYn3iNvQLjPB5"
}

Verify that the workerPeerId in the response matches your node’s peerID.

These are instructions or content that only pertain to the third step.