Content
@
https://ethereum.org
0 reply
0 recast
0 reaction
Conor Svensson (csvensson.eth)
@csvensson
The #TLS protocol gave web users a way to securely share information with websites. This was a major step forward for privacy and #UX. Users became accustomed to the padlock icon when sending information to websites which made them feel safer transacting online and the underlying data was encrypted. The TLS model isn't perfect, whilst it does secure communications with websites, users have to implicitly trust the operator of the site they are interacting with. A secure connection is no good if the data is being stored in an unsecured data store. In addition, there is a degree of centralisation with TLS as it relies on Root Certificate Authorities which establish a chain of trust for issuing certificates. However, it was a major innovation as far as bringing more people online is concerned. What does the equivalent look like in #web3? ctd đ
1 reply
2 recasts
2 reactions
Conor Svensson (csvensson.eth)
@csvensson
We have privacy protocols coming online such as @aztecnetwork which provide full privacy for users. However, at @enscribe what we want to create is something that is as powerful to users as the TLS padlock, which will tell them that the #smartcontract they are interacting is issued by the organisation or individual they believe it to have been. One part of this is to ensure teams are naming their smart contracts with @ensdomains. There are also standard procedures such as smart contract verifications via services such as @sourcifyeth that help here. Having attestations from contract audit firms would also be beneficial. But is this enough? ctd đ
1 reply
0 recast
0 reaction
