The system applied in Databloc is based on Blockchain Technology

DataBloc is the ninth generation of the blockchain developed by Stonefly with a fund of 40 million USD and worked on by 16 competent engineers. Its main founder is Griffin Rolander, Jacob Watton, Isaac Schlenker who has experience in software development in the financial sector, especially the Blockchain. And there are also several teams divided into professional teams, six market researchers, software development, and advisors. DataBloc is also known as Stone Cushion. The statement is that StoneCushion is not software that has Cryptocurrency-based financial transactions. Unlike the case with DataBloc, which is a cryptocurrency-based storage media utilizing Blockchain technology.

Stonefly has been built since 2006 and has spread to five countries, San Francisco, San Diego, Washington DC, Boston and Pakistan. Given that these five countries are countries that are very familiar with the world of technology and have started to enter the Asian market. The level of security of the DataBloc itself is evident from the collaboration with 2000 intended customers Diney, Wells Fargo, US Navy, and US Army.

So that DataBloc provides optimal and quality data storage quality, guarantees availability, provides quick access and provides secure information security.

The cloud system is currently divided into two types, claude services are centralized and decentralized. Centralized claude services can reach all types of services. Which if low performance offers will be subject to low costs and vice versa. But for companies that have more exclusive needs, they will certainly use high performance offers because the company must have a high security system as well. But all of that also does not guarantee its security even though the funds issued by the company are also quite large. Similarly, a decentralized cloud is used to store individual user data but is also vulnerable to erratic services.

Unlike the case with the DataBloc Platform that offers cloud permissions. With the claude system that is permitted, the company will only pay the minimum cost because it does not need to build and maintain a data center. Especially with Blockchain superior security and distributed nodes. This is thanks to the collaboration between DataBloc and Stonefly which has served around 2000 customers for various types of storage and certainly will increase the profitability of the company.

Each company must have different specifications and needs, therefore DataBloc as a digital data storage platform strives to always understand it. The needs of large companies and small companies are certainly very different. Newly developing companies certainly cannot produce as much data as large companies. But DataBloc will always adjust according to the development of the company.

DataBloc also offers a number of Bounties, which free tokens will be obtained after making promotional efforts. The types of tokens offered are

Ticker stone is a utility that interacts with the Databloc cloud that represents DataBloc to interact with company products and services but not for investment because it does not guarantee return on investment. But if more and more networks are growing, there will be more and more values in the tokens.

Hardcape sale Token amounting to 100,000,000 USD. This Hard Cap Token is the maximum amount of profit predicted.
Total token: 333,333,333
The budget for Bounty is 16,666,666
Prize of 5 percent

The token bidding process through the Bounty method is done so that users who want to get free tokens can promote the DataBloc platform. The distribution of this free token is not a loss for the company or DataBloc platform. Because the strategy used initially was to make offerings of tokens as attractive as possible in order to attract a large number of users to introduce more to the general public and companies known about the functions of DataBloc and interested in using this platform.

Published at Sun, 07 Apr 2019 05:46:02 +0000

November 12, 2017

De-briefing Ethereum’s Parity Predicament: What’s Next?

After an unidentified actor “accidentally” triggered a series of bugs that destroyed approximately $150 million worth of digital currency, the world waits for a substantive answer — is this vulnerability an anomaly? An “I told you so”? Or a humbling opportunity to secure the Ethereum network?

What Happened?

On November 6, “Devops199,” an alleged amateur programmer, set off a chain of bugs on Parity, a popular digital wallet for Ethereum. These bugs affected multisignature, or “multisig,” accounts — “wallets” that require multiple users to sign off with their keys before funds can be transferred.. The place these wallets connect to is known as a “library” contract.

According to Parity, an attempt to fix a vulnerability that allowed hackers to steal $32 million from multisignature wallets in July of 2017 inadvertently created a second vulnerability in the library contract. This allowed Devops199 gain sole ownership of the library that every multisignature wallet used for their code.
After Devops199 realized what had happened, he “killed” (deleted) the code. Unfortunately, this locked all funds into multisignature wallets permanently, with no way to access them.
Because of the functionality of the current blockchain, $150 million worth of ether (ETH), the tradable currency that fuels the Ethereum platform, is now effectively destroyed and inaccessible to anyone.

Among the victims of this bug are several recently successful ICOs that chose to store their funds in a Parity wallet because of its multisig option and compatibility with various hardware wallets.

Parity’s Response (So Far)

On November 7, tweets on Parity’s official Twitter account acknowledged the vulnerability and confirmed that the funds affected are frozen and can’t be moved anywhere.

A day later, on November 8, Parity de-briefed the bug, explaining that it was indeed possible to turn the Parity Wallet Library contract into a regular multisig wallet and become the owner of it, which is exactly what Devops199 did. Parity now has a tool to check if a user/wallet has been affected by the vulnerability.

Parity’s History of Hacks

This isn’t the first time Parity has fallen victim to a security exploit. Parity’s multisignature contracts were previously the target of three thefts totalling 150,000 ether in July of 2017 (the second-largest hack after the DAO fiasco). And losses could have been exponentially higher. However, the “White Hat Group,” a collection of hackers and activists, was able to intervene and drain the majority of other wallets before they could be compromised as well.

Future multi-sig wallets created in all versions of Parity Wallet have no known exploits.
– Official Parity website post following the July 19 hack

Jeff Coleman, an expert in blockchain technologies and currently a researcher and advisor with L4 Ventures, described Parity’s response to the July 19, 2017, attack as having been “worrying, to say the least.”

Coleman told bitcoin Magazine that his primary concerns centered around Parity’s inadequate response and its tendency to downplay the significance of the compromise, choosing instead to blame a large number of external causes:

They blamed observers for not finding the bug before it was exploited; they blamed lack of incentivization for observers; and they blamed the Solidity language for not blocking access by default to the functions the [Parity team] failed to protect.

He further noted that Parity seemed to be blaming the complexity of the well-audited wallet (which they still believed to be secure) from which they had originally modified their code. And also that Parity didn’t take responsibility for their own inadequate quality control and audit procedures.

S.O.S.?

Developers in the community are desperately trying to find a fix to the Parity predicament. Coleman believes that “from a technological perspective, there is nothing short of a hard fork [a non-backward-compatible change to the Ethereum protocol] to restore the destroyed funds.”

After the DAO hack in 2016, the Ethereum Foundation had already accepted a hard fork to restore lost funds, with the common understanding that this was a sort of “mulligan” — a one-time fix for a young, developing blockchain. This scenario, nevertheless, divided the Ethereum blockchain into two parts and created Ethereum Classic, the original Ethereum blockchain, backed by a community that vehemently opposes editing transaction history to restore lost funds.

Using hard forks as interventions to “correct” worst-case scenarios like this is highly controversial, especially since blockchains are meant to be immutable. So, it’s difficult to convince the Ethereum community to use a hard fork to rescue one team from a mistake. While many acknowledge sympathy for smaller accounts storing personal ETH, sentiment is not as sympathetic for the 300,000 ETH that belonged to the Polkadot Project, project associated with the Parity team.

Arseny Reutov, an application security researcher for blockchain security firm positive.com, affirmed this community sentiment, while acknowledging that hard forks can be solutions. However, he agrees that Ethereum cannot simply hard fork any time there is a problem on the network. He believes blockchains should expect “more and more high profile thefts and incidents,” and that the problem lies in the infant Ethereum platform itself — specifically, in the native Solidity programming language.

If a Hard Fork Isn’t the Answer, Then What Is?

Both Coleman and Reutov believe that the key to gaining the community support necessary to restore funds is to combine the Parity situation with similar situations in which funds have been lost due to various kinds of mistakes. As an example, Coleman referenced those detailed in EIP 156: “Reclaiming of ether in common classes of stuck accounts.”

Coleman also pointed out that in any of these instances, it must be “completely unambiguous who the original owners of the assets were.” The necessary changes could then be made and packaged together in an “already planned hard fork, such as the upcoming Constantinople fork.”

Even so, restoring funds is problematic. Ethereum core developers must discern which mistake-affected funds will be returned to users. Will all funds be returned or only a select few — or will this be a ~500,000 ETH learning experience?

The post De-briefing Ethereum’s Parity Predicament: What’s Next? appeared first on Bitcoin Magazine.