Still wondering how Preferido.us is Reinventing Identity Using Blockchain + AI ?

As stated: Some architectural models or reasoning steps are proprietary to the ongoing research and developments. Others may evolve into community-adopted standards — if and when they’re openly discussed, peer-reviewed, and deemed contextually appropriate. Adoption remains case-specific. This is also 25% of Page 1 in discussion.

As stated: This isn't a conclusion — it’s an ongoing exploration. Our work so far focuses on simulating, documenting, and co-developing decentralized identity flows using tools like ENS, IPFS, and GPT-4. We’re 25% into Page 1 of our MVAF (Minimal Viable Activity Flow) and actively capturing how AI and blockchain can coexist in practical, user-facing systems.

Title: From Domain to Decentralization: How Preferido.us is Reinventing Identity Using Blockchain + AI

Posted on: June 11, 2025 By: Abhishek Kumar | Preferido.us | Nuture.eth

👋 Welcome to a Real-World Experiment

Ever wondered what happens when someone visits a website like https://preferido.us?

Instead of typing in a password, what if your browser quietly asks your wallet, "Hey, do you own this identity?" And what if all of that was validated through Ethereum, IPFS, and supported live by a GPT-like assistant? That’s what we’re building.

We call it a Minimal Viable Activity Flow (MVAF) — and we’re 25% through Page 1.

🧠 What Are We Doing?

We’re building a decentralized verification system where your ENS domain (Ethereum Name Service) becomes your login. MetaMask becomes your ID card. And IPFS holds the proofs.

Here’s where it gets more exciting: everything we’re building is co-developed and tested using an AI (like ChatGPT), which simulates system behavior, breaks down edge cases, and helps us validate architecture.

💡 Who Cares and Why It Matters

Whether you're from IT, design, business, or blockchain — here's how it fits:

• For Developers: Identity checks happen using cryptographic signatures instead of passwords. If wallet or gas fails, fallback logic is already built in.

• For Designers: Every state — verified or unverified — is clearly mapped. Randomness, user failures, even missing wallets are simulated.

• For Product/Startup folks: This is a prototype for how decentralized apps (dApps) can onboard users without friction. One domain. Zero central servers.

• For Communities: We're documenting every step. This is not just code — it’s a shared journey into decentralized digital trust.
  

🔬 Simulation Snapshot

Above: A high-level view of the MVAF simulation flow and domain boundary handoffs.

We're simulating and testing:

• No wallet installed → UI guides to install MetaMask

• Low GAS → Warning + fallback

• ENS resolver fail → Retry

• IPFS delay → Alternate gateway switch

• All randomness modeled with GPT-4 as co-agent

These aren’t just theories. They’ve been run, tested, discussed, and logged.

🚀 What’s Next?

• Finish Page 1 of MVAF (shopping personalization)

• Add guest (non-wallet) mode

• Publish code + open test environment

• Open source our AI-based co-design model
  

📍 Clarifying Our Efforts

This isn't a conclusion — it’s an ongoing exploration. Our work so far focuses on simulating, documenting, and co-developing decentralized identity flows using tools like ENS, IPFS, and GPT-4. We’re 25% into Page 1 of our MVAF and actively capturing how AI and blockchain can coexist in practical, user-facing systems.

These shared learnings aren’t directives or roadmaps for everyone. Their value depends on the context — whether you're part of a technical team, business group, or broader community. Each audience brings its own perspective, and our goal is to present a transparent foundation that can be interpreted and adapted accordingly.

Some architectural models or reasoning steps are proprietary to the ongoing research and development process. Others may evolve into community-adopted standards — if and when they’re openly discussed, peer-reviewed, and deemed contextually appropriate. Adoption remains case-specific.

It’s especially important for me to clarify these boundaries — not only as a builder but also as someone who has lived under the weight of systemic threats and long-term victimization for over 20 years. Much of this work is deeply personal. Every architectural decision, every validation loop, and every edge case modeled is rooted in surviving trauma and imagining systems that respect resilience and human dignity.

If you're curious or want to explore with us, visit https://preferido.us — or check back for continued progress and shared artifacts.

— Abhishek Kumar