SAFE Network Dev Update - March 19, 2020

[joshuef]

Aye. You have understood well. That essentially implements a chunk of your excellent network starter scripts

And then ‘cargo bench’ will run the (likely to fail at some point) benchmarks thus far.

[Southside]

Looks like I didn’t understand that well…
I cloned GitHub - joshuef/sn_api: This crate implements a CLI (Command Line Interface) for the SAFE Network
built it with cargo build --release
copied the target/release/safe to ~/safe/vault
I grabbed safe_vault_lionel_pr_no_parsec.zip and unzipped it beside the new safe executable, but …

willie@gagarin:~/.safe/vault$ ./safe vault run-baby-fleming -t
error: Found argument 'vault' which wasn't expected, or isn't valid in this context

USAGE:
    safe [FLAGS] [OPTIONS] <SUBCOMMAND>

For more information try --help

[JPL]

Not quite sure what you’re up to but GitHub - joshuef/sn_api: This crate implements a CLI (Command Line Interface) for the SAFE Network hasn’t been updated since October by the look of it.

[Southside]

This much is true.
OTOH GitHub - joshuef/sn_api at MoreE2E was updated a couple of days ago. I pasted in the wrong link above - sorry

[bochaco]

Perhaps you forgot to actually checkout that branch @Southside? after you cloned it you need to git checkout MoreE2E

[Southside]

yep… its getting late - was up early and went for a walk on the hill for the first time in many many months and I’m knackered.

I’ll try again checking out the correct branch — duh

[happybeing]

You’re not the first person to make this mistake

[Southside]

@joshuef
Just to confirm, when building from MoreE2E, I should see safe-cli v0.9.0, NOT v0.10.0?? Confused.

....... Compiling safe-cli v0.9.0 (/home/willie/projects/maidsafe/joshuef/safe-api/safe-cli)
    Finished release [optimized] target(s) in 10m 25s
willie@gagarin:~/projects/maidsafe/joshuef/safe-api$ cp ~/projects/maidsafe/joshuef/safe-api/target/release/safe ~/.safe/vault/
willie@gagarin:~/projects/maidsafe/joshuef/safe-api$ cd ~/.safe/vault/
willie@gagarin:~/.safe/vault$ ~/.safe/cli/safe vault run-baby-fleming -t
error: Found argument '-t' which wasn't expected, or isn't valid in this context

USAGE:
    safe vault run-baby-fleming [FLAGS] [OPTIONS]

For more information try --help

then
willie@gagarin:~/.safe/vault$ ./safe -V
safe-cli 0.9.0

[bochaco]

It seems v0.9.0 is right: sn_api/Cargo.toml at MoreE2E · joshuef/sn_api · GitHub

[Southside]

So its not liking the -t flag then. I wonder where I messed up this time…

[Southside]

In other news, a 1Gb file get put to the network in 3min 37secs. We may be on the way to sketching out the first versions of SAFEtube

willie@gagarin:~/.safe/vault$ dd if=/dev/urandom of=/tmp/rand.dat bs=1M count=1000
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB, 1000 MiB) copied, 10.8343 s, 96.8 MB/s
willie@gagarin:~/.safe/vault$ time safe files put /tmp/rand.dat 
FilesContainer created at: "safe://hnyynyicsu7sdniizgfqdzdz3zhw6js3akn4feoupesxsc5ath99gbysmgbnc"
+  /tmp/rand.dat  safe://hbkyyods54j4p7jjfotgew51hkz7u3er7tkkqertwtd6txfpnyigcudu3w 

real	3m37.243s
user	2m50.812s
sys	0m34.127s

[bochaco]

The following should do it, note that AFAIK you can use the vault recently released, so just install latest vault with safe vault install, then:

• git clone https://github.com/joshuef/safe-api.git josh-api
• cd josh-api
• git checkout MoreE2E
• cargo run --release -- vault run-baby-fleming -t

[Knosis]

@Southside

the first versions of SAFEtube

With the rapidly growing censorship, this can’t come soon enough.

[Southside]

Perhaps should be moved to the Coronavirus mega thread but this is what US censorship is doing

‘Inhumane & reckless’: Twitter silences Venezuela’s anti-coronavirus...

[mav]

@Southside

a 1Gb file get put to the network in 3min 37secs

So that’s a rate of 38 Mbps which is pretty good I reckon. It’ll decrease when network latency, network bandwidth, and parsec overheads are introduced and increase when parallel operations are introduced. This seems like it will easily match consumer expectations of the ‘old’ internet. Will be interesting to see how it continues to change. Thanks for the stats @Southside.

[Southside]

Thank you. Definate progress getting made

I got this and will run it again with a backtrace in the morning

. …
…
…
Running target/release/deps/safe-5738596b78d37099

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

     Running target/release/deps/benches-7beaadd06001e376
Gnuplot not found, using plotters backend
Benchmarking cli put random tiny file
Benchmarking cli put random tiny file: Warming up for 3.0000 s

Warning: Unable to complete 40 samples in 5.0s. You may wish to increase target time to 648.7s or reduce sample count to 10.
Benchmarking cli put random tiny file: Collecting 40 samples in estimated 648.68 s (820 iterations)
[2020-03-20T00:57:43Z ERROR safe] safe-cli error: [Error] NetDataError - Failed to PUT Sequenced Append Only Data: Error(CoreError(Forbidden operation requested - CoreError::OperationForbidden))
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "command [\"safe\", \"files\", \"put\", \"test_file_random_content.txt\"] exited with code 1" }', safe-cli/benches/benches.rs:46:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

error: bench failed

Time for bed </zebedee> <— probably only @happybeing will get that one

[happybeing]

Booooiiiiiingggggg!

[Now discourse insists on sentences]

[Nigel]

@maidsafe

Last week the Rust fetch API was updated to support fetching a range of bytes from a file, so this week we updated the fetch and get_immutable_data C# APIs to also support range requests. This will allow devs to fetch the content between the given start and end index. We also released a new RC MaidSafe.SafeApp NuGet package. This new package provides support for the single-section / Baby Fleming network.

I know where this will come in handy!

@maidsafe

We are also starting to think about conducting some more quic-p2p tests to have better data about its scalability and resource requirements. We expect it to handle hundreds (or even thousands!) of connections at once and it’s important to know the limits and plan for them accordingly

So possibly another community P2P connection test! This will be exciting to see how much of an improvement quic-p2p is over crust.

@maidsafe

Therefore, to minimise loads on PARSEC and to achieve quick consensus for operations like querying of shared data, multisig wallets, etc., we face the requirement to sideload some of the consensus onto another mechanism

Once we have multi-sig I bet some pretty complex and next level stuff could come about. Smart contracts and escrow services anyone? Did the CRDT expert hire work still start on March 8th? Would be cool to get updates on CRDT progress too unless other things have taken priority in which case I understand. The goal posts shift from time to time.

There is so so much to look forward to (definitely looking forward to the functionality Labels will provide, to name one) and the progress and effort are second to none. Great job to all @maidsafe. We thank you.

[joshuef]

Excellent. That’s the known issue we’ve been seeing as well there So you’re definitely not doing anything wrong!

[jlpell]

@maidsafe

BLS-Distributed Key Generation, a cryptographic threshold signature scheme, that allows entities to attain consensus on some object swiftly via the nature of its six phases and forcing 100% participation from the corresponding nodes. You can read more about its workings and details here and here . A

If BLSDKG is a more efficient way to do consensus, why bother with PARSEC at all?