Quote from: bjlanza on September 03, 2020, 12:18:34 AM

Quote from: Miiike on September 02, 2020, 09:21:18 PM

But this IS a core feature. Your selling point is a service that allows people feel safe to keep their data without the fear of being lost (hence, cloud) or stolen (hence, a third party security system). How would they feel secure if there were no failsafe for the case of the unexpected? I don't think this is an additional feature.

Of course, we can rule this unfortunate event as a team's poor judgement or something that team failed to see. But, this leads to the second thing that pique my interest the second I study your project: team details.

Certainly you didn't plan to offer a data securing service without telling your clients who are the people behind the screen, right?

Miiike we can agree that this feature is important, by providing a security mechanism that facilitates that data does not become unreadable. And this allows people less versed to access this type of technology.

But we disagree that this is a core feature and disagree that this is due to poor judgment by the development team.

We are precisely in a bitcoin forum where value is transmitted, without that safeguard mechanism, when keys are lost or tokens are sent to the wrong address they are lost.
And we are talking about elements with a lot of value.

Nor do I think that similar solutions within the spectrum of decentralized storage solutions such as Sia, Storj, Arweave, Filecoin ... have incorporated such a feature since the launch. I do not know personally as it is difficult to know each solution in great depth if any incorporates it at present.

The priority of the development team is to create a secure network, and that the mechanism of consensus works, distributing the information through the nodes, with all the other challenges of speed and performance. The primary and most important thing is that the network works and that the wallet is integrated.

If this reduces the spectrum of users to those who are aware of the importance of managing their keys in situations of disability and death. We will work efficiently to expand that spectrum. But most cryptoeconomics projects do not have these safeguards at the beginning.
Your keys are your responsibility.

As we have commented throughout this thread, and with the help of your contributions and questions. Implementing this feature implies a detailed analysis of the possible solutions. To ensure as much as possible the privacy and security of the data. Some solutions involve providing data, that data like a phone number can be used all over the world, we perform biometric data hashes? In the end it is the trio of something that the user knows, something that he owns, and something that he is. Sometimes you can add something where he is.
https://en.wikipedia.org/wiki/Multi-factor_authentication And that doesn't solve the problem if the user doesn't share his data if he suffers a disability. It's not a trivial issue. It's a big mouthful that has to be chewed and swallowed and deserves its own space to be raised and developed when the network is working.

I'm sorry that we didn't meet the needs of a perfect solution from the launch, but we are working on it. But reaching perfection is not going to prevent us from first releasing a solution that works perfectly.

In short: team is still looking for a solution for this.

There are ways to get around this issue, one that's surely not that complicated, but I am not sure if I should really share the idea, not before I am sure you're not just another scam project. And by the lack of details, and several minor issues like the fact that your ann thread barely populated by people that's interested on your project, to be blunt, I have a serious doubt that you can survive.

Did you even consider some exposure? Made yourself known to the forum and cryptocommunity?

Quote from: bjlanza link=topic=5259364.msg55118792#msg55118792
date=1599094418

Well, again we are working in a field originated by a mysterious figure or group of developers hidden under an alias.

But we strongly agree that transparency is the best way to combat Smokeware or Scamware. Being aware of the unknown.
Hence the importance of having a section about us or our team in the project. An aspect that we must improve in our web.

At the end you are entrusting your data to a cryptographic mechanism that keeps it safe from other people's access. And to a decentralized network.

It's clear that no exchange will trade our token unless we provide verified and contrasted information about the security of the project. And we are working in the matter not only from the technological side, but also from the legal and business side to make this be done.

But our code is available for review and this is another way to check that the project does what we say and that there are no hidden elements that undermine their confidence.

At the end although it is important who this behind the mirror, if the Wizard or the scarecrow. The important thing is that when a user invests in SWR so that their data is distributed permanently and safely and only accessible to him, make sure that this is so and that the nodes comply with the contract.

But no, it is not the objective of Stasware members to be unknown, only that there are times and steps that are taken when a decentralized project is created.

So...? Will you share the team details? Soonest possible?