Pages:
Author

Topic: Stashware: a secure and permanent decentralized storage platform - page 2. (Read 1390 times)

copper member
Activity: 22
Merit: 0
Talking about security

We started a series of post about the Technological concepts in Stashware.

Stashware is based on a multitude of innovative, revolutionary and disruptive technologies. In our Medium channel, we explain each one of them so that you can better understand what our decentralized storage platform is based on

Today we start with the deduplication. How to replicate the data so that it is safe but without duplicating things unnecessarily.

https://medium.com/@stashware/secure-deduplication-a9e6b24d86f0
legendary
Activity: 2030
Merit: 1059
Wait... What?

For all we know, to think the negatively possible way, there could be only one person in this team, who tried to scam by pretending they're 10 different people working together. No evidence to support your statement of 10 people, no pictures, no background to trace back, and conveniently, they're also refuse to share their face because they don't feel comfortable with that. One "we are not scam" statement doesn't help.

--snip, snip, snip--

Our goal is to show not to sell.

But as I said before we are moving forward to improve those details.

And so far, there's almost nothing to show. Team has no face, product is lacking of (arguably) important features, and judging from how quiet this thread is, you also has little to zero interested people.

I still think putting name on faces is crucial. But as you refuses for whatever reason, I'd like to suggest a group photo with company brand visible. That way, you showed us your team but they're not necessarily needed to be identified individually.
newbie
Activity: 1
Merit: 0
Well, interesting conversation the one building up here.

But hey, based on what bjlanza just said. Let's wait and see. If this project is not on the hunt of getting money for their ICO, or trying to get people to buy their token on uniswap, or some scammy stuff like that, then I'll just keep checking their info as it comes out, and make my own opinion. I mean, I'm glad they are posting stuff here, and not just going directly to pay some youtuber to shill their coin...

With that being said, Miiike's idea about legacy keys for unexpected situations seem like a real good suggestion. I hope the team will reconsider that as part of core functions.

I'll keep my eye on this.
newbie
Activity: 62
Merit: 0

For all we know, to think the negatively possible way, there could be only one person in this team, who tried to scam by pretending they're 10 different people working together. No evidence to support your statement of 10 people, no pictures, no background to trace back, and conveniently, they're also refuse to share their face because they don't feel comfortable with that. One "we are not scam" statement doesn't help.

It could be but it isn't.
Again, let me emphasize that we are presenting Stashware's technology solution, its advances and improvements to other solutions, whether pre-existing or under development, within the decentralized storage ecosystem.

Publishing the Technical Whitepaper and the system of economy that will govern the network, and reward the miners and with which users will pay for the services of secure and private decentralized storage.
We have not launched any ICO, STO, IEO or asked for any investment, we do not have an announcement to buy the tokens at this point.  Nor are we collecting user information with any newsletter. We are developing the solution with our resources.

So there is no place to use the word Scam associated with Stashware no matter how much doubt you have about the current information available about the project.
You may have doubts, but let us have the benefit of the doubt until you see a buy from us ad.

We are more focused on discussing ideas, getting feedback from the people in the forum, and seeing the interest in the Decentralized Storage Networking trend.
For example your contributions are very interesting. And that is what we are searching for. We want the code and ideas to speak for the project, not our faces.

If you are interested, I have no problem connecting with you on linkedin. For me it will be a real pleasure.

I say again, and you know this very well, that reputation is everything, and that entering into an exchange or getting a positive review is not achieved if you don't give true and relevant information. Nor if your solution has no value or is not backed by expert people.
Besides, we know that one of our weaknesses in this forum is the lack of seniority.
We had to create fresh newly users like mine. We have had to create our users and they are brand new.
And a newly created group of accounts in a thread is not going to give much more confidence either.

As I have pointed out. What we are interested in is to show our network working. The latest versions of code in production are stable and with great performance.
The team is going to start releasing code more frequently to public repositories.
We will also change and improve the corporate image including logo redesign. To start improving communication and adding banners and better diagrams to spread better messages in our social channels.
We are in the process of implementing the faucet additionally.

Our goal is to show not to sell.

But as I said before we are moving forward to improve those details.
legendary
Activity: 2030
Merit: 1059
Wait... What?

Hi Miiike Always is  great to have your insights

In Long (as you see I like to explain with details)

--snip--


For all we know, to think the negatively possible way, there could be only one person in this team, who tried to scam by pretending they're 10 different people working together. No evidence to support your statement of 10 people, no pictures, no background to trace back, and conveniently, they're also refuse to share their face because they don't feel comfortable with that. One "we are not scam" statement doesn't help.
newbie
Activity: 62
Merit: 0

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?


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

Hi Miiike Always is  great to have your insights

In Long (as you see I like to explain with details)

As I commented before, that feature is within the product backlog to be developed within our roadmap. But currently the development team is focused on the mainnet.
It has not been addressed beyond what I said, although you can be sure that the development team is aware. But there are more pressing things like good network performance and ensuring your privacy.
When that stage of development arrives, we will wait for your input if you want to provide it.


No, this is not a Scam project. Let me remind you that we have presented a very interesting value proposal that makes improvements over other solutions within the decentralized storage ecosystem. Incorporating the most relevant technologies within the state of the art.As it is a Blockweave structure to manage the registry. Or Wildfire to propagate the information to the nodes.
Trust is everything in this field. and Trust and security is what we want to transmit to our users. In the development we haven't asked for any funds from the users, and we are doing it with our own resources, earned with effort and tenacity.
And the economic system to integrate the miners with PoS and the economy of the token that involves the purchase of the SWR users to store their data and pay for the space, you know that it has to surpass certain controls.
This is not a 2017 ICO without any value asking for money per idea and wishing to be millionaires and to something else. Of those we have seen many. This is a serious project that has an excellent idea developed by talented people and hopes that this idea is the one that gives value to the project. Real Content for Real Value.

As I've said before, the Stashware team consists of more than 10 people, 5-6 of whom are fully dedicated to development. The rest of us are in management, communication, documentation, business.

It is important to us that Stashware is known at BitcoinTalk, but we are a mainly Spanish and Latin American team. So now our main metric isn't how much interaction we get in our official threads right now. But as you see we value so much the interaction with some of the most involved brilliant people here.

But our core ecosystem doesn`t move or communicate here.
At the team communication level that's what I'm here for as a spokesperson or technical ambassador or the official accounts as a way to bring the messages together and facilitate their follow up and more in these forums that are based on account reputations.

Also in the state of our project we are well so. Even at the risk of raising some eyebrows. To tell you the truth I doubt that it will convince the cryptography and cyber security part of the team to reveal much of them.
You will know more about the front and business side, than about development, since many of them, because of their work, are not exactly prolific with complete profiles.

The community is a very wide thing. You find users and receive feedback, in multiple other channels. As I have also explained, I have been following an agile approach, trying to get the opinion of the potential interested parties right away.

That is why we have published the value proposal, and our ideas in the media, as we do, from CTOs of large companies to developers of our LATAM ecosystems.

Also remember that the times each project handles it differently. We are in interesting times and there are external factors such as Covid 19 that impact on planning.
It is not a question of sooner or later, but of doing it at the right time.

And that can be, after a milestone, a meeting, the securing of a support.
We are aligned with our planning and that is what is important

legendary
Activity: 2030
Merit: 1059
Wait... What?

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?
newbie
Activity: 62
Merit: 0
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?

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.

newbie
Activity: 62
Merit: 0

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.
legendary
Activity: 2030
Merit: 1059
Wait... What?

So uhh... in other way, to put it bluntly, your team still have not decide what implementation can be used to safeguard an unexpected event such as the user passed away unexpectedly?

Welcome again Miiike, hope you had a wonderful end of summer.

Yes. You are correct. The dev team is busy finishing the Mainnet and the core features.
The development has not advanced that far to be at the point of adding additional features.
So the safeguard feature has not yet been selected for development and therefore has not been analyzed in depth for its implementation.

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?
newbie
Activity: 62
Merit: 0

So uhh... in other way, to put it bluntly, your team still have not decide what implementation can be used to safeguard an unexpected event such as the user passed away unexpectedly?

Welcome again Miiike, hope you had a wonderful end of summer.

Yes. You are correct. The dev team is busy finishing the Mainnet and the core features.
The development has not advanced that far to be at the point of adding additional features.
So the safeguard feature has not yet been selected for development and therefore has not been analyzed in depth for its implementation.
legendary
Activity: 2030
Merit: 1059
Wait... What?

One of your key feature is the security and (one may say) impenetrability of your storage. I don't think I will goes down to one-on-one comparison between you and other cloud storage services, but one that comes to my mind, though, will there be a fail-safe method? Like for example one forgot their password, or (in a very likely cases) the storage owner passed away with their files encrypted in your service, which the family or next of kin was trying to retrieve (with or without the belated's permission is not a matter to be considered in this case) said files. Will there be a method to facilitate this?
--snip--

This is an interesting subject that we will surely deal with in our medium.

In short, if we have thought about it, we are aware of the problem and therefore we will implement a decentralized system of key management. But as value is added after the launch of the MainNet.

Well, to limit the topic, I am not talking the situation on philosophical view, so we can just leave it strictly on practical use, and I didn't mean to be rude, but I seems failed to grasp the main idea of your answer. Would you please explain again? Perhaps in a simpler and more direct answer

Of course you are not rude.  You are right in your concerns, We are aware of this kind of problem.
What safeguards can be implemented without losing the spirit of decentralization and the importance of the custody of the keys?
As I have commented, the implementation of a decentralized key management system is being considered in the design phase.

But this feature will not be available at the release.  It will be incorporated in future iterations of the development roadmap.

The way to recover access to files will involve a unique element that the user owns, for this we have considered a phone number or NFC smart identity card as it could be a modern passport.


So uhh... in other way, to put it bluntly, your team still have not decide what implementation can be used to safeguard an unexpected event such as the user passed away unexpectedly?
jr. member
Activity: 53
Merit: 1
looking forward to heard form you again with great news. Smiley
newbie
Activity: 62
Merit: 0
The development of Stashware continue without delay, as we continue with improve and test our platform.
We soon share great news with you here.
newbie
Activity: 62
Merit: 0
The privacy and security of data stored at Stashware is one of our highest priorities. That's why, from the outset, Stashware is designed with a number of features dedicated to ensuring your protection and privacy.

You can read about them in our latest medium article

https://medium.com/@stashware/security-and-privacy-services-of-stashware-252e0c30302
newbie
Activity: 62
Merit: 0
The articles on Medium are good, but I think it is important to use social media to facilitate the spread of articles.
There are many people who are looking even if it seems to be few at first glance.

Yeah we are aware of this situation that is why we publish our social media, and we are going to increase the channels where we publish. We want to spread the advantages of decentralized storage.
Now in forums, Medium and Twitter and soon in many other social networks.

Many people are currently interested in any crypto project.
I hope your project will gain great popularity:D

Well we are working hard and soon we will have great news about our network.
sr. member
Activity: 304
Merit: 250
The articles on Medium are good, but I think it is important to use social media to facilitate the spread of articles.
There are many people who are looking even if it seems to be few at first glance.

Yeah we are aware of this situation that is why we publish our social media, and we are going to increase the channels where we publish. We want to spread the advantages of decentralized storage.
Now in forums, Medium and Twitter and soon in many other social networks.

Many people are currently interested in any crypto project.
I hope your project will gain great popularity:D
newbie
Activity: 62
Merit: 0
The articles on Medium are good, but I think it is important to use social media to facilitate the spread of articles.
There are many people who are looking even if it seems to be few at first glance.

Yeah we are aware of this situation that is why we publish our social media, and we are going to increase the channels where we publish. We want to spread the advantages of decentralized storage.
Now in forums, Medium and Twitter and soon in many other social networks.
sr. member
Activity: 304
Merit: 250
The articles on Medium are good, but I think it is important to use social media to facilitate the spread of articles.
There are many people who are looking even if it seems to be few at first glance.
newbie
Activity: 62
Merit: 0
It's interesting.
look forward to the next.

Great to know about that p3ngu1n. Do you like our medium articles?

Yes. I think it's good to have a well-organized article.
Regular release of information about a product can attract a lot of people, as people aren't interested in things they don't know much about.


We released the last part of the series about the consensus mechanism. This week is Proof of Access.

https://medium.com/@stashware/existing-consensus-mechanisms-in-decentralized-cloud-storage-iv-poa-6f5a31d43073
Pages:
Jump to: