qTeVerse on Bluesky — Decentralized Marketplaces for the AT Protocol

🦋

qTeVerse Meets Bluesky

The first full-scale decentralized marketplace ecosystem built natively on the AT Protocol. Twelve apps, zero databases, one open network.

Bluesky PDS Native AT Protocol XRPC .NET 10 / MAUI

Why Build on Bluesky?

The AT Protocol isn't just for social networking. Its decentralized identity, user-owned repos, and open XRPC API make it the perfect foundation for a marketplace ecosystem.

How qTeVerse Extends the Bluesky Network

qTeVerse doesn't compete with Bluesky — it extends the network beyond social into commerce, education, entertainment, and services.

Network effect multiplier: Every Bluesky user is a potential qTeVerse user with zero onboarding friction. Same handle, same identity, same PDS. They don't need to create anything new — they just install an app and sign in.

What This Means for the Bluesky Ecosystem

📡

Beyond Social

qTeVerse proves the AT Protocol isn't limited to social networking. The same infrastructure that powers posts and follows can power marketplaces, education platforms, streaming services, and more.

🏗

Builder Ecosystem

qTeVerse provides a template and shared library for building AT Protocol applications. Any developer can use the same patterns to create new marketplace categories and contribute to the ecosystem.

🔍

Custom Lexicon Showcase

With 11 marketplace lexicons and 8 storage collections, qTeVerse demonstrates how custom lexicon namespaces enable entirely new application categories on the AT Protocol.

💱

Token Economy Model

qTeCoin introduces a token economy layer to the AT Protocol. Users earn rewards for participation, creating aligned incentives without requiring a separate blockchain or cryptocurrency.

🔒

Privacy-First Architecture

qTeVerse demonstrates that AT Protocol repos can store private application data alongside public social data. Private collections (app.qte.*) coexist peacefully with public Bluesky data.

🧬

Novel Data Science

The qTe encoding engine brings quantum-physics-inspired mathematics to the AT Protocol. The 65-to-64-byte bijective mapping and symph identity system are original contributions to data encoding.

Technical Integration Points

For Bluesky developers and AT Protocol engineers: here's exactly how qTeVerse interfaces with the network.

AT Protocol Endpoints Used

Endpoint	Purpose
`com.atproto.server.createSession`	User login
`com.atproto.server.refreshSession`	Token refresh
`com.atproto.server.deleteSession`	Logout
`com.atproto.repo.createRecord`	Write data
`com.atproto.repo.getRecord`	Read single record
`com.atproto.repo.listRecords`	Paginated queries
`com.atproto.repo.putRecord`	Update records
`com.atproto.repo.deleteRecord`	Remove records
`com.atproto.repo.uploadBlob`	Binary data uploads

Custom Lexicon Namespaces

Namespace	Visibility	Records
`com.qte.marketplace.*`	Cross-user discovery	11 types
`app.qte.storage.*`	Private (not indexed)	7 types
`app.qte.collection`	Public sharing	1 type

Marketplace lexicons are designed for cross-user discoverability. A buyer can query a seller's repo for their com.qte.marketplace.listing records directly. Storage collections are private by design and not indexed by any relay.

🔗 Fully Interoperable

qTeVerse uses zero proprietary network protocols. Every API call is a standard AT Protocol XRPC request. Any AT Protocol client, any PDS provider, any relay — qTeVerse works with all of them. The data format is plain JSON stored as standard AT Protocol records.

Open Data Format

Every qTeVerse record is a standard JSON document with a $type field matching its lexicon NSID. Here's what they look like.

Marketplace Listing Record

{
  "$type": "com.qte.marketplace.listing",
  "title": "Handmade Ceramic Mug",
  "description": "Hand-thrown stoneware...",
  "price": 24.99,
  "currency": "USD",
  "category": "crafts",
  "sellerDid": "did:plc:abc123...",
  "sellerHandle": "potter.bsky.social",
  "imageRefs": ["bafkrei..."],
  "status": "active",
  "createdAt": "2026-04-10T15:30:00Z"
}

Marketplace Profile Record

{
  "$type": "com.qte.marketplace.profile",
  "displayName": "Sarah's Pottery Studio",
  "bio": "Handmade ceramics since 2020",
  "roles": ["seller", "buyer"],
  "location": "Portland, OR",
  "rating": 4.8,
  "totalSales": 142,
  "avatarRef": "bafkrei...",
  "createdAt": "2026-01-15T10:00:00Z"
}

Standard JSON + Standard AT Protocol = Total interoperability. Any tool that can read AT Protocol repos can read qTeVerse data. No proprietary formats. No binary encodings (except for qTe symph data, which is intentionally opaque). The marketplace layer is fully transparent.

Get Involved

Whether you're a Bluesky developer, an AT Protocol builder, or just curious about decentralized marketplaces — there's a place for you in qTeVerse.

👨‍💻

Build an App

Use the qTe shared library and marketplace lexicons to create your own qTeVerse app. Publish it through the qTeVerse app store.

⛏

Mine the Symph Space

Run qTeCoin and contribute computing power to the symph encoding network. Earn tokens and coins for your participation.

🤝

Use the Marketplace

qTeVerse is built by sunsingsoft on the open AT Protocol.