I thought it was everything encrypted except pvt data.
So many things change I can’t be sure.
1 Like
We are encrypting all data and looking to make sure that is the case, although public data is readable via the data_map, i.e. the key to where data is and how to decrypt it. So you cannot decrypt in place, but you can recover enough bits to decrypt public data.
Think of it in 2 ways
We want to ensure all data held by any farmer is encrypted. To protect farmers etc.
We want publically readable data, so there is a mechanism to decrypt public data at the client. (the network nodes don’t know how to do this)
10 Likes
Thx… Your answer solved my question.
2 Likes
Compute on SN means/entails that the output of a computation can be trusted and that no third party has to verify the output (trustless computing - no trust in a third party) - so consensus via a networking mechanism. You may also think of this as a VM - a virtual machine that exists within SN.
Smart contracts are code that run in the compute VM environment. This is vital for smart contracts, otherwise their output can’t be trusted.
The network overall is like a VM, but only for the specific tasks laid out for Fleming and Maxwell - hence no ability to process smart contracts. The addition of a compute VM will hopefully come after.
3 Likes
wasm on SAFE?
Definitely. I made some test repos with this in mind while figuring out a way to create a decentralised git portal. WASM is used in the first proof of concept (GitHub - happybeing/p2p-git-portal-poc: p2p git portal proof-of-concept using Svelte Golang/WASM (experimental)) and the prototype (GitHub - happybeing/p2p-git-portal-wasi: Peer-to-peer Git Portal in Svelte, Rust/WASI on WasmerJS).
2 Likes
Smart Contract is quite a catch-all term though isn’t it? There are potentially things that people do with SCs that could be accomplished with DBCs.
So I guess it depends on the use-case.
5 Likes
@TylerAbeoJordan As far as trusting anything, you cannot trust any output from the computer without verifying it. A compute VM environment is hackable just like a native environment. Just mod the code on the PC to redirect the job to hacked code on a VM or native. No way for remote computer/person to know. There has to be a way to verify the computation or else its suspect.
Its the checks and balances that makes it trustable, not the compute VM
3 Likes
I’m thinking of a network VM that picks consensus answer. A local VM is a different animal.
I’m not following how that can work. Can you give more detail or an example?
1 Like
I think we might use the anology that the SafeNetwork is almost like rendering on a GPU (parallel section consensus) vs rendering on a CPU (total network consensus).
In short.
3 Likes