Is a utopian web a unstoppable reaction between Web2 and smart contracts catalyzed by zero knowledge proofs?

“DNS, but with superior web interoperability: what does it mean for Web3?”

The internet functions as an intricate web of interconnected devices communicating with each other. At its core, it embodies a design philosophy and architecture manifested through a comprehensive suite of protocols. These protocols serve as the established rules and standards governing machine-to-machine communication, designed with the flexibility to assimilate emerging technologies.

Analogous to a driver maneuvering a car without delving into the mechanics of its engine, our role as a technology company amidst the evolving landscape of the web demands a profound comprehension of how historical protocols can seamlessly transition and advance into new paradigms.

Delving deeper into the essence of protocols, consider Namefi's focus on domain name services (DNS) as a prime example. DNS acts as a facilitator, simplifying communication between users and devices. Internet Protocol (IP) represents another cornerstone protocol, enabling communication between devices. Each device is assigned a unique IP address—a numerical string translating into either 32 or 128 bits (IPv4 or IPv6 respectively)—which serves as the conduit for inter-device communication. While these numerical identifiers are indispensable for devices, they are less user-friendly for humans. Herein lies the significance of DNS: a protocol ingeniously designed to bridge this gap by mapping IP addresses to human-readable domain names, such as 'Google.com'. When a user seeks to interact with a domain, their device communicates with a domain name server to obtain the requisite IP address, facilitating seamless connectivity.

In the realm of Web3, protocols extend their influence to various blockchain networks. Within the Ethereum ecosystem, protocols or standards are encapsulated within Ethereum Request for Comments (ERC). Additionally, Ethereum Improvement Proposals (EIPs) serve as the conduit for proposing and implementing new protocols within ERCs. Picture blockchain as the contemporary backbone of computing; rather than obsolescing established protocols, we integrate and refine them to harmonize with modern backends, thereby fostering continuous evolution and innovation.

As Nick Johnson, the founder of Ethereum Name Service (ENS), has pointed out in one of the very first Namefi Spaces, “the enduring legacy of the internet persists alongside our exploration of innovative technologies. It's essential to acknowledge and integrate existing systems, exemplified by our extension of technologies like DNSSEC. Contrastingly, many Web 3 projects tend to adopt an attitude that dismisses preexisting internet infrastructure, an approach I find counterproductive. It's important to recognize that foundational systems are interconnected, and building upon them yields more fruitful outcomes than disregarding their existence.”

With the advent of Web3 technologies, we are expanding the domain of computer science, enriching it with a new facet closely intertwined with cryptography and its myriad applications. Transitioning to Web3 doesn't entail erasing existing components from the computer science landscape.

Similarly, the integration of DNS, ENS, and Web3 protocols presents both a challenge and an opportunity for the next generation to tackle. In a recent ERC development meeting hosted by Namefi's founder and CEO in early April, Todd Chapman, CTO of Snickerdoodle and author of ERC-7529, highlighted efforts to streamline DNS interoperability with smart contracts. This initiative aims to enhance user trust and simplify verification processes within the ecosystem.

Todd's research delves deep into enhancing the interoperability between the traditional web and Web3, which operates on blockchain technology and smart contracts. Armed with a PhD in Aerospace Engineering from Stanford University, Todd now serves as the Chief Technology Officer at Snickerdoodle Labs. His company pioneers innovative solutions that replace conventional cookies for user data collection, all while empowering consumer-centric precision marketing through blockchain technology.

In this dynamic landscape, exploring questions surrounding the improvement of DNS interoperability for Web3 users opens up intriguing possibilities. Particularly, how does this enhancement impact decentralized social networks, the creator economy, and e-commerce in the future?

Delving into Todd's journey down the Web3 rabbit hole, we uncover a fascinating transition from aerospace engineering to the forefront of blockchain technology. His perspective sheds light on the pivotal role of Web3 within the broader realm of computer science, as exemplified by initiatives like ERC-7529. Moreover, Todd offers insights into bridging the divide between the traditional web and Web3, ultimately empowering users to truly own their online experiences.

Original recording:

https://twitter.com/i/spaces/1OdJrjoDYdwJX

Namefi and SnickerDoodle are both bridging interoperability between Web2 and Web3. Namefi is bringing superior performance to domain name services (DNS), what is SnickerDoodle's focus?

Todd Chapman:

SnickerDoodle's mission aligns closely with Namefi's goal of bridging interoperability between Web2 and Web3. While Namefi focuses on domain names, which are integral to Web2 and even Web 1, SnickerDoodle operates in a similar sphere.

In today's digital landscape, we're bombarded with cookie pop-ups, often surrendering our information to third parties without much thought.

Cookies are small pieces of data stored on a user's device by a web browser while the user is browsing a website. These cookies contain information about the user's interactions with the website and can serve various purposes, such as remembering user preferences, tracking user behavior, and enabling personalized experiences. Cookies are commonly used by websites to improve user experience, provide targeted advertising, and gather analytics data. They can be either first-party cookies, which are set by the website the user is visiting, or third-party cookies, which are set by domains other than the one the user is currently visiting. *definition powered by ChatGPT.

SnickerDoodle, however, is pioneering zero-knowledge proof technology that surpasses traditional cookie-based techniques for audience segmentation, targeting, and impression metrics. We can achieve the same functionalities as cookies but with near-perfect privacy.

https://www.snickerdoodle.com/

Many people aren't aware that cookies and device fingerprinting power the personalisation and searcheability aspects of Web2 platforms like Google, Facebook, and Amazon. These platforms recommend content based on sophisticated user profiles created by tracking users across the internet. However, such capabilities are lacking in Web3.

Device fingerprinting is a technique used to uniquely identify devices based on their specific characteristics and attributes. These characteristics can include device type, operating system, browser version, screen resolution, language preferences, installed plugins, and other technical details. By analyzing these attributes, websites and online services can create a unique fingerprint or identifier for each device, allowing them to track and recognize users across different sessions and platforms without the use of cookies. Device fingerprinting is often employed for purposes such as fraud detection, targeted advertising, and analytics, but it raises concerns about privacy and user tracking due to its ability to identify users without their explicit consent. *definition powered by ChatGPT.

This is where SnickerDoodle steps in.

We empower users to own their data.

While users can be directly rewarded by brands for their data, our focus is on enabling personalised experiences in Web3 while preserving privacy.

We're building technology that allows users to have the same personalisation and searcheability enjoyed in Web2 but in a fully privacy-preserving manner.

Users maintain custody of their profile information, and tokenised economics drive how content is curated and recommended to them in a decentralised, permissionless architecture.

This shift towards user-centric data ownership marks a significant milestone in the evolution of the internet. It's an exciting journey, and we're proud to be leading the way in this innovation.

How does SnickerDoodle work to empower user data ownership through decentralised cookie solution? Or what is the decentralised Cookie solution specifically?

Todd Chapman:

It's actually not as complex as it may seem. Thanks to our strong technology partnerships, such as with O(1) Labs, who handle the intricate part of our stack – the ZK-SNARK engine – the most challenging aspect is managed effectively.

Essentially, our focus lies in replacing cookies with zero-knowledge proofs of membership.

In our system, when a user lands on a website, whether it's a website, web app, mobile app, or even a browser extension, and interacts with an application powered by SnickerDoodle, and a business or brand wishes to connect with the user, be it for analytics or first-party surveys, they prompt the user for consent.

Our system automatically generates cryptographically secure identity commitments for the user and utilizes ZK-SNARK efficient hashing functions to achieve this.

For those interested, ZK-SNARK technology introduces its own set of efficient hashing algorithms, such as Poseidon hashes, specifically tailored for its use.

These commitments are then relayed to the blockchain via an arbitrary transaction relay or gas sponsor. This process is entirely permissionless, allowing for flexibility in application layer relays. The identity commitment is stored publicly on the brand's consent contract on the blockchain, ensuring a one-time opt-in process. Once consent is given, the commitment is relayed to the blockchain.

Subsequently, when the user engages with the brand, whether through metrics reporting or interactions with recommendation systems, a zero-knowledge proof of membership is generated from the anonymity set in the brand's consent contract on the blockchain. This proof includes a deduplication aspect, ensuring that if the same metric is reported twice, it can be deduplicated at the server level.

However, across different events, these proofs of membership prevent tracking of the user over time, thus preserving user privacy.

The zero-knowledge proof of membership confirms user consent without allowing third parties to track users over time, which is paramount

---

Victor: Many people may not realize it, but cookies are almost everywhere on the internet.

They have been around since the beginning of the internet, where domains in browsers use them to track users.

The benefit of using cookies is that they allow authentication to occur. For example, users can log in and post on platforms like Facebook or Instagram, or authorize payments. However, cookies have been used to track online activity, which is a double-edged sword. Privacy is a significant concern, as I experienced firsthand while working at Google's Conversion Tracking Team.

I was in the core center of the entire internet's cookie base and witnessed the challenges.

Google had to implement numerous measures to ensure cookies were not abused by third parties or within Google. Access to cookies or associated data requires strict approval processes and audits. Sometimes, accessing cookies was necessary to ensure users weren't exposed to inappropriate content or unauthorized materials.

Cookies are used for both good and bad purposes, making privacy a critical issue. Apple's introduction of a new cookie system in Safari posed challenges for Google and Facebook, as it disrupted user experience and functionality.

So, how do we solve this problem?

I believe the perfect solution lies in Zero-Knowledge (ZK), which is what SnickerDoodle is utilizing. ZK allows verification of specific criteria without revealing unnecessary information. This ensures peace of mind for both users and companies needing to adhere to privacy regulations like GDPR (General Data Protection Regulation).

SnickerDoodle's approach, along with Namefile's assistance, connects the dots between user identity and verification using ZK proofs. This technology has vast potential applications and can provide reassurance to both users and companies navigating privacy concerns. That's how I would explain it in simple terms.

You are also the author of ERC-7529, an Ethereum Request for Comment for the interoperability between the Web native domain assets to smart contract through improving its searchability. How does ERC-7529 achieve this goal?

Todd Chapman:

Domain names are essentially the original digital assets. They were the first digital assets that garnered widespread attention, with people engaging in buying, selling, and trading them.

It was inevitable that this transition would occur, moving the entire process of ownership, transferability, and modularity from legacy cyber systems to smart contract platforms. This transition was not only necessary but also long overdue.

I'm pleased that there are individuals and teams actively pursuing this migration, such as Namefi. The inspiration for the ERC-7529 that we collaborated on stemmed from our recognition that domain names remain a fundamental aspect of the web.

We needed a mechanism within our protocol SDK to provide capabilities to the parent domain when embedded as an iframe into a site. Therefore, we required a way to identify and confirm the association between the smart contract and the parent domain.

An iframe, short for "inline frame," is an HTML element used to embed another HTML document within the current document. It allows content from one webpage to be displayed within a specified area of another webpage. This can include entire web pages, videos, maps, or any other HTML content. The iframe tag creates a window through which the embedded content can be displayed, with its own separate browsing context. It is commonly used for embedding advertisements, maps, or videos on web pages.*definition powered by ChatGPT.

This presented a generic technical challenge that needed addressing, irrespective of the application. Our research led us to an RFC from the Engineering Internet Task Force, RFC8484, which introduced DNS over HTTPS. This standard, adopted in 2018, enables web applications to securely communicate with DNS records directly, bypassing the need for a proprietary third-party service.

The introduction of DNS over HTTPS essentially solved our problem. It allows web applications to interrogate DNS records directly, much like how an ethers client communicates with Ethereum. This means that we can independently interrogate DNS settings within our web app's core package running in an iframe, confirming the association between the domain and the smart contract.

In essence, by leveraging DNS over HTTPS, we have successfully addressed the technical challenge at hand, providing a reliable solution for confirming the association between domain names and smart contracts.

---

Victor Zhou: I just wanted to share this RFC about DNS over HTTPS for anyone tuning in. It's a critical piece that many wallets I've used rely on for retrieving DNS stack features, and it's something we've also built to support.

As you mentioned, it's a powerful data layer that seamlessly integrates with existing browser infrastructure and API endpoints, enabling us to provide accurate DNS information.

Namefi has actually had the opportunity to connect with the author, Paul Hoffman, before. Yes, I actually had the chance to meet him near his home, and we had dinner together. It's reassuring to know that there are like-minded individuals in the technology space who prioritize compatibility and collaboration. We should definitely explore more opportunities to work together.

Interesting! So Tell me what is the outcome of integrating the Web native Internet Engineering Task Force protocol and smart contract?

Todd Chapman:

There's undeniable value in empowering client-side applications to independently verify DNS activities, which essentially serve as the trust center of the traditional internet.

The ability to cross-reference DNS information with blockchain data is a concept that hasn't yet gained widespread adoption in Web3 projects.

As we've discussed previously, Victor, many pressing issues could potentially find swift solutions. Take, for example, the unfortunate scenario frequently observed on crypto Twitter, where NFT artists fall victim to impersonation, leading to the fraudulent sale of counterfeit NFTs. Implementing standards like ERC-7529 could mitigate such risks effortlessly. With this standard, individuals could verify whether an NFT is genuinely associated with the artist's website before making a purchase.

Similarly, enhancing searchability on NFT marketplaces like OpenSea or Rarible could significantly improve user experience.

By enabling users to search collections by domain name, which often correlates with the artist's identity, we could streamline the process of discovering and interacting with desired NFTs.

What's more, by relying directly on DNS instead of proprietary implementations, we can establish a more robust verification framework.

Encouraging more projects to embrace the modular capabilities of traditional DNS, particularly DNS over HTTPS, holds immense potential.

Doing so would not only enhance verification processes but also elevate searchability and discoverability within the Web3 ecosystem. There's certainly room for improvement in these areas, and leveraging DNS technology could be a pivotal step forward.

Do you agree that the lower hanging fruits lying in the Web3 would be to capitalize on the cross-referencing potential between DNS and smart contracts?

Todd Chapman: With that proposal, if that's the route people choose to take, it's very simple to integrate into your project. It doesn't introduce bloat and only requires minimal logic to be added to a smart contract. The added logic doesn't interact with any existing logic.

On the DNS side, all you need to do is add a txt record. Adding a txt record to your domain name doesn't disrupt anything. Then, on your smart contract, if it's upgradable, you only need to add a single storage variable and a couple of read and write methods.

Once your project is capable of being associated with your domain name, you can explore various possibilities. This approach is the lowest hanging fruit. By making yourself compatible with being associated with your DNS name, you can experiment and derive synergistic value as more projects adopt this approach.

This compatibility is crucial for searchability. If only one project associates its smart contracts with its domain name, it won't significantly improve searchability. However, it does provide assurance to customers that the smart contracts they interact with are associated with your business domain, which is a valuable addition.

To truly enhance searchability, more projects need to recognize that DNS remains the original digital asset and the primary method people use to find things on the internet.

Adding a TXT record to your DNS and linking your smart contract to your domain has no downsides but can significantly enhance value as more projects adopt this approach, making Web3 more searchable and compatible with traditional technologies.

New Narrative: Data Searchability Layer Vs. Data Availability Layer

Namefi Customer Q&As:

Page

My name is Page. I've been exploring the Web2 and Web3 space, hoping to discover innovative solutions for the next 10 or 20 years. I must say, I love what you're sharing. Although I don't fully grasp all the technical details, I sense a simple elegance in your approach, which is something I always appreciate. It seems you're advocating for solutions that are accessible and open to innovation, rather than imposing a rigid standard that requires everyone to conform to a single platform.

As a marketer, I understand the importance of making these concepts marketable.

Additionally, I found it intriguing when you mentioned the shortcomings of platforms like OpenSea in terms of attributes and sortability. Are you suggesting that these marketplaces lack robust features beyond basic name recognition?

Todd Chapman:

Firstly, let's address the simplicity of this ERC-7529 proposal. It's arguably one of the simplest and most straightforward ERCs imaginable, making it incredibly easy to implement. Essentially, if you can navigate cloud services, setting up a TXT record and opting into connecting DNS to Web3 becomes a breeze. It's truly that straightforward.

Now, shifting gears to the topic of searchability, it's crucial to recognize the current gap in Web3.

While there's considerable research focusing on the data availability layer, such as eigenlayers, which are gaining traction, there's a glaring absence of a dedicated searchability layer in Web3.

Consider the success of Web2 platforms like Google, Facebook, and Amazon. Their popularity stems from the fact that they prioritize discoverability.

Whether it's the Google search bar, the Facebook feed, or the Amazon Marketplace, these platforms excel at providing recommendations and making content easily discoverable.

In contrast, the same level of cohesion and searchability is lacking in Web3.

However, initiatives like SnickerDoodle and Namefi are beginning to address this gap, presenting a significant opportunity to bridge the divide between the searchability of Web2 and Web3.

Monopoly of centralised nameservers - consequences in sale commisions and text record management

Page:

Well, that's fantastic to hear. From what I envision, over the past 15 years in the Web2 space, I've encountered countless requests for text record verifications. Engineers often approach me, stating that all I need to do is provide my name servers and a text record. However, what they fail to grasp is the burden this places on me as a Web2 domain owner, especially when multiple parties are vying for access to my DNS server.

The sheer number of requests can become overwhelming, and it often feels like I'm left to manage DNS issues on my own. In many ways, I'm beginning to see DNS management as the new hosting – a task that requires constant attention and coordination with multiple parties. It's a shift in perspective that highlights the evolving nature of web infrastructure.

I'd love to hear your thoughts on this matter. Feel free to share your insights.

Victor:

Exactly, Page, you're absolutely right. One of the key advantages or philosophies of Namefi is our commitment to working with existing systems as much as possible. Our compatibility serves as our competitive edge. Allow me to draw an analogy or metaphor using a map.

When Thomas Edison first introduced electricity, his goal was to bring light to the world. He began by wiring lights, introducing a revolutionary technology that made cities come alive. However, he didn't suggest tearing down homes and rebuilding them with integrated wiring. Instead, he simply routed the lights through existing structures as a demonstration. He didn't advocate demolishing homes. After all, many people were living in those homes and weren't prepared to undergo such drastic changes just to install lights.

We embrace a similar philosophy at Namefi. When you integrate with SnickerDoodle, for example, we ensure compatibility in a seamless manner. By leveraging text records (txt) and DNS, we know how to connect the dots without disrupting your existing setup. Your website continues to function, your emails still work, and communication with teammates and customers remains uninterrupted. You don't have to tear down your metaphorical house.

Of course, there's always room for improvement and innovation. But our approach is centered on maximizing compatibility and minimizing disruption, ensuring a smooth transition without the need for drastic changes.

Page:

Victor, let me interject for a moment. I'd like to emphasize the perspective of domain name owners, which may not always align with the ease of moving a text record to your platform. From our standpoint, it's not as straightforward as it may seem.

• We're faced with the challenge of finding a DNS provider that accommodates all our needs, or alternatively, selecting the most dominant use case for our domain name and hoping that the chosen provider allows us to add text records.

To illustrate, consider the example of GoDaddy. If we opt not to use their name servers, we incur a 10% higher commission on our sales. This means that if we generate $10,000 in monthly sales, it would cost us an additional $1,000 per month to move away from their name servers.

• Moreover, they don't always cooperate when it comes to updating text records.

This dilemma underscores the complexities faced by domain name owners.

We're torn between accommodating multiple parties vying for our exclusive name servers and utilizing independent services that work with text records, all while navigating conflicting interests.

I appreciate your acknowledgment of these challenges, and I'm glad to hear that your platform will strive to address them.

It's essential to provide support for domain owners and to offer flexibility in how we manage our DNS settings.

I'm reassured knowing that your roadmap includes plans to make it easier for those without name servers on their site, as well as enabling the use of non-name servers with convenience. This approach aligns with our needs and provides the flexibility we require.

Victor

This is precisely why domain names should be owned via a public blockchain network. Companies like GoDaddy often exploit their dominant position, knowing that users have limited recourse. They can easily take advantage of customers because there's often little that can be done to counter their actions.

Page:

As I reflect on my experiences over the years, I've managed my own domain servers and even commissioned scripts to handle forwarding and other tasks. Looking ahead to the next few years in what I like to call the Web2.5 domain space – the space between transitioning Web2 domains to Web3 or integrating Web3 domains into Web2 – I foresee name servers playing a crucial role.

The concept of connecting HTTPS and DNS is intriguing. It's almost as if we're inscribing our digital assets in a functional manner. Am I stretching too far with this analogy?

Victor:

No, not at all. In fact, I think you're right on point. Additionally, I'd like to touch upon why companies like CodeID or AppToNick, among others, often request users to use their name servers.

I can understand the rationale behind their approach, and I like to assume good intentions. I respect the technology and effort they've put into making domains easier to buy and sell. It's evident that they've made significant strides in this area. However, I can also appreciate why their previous methods were necessary. In the past, configuring a text record, for example, could be quite challenging for users like yourself.

Platforms like GoDaddy offered a convenient solution by simplifying the process. They could handle tasks like setting up a parking page or other services with just a simple name server configuration. This approach undoubtedly improved user experience, and it's a path we've also followed thus far.

What Namefi can do even better is through tokenization and collective ownership. Users can retain control and approve changes on their end, empowering them to update name servers without reliance on a single entity. This shift towards tokenization not only enhances ownership rights but also facilitates authentication, delegation, and collective decision-making.

I've been discussing this concept extensively on my social media channels, particularly regarding account abstraction. Native account abstraction, scheduled for implementation in Ethereum's upcoming hard fork (EIP 3074), will streamline authorizations and pave the way for a more intuitive user experience.

As these developments unfold, there will be a surge in user-friendly applications and tools built upon this foundation. Namefi aims to be at the forefront, providing users with clear insights into the authorization process and offering human-readable, globally unique identities through Namefi.

Utopian Science Fiction Future built on Smart Contracts

Namefi Yeah, absolutely. Victor, thank you for your insightful explanation regarding name servers and the exciting prospects they hold for future developments. Now, I'm not sure if anyone has any questions for Todd regarding cookies and DNS. If not, I have another question, more focused on the future.

We've discussed extensively how easily accessible it is for projects to integrate TXT records and smart contracts to enhance cross-referencing and searchability. However, looking ahead, I can't help but reflect on the shift we've observed in the blockchain space. Initially, there was this fervent idealism about decentralizing everything, from Uber to various other centralized entities. While that idealism may have faded somewhat, what we're discussing here is essentially bridging the traditional web with smart contracts, opening up a realm of possibilities.

This year, with the approval of Bitcoin ETFs and the increasing institutional adoption of blockchain infrastructure, we're witnessing a significant shift. As domains become tokenized and gain more exposure in the market, and as industry standards for higher searchability are adopted, we can envision a future where many of the ideals from the past, though perhaps not fully realized, could come to fruition.

So, Todd, I'm curious about your vision for the future. Can you visualize a world where everything operates seamlessly through smart contracts and automation? How do you imagine such a future unfolding?

Todd Chapman:

The era we find ourselves in, where trustless blockchain networks intersect with mind-bogglingly complex zero-knowledge proof technology, is poised to be transformative. While the roots of web technology trace back to the 1980s, its practical application only emerged toward the end of the 20th century.

This Web3 shift won't just resemble the transformative impact of the internet, which emerged in the 1970s and found widespread commercial use in the 1990s. Instead, it's more akin to the digital revolution sparked by the invention of the transistor.

Just as the advent of digital computers revolutionized analog calculation methods, the rise of trustless cyber systems underpinned by zero-knowledge proofs will be similarly revolutionary. These advancements unlock entirely new business models that were previously inconceivable. Moreover, they provide unprecedented security guarantees that were once relegated to the realm of science fiction.

Before the Great Financial Crisis, the notion of trustlessness was nonsensical.

However, with the emergence of Bitcoin, trustless systems became accessible to anyone with internet access. Similarly, zero-knowledge proofs, once considered science fiction, can now run on personal devices like smartphones, enabling concepts like proving membership without revealing identity. The potential economic value these innovations unlock is staggering.

Ultimately, businesses will inevitably transition to Web3 technologies, leveraging zero-knowledge proofs, trustless public networks, and tokenization of ownership.

While it may take time for non-technical individuals to grasp the full scope of these advancements, once understood, their superiority over previous methods becomes evident. Just as the digital revolution transformed manual calculations with digital computation, the transition to trustless systems represents a quantum leap forward in economic efficiency and security.

Victor:

Absolutely, Todd. I couldn't agree more. One of the core tenets of our company, as outlined in our founder's manifesto, is the concept of digital trust. We're witnessing a pivotal moment in human history where trust is undergoing digitization, a process akin to automation. My friend and ally, Eli Ben-Sasson, founder of Starkware, often refers to this as social integrity technology. Essentially, we're speaking about the same phenomenon.

To draw a historical parallel, I liken this era to the time of Johannes Gutenberg and the invention of the printing press. In those days, information was arduous to replicate and disseminate, typically requiring manual transcription. With the advent of the printing press, information became easily replicable, leading to an explosion of knowledge. Similarly, Bitcoin pioneered this concept in an economic context, leveraging game theory and the proof-of-work mechanism to imbue trust in mathematical formulas governing human behavior. Zero-knowledge proofs (ZK) represent another facet, ensuring trust without relying on human capabilities to verify.

Moreover, emerging technologies like quantum computing offer intriguing possibilities, such as including signatures in quantum states, which I'll delve into further in another Twitter space discussion. In essence, we're witnessing a transformative period in human history where trust is being tokenized and digitized, fundamentally altering how people collaborate and interact with one another.

Page Howel: Hey there! It's understandable to grapple with the delicate balance between trust and confidentiality, especially in light of recent developments like Google's ability to search through your ETH wallet. As an OG in this space, it hits close to home. I value my privacy but also recognize the necessity of trust in trustless systems.

Victor:

Absolutely, your concern is entirely valid, and it's precisely why we're here. Todd and I are excited to share that there's a solution that allows you to have both trust and privacy without compromising either. It's called Zero-Knowledge (ZK), and it's what Todd and our startup, SnickerDoodles, are all about. With ZK technology, we're pioneering a path that ensures trust in transactions while safeguarding your privacy.

Todd Chapman:

Absolutely, zero-knowledge proofs offer precisely the solution you're seeking.

However, it's worth pondering whether governments will permit ordinary citizens to utilize zero-knowledge proofs to maintain their privacy and control over their information.

This is a topic for another discussion, as it's not out of the realm of possibility for governments to view zero-knowledge proofs as potentially dangerous due to their significant enabling capabilities.

Consider the historical context of compiler control in the 90s, where there were serious discussions about making compilers controlled software. Similarly, there could be attempts to regulate zero-knowledge proof technology and public ledger technology.

My point is, without vigilance, we could find ourselves in a scenario reminiscent of a Neil Stevenson novel sooner than we think.

Future Twitter

Namefi: Certainly! Todd, envisioning a future Twitter with ZK login and people using their DNS as their internet identity is intriguing. How would you foresee this transformation impacting user experience, privacy, and the overall dynamics of social media interactions in the case of Twitter?

Todd Chapman:

In the future, a Twitter built on these technologies would likely maintain the familiar look and feel of the current platform. However, it would offer significantly enhanced privacy guarantees, ensuring better control over who can access your information and how secure it remains. While the user experience would remain similar, the underlying infrastructure would be much more robust and resistant to attacks or manipulation. Essentially, it's about preserving the essence of Twitter while upgrading its security and reliability.

Victor:

In envisioning the future of platforms like YouTube and Twitter, I believe they will still feature text, images, and videos, much like they do today.

However, there will be a notable shift in the user experience. Instead of encountering a random assortment of users, you'll find yourself in a more familiar and trustworthy environment, surrounded by friends and connections you've consciously allowed into your space.

This curated network will ensure that the information you see is relevant and reliable, minimizing the presence of scammers or impersonators.

Additionally, there will be mechanisms in place to recognize and reward valuable contributions within this community. Individuals who consistently provide valuable insights or content will earn quantifiable rewards and build a strong reputation within space. While the outward appearance of these platforms may remain similar, the underlying dynamics will be significantly different.

To draw an analogy, think of it like a house. The basic layout of a living room may not change much over time, but the atmosphere and the people who inhabit it can vary greatly. With advancements in technology and community management, the experience of using these platforms will feel both familiar and distinctly different, akin to stepping into a room with modern amenities and a welcoming atmosphere compared to one from centuries past.