Cloud Cover AMA | Blimp by Züs
Happy Wednesday, everyone! Tomorrow we will have our Cloud Cover AMA (Ecclesia #8), so make sure to attend as it will present the Blimp, by Züs, app. Blimp is an s3 compatible App for enterprises to transform their apps and websites for privacy, higher performance, and 100% uptime. Make sure to attend on Thursday, January 26th, at 9am PST. Now let’s dive into this week’s update!
Mainnet timeline
As of now, 124 outstanding issues need to be addressed before the Mainnet launch. The team expects to close 20 per week, finishing by March 15th, with Mainnet starting on March 31st. The timeline will be updated based on the pace of activity, as some issues take longer to close. There may be more uncovered bugs to be addressed, as well.
Storm of the Week
Messari DePIN
After our stunning community engagement with Messari, mentioned in the last update, we were featured on their Decentralized Physical Infrastructure Network (DePIN) list. Check out their current DePIN map here. Thanks again for the effort! In the coming years, DePIN will be essential for decentralization, as Web2 enjoys the benefits of Web3, such as privacy, cost-efficiency, security, and transparency.
Data Breaches reaching record levels in the US
Recently the Identity Theft Resource Center, a renowned non-profit institution that supports victims of identity theft, released a report on the data breach. Of 2022, revealing an increase of 41.5% from 2021 and a staggering 422.1 million victims. Also, most of the data breach notices did not provide enough details for their victims about the event. Only 34% of the notices provided victim and attack vector details.
Other shocking findings:
- 55% of social media accounts have been compromised, including 42% of Facebook and 32% of Instagram users.
- 16% of respondents didn’t act after a data breach notice, leaving them and their employers vulnerable to identity crimes.
- 48% changed the password only on the breached account; only 22 percent changed all of their passwords.
- Only 15 % of respondents say they use unique passwords for each account; the other 85% admit to reusing passwords on multiple accounts.
- When asked why they didn’t act after receiving a breach notice, 26% said, “my data is already out there;” 29% believed organizations responsible for protecting their data would address the issue; 17% did not know what to do; 14% thought the notice was a scam.
Results
These results highlight that nobody using the internet has their data secured. Few are taking steps to protect their data. Many people are not concerned or taking precautions to prevent or for damage control. For example, even after being notified about a breach, some do not even change their password. About half change only in the affected platform! Institutions worldwide should take this as a sign to educate more people on the matter to prevent harm if you consider that most people are already compromised. It is time for businesses to be held accountable as people struggle with identity theft and scams.
That said, data breaches could be easily avoidable with decentralized storage solutions like Züs.
Blockchain Team Update:
Last week the team mainly focused on bug fixes to approach the mainnet delivery. The team set up the testing process for doing unit tests for postgres database. With these tests, it will be possible to write and run tests that are event database related much easier on both local and CI. Previously, to run tests for the event database, they had to manually set up a postgres instance locally, comment out the `t.Skip()` code on tests and, configure the database set correctly, then run the tests. Also, the test could not be run on CI. However, with the PR, the team can simply set up an ad-hoc database instance when writing tests with the code below, and each test can have its instance run concurrently.
“`
db, clean := GetTestEventDB(t)
defer clean()
// init db tables with data
// run tests to update the db tables
// verify the changes
“`
With this, the team can perform unit tests for event database just as efficiently as other tests without the need to mock the sql.
Code Review and Merged Partition
Beyond the unit test setup for the event database, they also finished the code review and merged partition location PR. In the meantime, they put effort into fixing the system test errors on PR, which has been open for a while. During the system tests fixing, the team detected another ‘state hash mismatch’ error, which was luckily fixed before it got merged.
There are also a few other issues that got fixed. Check for details below:
- Fixed the `zcn.Mint` panic caused by zero division. This happened when there was no authorizer getting registered and not checked.
- Fixed the uint64 overflow issue on updating the open challenge stats for blobbers.
- Added last updated field to miner, sharder and delegate pool, `/nodeStat` Get miner sharder and stake pool in the same query to ensure self-consistency.
- Added a conductor test that checks when a miner is able to proceed to the next round if it has missed vrf phase and ignores notarizations.
- Added total_rewards to aggregates.
- Fixed issue [#1899], which is introduced when we try to calculate the step for taking data points from, which end up in floating point numbers that we convert to integers.
- Removed duplicate transfer event emit.
- Replaced the `gorm.Model` with a custom model to mark tables as immutable when needed.
- Fixed a flaky zcnsc service fee unit test.
Read Züs’ most recent article:
Have you ever wondered how Decentralized Storage works? If you are looking for a way to improve your database or marketplace, decentralize your web application, or simply want a more secure and efficient way to store data, then decentralized storage may be the right choice for you.
Set your calendars now to learn more about the Blimp app, by Züs, on Thursday, January 26th, at 9am PST.
