Identify Blockstack Users Within Gaia for Block Survey Migration

[andresgalante]

Block Survey is migrating away from Hiro's hosted Gaia Hub and needs a way to identify Blockstack users within Gaia. Specifically, we need to:

• Translate a user's domain name into their Gaia hub address.
• Access any APIs or methods that can help with user identification in this context.

Current Findings

• All Block Survey customers use the https://blocksurvey.io/ domain.
• Users have .btc or .id.blockstack domains.
• Some users do not have BNS names and are identified only via their wallet seed phrase.

Example User IDs

• compressstudio1.id.blockstack
• daniavorszky.id.blockstack
• david.id

Next Steps

• Investigate how to resolve user domain names to Gaia hub addresses.
• Determine the best approach for identifying users who lack BNS names.
• Estimate the effort needed:
  • Optimistically: 1-2 days for research and coding, followed by 1-2 days for DevOps and script execution.
  • Realistically: ~1.5 weeks.

cc: @zone117x

[andresgalante]

Here are the file names which will be there on BlockSurvey users Gaia:

mysurveysindex.json
blocksurvey_pgp_profile.json

[andresgalante]

The BlockSurvey team requires an increased rate limit to facilitate our migration away from Gaia. We can identify our requests using the header:

X-App-Identifier: blocksurvey

[raja-ilayaperumal]

Hi Team, This is a quick follow-up on the rate limit increment for BlockSurvey. It will help us to plan for a migration.

Any updates on this request?

[andresgalante]

Hey @raja-ilayaperumal, apologies for the delay on this.

We haven’t had a chance to get to it yet. I'll follow up with an update as soon as I can. I appreciate your patience!

[andresgalante]

Hi @raja-ilayaperumal

We’re having a hard time finding bandwidth on our side to take this on, so we wanted to check a couple of things that might help you move forward independently:

Does every Blocksurvey user bucket (Gaia hub address / directory) contain a clear indicator that it's associated with Blocksurvey?

For example, something like a blocksurvey-data.json file present in every relevant bucket. If that’s the case, it would make it easier for us to write a script internally to locate and potentially back up all Blocksurvey-related buckets.

Would your team be open to implementing some client-side migration logic yourselves?

For instance, you could add some client-side js that is ran when a blocksurvey page is loaded, and have it send something like the following payload to blocksurvey's servers:

• The user’s BNS ID
• Metadata
• Gaia hub bucket address
• List of Gaia URLs for Blocksurvey-related files

With that data collected, you could then build and run your own migration logic on the backend.

There’s no plug-and-play tooling for this, so your engineers will need to do some custom work either way.

Let us know what you think!

[raja-ilayaperumal]

@andresgalante Thanks for your reply.

I have gone through the two suggested approaches on GitHub.

We currently have a standard file name, "blocksurvey_pgp_profile.json," for every block survey user in Gaia. If you could get the user's list, that would also help us.

We plan to add the script to discover the Gaia-dependent user details. We will do it in the mid of May month.

[saralab]

Gaia Hub will be decommissioned May 30th, we will provide the data you need to save your data.
The team will reach out and update this issue with next steps and more details