C-ATTS: An Attestation Data Duplicator #190
Open
+4
−4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for optimism-ecosystem-contributions ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Nicca42
approved these changes
May 28, 2024
|
@Nicca42, I don't believe the format allows for more than one project to be listed for each idea. Please advice how to solve the merge conflict. 
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I am building C–ATTS, a platform to create, transform, combine and migrate EAS attestations.
A C–ATTS attestation is defined by a “recipe”. A recipe is a combination of a GraphQL query, a processing algorithm and an output schema. The output of running a recipe is a regular EAS attestation that is 100% compatible with the EAS standard.
C–ATTS supports queries to the EAS API as well as queries to any subgraph hosted on The Graph. This means that C–ATTS can attest to virtually any data stored on any EVM chain.
Some example recipes could be:
A C–ATTS recipe can include multiple queries, spanning multiple chains. The processing algorithm can be as simple as summing up the results of the queries or as complex as you can imagine.
Once a recipe is setup, users can claim attestations. Think of it a bit like POAPs.
Currently, C–ATTS is looking for projects that want to integrate composite attestations into their platform. If you are interested, please reach out to me at Twitter or Telegram.
You can find more information and try the prototype app at https://catts.run
The app is still in early development and I am looking for feedback and feature requests. Curretntly, you as a user can claim attestations from a number of pre-defined recipes. On the roadmap is a number of planned features:
🙏 Thanks!