How We See Web3

When we talk with people about our technology they often ask, “So, is this Web3 stuff?” 

Our answer is, “yes and no.” We definitely are Web3 in the most broad definition of the term—the next iteration of the Internet, privacy-focused, and decentralized. That said, we’re not looking to build it with blockchain.

A common approach to implementing the core principles of Web3 (decentralization and data ownership) is the use of the blockchain data structure, which is immutable and append-only. This may be beneficial to enterprises with private blockchains, affording businesses and suppliers an environment of trust whereby transactions are viewable and immutable. There are also cases where institutions of higher learning or auction houses might use blockchains as ledgers to establish provenance of materials and goods as a deterrent to looting and forgeries. 

While there is an argument for legitimate use cases of blockchain, the structure itself is only one of many Web3 data structures;  it has compromises that for some, are simply untenable. For example, the energy costs as well as the strain on the computer processor supply chain have been detrimental to the environment and the global economy. Not to mention, there are major privacy concerns derived from blockchain given that it is explicitly designed to make data publicly viewable–in fact, most people don’t want everything to be remembered; people should have the right to be forgotten and the right to control their data.

Here’s how we’re building a better Internet:

The atProtocol

The atProtocol is a new, open network protocol that allows every person, entity, and thing to be directly addressable on the Internet (without needing a fixed IP address) and to exchange end-to-end encrypted data with any other person, entity, or thing. 

atSigns

This E2EE (end-to-end encrypted) data exchange is possible thanks to the atSign, a unique address connected to each person, entity, and thing using the atProtocol. An atSign does several things:

• Encrypts
• Each atSign cuts its own keys that it uses to encrypt data specifically for a designated atSign and no one else. Data is encrypted before sending, and cannot be decrypted until it has been received by the designated atSign.
• Stores
• Each atSign communicates with its own dedicated microserver that stores data associated with that atSign (encrypted, always!)  
• Authenticates
• Only the atSign owner has access to their private key, which is used to prove their identity, eliminating the possibility of their data being seen by unwanted third parties.

The atPlatform

The atPlatform and SDK let developers build atProtocol applications that are completely end-to-end encrypted and privacy compliant by default, with no effort on the developer’s part. 

Atsign IoT

For IoT devices, the atProtocol provides baked-in security, and removes the need for traditional security layers like firewalls, VPNs, and static IP addresses.

Here’s how that works: 

With billions of connected IoT devices already in service, with no slowdown in sight, it is imperative that we build an environment that fully secures all the data. The atPlatform and the underlying atProtocol do just this:

For Device Manufacturers, Simplified Security & Setup.

• Zero Network Attack Surface
• Zero Open Ports
• Zero VPNs
• Zero Firewalls
• Zero Static IPs

For Consumers, Your thing, Your data.

• End-to-End Encrypted data transfer
• Encryption keys on both the sender’s and receiver’s end
• Even if a third party is managing your device usage/interaction, they can’t see your data

Our version of Web3 is ideal, in that it’s cleaner, private, less stressful, healthier for the planet, and more efficient for individuals and businesses.

Come chat about our open-source architecture, by emailing us at iot@atsign.com 

Follow our social channels to stay informed on all things Atsign:

https://twitter.com/atsigncompany

https://www.youtube.com/c/AtsignCo