# Community contributions and Social

[Open Social ↗](/social/) to connect your community identity, complete a verified
contribution and see where your points place you on the real leaderboard.
The page is open to visitors; only participation requires a signed-in wallet.

## GitHub community tasks

Sign in with your wallet, then select **Connect GitHub** in Community Tasks.
GitHub verifies your developer identity and returns you to this page. The original
wallet and sign-in session must still be selected before the first **50 points**
are credited. Reauthorization renews the same identity and awards no extra points.

The GitHub group includes a **10-point Follow** task for
[flybrainlabs](https://github.com/flybrainlabs) and ten independent **1-point Star**
tasks for miner, explorer, contracts, protocol, node, sdk, infra, research, docs and
[examples](https://github.com/flybrainlabs/examples). Open the target on GitHub,
perform the action yourself, return here and select **Verify**. Follow/Star rewards
are awaiting activation under the project's platform-review gate; the page shows
their real availability. All twelve configured tasks total **70 points**, once.

Completed tasks remain completed after refresh, reauthorization or undoing a
relationship on GitHub. One GitHub numeric identity belongs to one reward wallet.
Your private GitHub identity appears in your task group; public ranking keeps its
existing masked wallet display. GitHub credits share your usual point history,
rank and future community snapshots. X-based invitations keep their existing
qualification rule. GitHub authorization never follows or stars on your behalf.

## What the community budget means

The page highlights **25,000,000 FBW** for future community airdrops. This budget
comes from the existing **31,183,323 FBW Community & Ecosystem Pool**. The remaining
**6,183,323 FBW** is retained for other community and ecosystem uses.

| Use within the community pool | FBW | Share of this pool |
|---|---:|---:|
| Future community airdrops | 25,000,000 | Approximately 80.17% |
| Other ecosystem uses | 6,183,323 | Approximately 19.83% |
| Community & Ecosystem Pool | 31,183,323 | 100% |

“Over 80%” refers to this pool, not total token supply. This is a budget allocation:
it does not create new tokens or mean tokens have already been sent or locked in
a dedicated on-chain vault. The existing FBW asset is on Solana Devnet.

Verified community points determine your rank and record your contributions.

## The six sections

| Section | What you can learn or do |
|---|---|
| Community Airdrop Allocation | Understand the budget and its place in the pool |
| My Community | Read your actual points, rank, completed tasks and X identity |
| Community Tasks | Start available tasks and follow their verification state |
| Community Leaderboard | Browse verified community contribution rankings |
| Invitations | Create a link and track registrations, verified invitees and rewards |
| Activity | Read the dated point entries behind your personal total |

There are no sample participants inserted into the live leaderboard. An empty
ranking means there are no eligible positive community contributions yet. Your
personal rank remains available even if you are outside the first 100.

:::diagram social

## Connect a wallet and sign in

Use the same wallet button as elsewhere on the website. Connect a Wallet Standard
Solana provider, select your account, then sign the sign-in message. Connecting an
account and proving control of it are separate steps. Sign-in is a message
signature: it does not authorize a transfer or require a network transaction fee.

A refresh can restore your previously selected provider and account silently
when the wallet supports it. A matching unexpired login remains in the same tab.
A locked/missing provider or expired login may require your action. Explicitly
disconnecting keeps the account disconnected; changing accounts clears the old
participant's private view. Learn more in [wallet connection and sign-in](/docs/wallets/).

Social participation does not require an active mining grant or an unfinished
scientific target. Community points and scientific mining rewards are distinct.
The website never treats your token balance as your community score.

## Verify your X identity

The first available task is **Connect X Identity**. Its initial reward is
**10 Community Points**. It is a one-time contribution for each wallet and known
X identity. The server defines the reward; your browser cannot choose it.

### 1. Generate your verification post

Choose **Start verification** after signing in. The site creates a random public
challenge valid for **30 minutes**, bound to your wallet and current login.
The code starts with `FBW-VERIFY-` and is shown with its expiration.

Choose a neutral identity statement or a project introduction. You may edit the
text. Keep the entire code in the **original post body**. The reward does not
change with wording, promotional tone or engagement. A positive endorsement is
not required. Follows, likes and reposts are not rewarded by this task.

Generating another challenge invalidates the previous one. Use the current code,
not a screenshot or saved older post text. Refreshing the same signed-in tab can
recover an active challenge and its submitted URL.

### 2. Publish on X

Copy the text or select **Post on X**. X opens its own posting screen and you
confirm publication yourself. The website does not post for you and does not
request an X password, cookie or access token.

Keep the post public while it is being checked. A private or unavailable post may
not provide usable evidence. Put the code directly in your own body text;
embedding it only in a picture, link, display name or quoted post is insufficient.

### 3. Submit your post URL

Return to Social, paste an HTTPS X/Twitter status URL and select **Verify post**.
The backend reads official public oEmbed evidence, checks the actual author and
status identity, then finds the code in the original body. It also checks expiry,
session control, prior wallet completion, known identity conflicts and post reuse.

When all checks pass, binding, completion, points and history are saved together.
The page shows **X Identity Connected**, your admitted point reward, updated total
and real rank. The verified post and time remain available in My Community.
Refresh reads the stored result; it does not award the task again.

## Understand verification states

| State | Meaning | Useful action |
|---|---|---|
| Available | You have not completed the task | Start a challenge after sign-in |
| In progress | A challenge is active | Publish its code and submit the URL |
| Pending verification | A backend check is running | Wait; refresh can recover the state |
| Needs review | Available evidence or identity checks are insufficient | Keep the original evidence available for review |
| Completed | The contribution is recorded | Read your points, rank and post record |
| Expired | The code is outside its 30-minute window | Generate and publish a new challenge |

An unavailable X provider, unverifiable author or incomplete original body does
not produce points. The request is saved for review. A reviewer must inspect the
original public post and actual author; copying the challenge into a form is not
proof. Expired challenges or original login sessions require a new challenge.
If review rejects the evidence, the page explains the result and permits a fresh
attempt under the published task rules.

The public oEmbed method establishes **challenge_verified** control. It is not
OAuth and may not provide a stable numeric X user ID. That field remains empty.
X usernames can change or be reassigned; disputed changes need review. Official
Official X OAuth verification remains a future identity upgrade. GitHub uses the separate flow described above.

## Points and the leaderboard

Each point change has a source and timestamp. Successful task completion appends
one contribution entry. Corrections append a separate audited adjustment; the
old entry remains. A retry, extra click or refresh cannot create a second first
reward. Existing earned points remain unchanged. The community v2 migration changes
uncompleted identity challenges to 10 points; subsequent task revisions keep
the reward captured by their challenge.

The leaderboard considers effective positive community points. Higher totals
rank first. Ties use the time the current score was reached, then a stable wallet
address. A reviewed account may temporarily be excluded from public ranking
without erasing its ledger. Review and corrections leave administrative records.
Mining throughput, stake and token holdings do not affect this leaderboard.

Use **Refresh** to request current results, or load more ranking/activity rows.
A live leaderboard can change while you paginate. An approved immutable snapshot
is the record used for a reproducible allocation, rather than an arbitrary later
screen capture.

## Daily check-in

Sign in and choose **Check in**. One check-in earns **1 point** each UTC day.
The next day starts at **00:00 UTC**. Repeated clicks and refreshes read the same
receipt; they do not grant another reward. My Community and Activity show the
updated total and its dated check-in entry.

## Daily X posts

After verifying your X identity, select **Publish a post**. Generate the current
**FBW-POST-** code, publish it in a new original public post from the bound account,
then paste the post URL and choose **Verify post**. Each verified post earns
**1 point**, with at most **3 rewarded posts per UTC day**.

Use a separate code and original post for each contribution. Verification uses
the same official public evidence and original-author checks as identity binding.
A reused identity-verification post, repeated URL, old post or different author
cannot earn another reward. Codes expire after 30 minutes or at midnight UTC,
whichever comes first. Failed provider checks enter the existing review workflow
and do not consume a rewarded slot. The daily counter and limits are enforced by
the server, including concurrent requests.

## Invite new registrations

Choose **Create invitation link** after signing in. Your link stays the same on
refresh and is available to copy. Share it with a new participant, who opens the
link and signs in with their wallet on Social. Their first community registration
fixes the invitation attribution. Existing registered users cannot be reassigned,
and creating or opening a link alone earns no points.

The inviter earns **10 points** when the invited new user successfully completes
their unique X identity verification. The invited user separately earns the
normal 10 identity points. A replay, second login, previously rewarded X identity
or duplicate wallet registration does not create a second invitation reward.
There is **no invitation count limit**. The invitation panel shows actual
registered invitees, verified invitees and earned invitation points.

## Leaderboard privacy and layout

On desktop, the leaderboard is on the right of the participation sections.
Narrow screens use one column. Public ranking rows display the wallet at its
original length with exactly the middle **8 characters replaced by <code>********</code>**.
There is no wallet-copy action or X username display option. Public leaderboard
responses also omit the underlying full wallet address and X username.

Your own X binding remains visible only in your signed-in profile. Your public
verification post remains on X. The public contribution feed omits sessions,
private review reasons and administrator evidence.

You can unlink your X identity after a fresh wallet sign-in. Earned points and
first-task completion remain. Daily posting requires an active binding. Unlinking
does not permit another first reward or another wallet to reuse the known identity.

## Future allocations and administration

Authorized administrators can review original evidence, configure tasks, append
point corrections, mark account disputes and freeze rankings. A snapshot records
cutoff, rules, points, rank, eligibility and content hash; it cannot be overwritten.
Corrections preserve the previous snapshot and create an audited successor.

Candidate allocations use a selected frozen snapshot, an explicit finite budget
and versioned rules. The current preparation engine distributes exact integer
atoms proportionally to eligible points and resolves remainders by stable rank.
A candidate does not reserve funds. Approval reserves an internal amount only
after snapshot approval and rule publication, and all approved reservations count
against the 25,000,000 FBW limit. Cancellation records a release rather than
removing history.

CSV/JSON exports are preparation artifacts. They do not send tokens, provide an
immediate claim or establish a universal conversion rate. Actual future transfers
require a separately authorized execution process and verified chain evidence.

## Common questions

**Why is my token balance unchanged after verification?** You earned community
points. Points and FBW balances are different records.

**Why does the page say Needs review?** The backend could not establish sufficient
public evidence or resolve an identity conflict. No success is assumed.

**Can I earn the first reward again after unlinking?** No. Historical completion
and known identity uniqueness remain intact.

**Why does a refresh ask me to sign in?** The selected wallet can remain connected
while its login expires. A new signature proves control; it is not a transfer.

**What happens if there is no rank yet?** An account without eligible positive
community points is not ranked. This is an actual empty state.

For operators and integrators, read the maintained technical delivery document
`docs/social-community-system.md` in the docs component. For asset identity and
receipt scope, read [FBW Devnet reference](/docs/devnet/) and
[economic model](/docs/economics/).