You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Polish Group B project pages: fix inaccuracies, remove boilerplate, tighten copy (#10)
- ONE box: remove repeated "revealed at launch" filler, add verified tech stack (Shadcn UI, ecosystem-ui auth), cut Core Philosophy boilerplate
- ONE deal: fix fabricated directory tree to match actual repo structure, correct auth package reference from one-id-auth to one-ecosystem-ui, update wallet tooling from WalletConnect to Reown AppKit, add missing deps (Sonner, React Router)
- ONE chat: fix broken GitHub link (one-chat-landing -> one-chat), add multi-channel and Discord bridge capabilities from verified backend, add ONE loot/notification integrations, cut Core Philosophy boilerplate
- Overview: fix ONE pump subtitle to match actual product (sentiment tracking, not token launch), reorder projects by substance, fix Twitter handle and add target=_blank, standardize field labels
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
**ONE box** is a mystery experience platform within the ONE ecosystem. Full details will be revealed upon launch — stay tuned for announcements on official channels.
9
+
**ONE box** is an unrevealed experience within the ONE ecosystem. The concept, mechanics, and full details will be disclosed at launch.
ONE box is an upcoming addition to the interconnected suite of ONE products. Each product in the ecosystem serves a distinct purpose within the decentralized infrastructure, and ONE box will be no exception.
17
+
ONE box is in active development with a teaser landing page live at [box.expl.one](https://box.expl.one){:target="_blank"}. What it does, how it works, and how it connects to the rest of the ecosystem will be announced when the project launches.
18
18
19
-
Full details will be unveiled at launch. Follow official channels for announcements.
20
-
21
-
---
22
-
23
-
## Core Philosophy
24
-
25
-
Like every project in the ONE ecosystem, ONE box is built on three principles:
26
-
27
-
-**Open Source** — Every line of code is publicly available on GitHub
28
-
-**Community-Driven** — Built by and for the community
29
-
-**Fair Revenue Model** — 45% to Node owners, 45% to Creators, 10% to founders
19
+
The codebase is open source. If you want to look under the hood before launch, the repository is public.
30
20
31
21
---
32
22
33
23
## Technology Stack
34
24
35
-
ONE box is built with modern web technologies for optimal performance:
36
-
37
25
-**Frontend**: React 19, TypeScript
38
26
-**Build Tool**: Bun, Vite
39
27
-**Styling**: Tailwind CSS
28
+
-**UI Components**: Shadcn UI (Radix primitives)
40
29
-**Icons**: Phosphor Icons
41
30
-**Animations**: Framer Motion
42
-
-**Deployment**: AWS S3 + CloudFront
31
+
-**Authentication**: ONE id via `@explorills/one-ecosystem-ui`
43
32
44
33
---
45
34
46
35
## Roadmap Status
47
36
48
37
**Current Status**: In Progress
49
38
50
-
ONE box is currently in development. The landing page is deployed at [box.expl.one](https://box.expl.one){:target="_blank"} with the full experience coming soon.
39
+
The landing page is deployed. Full product launch is part of the 2026 roadmap.
**ONE chat** is the real-time communication layer for the ONE ecosystem. A WebSocket-based chat system embedded across all ONE projects, enabling authenticated users to communicate without leaving the platform they are using.
9
+
**ONE chat** is the real-time communication layer for the ONE ecosystem. A WebSocket-based chat system embedded across all ONE projects, so authenticated users can talk without leaving the platform they are on.
ONE chat provides a single global chat channel accessible from any ONE ecosystem project. Users authenticate through ONE id and can send messages, reply to others, react with emoji, mention users, and track unread messages — all in real time.
17
+
ONE chat provides multi-channel real-time messaging accessible from any ONE ecosystem project. Users authenticate through ONE id and can send messages, reply, react, mention other users, and track unread state — all in real time.
18
18
19
19
Key capabilities:
20
20
21
-
-**Real-time messaging** — WebSocket-based instant message delivery across all connected clients
22
-
-**Message editing & deletion** — Edit or remove your own messages after sending
23
-
-**Reactions** — Add and remove emoji reactions on any message
21
+
-**Real-time messaging** — WebSocket-based delivery across all connected clients
22
+
-**Multiple channels** — Separate channels for general discussion, support, and more
23
+
-**Message editing and deletion** — Edit or remove your own messages after sending
24
+
-**Reactions** — Emoji reactions on any message, with points credited to the author via ONE loot
24
25
-**Replies** — Reply to specific messages with inline previews
25
26
-**@mentions** — Mention users with autocomplete search
26
27
-**Typing indicators** — See when other users are composing messages
27
-
-**Unread tracking** — Per-userread state with unread count and mention notifications
28
+
-**Unread tracking** — Per-user, per-channel read state with unread counts and mention notifications
28
29
-**Message history** — Cursor-based pagination for scrolling through past messages
29
-
30
-
---
31
-
32
-
## Core Philosophy
33
-
34
-
Like every project in the ONE ecosystem, ONE chat is built on three principles:
35
-
36
-
-**Open Source** — Every line of code is publicly available on GitHub
37
-
-**Community-Driven** — Built by and for the community
38
-
-**Fair Revenue Model** — 45% to Node owners, 45% to Creators, 10% to founders
30
+
-**Discord bridge** — Messages can bridge to Discord channels
39
31
40
32
---
41
33
@@ -47,13 +39,15 @@ Like every project in the ONE ecosystem, ONE chat is built on three principles:
47
39
-**Database**: SQLite (WAL mode) for message persistence
48
40
-**Authentication**: ONE id token validation (internal HTTP)
49
41
-**IDs**: ULID for time-sortable unique message identifiers
42
+
-**Integrations**: ONE loot (reaction rewards), ONE notification (ecosystem feed), ONE agent notifier (Discord DMs)
50
43
51
-
### Frontend
44
+
### Frontend (Landing)
52
45
53
46
-**Framework**: React 19, TypeScript
54
47
-**Build Tool**: Bun, Vite
55
48
-**Styling**: Tailwind CSS
56
-
-**Deployment**: AWS S3 + CloudFront
49
+
-**Icons**: Phosphor Icons
50
+
-**Authentication**: ONE id via `@explorills/one-ecosystem-ui`
57
51
58
52
---
59
53
@@ -69,27 +63,21 @@ No separate login or registration is required — any user with a ONE id account
69
63
70
64
**Current Status**: In Progress
71
65
72
-
ONE chat backend is deployed and operational. The landing page and embedded chat widget are in active development.
66
+
The backend is deployed and operational. The landing page and embedded chat widget are in active development.
**ONE deal** is the NFT marketplace within the ONE ecosystem. It provides a straightforward interface for buying, selling, sending, and receiving digital assets across EVM-compatible networks.
9
+
**ONE deal** is the NFT marketplace for the ONE ecosystem. Buy, sell, send, and receive digital assets across EVM-compatible networks through a fixed-price model — no auctions, no bidding.
ONE deal serves as the primary marketplace for digital asset exchange within the ONE ecosystem. The platform supports standard NFT operations — listing, purchasing, and peer-to-peer transfers — without the complexity of auction or bidding mechanics. Users authenticate through ONE id, maintaining a single identity across all ecosystem projects.
17
+
ONE deal handles digital asset exchange within the ecosystem. The interface supports listing, purchasing, and peer-to-peer transfers. Users authenticate through ONE id, so a single identity works across all ONE projects.
18
18
19
19
Key capabilities:
20
20
21
-
-**Buy / Sell** — List and purchase NFTs with fixed-price transactions
22
-
-**Send / Receive** — Transfer assets directly between wallets from your profile
23
-
-**Collection browsing** — Explore and discover collections with filtering and sorting
24
-
-**Profile management** — View holdings, track activity, and manage assets tied to your address
25
-
-**Cross-ecosystem identity** — Authentication handled by ONE id; one account, all platforms
26
-
27
-
---
28
-
29
-
## Core Philosophy
30
-
31
-
Like every project in the ONE ecosystem, ONE deal is built on three principles:
32
-
33
-
-**Open Source** — Every line of code is publicly available on GitHub
34
-
-**Community-Driven** — Built by and for the community
35
-
-**Fair Revenue Model** — 45% to Node owners, 45% to Creators, 10% to founders
21
+
-**Buy / Sell** — Fixed-price NFT transactions
22
+
-**Send / Receive** — Direct wallet-to-wallet transfers from your profile
23
+
-**Collection browsing** — Explore collections with filtering and sorting
-**Cross-ecosystem identity** — ONE id authentication; one account, all platforms
36
26
37
27
---
38
28
39
29
## Technology Stack
40
30
41
-
ONE deal is built with modern web technologies for optimal performance:
42
-
43
31
-**Frontend**: React 19, TypeScript
44
32
-**Build Tool**: Bun, Vite
45
33
-**Styling**: Tailwind CSS
46
34
-**Icons**: Phosphor Icons
47
35
-**Animations**: Framer Motion
48
-
-**Authentication**: @explorills/one-id-auth (ONE id integration)
49
-
-**Wallet Support**: wagmi, viem, WalletConnect
50
-
-**Deployment**: AWS S3 + CloudFront
36
+
-**Routing**: React Router
37
+
-**Notifications**: Sonner
38
+
-**Authentication**: ONE id via `@explorills/one-ecosystem-ui`
39
+
-**Wallet**: wagmi, viem, Reown AppKit
51
40
52
41
---
53
42
54
43
## Architecture
55
44
56
-
ONE deal follows the standard ONE ecosystem frontend architecture:
57
-
58
45
```
59
46
one-deal/
60
47
├── src/
61
-
│ ├── components/ # Reusable UI components
62
-
│ │ ├── layout/ # Header, Footer, Layout
48
+
│ ├── components/
49
+
│ │ ├── layout/ # Page layout shell
63
50
│ │ ├── nft/ # NFT cards, grids
64
-
│ │ └── ui/ # Buttons, inputs, shared primitives
51
+
│ │ ├── search/ # Search and filtering
52
+
│ │ └── ui/ # Shared primitives
65
53
│ ├── pages/ # Route-level page components
66
-
│ ├── data/ # Mock data (pre-backend)
67
-
│ ├── lib/ # Utilities, constants
68
-
│ └── types/ # TypeScript type definitions
54
+
│ ├── lib/ # Utilities, constants, contracts
55
+
│ └── styles/ # Global styles
69
56
├── .github/workflows/ # CI/CD pipeline
70
57
└── package.json
71
58
```
72
59
73
-
Authentication is fully delegated to the `@explorills/one-id-auth` package. ONE deal does not implement any wallet connection or session logic directly — it wraps the application in `OneIdProvider` and renders the `OneIdAuth` component in the header.
60
+
Authentication is delegated to the shared `@explorills/one-ecosystem-ui` package. ONE deal wraps the application in `OneIdProvider` and does not implement wallet connection or session logic directly.
74
61
75
62
---
76
63
77
64
## Integration with ONE id
78
65
79
-
ONE deal uses ONE id as its authentication layer. Users connect their wallet through the ONE id widget, which handles:
66
+
ONE deal uses ONE id as its authentication layer. Users connect their wallet through the ecosystem-wide ONE id widget, which handles:
80
67
81
-
- Wallet discovery (EIP-6963 browser wallets)
82
-
- WalletConnect for mobile wallets
68
+
- Wallet discovery via Reown AppKit
83
69
- Signature-based authentication
84
70
- User registration and session management
85
71
86
-
No additional wallet configuration is required in ONE deal. The `@explorills/one-id-auth` package manages all connection logic internally.
72
+
No additional wallet configuration is required in ONE deal.
87
73
88
74
---
89
75
90
76
## Roadmap Status
91
77
92
78
**Current Status**: In Progress
93
79
94
-
ONE deal is currently in active development. The marketplace interface is deployed at [deal.expl.one](https://deal.expl.one){:target="_blank"} with core buy/sell and send/receive functionality. Backend integration for on-chain transactions is planned for a subsequent phase.
80
+
The marketplace interface is deployed at [deal.expl.one](https://deal.expl.one){:target="_blank"} with the frontend operational. Backend integration for on-chain transactions is planned for a subsequent phase.
0 commit comments