Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Investigation] How to migrate projects using Gelato to Massa in 2-clicks #122

Open
2 tasks
SlnPons opened this issue Feb 4, 2025 · 0 comments
Open
2 tasks

Comments

@SlnPons
Copy link
Collaborator

SlnPons commented Feb 4, 2025

Objective

For our Gelato-like product to penetrate the market we'll aggressively target projects currently using Gelato or Chainlink. We'll offer them a cheaper solution.
But we would also need to assure that the migration is not only smooth but also easy-to-manage otherwise we won't be able to convert them.

The objective of this investigation is to look at existing projects using Gelato and/or Chainlink and to deep dive into the existing connection to make sure we can assure a 2-click migration (aka easy on both sides: us and them).

How to

  • Identify an easy and complex use cases to deep dive: Aave or Compound and Aavegotchi for instances seems to be relevant.
  • Analyse and document the connection, transaction and what would be needed to migrate them on Massa automation service
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant