🛠️Bridge
- Был протестирован функционал Enex.Space и его работа с последними обновлениями, было найдено и исправлено пару ошибок в UI;- успешно завершили все тесты по функционалу бриджа и интеграционные тесты в том числе.

🛠️Pulse Network
- Были получены репорты о низких показателях доходности при майнинге, причина была в нестабильном выходе блоков и на данный момент она устранена.

Сайт| Скачать Мастерноду | Кошелек ENQ | Medium | Блокчейн Эксплорер

Команда Enecuum рада сообщить об успешном завершении процесса голосования по алгоритму генерации тикера для токена, выпущенного в сети назначения с использованием бриджа.

По итогам голосования был выбран вариант "Change logic. Save the original token’s ticker in the destination network" , он набрал наибольшее количество голосов - 537 923. Исходя из этого, мы изменим алгоритм генерации тикера для токенов и не будем добавлять префикс SB.

Результаты голосования на момент снимка:
- Save current logic. Add “sb” prefix to token’s ticker in the destination network | Общий стейк = 15 ENQ
- Change logic. Save the original token’s ticker in the destination network | Общий стейк = 537 923 ENQ

Спасибо нашему сообществу!
Мы высоко ценим активное участие и вовлеченность сообщества Enecuum в этот процесс. Ваш вклад и отзывы бесценны для нас, и мы по-прежнему стремимся поддерживать атмосферу прозрачности и сотрудничества, продолжая развивать и наращивать платформу Enecuum.

Сайт| Скачать Мастерноду | Кошелек ENQ | Medium | Блокчейн Эксплорер

🛠️Была устранена нестабильность в работе с валидаторов о которой мы сообщали на прошлой неделе в отчёте разработки.

🛠️Запустили голосование касающееся префиксов токенов которые выпускает бридж в сети назначения.

🛠️Готовимся к мёрджу функционала сети BIT с сетью Pulse Network.

Сайт| Скачать Мастерноду | Кошелек ENQ | Medium | Блокчейн Эксплорер

🛠️Bridge

- От комьюнити поступило предложение отказаться от префикса для обёрнутых токенов, скорее всего это предложение будет вынесено на всеобщее голосование.

- Приняли решение не предоставлять Docker образы заранее для PoS нод с целью ускорения бриджа.

- Готовим тестовое окружение c копией сети Pulse для тестирования функционала бриджа.

🛠️Сеть BIT

- Произвели обновление сети. Пришлось удалить историю транзакций. Цель обновления - добавить индексацию данных и API для блокчейн проводника с функцией предоставления истории транзакций по бриджу.

- Наблюдается нестабильность в работе валидаторов - ищем причину.

🛠️Chrome Extension

- Была улучшена обработка переключения аккаунтов в расширении для Chrome, готовим к релизу новую версию.

Сайт| Скачать Мастерноду | Кошелек ENQ | Medium | Блокчейн Эксплорер

🛠️Bridge

- Продолжается работа над стат.сервисом, в рамках этой работы мы модифицировали несколько аспектов бриджа.

- Получили и обработали отзывы от комьюнити после тестирования бриджа в сети BIT, огромное спасибо за ваши фидбеки.

🛠️PWA
- Ведётся работа над разделом по взаимодействию с PoS.

Сайт| Скачать Мастерноду | Кошелек ENQ | Medium | Блокчейн Эксплорер

🛠️Bridge

- Последняя версия бриджа работает в сети BIT, поэтому у комьюнити есть возможность его тестировать. В данный момент команда сосредоточена на доработке истории транзакций, для этого мы разрабатываем стат. сервис.

- Для работы с бриджом мы обновили расширение для браузера и ios app, обновление для android появится в скором времени.

🛠️PWA

- Ведём работы над добавлением раздела по взаимодействую с PoS в интерфейс PWA.

Сайт| Скачать Мастерноду | Кошелек ENQ | Medium | Блокчейн Эксплорер

🛠️Bridge

- Трудности с EVM сетями о которых мы рассказывали на прошлой недели были успешно разрешены. Приступаем к интеграционным тестам и тестам пользовательского интерфейса.

Касательно запуска бриджа: готовы дать оптимистичный прогноз о запуске через неделю, если не столкнёмся с какими-либо трудностями.

🛠️PWA (Android)

- Продолжается работа над добавлением PWA в PlayStore, на текущем этапе осталось разобраться с модерацией.

Сайт| Скачать Мастерноду | Кошелек ENQ | Medium | Блокчейн Эксплорер

🛠️Мобильная разработка
- работаем над добавлением приложения PWA в Google Play.

🛠️Мост
- обновление прошло успешно в сети BIT, но мы столкнулись с небольшими трудностями на стороне EVM сетей, сейчас занимаемся устранением неполадок.

🛠️Стабильность сети
- Мы получили репорты о переодических сбоях в частоте выпуска блоков в сети Enecuum, мы нашли причину сбоя и оперативно устранили её.

🛠️Партнёрства
- ведём переговоры по различным направлениям с компанией производителем смартфонов, поделимся новостями в скором времени.

Сайт| Скачать Мастерноду | Кошелек ENQ | Medium | Блокчейн Эксплорер

Serge: [00:00:01] Today I will be alone because man doesn't feel well he's got a bit high temperature something like this but nevertheless let's start and our first. The news is about. Any of them. Space Bridge. So. So this week we started deploying final version to BIT Network, but it didn't work out perfectly. So we got troubles with initializing transactions, coding. So we investigating the issue. And our current version of the cause of the issue is that we need to update. Assigning library. It's. And transaction data section. Uh, handling code. So currently in network. Space bridge is not working. So we discarded previous version, but new version is not initialized. So currently it is not it's not functioning, but we continue to work on it and it is a practical side and so theoretical aspect. We finally published any technical proposal ETB eight that describes theoretical or algorithmic side of space bridge, so you can check it in our docs GitHub Repository. Feel free to comment on it. Maybe you can make some valuable additions. So it's open, open source. And now you can we can discuss the specs that we made public finding. Um, so there are other. Events that were consuming our our force and mind intentions. And that is connected with a discrepancy in time between blocks.

Serge: [00:03:19] So last couple of days, main network, they were in random events of enlarged delays between blocks. So it didn't require any intervention from our side to like help blocks to happen. But these delays, it's not how we're supposed to work. So we investigate the cause of these delays. So maybe it's just some repetitive pattern of publishing blocks more frequently than it should. And then when this increased frequency accumulates, then our model that is responsible for time, difficulty and mining, difficulty and time time between blocks tuning, this model may be decides to make some kind of pause to compensate this increased time between blocks to make it in general equal to target time of 15 seconds. But it's only one of the versions, so it's not like our final state just I give you an idea and we're investigating it. So on the other hand, there were reports of incorrect behavior of the application in case of rejecting transactions. So we found the found the reason of this issue. We made a fix and now we are testing this new version and preparing it for. For deployment for the release. So it will be done as soon, I think, the beginning of the next week. Um. Yeah. So. We were planning to have a special guest today also.

Serge: [00:06:03] But again, this episode of News not happening as planned. So special guest, I hope will be next time. Because he has some health related issues also. I hope we we we can meet next week. So I'm I moved to questions sections so we've got some, uh, we received some questions during this week. And let's start first. Two of them are. Why is all this taking so long and why the bridge launch delayed? And the next question also about annex or other things. Update So people not happy with the speed of development team. So. As we described in our previous episodes and answering questions sections. There are a lot of complicated stuff happening around the breach and it has a really big, big importance. And that is why. We are not in a hurry with this bridge stuff. So also it was a big extensive rally at the end of previous year, and most of the team were were exhausted. So some people went to vacations. For example, I had two weeks of and it was first vacation for a very long time and a couple of other developers also. He got the pause. It's another reason to to like, refresh, refresh your brain before making important decisions. I mean, bridge launch. So it's also takes time and.

Serge: [00:09:05] Uh.

Serge: [00:09:07] So to the next question. Why am I unable to mine on my mobile phone app any longer? So it is hard to tell from the question whether it is about mobile masternode application or is it about PWA. So nevertheless, my third suggestion is to try another another app. So if you have troubles. We the Master Node app. Please try a PWA application. If you have trouble with the PWA, check. Master node. So we have planned release for master Node app which will update support of new newer android version. So maybe the the. If the question is about any master node, maybe your mobile phone received a over the air update of Android operating system and or two or maybe three latest Android OS versions. They had some. In some issues with Master Node, the current master node version. So I think we got like a test build and maybe we can share this test build and you can try it. It is not released yet because we, we plan to, uh. Update management of any nodes discovery with the update of master Node app. So it makes some transition and easier transition between various nodes and there is versions of PWA or PA apps. Master Node and PvP. So to make them both work in similar way. So it is called like Node update. It is just planned long ago actually, but. And we always have some more. Some task of higher priority. So it's still waiting. Its time unfortunately. Couldn't make everything at once. Um. Yeah. So that's all questions from, uh.

Serge: [00:12:06] Form.

Serge: [00:12:07] Question form. So do we have any in chat?

Serge: [00:12:13] Let me check it. Uh. I don't see.

Serge: [00:12:19] Then thank you for your attention and thank you for your interest in Enecuum. And let's meet next time, I hope, with ramen together and special guests and.

Serge: [00:12:37] Yeah.

Serge: [00:12:37] Bye bye.

Roman: Hello everyone, and welcome to the News Digest. We are expected to share with you the latest developments news and events that have taken place with our team and project over the past week.
As a short reminder: you can ask your question in several ways by raising your hand in the Q&A sections in the voice chat, writing your questions in the Telegram chat or submitting it through the Google form. The recording will be available as usual in several hours after the end of the news episode. And our special guest today is Constantin, who will be discussing the bridge and answering the questions from our community.

Konstantin: [00:00:22] Hi, guys.

Roman: [00:00:24] So first, before we will dive into the bridge topic, let's have a quick update on some of our products. First of all, about EnexSpace and here during the week we made some improvements and addresses, minor bugs and as the result yesterday and a couple of days before opening Enex Space could be unavailable. But now it's quite more stable and smoother. So let's move to the second news. And here we pleased to announce that we have distributed all the bug bounty rewards to eligible participants, and all the rewards in ENX were distributed in Ethereum network and who took a part in our bug bounty check your wallets and you will found some ENX there. Yeah. And let's move on. And let's move to the bridge And Konstantin, please tell us about the progress and what's happening.

Konstantin: [00:02:07] Yes, all the code is written at the moment. So at the moment we are testing bridge in closed alpha testing. And in view of recent hack we are trying to improve our security and strengthened, strengthened to the maximum. So our goal is to prevent these incidents from happening again in future. and save our users from financial losses. So that's that's why testing is taking so much time. Uh, and the status is, I think that next week we will, uh, release our bridge in public beta or closed beta. But I don't, we didn't decided yet. I mean, local testing will be completed.

Roman: [00:03:37] Yeah, Serge! Maybe you have something to add.

Serge: [00:03:44] Yeah. Also, we we're finalizing our documentation or core explanation of the core of the bridge protocol. During last weeks, we found several parts of this document. To be clarified to make it more straightforward, to understand the bridge functionality. I hope we will publish the this documentation also.

Roman: [00:04:40] Yeah. Thank you, Serge. And let's move to the questions about the bridge. First question is about timing.
"What about the bridge? when the code review will be finished?"

Roman: I guess we already answered this question. Or maybe Serge, you have something to add.

Serge: [00:05:07] It is important to say that it is our internal review and audit, but it to fully rely on the bridge we need certainly external audits but for now it is too expensive. Form this check. So that's why. We take additional time for internal testing. And we hope that when we run, when we deploy the bridge, it will help us to find additional interest in it and it will help to find. Uh. Or funds to make external security checks. Thank you.

Roman: [00:06:22] Yeah. Thank you, Serge. And the next question is
"Did any critical vulnerabilities were found during our internal code review?"

Konstantin: [00:06:35] Oh, of course, critical. They were founded at the initial stage of testing. That was the purpose of our testing. Basically, it's not architecture flaws, but some typos or forgotten private keys and stuff like this. So like, it was the first stage of our audit to make some code clean up. So it was like a silly mistakes, not security flaws or architecture or bad architectural decisions.

Roman: [00:07:25]. Thank you, Konstantin. Let's move to another questions. And the nexy question.
"Why so much silence in Spanish? They'll do events. But what they and why the price is falling so much"

Roman: So first of all, now we saving our costs and we reduce our activity. So it's a temporary decision. So and as soon as possible we will continue all the marketing activities and about the price. As I said, in case of reducing marketing activities, we have some let's call like we count who decided to sell. So it's their choice. But we anyway continue working on the project and hope we will makes our community much more happy in the near future. The next question is
"What problem does Enecuum have today?"

Serge: [00:08:52] I think I have another question that might be an answer to this. So why do people invest and buy some meme coins, but not coins of technological startups? So I really don't understand how it works. So I think this is the main problem with Enecuum. But maybe I just it looks like only from my point of view, maybe there are other opinions.

Roman: [00:09:35] Let's move to another question. And the question is about the
"I'm a member of the team of collaborators, and it seems unfair to me that the program is suspended"

Roman:So it's a temporary decision to close all our work programs and we will continue it as soon as possible. And then that's all the questions, because here we have one more question about the silence and about the bridge stage and one more question about events in Latam. So as I said, we will have events in Latam soon and we will announce it and Rafael will announce it In the near future. So if someone has a question, please feel free to raise your hand or type it in our chat.

Roman: Now I see that there are no additional questions. So thank you, Serge. Thank you, Konstantin. Have a great weekend.

Serge: [00:10:59] I'd like to add one more thing. Sorry. Okay, no problem. There were questions about labeling active and inactive mining tokens in Explorer, so there were some inconsistency after the change of the some minimal balance to how to enable mining slot. So we are investigating what is happening. So we made changes to display these labels correctly, but we made it in a like quick way. But now we. In checking why there were this problem of incorrect labeling. So for people who are asking these questions. So we're working on on your request. Thank you.

Roman: [00:12:13] Yeah. Thank you, Serge. And the question was from JTaylor, as I remember. Yeah. From JTaylor. Yeah. Thank you guys. Have a great weekend!

Serge: [00:12:29] Bye-bye. Thank you.
Konstantin: Bye-Bye