You don’t need to create it again, but you’ll need to install authd on both computers as it still doesn’t support for connection from non-local IP, so just install CLI and authd on computer B and you should be able to unlock it using the passphrase and password you created it with from computer A
4 Likes
THat deserves a reward
willie@gagarin:~/.safe/node/local-node$ safe keys transfer --to safe://givewydileiemoney 110
Success. TX_ID: 1
But when I try again cos that wasn’t enough
willie@gagarin:~/.safe/node/local-node$ safe keys transfer --to safe://givewydileiemoney 210
Error: InvalidInput: Failed to parse the 'to' URL: safe://givewydileiemoney
I’ll look at it harder in the morning - I’m cream-crackered
Try stopping it first ($ safe auth stop) and see if that succeeds and then try starting it again. You can always run authd directly using its binary to see perhaps more info, e.g. $ ~/.safe/authd/sn_authd start or restart/stop as well.
@bochaco I tried that but getting an error which is why I ask, am I missing a step?
[tom@jutsu ~]$ rm -rf $HOME/.safe
[tom@jutsu ~]$ curl -so- https://sn-api.s3.amazonaws.com/install.sh | bash
=> Downloading Safe CLI package from 'https://sn-api.s3.eu-west-2.amazonaws.com/sn_cli-0.23.0-x86_64-unknown-linux-musl.tar.gz'...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 10.3M 100 10.3M 0 0 454k 0 0:00:23 0:00:23 --:--:-- 415k
=> Unpacking Safe CLI to '/home/tom/.safe/cli'...
=> Adding statement to '/home/tom/.bashrc' profile to have Safe CLI binary path in the $PATH
=> Profile '/home/tom/.bashrc' already contains a statement to set Safe CLI in the $PATH
[tom@jutsu ~]$ source .bashrc
[tom@jutsu ~]$ safe -V
sn_cli 0.23.0
[tom@jutsu ~]$ safe auth install
Latest release found: sn_authd v0.5.0
Downloading https://sn-api.s3.eu-west-2.amazonaws.com/sn_authd-0.5.0-x86_64-unknown-linux-musl.zip...
[00:00:01] [========================================] 7.63MB/7.63MB (0s) Done
Creating '/home/tom/.safe/authd' folder
Installing sn_authd binary at /home/tom/.safe/authd ...
Setting execution permissions to installed binary '/home/tom/.safe/authd/sn_authd'...
Done!
[tom@jutsu ~]$ safe networks add fleming-testnet https://sn-node.s3.eu-west-2.amazonaws.com/config/node_connection_info.config
Network 'fleming-testnet' was added to the list. Connection information is located at 'https://sn-node.s3.eu-west-2.amazonaws.com/config/node_connection_info.config'
[tom@jutsu ~]$ safe networks switch fleming-testnet
Switching to 'fleming-testnet' network...
Fetching 'fleming-testnet' network connection information from 'https://sn-node.s3.eu-west-2.amazonaws.com/config/node_connection_info.config' ...
Successfully switched to 'fleming-testnet' network in your system!
If you need write access to the 'fleming-testnet' network, you'll need to restart authd, unlock a Safe and re-authorise the CLI again
[tom@jutsu ~]$ safe auth start
Creating '/home/tom/.safe/authd/logs' folder
Starting SAFE Authenticator daemon (sn_authd)...
sn_authd started (PID: 232092)
[tom@jutsu ~]$ safe auth status
Sending request to authd to obtain a status report...
+------------------------------------------+-------+
| Safe Authenticator status | |
+------------------------------------------+-------+
| Authenticator daemon version | 0.5.0 |
+------------------------------------------+-------+
| Is there a Safe currently unlocked? | No |
+------------------------------------------+-------+
| Number of pending authorisation requests | 0 |
+------------------------------------------+-------+
| Number of notifications subscribers | 0 |
+------------------------------------------+-------+
[tom@jutsu ~]$ safe auth unlock
Sending action request to authd to unlock the Safe...
Error: AuthdError: ClientError: Requested data not found
Everything you did looks good to me, can you check the authd logs at /home/tom/.safe/authd/logs/sn_authd.log and see if you find some obvious errors there?
All I can think of is some connectivity issues, also please try this command with CLI: $ safe keys create --test-coins if that fails then it’s very likely just connectivity issues
BTW, did you get the prompt to enter passphrase and password?
I am getting a bunch of these?
[sn_node] ERROR 2021-04-08T19:14:40.838865485-04:00 [src/node/messaging.rs:68] Unable to send Message to Peer: MissingSecretKeyShare
@bochaco do you have any idea? It has somewhat taken over my logs.
I’ve also seen a handful of those but not a lot. Don’t know what it means though…
I am inundated
It is not blazing but David said several times that with this first iteration that it would be. I expected pretty much this.
2 Likes
I think your expectations are too high for test code still under debug mode. Did you compile with -O3 fast-math optimizations turned on? Does rust even have that? 
2 Likes
I was able to create test coins, but auth unlock still fails:
[tom@jutsu ~]$ safe keys create --test-coins
New SafeKey created at: "safe://xxx"
Preloaded with 1000.111 testcoins
Key pair generated:
Public Key = xxx
Secret Key = xxx
[tom@jutsu ~]$ safe auth unlock
Sending action request to authd to unlock the Safe...
Error: AuthdError: ClientError: Requested data not found
I do see 2 errors in the logs generated when I run auth unlock command. In case it helps, here is the log:
INFO 2021-04-08T18:50:18.039520061-05:00 [sn_authd/requests/mod.rs:77] Processing new incoming request (1130680454): 'unlock'
INFO 2021-04-08T18:50:18.039583824-05:00 [sn_authd/requests/unlock.rs:25] Unlocking a Safe...
INFO 2021-04-08T18:50:18.050295309-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/client/mod.rs:109] Client started for specific pk: PublicKey::Ed25519(1b4af248379b207a4f995554b4e663940ae895321fc4c376b9dbd70f9506e15a)
WARN 2021-04-08T18:50:18.050323595-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/config_handler.rs:73] Failed to open config file from '/home/tom/.safe/client/sn_client.config': No such file or directory (os error 2)
WARN 2021-04-08T18:50:18.050503847-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/qp2p-0.11.7/src/endpoint.rs:235] Ignoring 'forward_port' flag from config since IGD has been disabled (feature 'no-igd' has been set)
WARN 2021-04-08T18:50:18.718850946-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.146.110:58306
INFO 2021-04-08T18:50:19.036605760-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.139.187:33546
WARN 2021-04-08T18:50:19.036686730-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 1 new_elders.
INFO 2021-04-08T18:50:19.038274443-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.72.229:52737
WARN 2021-04-08T18:50:19.038332187-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 2 new_elders.
INFO 2021-04-08T18:50:19.039020113-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 178.62.58.241:42766
WARN 2021-04-08T18:50:19.039095247-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 3 new_elders.
INFO 2021-04-08T18:50:19.039273601-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.152.156:51182
WARN 2021-04-08T18:50:19.039329621-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 4 new_elders.
INFO 2021-04-08T18:50:19.042773065-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.131.119:50694
WARN 2021-04-08T18:50:19.042861940-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 5 new_elders.
INFO 2021-04-08T18:50:19.043654541-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.142.144:55064
WARN 2021-04-08T18:50:19.043706564-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 6 new_elders.
INFO 2021-04-08T18:50:19.044510044-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.154.164:44520
WARN 2021-04-08T18:50:21.262123727-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 46.101.72.229:52737
INFO 2021-04-08T18:50:21.568679791-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.131.119:50694
WARN 2021-04-08T18:50:21.568758048-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 1 new_elders.
INFO 2021-04-08T18:50:21.584975487-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.139.187:33546
WARN 2021-04-08T18:50:21.585054632-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 2 new_elders.
INFO 2021-04-08T18:50:21.585216690-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.72.229:52737
WARN 2021-04-08T18:50:21.585259106-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 3 new_elders.
INFO 2021-04-08T18:50:21.591646701-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 178.62.58.241:42766
WARN 2021-04-08T18:50:21.591722663-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 4 new_elders.
INFO 2021-04-08T18:50:21.593113900-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.152.156:51182
WARN 2021-04-08T18:50:21.593179321-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 5 new_elders.
INFO 2021-04-08T18:50:21.593556516-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.142.144:55064
WARN 2021-04-08T18:50:21.593624322-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 6 new_elders.
INFO 2021-04-08T18:50:21.593759942-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.154.164:44520
WARN 2021-04-08T18:50:21.599677927-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.131.119:50694
WARN 2021-04-08T18:50:21.605470333-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.139.187:33546
WARN 2021-04-08T18:50:21.611414479-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.142.144:55064
WARN 2021-04-08T18:50:21.617192386-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.152.156:51182
WARN 2021-04-08T18:50:21.622947276-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.154.164:44520
WARN 2021-04-08T18:50:21.627708396-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 178.62.58.241:42766
INFO 2021-04-08T18:50:22.029112210-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 178.62.58.241:42766
WARN 2021-04-08T18:50:22.029188983-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 1 new_elders.
INFO 2021-04-08T18:50:22.048800113-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.139.187:33546
WARN 2021-04-08T18:50:22.048875157-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 2 new_elders.
INFO 2021-04-08T18:50:22.051420298-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.131.119:50694
WARN 2021-04-08T18:50:22.051507938-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 3 new_elders.
INFO 2021-04-08T18:50:22.052023521-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 46.101.72.229:52737
WARN 2021-04-08T18:50:22.052080990-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 4 new_elders.
INFO 2021-04-08T18:50:22.054087762-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.152.156:51182
WARN 2021-04-08T18:50:22.054187695-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 5 new_elders.
INFO 2021-04-08T18:50:22.054642716-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.142.144:55064
WARN 2021-04-08T18:50:22.054706171-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:537] Connected to only 6 new_elders.
INFO 2021-04-08T18:50:22.054738097-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:527] Connected to elder: 138.68.154.164:44520
WARN 2021-04-08T18:50:22.054909851-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/client/mod.rs:172] No automatic simulated payout occurs for clients created for pre-existing SecretKeys
INFO 2021-04-08T18:50:22.054935599-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/client/transfer_actor/mod.rs:124] Getting SnTransfers history for pk: PublicKey::Ed25519(1b4af248379b207a4f995554b4e663940ae895321fc4c376b9dbd70f9506e15a)
INFO 2021-04-08T18:50:22.054984341-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:215] sending query message Query { query: Transfer(TransferQuery::GetHistory), id: MessageId(339d82..), target_section_pk: Some(PublicKey::Bls(b4808ea4954e5735ad7a43f91fc774a39718bd89069f1bfc4ecb90fc5c5241a5)) } w/ id: MessageId(339d82..)
WARN 2021-04-08T18:50:22.375517843-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 46.101.72.229:52737
WARN 2021-04-08T18:50:22.584918010-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.131.119:50694
WARN 2021-04-08T18:50:22.786256177-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.139.187:33546
WARN 2021-04-08T18:50:22.996131087-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.142.144:55064
WARN 2021-04-08T18:50:23.224376005-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.152.156:51182
WARN 2021-04-08T18:50:23.434765604-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.154.164:44520
INFO 2021-04-08T18:50:23.541721253-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:215] sending query message Query { query: Data(MapRead::GetMap), id: MessageId(903e16..), target_section_pk: Some(PublicKey::Bls(b4808ea4954e5735ad7a43f91fc774a39718bd89069f1bfc4ecb90fc5c5241a5)) } w/ id: MessageId(903e16..)
WARN 2021-04-08T18:50:23.646868579-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 178.62.58.241:42766
WARN 2021-04-08T18:50:23.860441826-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 46.101.72.229:52737
WARN 2021-04-08T18:50:24.073428081-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.131.119:50694
WARN 2021-04-08T18:50:24.281768555-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.139.187:33546
WARN 2021-04-08T18:50:24.495721470-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.142.144:55064
WARN 2021-04-08T18:50:24.710605904-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.152.156:51182
WARN 2021-04-08T18:50:24.916896487-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 138.68.154.164:44520
ERROR 2021-04-08T18:50:25.015563368-05:00 [sn_authd/requests/unlock.rs:48] Error occurred when trying to unlock a Safe: ClientError: Requested data not found
ERROR 2021-04-08T18:50:25.015635803-05:00 [sn_authd/requests/mod.rs:120] Error when processing incoming 'unlock' request with id 1130680454: ClientError: Requested data not found
INFO 2021-04-08T18:50:25.016299671-05:00 [sn_authd/authd.rs:207] Response sent, request 1130680454 complete
WARN 2021-04-08T18:50:25.241203017-05:00 [/home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/sn_client-0.52.9/src/connection_manager.rs:921] Message received at listener from 178.62.58.241:42766
My comment was a bit of a tongue in cheek rhetorical question. Speed will come, first it needs to just work.
1 Like
If you can confirm you are not entering the incorrect passphrase and/or password then there is some other issue. Can you confirm creating some other Safe, and then trying to unlock it from the other computer and see if you still have issues, from the logs it looks like the passphrase is wrong, …or we have a bigger issue
In sn_node.log I get the expected:
Routing(TryJoinLater)
But should I also see in the root_dir, sn_node this error?:
Start node due to error: Routing(Network(UnspecifiedLocalIp))
Is this just because of the first local-node error?
@bochaco Thank you! That was it - just a user-error I was using, unknowingly, wrong passphrase/password. What tripped me up were old values in environment variables in my .bashrc
2 Likes
Awesome, I’m glad we sorted it out, thanks a lot to you too!
3 Likes
I don’t think .1s is realistic, even for the finished product. Latency, alone, with a distributed network like this would make that an impossible feat. However, I am also experiencing long delays of 30-60 seconds for simple things like checking a wallet balance, which is somewhat troubling.
Seeing as this is the first test net in the wild, though, I’ll give them the benefit of the doubt. If we are six months down the road and we are still at 10s, or more, for a response, I’ll start to be concerned.
I’m not fully sure, it could be just part of the Lazy-Messaging / Anti-Entropy where a node is just out of date with section chain keys as compared to other nodes, if this is the case perhaps it’s not an error but should be an informative log entry since the remediation to that is to sync up with other nodes (that’s what the anti-entropy will take care of), so if I’m right this shouldn’t be a problem and just logged incorrectly as Error, again, not fully sure, Anti-entropy is not fully complete yet so…let’s see if other Maidsafe folks know more tomorrow
5 Likes
This is the problem here. AE will remove all sync problems and that is the beauty of it. We will get that 100% in place in the next few days/weeks and no other testnet will have this issue. Then all we focus on is consistency and logic errors. What a great place to be in.
For info
The other part that @bochaco is leading is the API and consistent data. that is also close. With that and AE we have an unfailable network, barring one single issue. That is a loss of consensus, all projects have that issue, however, we have a solution to it and that is exciting. We will lose all data before consistency and that is the holy grail here. Great thing is these are tweaks (apart from single crdt data type) and calculable. We are past the point of don’t know in terms of what’s left. We can now work to timescales or very close to it.
Job done folks and what a job we have done here (be aware I have done almost zero code, this is all the team, not me). All I have done is chat and give some ideas, this team have done the hard graft, @bochaco with almost everything @joshuef with just get it done, @oetyng with economy stuff (all of it), @adam and @qi_ma in routing, @lionel.faber and @yogesh actually pulling it all together, @JimCollinson making sense of it all and @StephenC leading the way to release and confirming capabilities. (@danda and David Rusu with many CRDT components) With @sharontannahill taking care of us all and the cash, the team have been something to just admire. Me, my job has been the most simple it’s ever been and considering we put the original design in place this past 12 months, that is amazing.
A great team, we all lean on each other and all prop each other up when needed. We may not be the best, possibly not the most vocal or self publicising, but we did this and to me that’s beyond incredible.
Hat’s off.
52 Likes
Congrats team.
1 Like