SAFE Network Dev Update - April 9, 2020

That comment is probably the best I have ever seen from you. I hope you can keep it up and evolve to become a more balanced human being.

Happy easter to David, all of the Maidsafe team and community, I wish you all health and Joy.

20 Likes

I would say happy. Performance, security, and usability improvements should continue as they are pretty much required for a minimum and viable safe internet that would be for the masses.

18 Likes

Nice Update and Happy Easter to all the great people helping make this dream come true.

The silent majority is still here watching, over the moon that the visible, honest and genuine efforts of the last few years are beginning to come to fruition.

18 Likes

I think we can all agree on that, @gouda123
AIUI David is taking a week off. He lives in a lovely rural location, well off the beaten track and unlikely to be bothered by the contagious Easter campervan idiots. He is probably as safe as any of us. He has been quietly active with some likes recently.
I’m sure we will hear from him soon.

13 Likes

Can anyone give me a brief detail about " framing " part
Thanks

Finally got a new Safe Network App Alpha build up now the mac build is going again: https://github.com/maidsafe/safe-network-app/releases/tag/v0.0.6-alpha.18

This is alpha software, so not for the faint of heart. Fixes since last week:

  • Error notification when authd subscribe fails (and you therefore wont be able to login until you restart authd and the app itself).
  • menu bar in windowed mode has been fixed on linux. Close button exists!
  • quit option now exists in the app’s dropdown menu
  • command line logging output has been tidied up.
  • SNAPP will now use cli v0.11.0, the update was missed in the last release ( :expressionless: ) and probably accounts for a lot of issues. (I’ll be working on automating this w/ cli releases so we always get the latest release and the manual step is no longer needed).

Enjoy!

25 Likes

I don’t think this has been mentioned, but fleming branch has been merged into master branch in safe_vault repository on GitHub. This means that an important step has been finalized.

17 Likes

Any hints as to what I should do now? Android Samsung 7 <-- a screenshot wont capture that overlay, hence the faffing with webcam

image

1 Like

That looks like attempt to download safe-network-app on a mobile?.. which is a for desktop download…did you intend the Authenticator perhaps or hoped for a mobile snapp that maybe doesn’t exist yet.

from SAFE Network Dev Update - April 2, 2020

5 Likes

Doh!
My brain is seriously mince today. I was up too late last night and I have suffered for it all day. I just can’t pull all-night sessions like I used to…

Im going to download it on the laptop and get to my kip - thanks

EDIT - SNApp looks good here

If anyone is bored - go to safe://vue-shop and leave a review on the socks so I have some data to format nicely tomorrow - Ta!

3 Likes

I’m to the point where half night sessions knock me out the next day.

4 Likes

I’m at the point of not getting to bed before midnight = drinking 15 beers + pulling an all-nighter at 18.

6 Likes

Amateurs! I had to quit drinking altogether years ago. :wink: Off to take my afternoon nap now.

6 Likes

Get off me grass you young kids. Bah humbug

9 Likes

Left a review but it doesn’t seem to have persisted.

2 Likes

Yes I realised I still have more work to do but thanks anyway

1 Like

I am using latest safe_vault and latest safe-api compiled from source to play with a local network and I came across 2 problems uncovered by the following operations:

  • Create genesis vault on port 5483

  • Create a key with test coins

  • Create 6 additional local vaults on random ports (to reach 7 elders default limit)

  • Try to create an account paid by the key with command: RUST_LOG=trace ./safe keys create --preload 0.000002 --pay-with “…” --output json`

The output is sometimes a success:

...
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:48340: Message: [ 01 00 00 00..a2 ec 98 4b ].
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:48340), msg_id: MessageId(2ea604..), resp: Response::Transaction(NoSuchBalance)
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:41536: Message: [ 01 00 00 00..a2 ec 98 4b ].
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:41536), msg_id: MessageId(2ea604..), resp: Response::Transaction(NoSuchBalance)
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:35555: Message: [ 01 00 00 00..a2 ec 98 4b ].
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:35555), msg_id: MessageId(2ea604..), resp: Response::Transaction(NoSuchBalance)
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:56965: Message: [ 01 00 00 00..a2 ec 98 4b ].
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:56965), msg_id: MessageId(2ea604..), resp: Response::Transaction(NoSuchBalance)
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:57052: Message: [ 01 00 00 00..a2 ec 98 4b ].
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:57052), msg_id: MessageId(2ea604..), resp: Response::Transaction(NoSuchBalance)
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:53098: Message: [ 01 00 00 00..a2 ec 98 4b ].
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:53098), msg_id: MessageId(2ea604..), resp: Response::Transaction(NoSuchBalance)
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:5483: Message: [ 01 00 00 00..a2 ec 98 4b ].
[2020-04-12T15:07:31Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:5483), msg_id: MessageId(2ea604..), resp: Response::Transaction(Success)
...
[
  "safe://hbyyyybgfh8rm4611u1se1gp9qgxjmre4z3kaxjztcitzwfmtswqccyxf6",
  {
    "pk": "98bc3917af4a5395912337ee33d2b22357cab0f4de2cac6f42ae36a398c03cbe7eb667ac1fc326d1f5ed6b36d76b9ec3",
    "sk": "227797a6c8d8b1e1b0b9a75b587ba73c8f6dd6a78db8dedb253205245acb3769"
  }
]
...

But more often a failure:

...
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:56965: Message: [ 01 00 00 00..df be 26 c2 ].
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:56965), msg_id: MessageId(a1febe..), resp: Response::Transaction(NoSuchBalance)
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:41536: Message: [ 01 00 00 00..df be 26 c2 ].
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:41536), msg_id: MessageId(a1febe..), resp: Response::Transaction(NoSuchBalance)
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:35555: Message: [ 01 00 00 00..df be 26 c2 ].
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:35555), msg_id: MessageId(a1febe..), resp: Response::Transaction(NoSuchBalance)
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:53098: Message: [ 01 00 00 00..df be 26 c2 ].
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:53098), msg_id: MessageId(a1febe..), resp: Response::Transaction(NoSuchBalance)
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:48340: Message: [ 01 00 00 00..df be 26 c2 ].
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:48340), msg_id: MessageId(a1febe..), resp: Response::Transaction(NoSuchBalance)
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:5483: Message: [ 01 00 00 00..df be 26 c2 ].
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:5483), msg_id: MessageId(a1febe..), resp: Response::Transaction(Success)
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] 192.168.1.68:57052: Message: [ 01 00 00 00..df be 26 c2 ].
[2020-04-12T15:07:01Z TRACE safe_core::connection_manager::connection_group] Response from: V4(192.168.1.68:57052), msg_id: MessageId(a1febe..), resp: Response::Transaction(NoSuchBalance)
...
[2020-04-12T15:07:01Z ERROR safe] safe-cli error: [Error] Unexpected - Unexpected error when attempting to create Key: [Error] NetDataError - Failed to create a SafeKey: CoreError(Data error -> Balance does not exist - CoreError::DataError -> NoSuchBalance)
...

First problem is that the key balance has not been duplicated to other vaults. Only the genesis vault is able to finalize the transaction successfully. The other vaults return NoSuchBalance error.

Second problem is that there isn’t any vote to decide of the outcome of the operation: Success of command depends on which node sends the information last. If the genesis vault is last, then the operation is successul (as shown by json result). But if another vault is last then the operation fails.

I don’t know if these problems are bugs or missing features and I would like to have a status on them.

Note: The same problems also happen for other data structure like files and file containers.

2 Likes

What commands are you using for steps 1 and 3?

  • to create genesis vault: ./safe_vault --ip 192.168.1.68 -p 5483 -f -vv -r ~/.local/share/safe_vault/root_dir_00 where 192.168.1.68 is my local IP address.

  • to create additional vaults: ./safe_vault --ip 192.168.1.68 -h '["192.168.1.68:5483"]' -vv -r ~/.local/share/safe_vault/root_dir_NN where NN stands for the vault number (from 01 to 06)

1 Like

Just guessing here, but sounds related to PARSEC being removed from the vault layer.

2 Likes