Add a Market Manipulations Widget

[evgenydmitriev]

To participate, submit a pull request that adds a simple and lightweight widget for displaying Wash Trading and Front Running Metrics on the Market Health Metrics Documentation page located here, and add this issue assignee as a reviewer. Feel free to use whatever JS/TS libraries and frameworks, but keep in mind that your submissions will be evaluated based on the combination of cost/efficiency, security, and load speed. Below is a rough sketch of the widget position on the page, no need to make it look identical:

This time, we offer multiple bounties for the top 3 submissions:

🥇 $1000
🥈 $500
🥉 $250

Anyone can participate and submit their pull request before the deadline. We will also reach to all challenge participants with successful submissions to talk about more permanent research and development opportunities within our projects. Spread the word - additional $250 💰 will be paid for referrals of any winning submissions!

See more details on the Challenge Program and check out the success stories of the challenge winners.

Looking forward to your submissions!

[junowoz]

Hello. I'm getting several issues with missing files when trying to run Hugo locally. Templates for certain page types and specific shortcodes such as "columns" and "katex" are not being found. Do I have to create those, or are they missing from the repo? Would appreciate any guidance on this. Thanks!

[evgenydmitriev]

The website is hosted on GitHub pages attached to this repo. What see you here is what goes into the CI/CD pipeline. You might also want check out the hugo build action and use our devcontainer if it helps.

[junowoz]

The website is hosted on GitHub pages attached to this repo. What see you here is what goes into the CI/CD pipeline. You might also want check out the hugo build action and use our devcontainer if it helps.

thanks!
I have everything implemented and all set up. Now, I'm just trying to determine the most appropriate data to fetch in order to demonstrate the wash trading data. Should we perform some mathematical operations between the values, or can we, for instance, use the volume_distribution_median to represent wash trading data? I was also wondering if we can use the vwap to represent front running.

should we keep the input scales as they are, or should we apply some weighting to make the chart look better?

and regarding the chart's time frame, how long should it be? the API provides data for only one week, so should we use labels from monday to sunday?

thank you in advance for your responses!

[evgenydmitriev]

I'm just trying to determine the most appropriate data to fetch in order to demonstrate the wash trading data. Should we perform some mathematical operations between the values, or can we, for instance, use the volume_distribution_median to represent wash trading data? I was also wondering if we can use the vwap to represent front running.

No need to do any data manipulation at this point. The challenge is about visualizing existing Wash Trading and Front Running Metrics as is.

should we keep the input scales as they are, or should we apply some weighting to make the chart look better?

You are free to chose whatever scales you want, make them adaptable, or give users additional controls.

and regarding the chart's time frame, how long should it be? the API provides data for only one week, so should we use labels from monday to sunday?

Feel free to choose whatever looks good to you. As stated in the issue description, the sketch is there to show its position on the page, no need to make it look identical.

[junowoz]

I'm just trying to determine the most appropriate data to fetch in order to demonstrate the wash trading data. Should we perform some mathematical operations between the values, or can we, for instance, use the volume_distribution_median to represent wash trading data? I was also wondering if we can use the vwap to represent front running.

No need to do any data manipulation at this point. The challenge is about visualizing existing Wash Trading and Front Running Metrics as is.

should we keep the input scales as they are, or should we apply some weighting to make the chart look better?

You are free to chose whatever scales you want, make them adaptable, or give users additional controls.

and regarding the chart's time frame, how long should it be? the API provides data for only one week, so should we use labels from monday to sunday?

Feel free to choose whatever looks good to you. As stated in the issue description, the sketch is there to show its position on the page, no need to make it look identical.

Thanks! just submitted my PR.

[evgenydmitriev]

This issue is about creating a dynamic widget based on this Wash Trading and Front Running Metrics API endpoint that visualizes returned objects. Feel free to provide your solution to the challenge in a pull request.

[arlansonic]

I raised a PR for this activity about 5 days ago and ended up not announcing it here:

Follow the PR link: #303

The environment variables I added to my github:
RAPIDAPI HOST
SECRETRAPIDAPI,
I added them to Actions secrets and variables which is on Github itself

[CrytoCodeWizard]

May I take part in this code challenge?
I mean I am so late to take part in this ?.

[marina-chibizova]

@NightSkyHoney please participate, the valid solution has not been submitted yet

[CrytoCodeWizard]

thanks for your reply, I will submit my solution.

[JediFaust]

@evgenydmitriev Wanted to inform that I faced authorization issues on Metrics API. Tried various methods, however, invalid session: error finding user for endpoint error remains. I guess issue is related to MongoDB. Is there possibility to fix it, if the submission acceptance is still active?

[marina-chibizova]

@JediFaust yes, it's a problem on our side. I'll fix it today

[marina-chibizova]

@JediFaust it's fixed

[JediFaust]

@marina-chibizova Thanks!

[JediFaust]

@marina-chibizova I reached to some point in submiting a solution. Now I have a two ways to design a widget:

• According to API returned data, there is no metrics as Market Manipulation and Front Running Index. Assuming that no data manipulations needed, I've decided to visualize different indicators from the docs page and the current widget is designed like this.
• I noticed that returned data contains different metrics from the docs page, and wanted to know how exactly they should look.

[marina-chibizova]

@JediFaust all metrics in the new API generally fall under "wash trading metrics" cause they can be used to identify wash trading. but none of them will be specified as manipulation index. The task is to visualize them as they are in the API, so your MVP is fine.

I noticed that returned data contains different metrics from the docs page

that's true, I'm working on new documentation and we also will add more of the old metrics to the API eventually. I plan to finish the docs tomorrow

[marina-chibizova]

@JediFaust I updated the docs

[JediFaust]

@JediFaust I updated the docs

@marina-chibizova Thank you!

[Hjklvfr]

@evgenydmitriev I need a review

[evgenydmitriev]

@Hjklvfr, you need to address the gitguardian bot comment. Hard-coding tokens is generally not a good idea. Keep in mind, we have the following secrets added as repository variables:

[Hjklvfr]

@evgenydmitriev, I fixed it.

[steph-crown]

This issue specifies a hard deadline of November 25. I want to confirm if I can still work on it now.

[evgenydmitriev]

@steph-crown, we still accept submissions.