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

Lambdas: move Contracts API to an easy to use catalyst-client implementation #1470

Closed
pentreathm opened this issue Mar 20, 2023 · 0 comments · Fixed by decentraland/catalyst-client#330
Assignees
Labels
epic lambdas-deprecation Lambdas deprecation

Comments

@pentreathm
Copy link
Contributor

pentreathm commented Mar 20, 2023

The following endpoints:

/lambdas/contracts/servers
/lambdas/contracts/pois
/lambdas/contracts/denylisted-names

should be available inside catalyst-client in a way that's easy to use without adding unnecessary dependencies. Once there, we should encourage its use internally in the organization and then evaluate if we should keep them as part of the protocol (and move them to lamb2) or deprecate them.

@hugoArregui hugoArregui changed the title Lambdas: Signature API Lambdas: move Signature API and Contracts API to an easy to use catalyst-client implementation Apr 24, 2023
@hugoArregui hugoArregui added the lambdas-deprecation Lambdas deprecation label Apr 27, 2023
@hugoArregui hugoArregui changed the title Lambdas: move Signature API and Contracts API to an easy to use catalyst-client implementation Lambdas: move Contracts API to an easy to use catalyst-client implementation Apr 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic lambdas-deprecation Lambdas deprecation
Projects
Status: Done
3 participants