-
Notifications
You must be signed in to change notification settings - Fork 17
Frontend Contest: TON status page, Stage 1 #43
Comments
Question: Are we to build the open-source backend or consume an already available one? |
Using of publicly available APIs are not forbidden, however since it is expected that status page will display status of those APIs too, perfect solution still requires it's own backend. |
Why is the deadline so short? :( can't do it due to traveling :((( |
Deadline is too short. |
Should it be written on specific language? Could it be .net? |
https://github.com/undrfined/tonstatus-backend (2fb2b45) tonstatus-backend repo has frontend as a git submodule, so there's no need to pull the second repo
Implemented:
EQCEU2c1HzLz5kZUfRbAoK9h4NP8sVyOaP_MRNte2bG4JYJ3 |
TON Status
GitHub: https://github.com/rgabdullin/ton-monitor |
Introducing TonMonitor which was integrated into tonAdmin and upgraded with backend server. Backend: https://github.com/Web-Rangers/ton_admin_server
Frontend: https://github.com/Web-Rangers/tonadmin
Page will be available at http://localhost:3000/statuspage wallet: EQDzRLjYsmwWXJJYEnQMbfK5NZRzjimLwabZAbqoNp6C6K42 |
That's actually my favorite, just not sure if they'll like Material Design :) |
Received 4 submissions. ReviewThere is no first place in the results of this competition, because basically the works duplicate already existing functionality: https://tonmon.xyz/, https://ton.org/global-config-wallet.json (autoconfig), https://newton-blockchain.github.io/status. However, we note that some works use an alternative implementation to collect metrics. To get the main prize, it is not enough to simply collect existing metrics in one place and add ping of http pages. Nevertheless, we see that the participants of the competition have dived deep enough into the TON and their work can be used to create a full-fledged TON status center. We will contact some participants with a proposal for a continuation of the work. @undrfinedFeatures:
Implementation: Frontend: React Backend: NodeJS + MongoDB Data collection occurs by lite-client call. Additional advantages:
Additional cons:
@rgabdullinFeatures:
Implementation: Frontend: React Backend: Python + Celery + RabbitMQ + MongoDB It installs its own full-node and full-node are used to collect data. To work with the node, the code from mytonctrl is used. Additional advantages:
@OmaiwoHochetDenegFeatures:
After the deadline, the following was done:
Implementation: Frontend: React Backend: NodeJS + mytonctrl JSON RPC API Data is received from the mytonctrl node by json rpc api. Additional advantages:
Additional cons:
@maxistarFeatures:
Implementation: Frontend: React Backend: tonmon.xys scripts + NodeJS + InfluxDB Slightly modified tonmon.xyz scripts are used Results2nd place π₯ @rgabdullin - 2000 TON 3rd place π₯ @undrfined - 800 TON Bonus prize π @maxistar - 200 TON Second places will also receive an offer to continue work. |
Please send TON address (https://ton.org/wallets) to receive bonus prize |
Thank you @tolya-yanot, it was really fun to participate in the contest, it is always great getting familiar with such a cool technology! I wish you all the best, thanks for contributing to the great product! My wallet address is: EQC0wM4wqHvpswRw3Xh06vjmAj15ftAK0hH8OLtS9prx57jY |
π Frontend contest: TON status page
Prize fund: $30β000 in Toncoins (currently 10β000 TON).
Deadline: 18:00 on Nov, 17 (UTC).
Task:
Create a web app and corresponding open-source backend, which display summarized data on the state and availability of TON Blockchain.
In particular, the page should display:
API and integration with notification services (Telegram channel/bot) will increase your chances to win.
Evaluation priorities:
Who can take part: Anyone.
How do I submit:
Comment on this issue on GitHub by attaching an archive or link to the open-source code with a solution, a description of the functionality, the build process, your TON address to receive an award. Submission must be under the MIT license.
To avoid plagiarism, you can attach a link to a private repo to the submission and hash of the last commit, which you will make public after the deadline.
The text was updated successfully, but these errors were encountered: