The meetup participants suggested solutions to the issue of insufficient voting signatures, discussed how contests are being announced in various media, and conducted a mini-blitz on topical issues of interest within DevEx Subgovernance.
Voting Signing Issues
Every time there is a vote (judging a contest or conducting a transaction), there is a problem with the signing: not all initiative Subgovernance members participate. Alexander Khramtsov suggested that perhaps the issue is in the interface — you need to be present at the computer, and often it is not possible.
Besides, you have to enter the password, and the seed phrase has to be stored somewhere. If the question of where it is comfortable and reliable to do this (for example, in a verified password store) is successfully resolved as suggested by Alexey Novikov, it is possible to vote through an open-source web interface.
For example, Ivan Kotelnikov wrote push money. “It’s not a very super mega-comfortable interface, but it’s simple, like a rifle, and it works — you can see everything there”, Alexey explained. “You can do everything through your smartphone, you don’t have to be at your computer”.
There was also a suggestion that it might be necessary to remove those who never vote from the list of initials. Mitja admitted that he simply does not have time for this, so he doesn’t mind if he is “expelled”. But he will continue to participate in meetups. In place of Mitja, they decided to include Sergey Tyurin in the initial members of DevEx SG.
Contests Announcements In Different Media: Current Status
Alexey Novikov reported they started to make a table with three Subgovernance: Influencers, SMM, and Community Voice, which is planned to include a list of all media in which there will be announcements. And it is important that for each media one representative of the above SGs is assigned as a responsible person.
“In the coming contests we’ll add a clause stating that we distribute the money among these Subgovernances according to the active users on these resources”, Alexey added. “And then they divide it as they see fit”.
Questions And Answers
Presentation of the Free TON wallet as a Chrome extension contest
A proposal was made to hold a separate AMA session for all 13 participants of the Free TON wallet as a Chrome extension contest so that they could present their solutions.
According to Alexey Novikov, it will be enough to give 7 minutes for the report, and then to post the recording on YouTube and if necessary to ask questions. The meetup was scheduled to take place in a week (June 3).
Attracting new judges to zkSNARK contests
Two members of Formal Methods Subgovernance will be added to the zkSNARK contest jury. As Mitja mentioned, these are special contests that require certain skills, and people involved in formal verification are more likely to be able to do quality judging.
Let’s have identification!
Alexey Novikov believes that ideally, a person should use the same nickname in zoom as in Telegram. To make it easier to identify one or another participant in the meetup.
DevNet: What’s wrong?
Sergey Tyurin asked why DevNet does not want to synchronize? According to Sergey, there were corrupted archives: “While the network was hanging on 11 validators, blocks were not produced, somehow only shards lived weirdly…” Catherine Pantaz asked to send her the logs.
Techblitz: Questions to Mitja Goroshevsky
- What about the Rust Cup?
It’s a process that takes time. We have four edits, and they all need to be tested consistently. CI broke on the slashing yesterday. While we were uploading, dealing with versioning, we didn’t have time to test the slashing. Along the way, our front crashed on the test so that it no longer shows us TPS. Because of that, we had to write a patch in a node so that it will capture TPS separately in the metric. Because if a front crashes, we’ll know what’s up with TPS. It all has to be uploaded to the master…
- Has the Arango been dealt with?
Dapp does not keep up with the speed, but now there are other tasks. Parallel development is in progress, and sometimes this causes a conflict. For example, we need to load in the Rust Cup. But in production, we will not have such a load for another two years, if not more. There is no point in prioritizing work on a highly loaded blockchain across the entire pipeline of our products right now. So we are putting in a “kludge” just to figure out that there is a TPS there.
- Database: is anyone still working on it?
I keep looking at who came up with what databases. It’s not about choosing a database. If you take the architecture of a modern database, they’re all about the same at the bottom. They usually have RocksDB as a storage QL, and they add everything to it: graph, document, SQL…
We now have deployed on all fronts, now if you count all RocksDB on the front node — there will be at least three. And we move from one RocksDB to another, going through everything… And we have to cut it all out and leave one RocksDB. And in the same node to make GSON-objects from the tree and put that back to RocksDB and return to TVM, using methods. And then put any query engine directly in the node, a layer between RocksDB and TVM, adding to TVM a search instruction.