In my opinion, MateSafe is a digital anonymity cash network, like fiat currency. This will be realized by digital bearer certificate(DBC).
However, I think the smart contract platform emphasizes transparency by eliminating intermediaries, so smart contracts as intermediaries must be transparent, that is, open source.
Therefore, I think negatively about whether MadeSafe Network can become a smart contract platform because of its anonymity. Is this right?
Just to be certain, you are referring to the Safe Network here?
If so then the token and its uses/benefits are really only a small part of what the safe network is and will be.
Smart contracts may need to wait for compute on the platform and this will be something that will be done after launch.
But by smart contracts what functions are you wishing to happen. With multi-sig ownerships and other similar things then some of the things done by smart contracts can be done in applications. Pure smart contracts will need to wait.
I think that the smart contract platform is possible only if the anonymity is removed. However, anonymity in MaidSafe is not an option, but an essential feature.
I’m asking what I’m curious about and I don’t want an argument. Trx
Smart contracts basically aim to eliminate the existing intermediaries and introduce new automated intermediaries. However, I believe that the source code of all smart contracts must be public for trust, because even these new intermediaries can trick users. Therefore, as a new intermediary, smart contracts must be made public so that the source code can be viewed by everyone in order to gain trust.
Of course, it would be nice to disclose the results of the smart contract as well, but this may be an option.
If/when smart contracts happen on SafeNet, the code for them could live on the network for anyone to inspect before executing them. Would this be a solution for your concerns?
I don’t like new watchers to audit the source code before uploading like Apple’s app store. But it could be possible, but it will cause a lot of problems, so I don’t see this as the right solution.
I am talking about smart contract platforms like Ethereum. Such a smart contract will be able to function properly as a new automated intermediaries if anyone can view its source code. Thx…
Just to clarify, anonymity on Safe Network is optional for people and code - you choose whether you identify yourself and whether everyone can read some data or code you upload, or whether to restrict who can read it. So I don’t see anonymity as a problem for smart contracts on Safe Network.
But that does not imply that the code that is running on the SN is OS as well. The executable (say wasm for example) could even be private on the SN, the same way the internal state of a SN section is private to the section. The executable could be uploaded to the SN and live (with its state) in a section without the possibility of downloading it from the section.
What’s the difference between smart contracts & compute? Do smart contracts guarantee atomic execution and allow for sub-calls to other contracts? Is consensus a requirement for both (multiple nodes getting the same result for the same calculation)?
Are you implying that Ethereum runs open source contacts? If so, that is not the case. Ethereum runs compiled byte code in the EVM. Normally people publish their source code, then verify through etherscan that the byte code deployed to the network corresponds to the published source code by specifying the compiler version so that etherscan can also compile the contract and compare the byte code.
I too am a bit confused since from my understanding interaction with the SAFE network is done through a series of APIs. So open or closed source anything done at the application layer would use these APIs regardless of how transparent their code was. This is not to say open source smart contracts are not desirable but I’m just saying it just seems it’s not an issue with the SAFE Network itself but rather what the userbase tolerates via their selection of apps to use. Yes intergrating smart contract creation into the network itself would be good but I don’t see why they couldn’t be created at the app layer as well.
As far as i know it’s just the immutable data that is encrypted when uploaded by the client. The mutable (everything else) is stored as clear text, mi wrong on this? Mutable data has access control lists, so you can control who is able to read it.