Case Study

Fanslayer

Creator memberships with passes, tiers, revenue splits, and partner verification.

In Progress

Project Status

Primary Users

Core Screens

Pass-Based

Core Model

Fanslayer

Next.jsReactTypeScriptTailwind CSSNode.js+8 more

Project Overview

About This Project

Fanslayer is a creator membership platform in progress. Creators can launch paid tiers, define perks, route revenue splits, issue reusable digital passes, and let partner apps verify access. ChainScore Labs is shaping the product architecture, creator workflows, pass model, tier configuration, verification layer, and implementation foundation.

Client

Fanslayer

Timeline

Start

May 2026

Status

In Progress

Duration

In progress since May 2026

Product Thesis and Market Positioning

Information Architecture and Flows

Membership and Pass Model

Implementation Foundation

Technologies

Next.jsReactTypeScriptTailwind CSSNode.jsPostgreSQLRedisWalletConnectApple Wallet / PassKitGoogle Wallet APIERC-1155REST Verification APIWebhook Events

Creator Memberships Need a Better Ownership Layer

Most creator membership tools stop at billing. The membership stays locked inside one platform, fan proof does not travel cleanly to events or partner apps, and teams still handle collaborator splits with manual work. Fanslayer treats membership as a portable entitlement. A creator publishes tiers and perks, a fan joins, and the system issues a digital pass with tier, status, expiry, and verification data. Revenue routing and access checks live in the same product instead of being patched in later.

Fanslayer hero section introducing wallet-native memberships

Creators, fans, and partner apps share one entitlement model

A Membership Layer, Not Just a Subscription Page

The product is structured around three connected surfaces. Creators configure tiers, perks, pricing, and split rules. Fans join a tier and receive an active membership pass. Partner apps verify that pass and decide whether to unlock content, events, discounts, community access, or other perks. That architecture keeps the creator in control of the fan relationship. Membership is no longer only an account state inside one app; it becomes a reusable proof layer that can travel across the creator's ecosystem.

Creator Surface: Launch paid tiers, define perks, configure revenue splits, and monitor membership performance.
Fan Surface: Join a membership, view unlocked benefits, manage renewal, and carry proof through a digital pass.
Partner Surface: Verify active status, tier level, and expiry through an API before granting access.

Fanslayer landing page explaining creator, fan, and partner workflows

Tiers, passes, split rules, and verification logs

The Membership System Model

Fanslayer's core data model is intentionally compact. A creator owns tiers. A fan becomes a member of a tier. Each membership can issue a pass. Each tier can carry split rules. Every verification attempt produces a log. This gives the system enough structure to support recurring billing, access control, payouts, and partner integrations without becoming a generic social network.

Creator

Stores profile, handle, category, wallet or payout rail, and business configuration.

Membership Tier

Defines price, billing cycle, included perks, access level, featured state, and optional slot limits.

Member

Connects a fan wallet or account to a creator, tier, status, start date, and expiry date.

Pass

Represents portable proof through a wallet pass, QR credential, signed token, or optional on-chain record.

Split Rule

Routes payment shares to creator, editor, co-host, manager, production studio, treasury, or platform fee.

Verification Log

Records partner checks, access decisions, pass status, and timestamps for support and audit.

From creator profile to published membership

Protocol Onboarding

The onboarding flow is designed to get a creator from zero to a live membership offer without hiding the operational pieces. The setup captures profile data, wallet or payout rail, first tier details, and publish readiness in a guided sequence. The important product choice is sequencing. Creators should not have to understand every advanced setting on day one, but the system still needs enough data to issue a real entitlement and route money correctly once the first fan joins.

Profile First: Creator name, handle, category, bio, avatar, and public identity are established before monetization.
Payout Rail Early: Wallet or payout details are collected before publishing so revenue routing is not an afterthought.
First Tier Fast: A creator can publish with one starter tier, then refine perks and advanced split rules later.
Preview Before Launch: The final step shows what fans will see before the membership becomes public.

Fanslayer protocol onboarding flow for creator setup

Make the offer clear and the payout rules explicit

Tier Configuration and Revenue Splits

Tier configuration is where the product becomes concrete. A tier needs a name, price, billing cycle, perk list, access level, and featured state. Fans need to understand the value quickly; creators need to know what they are promising before they publish. Fanslayer also treats revenue splitting as a first-class configuration problem. Many creators work with editors, co-hosts, managers, and production teams. Instead of exporting payment data into a separate payout workflow, split rules can attach to a tier and execute automatically when membership revenue arrives.

Clear Perk Packaging: Exclusive content, early access, community entry, live Q&A, discounts, event access, DM access, and badges can be configured per tier.
Featured Tier Logic: Creators can highlight the tier they want fans to choose without redesigning the public page.
Split Preview: The creator can see how a payment distributes before the tier is published.
Contributor Payouts: Creator teams can route shares to collaborators, studios, managers, treasury, and platform fees.

Fanslayer tier configuration screen with pricing and perks

The operating center for a membership business

Creator Terminal

The creator terminal is the workspace for day-to-day membership operations. It should answer the questions a creator cares about immediately: how many active members do I have, which tier is working, what revenue is recurring, what payouts are pending, and which partner verifications are happening. The screen is intentionally closer to an operating dashboard than a creator profile editor. Fanslayer is designed for people who treat membership revenue as a serious business line, not a passive tip jar.

Fanslayer creator terminal showing membership and revenue operations

Membership becomes portable proof

Digital Identity Pass

The digital identity pass is the product's main differentiator. When a fan joins, the pass can contain creator identity, tier name, active or expired status, expiry date, member ID, and a QR or verification token. It can live in Apple Wallet, Google Wallet, inside Fanslayer, or optionally as an on-chain token where that adds real value. The key is that the pass is useful beyond the checkout moment. A fan can use it for events, commerce discounts, community access, private content, or partner apps without re-registering for every surface.

Portable Status: The fan can carry active membership proof outside the original checkout flow.
Tier-Aware Access: Partner apps can distinguish Supporter, Member, Inner Circle, or any creator-defined tier.
Expiry and Revocation: Expired, revoked, or downgraded memberships can be reflected in verification responses.
Multiple Pass Formats: The system can support wallet passes, signed credentials, QR tokens, or optional tokenized records.

Fanslayer digital identity pass for fan membership verification

Make the membership feel active after payment

Fan Access Portal

The fan portal is where the membership becomes tangible. Fans see active tier status, unlocked perks, content access, pass entry, expiry, and renewal controls from one surface. The goal is to make joining feel like entering a managed access system, not just completing a payment. Perks are represented as actionable items. A fan should be able to open content, join a community, claim a discount, enter an event, or view the pass without searching through scattered creator links.

Active Membership: Tier, status, expiry, and renewal state are visible without support tickets.
Perks Vault: Benefits are grouped as cards that lead directly to content, events, community, or discounts.
Wallet Pass Entry: The fan can open or save the digital pass from the same portal.
Self-Serve Management: Fans can change, renew, pause, or cancel without leaving the membership surface.

Fanslayer fan access portal with perks and pass controls

A simple API for cross-app access

Partner Verification Layer

The verification layer is what makes the pass operational. A partner app should be able to ask a narrow question: does this wallet or pass have an active membership for this creator, and is the tier sufficient for this benefit? The response should be small, fast, and easy to integrate. This keeps Fanslayer from becoming a walled garden. Community apps, event tools, commerce storefronts, and content systems can honor membership without importing an entire creator membership database.

Verification Request

Partner apps can check wallet address, creator handle, pass ID, or QR token.

Access Response

The API returns valid, creator, tier, expiry, and reason fields for an access decision.

Revocation Handling

Expired, revoked, wrong-tier, or missing memberships return explicit denial reasons.

Audit Trail

Verification events are logged so creators can see where membership access is being used.

Metrics

Current Progress

Fanslayer is presented as an active product build, not a finished public launch. The current work is focused on product architecture, screen implementation, membership data modeling, pass issuance options, revenue split rules, and partner verification boundaries. Usage numbers are intentionally excluded until there is real launch data.

May 2026

Started

Product strategy, visual direction, and core workflows started in May 2026.

In Build

Status

Membership architecture and UI implementation are in progress.

Core Workflows

Creator onboarding, tier setup, split rules, digital pass, and partner verification.

Pending

Metrics

No fabricated adoption, revenue, or verification metrics are included.

Project Gallery