ContestBot is now ready to accept submissions for Blockchain Contest Round 1.

Start the bot, choose either challenge, answer the bot’s questions, then send:

for “TON Block Validation Challenge”
an archive containing the following:

– solution.patch – a patch to the original branch.
– README.md – a description of the implemented optimizations and their effectiveness. If you tried some optimizations that didn't work, kindly provide details regarding them as well.

For this challenge, your submissions will be tested in the following environment:

OS: ubuntu-22.04
Compiler: clang-14
Hardware: AX-42 Hetzner

for “TON Trustless Bridge Challenge”
an archive containing the following:

1. Code of Lite-client smart-contract and script for generation messages for that contract with build instructions.
2. Code of Transaction-checker smart-contract and script for generation messages for that contract with build instructions.
3. Addresses of smart-contracts deployed in Testnet and Fastnet respectively, with the tx_hash of transactions that demonstrate both successful and unsuccessful checks of blocks and transactions.

Note: If you completed both challenges, send your submissions consecutively by choosing either option.

@ContestBot is now ready to accept submissions for the JavaScript Contest, Round 1.

New deadline: 23:59 on February 22nd (Dubai time)

We are extending the deadline to give all contestants enough time to properly prepare their submissions. Please prepare your submission at least 2–3 hours before the deadline and avoid uploading until the last moment, as late submissions will not be accepted.

Build the application, then prepare:
- A ZIP-archive with the following structure:

 
-> dist - folder with the build.
-> src - folder with the app's source code.
-> contest.md – a text file that briefly describes the approach used for each task.

- A link to the commit on a public GitHub repository, forked from the Telegram Web A repository.

Your repository may stay private until the deadline.

We are attaching a breakdown of the Final Results for each submission.

1. Final Results:

Initially, for preliminary testing published on contest.com, we ran each test in a separate process. This allowed us to fully evaluate even solutions that crashed or hung on specific tests. However, this method disrupted many participants' performance optimizations and introduced substantial noise into the results.

Therefore, for the final evaluation, we executed all tests in a single process using a grader closely resembling the provided contest-grader.cpp. Consequently, solutions that crashed or hung on any test received a final score of 0.

2. Post-Contest Corrections:

After announcing preliminary results, several participants submitted bug fixes via comments on contest.com. Although we typically do not accept post-contest corrections, one corrected solution turned out to be significantly faster than any solution submitted during the contest. As an exception, we decided to evaluate all corrected submissions and include them in the final standings. To maintain fairness, these late submissions incurred a 20% penalty on the prize amounts awarded.

@ContestBot is now ready to accept submissions for the JavaScript Contest, Round 2.

New deadline: 23:59 on April 27 (Dubai time)

Build the application, then prepare:

- A ZIP-archive with the following structure:
-> dist - folder with the build.
-> src - folder with the app's source code.
-> contest.md – a text file that briefly describes the approach used for each task.
- A link to the commit on a public GitHub repository, forked from the Telegram Web A repository.

Your repository may stay private until the deadline.