📦 Release v2.7.0 — inaready

0.0. 🧭 Staging 2.7.0 by Pre Roti - Ready for InaReady

0.1.0 🧭 This Release Notes

✅ Highlights

docs(readme): fix the dynamic badge for dev. version and status.
chore(package): remove the codename data.
docs(security): fix the description of supported version, and remove the table.

🔗 Diffs

Compare: v2.6.7...v2.7.0

0.2.0. 🧭 Notes Quick Map

Section	Title	Status
0.0	Staging	—
1.0	Landing Protocol	In Progress
2.0	Login Protocol	Released
3.0	Digital ID Protocol	In Progress
4.0	Wallet Protocol	In Progress
5.0	Token Protocol	In Progress
6.0	NFTs Market Protocol	Planned
7.0	Terms of Use Protocol	Released
8.0	Dashboard Protocol	Planned
9.0	Notes	—
10.0	Feedback & Contribution	—

0.3.0. 🧭 Staging Preview Image

Preview 1	Preview 2

0.4.0. 🧭 Support Status

Version	Codename	Status	Relation
2.7.00	inaready	Handed-Over	Cloned Here

0.3.0. 🧭 The dApp Staging Link

Link #1: pabrikroti.endhonesa.com
Link #2: preroti.endhonesa.com

1.0. 🧭 Landing Protocol ⚠️ (In Progress)

A set of rules that governs the data transmitted and received between this dApp and the client on the user device.

1.1.0. 🔍 Host Detection ✅ (Released)

Rules to detect the Domain and/or Subdomain used by the client, allowing the dApp to determine what content to serve dynamically.

1.2.0. 🧱 Header Component ✅ (Released)

A frontend component that organizes and renders:

1.2.1. 🔗 Main Logo ✅ (Released)
...
1.2.2. 🔍 NFTs Search Form ✅ (Released)
...
1.2.3. 🔐 User Button ✅ (Released)
...
1.2.4. 📎 URL to QR Code ✅ (Released)
...
1.2.5. ☰ Drop Down Menu ✅ (Released)
...

Designed for client-side accessibility and responsive navigation.

1.3.0. 🎯 Landing Content ⚠️ (In Progress)

A dedicated content designed to guide users toward a single, clear objective—whether conversion, lead generation, or direct interaction.

This content includes:

1.3.1. 🦸 Hero Slider ⚠️ (In Progress)
...
1.3.2. 🌟 Featured Grid ⚠️ (In Progress)
...
1.3.3. 🎨 Visual Display CTA ⚠️ (In Progress)
...
1.3.4. 📹 Video Embed CTA ⚠️ (In Progress)
...
1.3.5. 📝 Paragraph Text CTA ⚠️ (In Progress)
...

Those contents focused on intention rather than exploration.

1.4.0. 🦶 Footer Component ✅ (Released)

A frontend component that provides:

1.4.1. ✉️ Email Subscription ✅ (Released)
...
1.4.2. 🌐 Social Link List ✅ (Released)
...
1.4.3. ©️ Copyright ✅ (Released)
...
1.4.4. 📜 Terms of Use Link ✅ (Released)
...
1.4.5. 🖼️ Footer Logo ✅ (Released)
...

Organized for easy access on the client side and designed for brand reinforcement.

2.0. 🔐 Login Protocol ✅ (Released)

A protocol that enables users to securely access the dApp using a variety of authentication methods using the Thirdweb Connect

2.1.0. 🧭 Login Page ✅ (Released)

A dedicated page is displayed when a user has not logged in to restrict access to Wallet-Gated Content, ensuring that only authenticated users can interact with specific features or view protected sections of the dApp.

This page includes:

2.1.1. 🎨 Login Art ✅ (Released)
— Visual element representing the dApp's identity and aesthetic.
2.1.2. 📢 Login Banner ✅ (Released)
— Highlight section to convey key messages or campaigns.
2.1.3. 🎯 Login CTA ✅ (Released)
— Text element used as a call-to-action message and branding.
2.1.4. 📝 Login Form ✅ (Released)
— Interface for selecting login methods via Thirdweb Connect.
2.1.5. 📄 Terms of Use Link ✅ (Released)
— Redirects users to the platform terms before entering.
2.1.6. 🖼️ Footer Banner ✅ (Released)
— Optional call-to-action or branding component at the bottom of the login view.

Focused on user onboarding while reinforcing visual identity and content access policies.

2.2.0 🔗 ConnectButton Integration ✅ (Released)

This dApp uses the ConnectButton component from the Thirdweb Connect SDK, which enables seamless login experiences across multiple authentication methods. Upon successful login, a non-custodial in-dApp wallet is generated, allowing users to store tokens and interact with the dApp securely.

Supported login methods:

2.2.1. 🟢 Google Login ✅ (Released)
— Uses OAuth 2.0, a widely adopted authorization protocol, to authenticate users via their Google account. Automatically generates an in-dApp wallet, enabling secure asset storage and interaction without needing browser extensions.
2.2.2. 🍏 Apple ID Login ✅ (Released)
— Provides a Web3 onboarding flow through Apple ID credentials. It ensures a secure and frictionless user experience by leveraging the user’s trusted Apple ecosystem.
2.2.3. 📧 Email Login ✅ (Released)
— A familiar Web2-style login that supports passwordless authentication. Upon login, an in-dApp wallet is created in the background, enabling users to interact with the dApp without needing traditional credentials.
2.2.4. 📱 Phone Login ✅ (Released)
— Similar to Email Login, this method streamlines the onboarding process by allowing users to authenticate with their mobile number and receive a verification code—ideal for mobile-first experiences.
2.2.5. 🔑 Passkey Login ✅ (Released)
— A modern, secure, and passwordless authentication method. Uses biometric verification (e.g., Face ID, fingerprint) or local PINs for smooth and safe access.
2.2.6. 🧩 Connect a Wallet ✅ (Released)
— Opens a wallet selection modal, allowing users to connect an existing Web3 wallet, such as MetaMask, Phantom, or OKX, giving experienced users full control over their digital assets.

Each login method creates a secure, user-friendly entry point into the decentralized experience, with no seed phrases, no password fatigue, and maximum Web3 usability.

3.0. 🪪 Digital ID Protocol ⚠️ (In Progress)

The next iteration of digital identity on the Internet — powered by distributed systems, blockchains, decentralized applications, and tokenomics — to define and own identity beyond centralized platforms.

This Digital ID Protocol transforms wallets into identities, identities into reputations, and reputations into trust — on your terms.

3.1.0. 🧊 User Default Modal 🧪 (Experimental)

A reusable modal interface that appears on demand for user actions like login, wallet selection, or digital identity initialization.

In addition to handling authentication (email, phone, or wallet), this modal also acts as a gateway to the user's in-dApp wallet — allowing interactions with the blockchain, token balances, and transactions without ever leaving the dApp environment.

3.2.0. 👤 User Account ⚠️ (In Progress)

A secure, user-controlled page that stores and manages identity data on-chain. Privacy settings and data visibility are fully managed by the user. Smart contract-based identity will follow ERC-725 (for claims & keys) and ERC-735 (for verifiable credentials).

This identity system includes:

3.2.1. 🆔 User Name ⚠️ (In Progress)
— By default, the user’s in-dApp wallet address serves as their identifier. However, users can customize it into a readable username, making it easier to share and remember.
3.2.2. 🖼️ User Photo ⚠️ (In Progress)
— A customizable avatar or profile image stored either off-chain (via IPFS) or on-chain via metadata URI. This visual identity reinforces recognizability and can be used across multiple Web3 platforms that respect the same identity schema.
3.2.3. 🧬 User Bio ⚠️ (In Progress)
— A short description or statement representing the user’s intent, background, or values. The bio is public-facing and can be updated by the user every time. It humanizes on-chain identity and adds context to the user’s presence in the ecosystem.
3.2.4. 🗃️ User Records ⚠️ (In Progress)
— A collection of structured personal records that form a deeper layer of the user’s identity. These records are the user’s role, contribution, and experience within the PABRIKROTI ecosystem — enabling identity-driven reputation across the PLW framework: Playing, Learning, and Working.
— These records are modular, optionally encrypted, and under user control. They don’t just say what a user did — they show who they are becoming in the world of tokenized playing, learning, and working.
3.2.5. 🔗 User Social ⚠️ (In Progress)
— An optional collection of external links that help bridge the user’s profile to their Internet presence (Twitter, Lens, Farcaster, personal site, etc.). Each link can be toggled for visibility and verified via linked wallet signatures.
3.2.6. 🪪 User Profile Page ⚠️ (In Progress)
— A public-facing profile view where other users can view selected identity fields, depending on the privacy settings defined by the profile owner. Accessible by URL based on User Name, it serves as a decentralized personal homepage within the dApp ecosystem.

4.0. 🔐 Wallet Protocol ⚠️ (In Progress)

Provide a user-friendly and secure way to interact with blockchain technology, allowing users to store, manage, and utilize digital assets such as NFTs and fungible tokens. This protocol simplifies onboarding into Web3 by abstracting traditional wallet complexities.

The Wallet Protocol is the heartbeat of interaction within the dApp — managing not only assets, but experiences, permissions, and proof of belonging.

4.1.0. 🧱 In-dApp Wallet ✅ (Released)

An embedded, non-custodial wallet is directly integrated into the dApp. It allows users to:

4.1.1. 🎒 Manage assets (NFTs & FTs) ✅ (Released)
...
4.1.2. 🔗 Interact with smart contracts ✅ (Released)
...
4.1.3. 🔐 Authenticate within the dApp ✅ (Released)
...
4.1.4. 🌐 Experience Web3 without ever leaving the interface ✅ (Released)
...

No need to install browser extensions or manage seed phrases.

4.2.0. 🧠 Smart Wallet ✅ (Released)

A Web3 wallet built using account abstraction, utilizing smart contracts instead of EOA private keys. It unlocks features such as:

4.2.1. ⛽ Gas sponsorship ✅ (Released)
...
4.2.2. 📦 Batched transactions ✅ (Released)
...
4.2.3. ✍️ Signless interaction ✅ (Released)
...

Often referred to as smart accounts, they radically improve usability and security.

4.3.0. 💸 Sponsored Gas ✅ (Released)

Allows the dApp to pay gas fees on behalf of users. This creates a seamless, gasless experience — essential for onboarding non-technical users and enabling frictionless blockchain interaction.

4.4.0. 🔐 Wallet-Gated Content ✅ (Released)

Content and features within the dApp can be restricted based on wallet status (logged in or not). This enables:

4.4.1. 🌟 Exclusive experiences ✅ (Released)
...
4.4.2. 📋 Allowlist-based utilities ✅ (Released)
...
4.4.3. 🗝️ Access to unlock interactions ✅ (Released)
...

All are managed in a transparent and decentralized manner.

4.5.0. 🖼️ Owned NFTs ⚠️ (In Progress)

Display a visual list of NFTs owned by the user, presented as clickable thumbnails. Each opens a brief detail modal with metadata and potential actions (e.g., view, share, transfer).

4.6.0. 💰 Owned FTs ⚠️ (In Progress)

Display a list of fungible tokens (FTs) held in the user's wallet, shown as token balances. Each entry opens a detailed view showing metadata and interactions like transfer or staking (if available).

4.7.0. 🔁 Swap NFTs ⚠️ (In Progress)

Allows users to transfer an NFT to default destination addresses in the PABRIKROTI ecosystem and other addresses manually input by the user. This is accessible via the NFT detail view.

4.8.0. 🔁 Swap FTs ⚠️ (In Progress)

Allows users to transfer a fungible token (FT) to default destination addresses in the PABRIKROTI ecosystem and other addresses manually input by the user. This is accessible via the FT detail view.

4.9.0. 📜 User NFTs Records ⚠️ (In Progress)

Displays the user's NFT activity log, including:

4.9.1. 📥📤 Received / Sent NFTs ⚠️ (In Progress)
...
4.9.2. 🔥 Burned NFTs ⚠️ (In Progress)
...
4.9.3. 🔗 Blockchain transaction hashes ⚠️ (In Progress)
...

Each activity log is clickable and opens the corresponding record on the blockchain explorer.

4.10.0 📜 User FTs Records ⚠️ (In Progress)

Displays the user's fungible token (FT) transaction history, including:

4.10.1. 📈📉 Incoming / outgoing transfers ⚠️ (In Progress)
...
4.10.2. 🔥 Burn events ⚠️ (In Progress)
...
4.10.3. 🔗 Transaction or event hashes ⚠️ (In Progress)
...

Explorer links are provided for full transparency and auditability.

5.0. 🪙 Token Protocol ⚠️ (In Progress)

A modular system that allows each tenant to deploy, publish, and distribute their NFTs and FTs, manage gated content, and provide claimable interactions for users — all backed by on-chain smart contracts and wallet integration.

5.1.0. ⚙️ Tenant Deploy Contract ⚠️ (In Progress)

Allows each tenant (sub-project or brand) to deploy their own NFT and FT smart contracts. This ensures independence, traceability, and ownership over digital assets.

5.2.0. 📤 Tenant Publish NFTs ⚠️ (In Progress)

Enables tenants to publish NFT collections, including metadata, images, edition types, and claim conditions, ready to be minted and distributed.

5.3.0. 🗂️ NFTs Lister ✅ (Released)

Displays all available NFTs across the tenant scope. Includes filters, sorting, and visual previews for easy exploration.

5.4.0. 📝 NFT Form ✅ (Released)

A dynamic form component for claiming NFTs based on type and conditions:

5.4.1. 🧬 Claim NFT 1 of 1 Edition ✅ (Released)
— A unique, single-edition NFT that can only be claimed once by a user.
5.4.2. 🔢 Claim NFT Limited Edition ✅ (Released)
— NFTs with a fixed number of editions available for public or gated claiming.
5.4.3. 🌊 Claim NFT Open Edition ✅ (Released)
— NFTs are available in unlimited supply, optionally gated by time or wallet criteria.

5.5.0. 🔐 NFT Gated Content ✅ (Released)

Restricts access to exclusive content or features based on NFT ownership. Enables NFT-based memberships, unlockable resources, or privileges.

5.6.0. 📤 Tenant Publish FTs ⚠️ (In Progress)

Allows tenants to publish fungible tokens (ERC20) for reward, utility, or governance use. Metadata and supply configurations are set during publishing.

5.7.0. 📊 FTs Lister ✅ (Released)

Displays available fungible tokens, including token name, balance, supply, and eligibility for claim or interaction.

5.8.0. 📝 FT Form ✅ (Released)

An interactive form to claim or receive fungible tokens based on defined conditions:

5.8.1. 💰 Claim FT Fixed Supply ✅ (Released)
— A capped total supply, distributed proportionally or through public drops.
5.8.2. 🎯 Claim FT Limited Supply ✅ (Released)
— A subset of the total supply is made claimable via specific windows or criteria.
5.8.3. 💧 Claim FT Open Supply ✅ (Released)
— Unlimited supply of tokens claimable at any time, subject to gating logic.

5.9.0. 🔐 FT Gated Content ✅ (Released)

Restricts access to features or areas of the dApp based on fungible token balance — e.g., voting, access to downloads, or special pages.

6.0. 🛍️ NFTs Market Protocol 🧩 (Planned)

Enables users and tenants to list, trade, and showcase NFT assets using fixed-price or auction models, forming a decentralized NFT economy across the platform ecosystem.

6.1.0. 🎨 Collections Showcase 🧩 (Planned)

Visual display of curated or trending NFT collections, aimed at increasing discovery and engagement across the marketplace.

6.2.0. 🧾 NFTs Collection 🧩 (Planned)

Dedicated collection pages (based on a single smart contract) showing all NFTs within a set, including metadata, floor price, supply, and minting status.

6.3.0. 💱 NFT Buy/Sell 🧩 (Planned)

Enables transactional functionality for NFTs via multiple methods:

6.3.1. 💵 NFT Fix Price Listing 🧩 (Planned)
— Sellers can list NFTs at a specific price.
6.3.2. 🛒 NFT Fix Price Buying 🧩 (Planned)
— Buyers can purchase listed NFTs instantly at stated prices.
6.3.3. ⏳ NFT Auction Listing 🧩 (Planned)
— Sellers can start time-based auctions with min/max bid limits.
6.3.4. 🧤 NFT Auction Bidding 🧩 (Planned)
— Buyers can place bids during active auctions.
6.3.5. 📩 NFT User Best Offer 🧩 (Planned)
— Allows buyers to submit offers for NFTs, which sellers can accept or reject.
6.3.6. 🧾 NFT Buy/Sell History 🧩 (Planned)
— Full record of all transactional activity per user and NFT.

6.4.0. 📡 Market Live Activity 🧩 (Planned)

Real-time stream of NFT market activity, including claims, transfers, bids, and sales — designed for visibility and social proof.

7.0. 📜 Terms of Use Protocol ✅ (Released)

Defines the terms of interaction between users and the platform, including digital asset rights, publishing rules, moderation, and access control.

May include programmable enforcement using smart contracts.

8.0. 📊 Dashboard Protocol 🧩 (Planned)

A central control panel for tenants and admins to configure and monitor their dApp experience.

8.1.0. ⚙️ Settings Dashboard 🧩 (Planned)

Admin interface for adjusting UI, content, and behavior of tenant-level web apps:

8.1.1. 🧱 Basic Setting 🧩 (Planned)
— General config such as title, description, domain, and metadata.
8.1.2. 🖼️ Header Setting 🧩 (Planned)
— Logo, nav items, and search form.
8.1.3. 🎯 Landing Setting 🧩 (Planned)
— Hero sliders, featured grids, CTA sections, and video embed.
8.1.4. 🦶 Footer Setting 🧩 (Planned)
— Copyright, social inks, logos, and subscription.
8.1.5. 🔐 Login Setting 🧩 (Planned)
— Banner, terms, login form, and footer logo.
8.1.6. 🖼️ NFTs Lister/Form Setting 🧩 (Planned)
— Setting any displayed options for NFT components.
8.1.7. 💰 FTs Lister/Form Setting 🧩 (Planned)
— Setting any displayed options for FT components.
8.1.8. 📜 Terms of Use Setting 🧩 (Planned)
— Setting and editing the content of the terms of use and legal.

8.2.0. 📈 Analytics Dashboard 🧩 (Planned)

Provides metrics and insights for monitoring performance:

8.2.1. 📊 Traffic Analytics 🧩 (Planned)
— Pageviews, referrers, bounce rate, etc.
8.2.2. 👥 User Analytics 🧩 (Planned)
— User growth, retention, login patterns, etc.
8.2.3. 🪙 Token Analytics 🧩 (Planned)
— Token claims, distributions, supply usage, etc.
8.2.4. 💹 Market Analytics 🧩 (Planned)
— Sales volume, bids, pricing trends, etc.

9.0. 🛠️ Notes

Scalable, fully branded Onchain tokenize — flexibly and with full brand control.

Built by Prof. NOTA and Prof. NOTA Inc. in 0101 Universe

Built with Next.js, Tailwind CSS, and TypeScript

Blockchain-integrated via ThirdWeb SDK v5

Fully modular and multi-tenant ready.

9.1.0. 📈 Changelog Highlights

⚙️ Prepared Dashboard Protocol with Settings Dashboard and Analytics Dashboard.
✅ Implemented Terms of Use Protocol.
⚙️ Prepared NFTs Market Protocol with Collections Showcase, NFTs Collection, NFT Buy/Sell, and Market Live Activity.
⚙️ Prepared Tenant Deploy Contract, and Tenant Publish FTs as part of Token Protocol.
⚠️ Introduced Tenant Publish NFTs as part of Token Protocol.
✅ Implemented Token Protocol with NFTs Lister, NFT Form, NFT Gated Content, FTs Lister, FT Form, and FT Gated Content.
⚠️ Introduced Owned NFTs, Owned FTs, Swap NFTs, Swap FTs, User NFTs Records, and User FTs Records as part of Wallet Protocol.
✅ Implemented Wallet Protocol with In-dApp Wallet, Smart Wallet, Sponsored Gas, and Wallet-Gated Content.
⚙️ Prepared User Account as part of Digital ID Protocol with User Name, User Photo, User Bio, User Records, User Social, and User Profile Page.
🧪 Enabled User Default Modal as part of Digital ID Protocol.
✅ Implemented Login Protocol with Login Page, and ConnectButton Integration.
⚠️ Initial implementation of Landing Content part of Landing Protocol with Hero Slider, Featured Grid, Visual Display CTA, Video Embed CTA, and Paragraph Text CTA.
✅ Implemented Landing Protocol with Host Detection, Header Component, and Footer Component.

10.0. 📩 Feedback & Contribution

Feel free to open an issue or submit a pull request.

For questions or support, please send to this contact nota@endhonesa.com.

Prof. NOTA Inc. — Making Web3 Meaningful.

Release 2.7.0 (inaready)