For projects

Run access campaigns you can defend.

Build allowlists, community rounds, creator cohorts, playtests and drops with declared rules, reviewable evidence and locked results.

Create a project Inspect an example campaign

Campaign control planeNorthstar / draft 04

Operating record

Closed playtest access

Rules ready to publishv1.0

50Declared seats

01
Draft rules
Editable
02
Public campaign
Declared
03
Entry review
Resolve
04
Locked allocation
Once
05
Fulfilment
Export

3 declared checks · 2 allocation groupsOne lock. No rerun.

Follow the operating sequence Five product moments

01 · Start with the job

A practical structure, not a blank form.

Choose a shipped campaign pattern, then shape it around the access you are allocating. Every field remains editable before publishing.

Allowlist spots

Collector allowlist

Mint or allowlist access for holders and collectors.

Typical capacity: 100
Evidence focus: Wallet proof and Discord standing
Starting method: Random eligible

A practical starting structure. Every declared field remains editable before publishing.

02 · Declare

Publish the rules before anyone enters.

Access type, capacity, dates, chain, checks, allocation groups and fulfilment instructions are part of the same published record.

Rules manifest

Northstar Closed Playtest

Editable

Access: Playtest seats
Capacity: 50
Chain: Ethereum
Wallet: Proof required
Discord: Membership required
Answer: Review required

One source of truth. Participants see these same fields before entry.

03 · Resolve

Automate facts. Record judgement honestly.

Wallet control and provider facts can resolve directly. Submitted answers and ambiguous evidence stay visible as review work.

01Wallet controlProvedResolved

02Discord accountImportedResolved

03Playtest setupReviewed3 waiting

04Token holdingProvedProvider retry

04 · Lock and fulfil

Close the campaign. Resolve the queue. Seal the result.

Intake closes, unresolved review blocks allocation, and the result runs once. Delivery starts from that sealed outcome.

Allocation ready

Run allowed

No second execution

Intake closed
Review queue resolved
Commitment recorded
Second run disabled

Fulfil from the result

HASHED EXPORTS

01Winners CSV

02Claim-wallet CSV

03Selected addresses

04OpenSea allowlist

05Audit JSON

Discord delivery and reports point back to this locked result.

05 · Publish

Put the project on the record.

A verified project profile connects public campaigns, dates, accounts and result history without turning the marketing site into a detached brochure.

Verified project

Northstar Studio

Example public record

PROJECT / PUBLIC

Campaigns: Public
Dates: Visible
Results: Recorded

One public identity connects the campaign promise, current dates and final receipt.

Practical questions

→Do participants need every connected account?

→Can a campaign require a specific token?

→Can rules change after publishing?

→What files can a project export?

Project workspace

Build the campaign before the crowd arrives.

Create the workspace now. Verification gates publishing and sensitive controls before they go live.

Open the next operating surface

Create a project