-
Notifications
You must be signed in to change notification settings - Fork 14
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
Standardize events data #68
Comments
I will love to work on this @lukaspetrasek |
I'll love to handle this issue |
Hi, can you guys please tell me something about you, what skills/experience do you have and how do you plan to tackle this issue? This task is not simple, so I have to learn more information before I assign anyone 🙏🏼 |
Hello I will love to work on this issue, @lukaspetrasek |
Okay, assigning you @godekina 👍🏼 @godekina Let me know if everything is clear. If you have any questions, please ask here. What is you TG handler please? 🙏🏼 Consider joining our TG group. |
Thanks @lukaspetrasek I'd like to have the sample data so I can work on writing code to standardize them. |
Hi @godekina , you can find the sample e.g. for zkLend here: https://storage.googleapis.com/derisk-persistent-state/zklend_data/events_sample.parquet. To obtain the sample for other protocols, just change the folder in the address, e.g. https://storage.googleapis.com/derisk-persistent-state/nostra_alpha_data/events_sample.parquet for Nostra Alpha. |
@lukaspetrasek the pull request #123 for this feature is ready for review. |
Hi @godekina , 🔙 |
DeRisk currently works with event data in a raw format where the relevant data (like the user, token, amount, etc.) is saved in a dictionary or list-like structure in one of the columns. To better extract information from the database, it would be helpful to have a unified data structure where all relevant pieces of information would be saved in a separate column. Thus, we could, e.g., easily query all events of the given type (deposit, withdrawal, liquidation) for the given user, lending protocol, etc.
The task is to take a sample of events (which will be provided on demand) and convert it to a standardized format that can be used to store information about any type of event and any lending protocol.
The text was updated successfully, but these errors were encountered: