Sat. Jan 1st, 2022
    DevEx , Free TON, Meetup

    The Solidity Syntax Highlighting contest has started, and everyone is welcome to participate. Community members are discussing a series of new contests for creating a notification service and are looking forward to ideas and suggestions from colleagues.

    Syntax Highlighting Contest

    Contest # 36 Syntax highlighting for Solidity files written for Free TON – VSCode has been announced.

    The use of the Solidity programming language on Free TON has its own specifics, so the syntax highlighting tools should be different from what was previously written for Solidity on Ethereum. Therefore, the goal of the contest is to develop new plugins designed to implement syntax highlighting for popular source code editors and IDEs.

    At the moment, the contest has already been launched and submissions will be accepted until September 20, 2021. Participants in the top 10 will receive awards. The first place award is 50,000 TON.

    At the online meeting, the speakers explained that the requirement to use the VSCode editor is due to its simplicity and widespread use. Therefore, the first stage applies only to MS Visual Studio Code. However, after the first stage, a vote is planned to select the most popular editors and IDEs. After that, more contests will be announced.

    Proposals for Notification Service Contests

    The participants continued the theme presented at the previous meeting. They discussed the idea of creating a notification provider with the ability to send notifications via HTTP as well as send push notifications to mobile devices.

    You can read about the initial idea here.

    In general, the proposed architecture looks like this: there should be several independent queue providers and separate from them a notification service, several notification providers. On-chain events are monitored by queue providers. There are several queues, and notification providers select events from these queues using specific criteria and send notifications to users.

    It is suggested to start by creating a notification service, since there is already one queue provider from TON Labs that can be used to develop it (the Apache Kafka system is mentioned).

    First, the contest participants must register and pass authorization in the Kafka system, then integrate their solutions into the notification service provider. The end user should test the solution – enter the device token and specify the filter of notification by selecting the account to monitor. In accordance with the specified parameters, a notification should be generated and the provider should send it to the user’s device.

    Thus, the email notification service contest is scheduled first. In the future, they are planning contests to create queue providers and push notifications. So far, there is only a queue provider from TON Labs. But it is possible that teams like Broxus, RSquad, and others will want to compete with them.