-
Notifications
You must be signed in to change notification settings - Fork 11
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
Data tile BE: Transactions burning most steps by entrypoint ID #10
Data tile BE: Transactions burning most steps by entrypoint ID #10
Comments
Hey @mazurroman, I would like to tackle this issue. Just wanted some references to understand the entrypoints and on which language is the backend going to be implemented in? Can you give some directions, so then I will be able to come up with a strategy to handle the task. |
Hi, I will to take this up |
@KeneePatel we updated the description and it now also contains a link to the backend repo for more context @aweolumidedavid please check our contribution guidelines and update your comment accordingly #12 |
@mazurroman hi, you can call me David. To implement the API, I will do the following
|
Assigning to @aweolumidedavid who provided the most detailed information on how to approach this issue |
Apologies for a confusion here. @aweolumidedavid your comment is incorrect - you are suggesting to create a node.js endpoint; however, we state that we use PostgREST in the starkflare-indexer repo README This issue remains open and unassigned. @KeneePatel if you are up for it can you add instructions on how would you solve this issue, according to our contributor guidelines |
I guess I lacked a proper structure on how the endpoint functions will be handled. To be honest, I will be learning it along the way, but looking at the current codebase, I guess I will need to create a model for the input and output. Maybe even write a migration SQL script to create necessary queries or tables. Write the implementation in a function similar to that of account-calls.ts which will have the logic for conversion and processing of the input data. If I come across any doubts, I will be quick to mention the specifics in our TG group and ask for directions. And let me know if any more clarity is needed. |
@mazurroman I will like to give this another shot.
The sql code snippet look like this Finally, I am open to corrections and willing to learn. Thank you very much. |
Hi everyone! Thank you for your interest in this issue. @KeneePatel, your comment lacks the specific info we need according to our contribution guidelines. We expect details about you, your relevant experience, and detailed technical instructions on how you plan to tackle the task. I have assigned this issue to @aweolumidedavid based on their last comment, which provided the necessary information and understanding of the problem and solution. |
Thank you very much, working on it right away @mazurroman @barabanovro |
Hey @aweolumidedavid are you still working on this? |
Hi @aweolumidedavid, I wanted to check in on the progress of this task. Could you please provide an update? |
@barabanovro @mazurroman I hope this message finds you well. I regret to inform you that I am currently unable to complete the issue assigned to me due to unforeseen circumstances that have taken me away for a while. Given the importance of timely progress on this matter, I kindly request that the issue be reassigned to another team member @saimeunt who can continue the work without delay. |
I'd like to tackle this issue for several reasons. Firstly, I have experience in developing RESTful APIs and working with some databases. Moreover, I've carefully reviewed the requirements of the problem and feel confident in implementing the API endpoint as specified. I'm committed to adhering to project guidelines and have the availability to efficiently complete this task. In summary, I believe I can effectively contribute to resolving this issue, and I'm excited about the opportunity to work on it. |
Feel free to join our telegram to get latest updates: https://t.me/+DYI4FMia43I1NDI8
Create an API endpoint in the https://github.com/walnuthq/starkflare-indexer backend repo that accepts two parameters: contract hash and entrypoint selector. The endpoint should return a list of transactions for the given contract and entrypoint, sorted by the number of steps consumed in descending order.
The returned data for each transaction should include:
Follow the guidelines outlined in the starkflare-indexer repository. Note that this endpoint should be implemented separately from the
get_common_data
endpoint as it requires specific arguments.The text was updated successfully, but these errors were encountered: