Investigate if XP code can be used for TAHOclaiming

[jagodarybacka]

No description provided.

[jagodarybacka]

Spike results:

The goal of the spike was to decide if we want to change anything about the allowlist mechanism that we are using for XP drops for implementing the TAHO claim feature.

Choosing the mechanism

Projects that need allowlists the most are NFT projects. The outcome of the spike is that most NFT projects are not using merkle trees as a way to verify who is on the allowlist. The most popular solution is to do signature-based allowlisting. As we don't want to change the existing contracts that is a no-go for us and it will be safer to use the same merkle tree code as we used for XP claiming.
More on signature based allowlists: Source 1 Source 2

XP claim mechanism pain points

• generating XP requires manual work and is quite slow - that won't be the issue for the TAHO claim because the allowlist will be generated only once
• storing XP and fetching XP claim files - XP drop source files are stored inside the dapp repository which requires using our own infra to keep quite a lot of JSON files up and running. We may want to use external source to store TAHO claim files so we can decentralize the claim source data more.

Things that are left to do are:

• decide on where do we want to store TAHO claim source files
• abstract the XP code to be reusable for TAHO claims
• add unit tests for the claiming code
• add e2e tests for claiming UI
• automate the generation of XP claim files