MaidSafe Dev Update :safe: 5th April 2016

Development Updates
61

That’s been the plan from the get go. Development occurs in upgrades until it’s ready for full release.

Things are getting exciting!

EDIT: Just found this excellent document explaining important steps SEE - “Todo Items”. - https://github.com/maidsafe/safe_vault

1 Like
62
  • Ability to run both a Client and Vault from home.
  • Ability to log on to the network like you already can do now.
  • Store and retrieve data (like a website) like you can do today as well.
  • Register your own domain name like you can do now.
  • A lot of great stuff for Devs using API’s and different data types.
5 Likes
63

What does that mean?

BTW, I forgot to attach some of the log stuff - see below:

3.7M	/home/phil/txts
299     files

pricom

- Uploading txts dir jammed on 71% - still there after 24 hours

- Restarted, some texts uploaded (neglected to count how many)

- Deleted txts dir - could never upload any more dirs but could upload
  individual files


pricom1

- Uploading txts dir jammed on 71% again after about an hour?

- From launcher log:

T 13:17:41.583704 Client thread
[routing:...c128001ac3a9a/routing-0.11.1/src/core.rs:1015] Got response
PutFailure { MessageId(fc49..), RequestMessage { src: Client { client_name:
9200.., proxy_node_name: 0db5.., peer_id: PeerId(cb9b..) }, dst:
ClientManager(name: 9200..), content: Put(ImmutableData { Normal, 0513.. },
MessageId(fc49..)) }, .. } from ClientManager(name: 9200..) to Client {
client_name: 9200.., proxy_node_name: 0db5.., peer_id: PeerId(cb9b..) }.
thread '<unnamed>' panicked at '

 =========================================================================================
 | Result evaluated to Err: CoreError::MutationFailure::{ImmutableData {
 Normal, 0513.. }} |
  =========================================================================================

  ', ../safe_core/src/core/self_encryption_storage.rs:60

- Deleted txts dir - could never upload any more dirs but could upload
  individual files


pricom2

- Uploading txts dir jammed on 71% again after about an hour?

- From launcher log:

T 19:14:10.747678 Client thread
[routing:...c128001ac3a9a/routing-0.11.1/src/core.rs:1015] Got response
PutFailure { MessageId(6c83..), RequestMessage { src: Client { client_name:
864e.., proxy_node_name: af16.., peer_id: PeerId(0964..) }, dst:
ClientManager(name: 864e..), content: Put(ImmutableData { Normal, 2ef8.. },
MessageId(6c83..)) }, .. } from ClientManager(name: 864e..) to Client {
client_name: 864e.., proxy_node_name: af16.., peer_id: PeerId(0964..) }.
thread '<unnamed>' panicked at '

 =========================================================================================
 | Result evaluated to Err: CoreError::MutationFailure::{ImmutableData {
 Normal, 2ef8.. }} |
  =========================================================================================

  ', ../safe_core/src/core/self_encryption_storage.rs:60
64

Does that suggest PUTs are for free, until Safecoin is introduced to the network?.. Will data be wiped one final time or will the MVP be simply added to and data considered stable after MVP??

1 Like
65

There is no set time for network wipes. There may be changes that are not backwards compatible and will require a network wipe. Although, after vaults get in the hands of the public, it’s going to be quite hard. If you can convince people not to upgrade, you can keep the network alive, though you’ll miss any new features that come out as well.

All that to say, I would not plan on any data from beta making it to the final product, but I guess there is a remote chance it could happen.

1 Like
66

Yes, until safecoins are introduced puts are free, but there is a 1GB limit per account. This is currently implemented in maid manager:

const DEFAULT_ACCOUNT_SIZE: u64 = 1024;  // 1024 units, max 1GB for immutable_data (1MB per chunk)

There is also a 5MB limit per file.

3 Likes
67

No SAFEcoin so how would you pay for them? :stuck_out_tongue_closed_eyes:

MVP is what some are calling pre-beta. So network resets are going to happen, until that is its announced that the network is live. So a lot of testing and upgrades to be done after MVP before its really live.

MVP it seems is what could run a network, but is not what the network will become.

2 Likes
68

Love this project but the idea of lunching a pure TCP Network going to get people thinking of all those TOR UTP Leak issues and they are huge. What are you going to do to help convince people this is not just a new TOR and that Security secure and UTP will be supported? Many beleive that TOR project errored in not supporting UTP early on with the words “We get to it later” and Later never came as there was always a New shiny goal but the basic Flaw never corrected. Will Later ever Come for UTP?

69

Later already came. Vinicius fixed it. MVP will have TCP and UTP. :smiley: :smiley: awesome isn’t it

6 Likes
70

The new weekly update from Tuesday advised that TCP and Utp are both going to be included in the initial launch. :slight_smile:

2 Likes
71

A Think of BEAUTY! :heart_eyes:

73

The Pun was intended. :wink:

74

Basically all the things good you(TP) can think of have been said and confirmed in the Original Post of this thread. Don’t miss a single word.

edit: I thought this was the April 12th update thread.

2 Likes
75

Hi Ross
As an IT Professional I am interested in looking at this could based storage solution. When do you think there will be a MVP that I can see?
Lok

1 Like
76

Hi there, welcome to the forum :thumbsup:. This is be the topic for the latest info about the MVP. And we are very very close.

1 Like
77

Ross is on a small break this week

There has been a newer Dev Update last Tuesday w/more current info. You can search for it in the search bar above and read up on it.

But it basically says they’re extremely close, and it might be released before next Tuesday.

…OMG wait that’s in only a few days!!!

3 Likes
78

Cool. Thanks for swift reply

2 Likes