← Federation Alliance

PROJECT TEAMS // DISCUSSION DRAFTS

Bring a crew. Build something worth sharing.

Choose a format your members would enjoy, then agree on one clear deliverable with another project.

Proposals — entries are not open. No teams, dates, judges or prizes are confirmed. This page does not enroll projects, collect entries or track scores.

FIRST PILOT PROPOSAL

Creative Clash

Theme: Different crews. One useful goal.

Deliverable: one original image, meme or short video explaining how two communities could solve a useful problem together, plus a short explanation. Agree on one medium, length and file limits for everyone before opening entries.

Proposed format: four mutually approved projects, up to three eligible entries each, over two weeks after a separately announced start. Each project's best eligible entry determines its team result.

Proposed scoring: originality 40%, execution 30%, usefulness 20%, clarity 10%. Reviewers explain scores. Ties share a place unless final rules publish another method before entries open.

Why join: creative collaboration and a reviewed showcase. Token-price promotion and paid hype are outside this brief.

ALTERNATIVE FORMAT

Research Showdown

Shared question: What do public mint controls, concentration and liquidity records tell us at a stated time, and what remains unknown?

Deliverable: one concise, source-linked note per team. Use the same asset, observation window and agreed source set. Date observations and separate facts, interpretation and unanswered questions. An unavailable source remains an explicit gap.

Criteria to agree: source quality, reproducibility, accurate limitations and clarity. Publish scoring weights before accepting work.

Why join: learn research together and compare reasoning. A result is not a safety verdict, identity claim or investment recommendation.

ALTERNATIVE FORMAT

Builder Battle

Goal: make one community task easier, such as planning an event, explaining a concept or organizing public resources.

Deliverable: a small working demo, tool or reusable resource with setup instructions and a repeatable example. Agree on a common scope and permitted tools.

Criteria to agree: usefulness, working behavior, accessibility and documentation. Publish weights and a common test checklist first. Use sample data; participation should require no real funds, seed phrase, private key or wallet signature.

Why join: create something other crews can use, with clear contributor credit.

Founder checklist

  1. Introduce the project. Share an official link, authorized representative and project contact. Include chain and mint where relevant. Confirm permission to represent the team.
  2. Choose a format. Describe the member benefit, deliverable, team size and realistic contribution.
  3. Agree on fair rules. Confirm eligibility, entry limits, deadline and time zone, permitted tools, AI-use disclosure, originality, rights, accessibility and moderation.
  4. Confirm reviewers. Disclose conflicts, require recusal and an independent replacement, and publish scoring, ties, correction rules and a dispute window.
  5. Approve publication. Agree on the final brief, submission route and consent to publish names and work. Announce a start only after all participating projects approve.

Do not include member lists, passwords, private keys or unpublished sensitive material in proposals.

Recognition and tracking

Proposed recognition is a reviewed winner showcase and station achievement, with contributor credit and publication consent. No cash, tokens, allocations, giveaways or financial benefits are promised.

Today, proposals are reviewed privately. Agreed briefs and reviewed results are published through approved site updates. There is no live competition tracker, automatic acceptance or connected founder analytics.

Prepare your project discussion draft →

See how a proposal becomes a published match →

Keep a copy of your submission. Follow up through the GFOF contact on the Alliance page using your project name.