I suggest to reduce Jury Remuneration Fund by five times - to 2 000 * 3 = 6 000 * 4 = 24 000
We supposed to keep 5% of contest budget as it works in main governance. If budget for whole contest about 50000 than jures will receive 2500 and etc
I think it’s reasonable just because it’s techinal contests which require downloading of code, running, testing and etc., not just vote.
Думаю девопс нужен, куда же без него. Конечно это будет дербан бюджетов, без этого никак, но иначе развитие застопорится.
1 Like
I think this direction is very important for whole ecosystem!
2 Likes
Half of the document is devoted to juries and how juries led by the initial members will be spending the budget tokens. As Mitja correctly put it recently - juries should be separated from and independent of Subgovernances. Not chosen by Subgovernance. The main role of juries is to provide an expert appraisal of the contestant work and not to participate in distribution of funds. Lets cut out the Jury part from the proposal and see what remains.
5 Likes
We already have Dev Experience Governance. Why duplicate? It looks so that the sub-government is created for the sake of the sub-government. In fact, the main benefit from this will not be for the community, but for the organizers of this sub-government themselves. Such global and important contests as the search for new validators for the mainnet are best left to TON Labs, which everyone trusts.
1 Like
It looks like a fait accompli, at least because it is not in the proposal section, but in the one created for these needs 
Decentralization pure 
Did the initial members even sign the DoD?
DevExp already have 5 or more directions, initially we thought the same way and have plan to organize a group inside DevExp, but DevExp already overloaded that’s why we decided to go this way. Just to scale development
This part of ecosystem is very important. But we already had something very similar here: Validator Contest: Devops tools [Finished]
Now subgov, whats the difference?
The proposal is more about jury rewards, not the tools themself.
Agree. Just discussed that on today meeting, I totally agree with this idea, but for now we don’t have such mechanic as I know. How we can proceed now without jury? I understand correctly that we can just create Jury contest and say that initial members can’t be in jury list, right?
Oh, I see. Initial members should not vote for jury selection, but who will vote? We can delete all about jury from the document but what to add instead?
Yes, it’s first devops contest, check the list of contents in our proposal, we have match more. Regarding jury rewards, we got it, we will completely remove jury section from the proposal. Initial members will not be in jury list. At least we can try to go this way
Very detailed and interesting Topics of Contests. I would like to take part in some of them. So I’m in.
But it is very important for the community to achieve all results published more widely. Maybe wiki, maybe some catalog, so everyone (even with currently pessimistic voice) will see the real results.
Please add some information about members into the proposal. You can take a look how Korean SG did it.
1 Like
Thanks! Working on it.
Thanks! Will rework a document little bit.
That is, these 4 people from Free TON DevOps Org will receive all the Organizational Funds?
for sure - no, we will rework this part of the document
Hi folks! Thank you all for your criticism and support. We updated document including all your proposals and corrections:
- We removed part regarding jury to separate members from juries
- Changed rewards for org works and etc
- Added additional info about gov members
- Created additional table with budget estimation for each contest
- We have devided whole requsted budget on 4 parts
We requst only first part, community will see results and only after that we will request budget for second list of contests and etc.
Please GOD not to TON Labs 
We need to get away from TON Labs and do this as a community. No opinion on the proposal, just isolating the TON Labs part. ))))
Free TON DevOps SubGovernance
Google doc - Free TON DevOps Governance - Google Docs
General description
This document suggests an implementation of on-chain governance for FreeTON DevOps as a separate interface with all the functions that the main Free TON governance has, based on https://freeton.org/contests as an additional bookmark.
The mission of the FreeTON DevOps governance is to improve the Free TON infrastructure, including FreeTON services, tools, and software with the goal of enhancing the Free TON ecosystem. Create a group of qualified juries to provide professional feedback and support in a DevOps field.
Build the FreeTON Application platform based on TON OS DApp Server to make Free TON more attractive for end users and ensure End-to-end Decentralization.
Governance proposal specification
It is proposed to create on-chain governance integration for Free TON DevOps within which the following will be available:
-
Free TON DevOps Governance Initial Members are to form the initial Free TON DevOps Governance for the next 4 months (until 1 of April 2021)
-
Further members of FreeTON DevOps Governance will be based on DevOps Governance contests and everyone who took places from 1st to 3rd may propose themselves to the government member
-
The max number of members of the Free TON DevOps Governance Org is 15, the min number is 10. The decisions within the Free TON DevOps Governance Org are to be taken by 50% + 1 vote.If the quantity of members will hit a limit, candidates can be able to join in the next cycle (equals 4 months)
-
The Free TON DevOps Governance Org has to ensure:
- smooth running of Free TON DevOps Governance;
- running of Contests;
- development and review of Contest Proposals (CP);
- distribution of funds to contest winners
- administrative work such as announcing Contests, inviting developers to apply for Contests, consulting developers, announcing results of Contests, consulting jurors, etc
- The Contests that are to be run by Free TON DevOps governance have the following characteristics:
- to be on the topics mentioned below;
- could be multistaged with the limited access to the 2, 3, N stage for the winners from earlier stages;
- to be launched by accepting CPs by Free TON DevOps Governance members;
- could be run in parallel;
The Free TON DevOps Initial Members are the following:
| Name | Telegram | Background | Public Key |
| Renat Skitsan | Telegram | DevOps with 5+ years of experience, Validator | dbab2a32120be106f1eb9dbd80ca7c87742f574f31a5d7f188f695efa47e5e6d |
| Senya Ostrovsky | Telegram | DevOps with 5+ years of experience, winner of previous DevOps contest, top 50 of DePool game | 9b5bcf6ccdb180da143fa9fa784abb8917efabda1dde9fddede28e392e4c1b43 |
| Artem Ryabov | Telegram | TON Labs | 498849b2c8881cb7ece1e92f965933d0780c2852eb8760d97c0eb7ce828dd02f |
| Mitya Goroshevskiy | Telegram | TON Labs | 6ff322ad669dfad2f396b98bdc8690cc49926f6a10cd7f10d07f031841cf09ef |
| Anatoly Ustinov | Telegram | DevOps with 20+ years of experience.
Enterprise infrastructure architect. Enterprise storage senior engineer. Enterprise virtualization arch\engineer Top 10 of DePool game on a low cost server ^_^ |
865a7eb0e94d2623135dc00f3c060efdc3211309e93b279ff7d4422c5f21195d |
| Serge Medvedev | Telegram | Software engineer, winner of the 1st DevOps contest, author of TONOS SDK bindings for Lua and Clojure, creator and maintainer of the freeton-staking-manager | 2aedb672fa9944bafca2a9517bd96b255e9e0da2ca8da4668b356320f34eb91e |
| Sergey Tyurin | Telegram | Engineer; C, C++, ... programmer; DevOps; admin of FLD network | 2c0ec55a109eb466d9db5ee7c3adb075e77627ade83ae17cea847671ab8f0a85 |
| Itakura | Telegram | Active community member | 9176985c03dd3aaaa8ba4952b775af86776412fe6ed99fe9ff366768967b92da |
| Vladimir Simonov | Telegram | Validator for Freeton and different current blockchain projects, Magister Ludi and Depool game winner, Devops as a hobby, E-commerce and retail projects CEO, International logistics and supply chain management. | 47280bcd8ec7f71dd189a374ba7fc0e8837eafbb61f073a1d12954232a4c0f10 |
| Anton Zavodovskyi | Telegram | DevOps with 5+ years of experience. | 7c560a506bfc0df38ac9f70bcecb21e70cdab72b0284c331f19099965aaa68b1 |
| Stanislav | Telegram | DevOps 5+ years. Free TON Validator. Python developer. 2nd place in Game0 of Magister Ludi contest, in top 10 of DePools Game. | a4ee077ead36bed587e9afbcb44fb1d652dc8d11e892a40c6374f129241c19f2 |
| Artem Moiseenko | Telegram | SRE, DevSecOps, AWS solution architect ~15 year working with linux system |
dfd9209078f2a72fc1cfac5591fc70caa121d831d4ac4306a026bd914abffc98 |
| Anton | Telegram | DevOps with 20+ years of experience.
Go developer. 1st place in Game0 of Magister Ludi contest, in top 10 of DePools Game. |
bb1f2e4671eeccfdaefc5e07437d32f08da1aa23fdcdd909a1dfe41fb23e2943 |
| Dmitry Summit | Telegram | Validator in Free TON and different current blockchain projects, Magister Ludi and Depool game winner, Devops, system analyst, CTO w/programmer background. | ef060a52434c315ea4f32e75d524c6634ebe10478fb09db5c667d22ce5e9912e |
| Ekaterina Pantaz | Telegram | TON Labs | c9ae3b1c6aca828864702999e7bf1bd6f760f62988e056a4ba3a6104cde5fc17 |
Free TON DevOps Governance multisig wallet
0:f92be05a0ff2aab349a0681c8f08d92e1d6dbd0ab791aa53b877c020c9c07202
Summary table
| Stage | TONs amount | When | Contests |
| 1 | 673 120 | Upfront |
|
| 2 | 560 000* | After completing previous stage |
|
| 3 | 448 000* | After completing previous stage |
|
| 4 | 448 000* | After completing previous stage |
|
* the list of contests and required budget can change depending on results of previous stages
Free TON DevOps Costs Estimate
This estimate is based on a forecast of the total Tons required to run all Free TON DevOps Contests within the 4 months (until 1st of April 2021) after the Free TON DevOps SubGovernance is launched.
| Contests Funds | Tons per Contest | Possible Contests per month |
Subtotal Tons
per month |
Total Tons per 4 months |
Contests Remuneration Fund:
|
200 000 | 3 | 600 000 | 2 400 000 |
Jury Remuneration Fund:
|
20 000 | 3 | 60 000 | 240 000 |
| Org Funds | Tons per Contest |
Subtotal Tons
per month |
Total Tons per 4 months | |
Administrative Fund:
|
4000 | 12 000 | 48 000 | |
| Total | 672 000 | 2 688 000 |
Topics of the Contests
The topics of the nearest Contests mentioned according to their priority
1) Free TON DevOps Jury Contest
Goal: attract professionals which will be motivated to grow and enhance the Free TON ecosystem by participation in the FreeTON DevOps SubGovernance structure. This will help achieve the goal of decentralized Governance 2.0. This is the first contest to be run by the FreeTON DevOps Initial Members.
2) FreeTON infrastructure development and support
Goal: build and support all the tools/services required for development and reliable operation of FreeTON infrastructure
Subtopics
- Deployment (using docker images as well as bare-metal) and release workflow for Rust/C++ fullnode, TON OS CLI and other tools/services/libraries.
- High Availability & Disaster recovery for the FreeTON services, backups and restores
- Performance and latency optimization for the FreeTON services. Performance tests
- Logging (collecting, parsing, anomaly detection and alerting). Logs specification
- Monitoring (availability metrics, performance metrics, High Availability, Disaster Recovery statuses)
- RTDB deploying/managing/support tools/scripts/instructions and etc
- Develop security best practices for FreeTON services. Node security standards (settings to mitigate the impact of DDoS attacks, сomplex system security settings, best practice of node install)
- Ton validators pool - a resource which will publicity in real-time information about validators - name, id, stack, total balance, staking tools, transaction confirmations tools
- Collecting technical wiki about commands, tricks, hacks for a node like manual sending stack, manual checking voting, etc.
Contests
- Packaging and releasing to public repositories (for any OS) the following tools (TONOS-CLI, tonnode(c++,rust), tvm_linker, etc)
- Scripts to create local environment for developers for Linux/OSX,Windows, compiler scripts for smart contracts, etc
- Developing non-docker TON OS Startup Edition deployment (Linux, OSX, Windows)
- Validator Failover Solution - Validator Redundancy and Network Availability
- Backups and disaster recovery solutions for TON Node (C++)
- Backups and disaster recovery solutions for TON Node (Rust) and TON OS DApp
- Design documents for security best practices (including OS system configuration, hardware and requirements for providers, signing transactions)
- Common practices for configuring systems with C++ Node, Rust Node and TON OS DApp Server for better performance and lower latency. Kernel parameters, network parameters, tuning OS, filesystems, optimizing hardware configuration and C++ Node/Rust node/DApp Server settings.
- Documenting Rust Node and TON OS DApp Server logging subsystems, categories of events and events severity. Identifying log patterns, corresponding to the most common anomalies, requiring attention. Collecting logs from Rust Nodes and TON OS DApp Servers. In-depth analysis of logs collected. Real-time monitoring of logs, detecting anomalies and alerting
- DePool monitoring (balance, slashing, efficiency)
3) Free TON E2ED Application platform
Goal: build a decentralized platform for developers and businesses to make it really easy to develop, deploy, monitor and access their DApps based on the FreeTON network, ensuring end-to-end decentralization for each user
Subtopics
- TON OS DApp server endpoints information availability on-chain. Implement TON OS DApp server reliability metrics (сlients should use the most reliable ones)
- Mechanism for clients to discover and access TON OS DApp server endpoints in an anonymous and decentralized way.
- Specification/Design of technical requirements/characteristics for FreeTON E2ED Application platform (e.q acceptable latency/delay for user experience, throughput/performance)
- Develop an easy to use tooling for creating and deploying TON OS DApps
- TON OS DApp server reliability contest (needs economical model first)
Contests
- Design reliability metrics for TON OS DApp server endpoints
- TON OS DApp server reliability game (needs economical model first)
4) Economics & monetization/rewarding
Goal: find a way to make it attractive to join and become a provider of TON OS DApp Servers / Oracles / Databases. Build a monetization and rewards model for supporting TON OS DApp server infrastructure / Oracles / Databases
Subtopics
- Design economical model for L1 E2ED Application Platform (rewarding of running TON OS DApp servers based on FreeTON network fees)
- Design fees price in terms of estimated complexity of the query, size of the query response, latency or any other parameters
- Design reliability metrics for TON OS DApp servers and slashing conditions based on them (e.q. big latency, response an error, malicious responses)
Contests
- Design economical model for L1 E2ED Application Platform (rewarding of running TON OS DApp servers based on FreeTON network fees)
5) Validators contests
Goal: to build and debug Rust node validator infrastructure. Run contests to compete in validation cycles
Contests
- DevOps Rust node contest
- Rust node debug contest
- Rust node validators contest
Costs estimates per Stage
(1 Stage ~ 1 month)
| Contest | Participants reward | Jury reward | Org reward | Total |
| Free TON DevOps Jury Contest | 1000 | 100 | 20 | 1120 |
| Packaging and releasing to public repositories (for any OS) tools like TONOS-CLI, ton-node(c++,rust), tvm_linker, etc. | 100 000 | 10 000 | 2 000 | 112 000 |
| Scripts to create local environment for developers for Linux/OSX, Windows, compiler scripts for smart contracts, etc | 100 000 | 10 000 | 2 000 | 112 000 |
| Validator Failover Solution - Validator Redundancy and Network Availability | 200 000 | 20 000 | 4000 | 224 000 |
| DevOps Rust node contest (tooling, automation scripts, validator monitoring) | 200 000 | 20 000 | 4000 | 224 000 |
Stage 1 |
673 120 | |||
| Rust node debug contest | 200 000 | 20 000 | 4000 | 224 000 |
| Rust node validator contest (MLudi game for Rust validators) | will be requested additionally | |||
| Developing non-docker TON OS Startup Edition deployment (Linux, OSX, Windows) | 100 000 | 10 000 | 2 000 | 112 000 |
| Design economical model for L1 E2ED Application Platform (rewarding of running TON OS DApp servers based on FreeTON network fees). | 200 000 | 20 000 | 4000 | 224 000 |
| Stage 2 | ~ 560 000 | |||
| Design documents for security best practices (including OS system configuration, hardware and requirements for providers, signing transactions) | 100 000 | 10 000 | 2 000 | 112 000 |
| Common practices for configuring systems with C++ Node, Rust Node and TON OS DApp Server for better performance and lower latency. Kernel parameters, network parameters, tuning OS, filesystems, optimizing hardware configuration and C++ Node/Rust node/DApp Server settings. | 100 000 | 10 000 | 2 000 | 112 000 |
| Design reliability metrics for TON OS DApp Server | 200 000 | 20 000 | 4000 | 224 000 |
| Stage 3 | ~ 448 000 | |||
| Backups and disaster recovery solutions TON OS DApp | 200 000 | 20 000 | 4000 | 224 000 |
| Documenting Rust Node and TON OS DApp Server logging subsystems, categories of events and events severity. Identifying log patterns, corresponding to the most common anomalies, requiring attention | 200 000 | 20 000 | 4000 | 224 000 |
| TON OS DApp server reliability game (needs economical model first) | will be requested additionally | |||
| Stage 4 | ~ 448 000 |
Disclaimer
Anyone can participate, but Free TON does not distribute Tons to US citizens or entities.
3 Likes