Q token mark QUADPublic Accountability

Community onboarding

Discord Onboarding

Discord is for public coordination: status questions, tester reports, validator interest, docs feedback, and links back to the surface that owns the proof.

Open Discord Community Front Door Receipts And Support Public Updates

First Five Minutes

Start with the public map, then ask from evidence. A good first post names the surface and the page or receipt you are looking at.

1. Read the map

Open Start and Why Use QUAD so the four surfaces stay separate.

2. Pick your path

Observer, tester, validator, builder, reviewer, provider, or docs contributor.

3. Open the owner route

Core for chain observation, Infra for work receipts, Bridge for passage evidence, Liquid for motion posture.

4. Bring a public id

Use a transaction hash, receipt id, quote id, route id, proof URL, or exact page URL when asking for help.

5. Keep secrets out

Never post seed phrases, private keys, recovery phrases, private payloads, payment details, or private logs.

Role Paths

Roles are coordination labels only. They do not create allocation, reward eligibility, governance rights, validator advantage, or future entitlement.

ObserverWatch Core state, metadata, validators, blocks, and public chain labels. TesterTry open Infra product paths and report exact page, receipt, quote, or status issues. Validator interestRead operator labels, degraded-state boundaries, and chain-owned readiness before asking about validation. BuilderRead public contracts, stale-state rules, receipt shapes, endpoint boundaries, and must-not-build warnings. ReviewerRead the public model, rollout, security assumptions, governance posture, and chain interactions. Docs contributorReport confusing terms, stale links, missing plain-language paths, or mismatched surface labels.

Suggested Pinned Welcome

This is the public shape the Discord should keep pinned. It is a routing guide, not an offer.

PinPurposeLink
Start hereOne page for first readers and safe routing.start.html
Why use QUADPlain utility map before deeper docs.why.html
Public statusSurface labels and current public destinations.status.html
Report an issueUse the bug report shape below.Bug report template
SafetyNo seed phrases, no private keys, no payment details, no private payloads.support.html

Bug Report Template

Keep reports specific enough to reproduce without exposing secrets.

Surface

Core, Infra, Bridge, Liquid, main site, wallet metadata, docs, or Discord.

Public route

Exact URL, page name, endpoint-contract URL, transaction hash, quote id, receipt id, route id, or proof id.

Expected result

What the page, transaction, quote, receipt, or status label led you to expect.

Observed result

Error label, stale state, wrong copy, broken link, failed action, missing receipt, or confusing wording.

Environment

Browser or wallet type, device class, and approximate time. Public details only.

Boundary

Do not include keys, seed phrases, private payloads, private logs, payment details, or exploit steps.

Docs Feedback Path

  • Point to the exact page or sentence that caused confusion.
  • Say which audience path you were following.
  • Say what you expected the page to answer.
  • Flag stale subdomain links, raw hyperlinks that should be buttons, or pages that feel too dense.
  • Do not ask Discord to become the source of truth; the fix should land on the owning public page.

Update Channel Shape

  • One public update channel should link to Updates and owner surfaces.
  • Updates should use dated, plain labels: changed, fixed, blocked, stale, opened, closed, or needs evidence.
  • Release notes should not imply sale access, reward eligibility, market access, or private support.
  • If an update depends on a subdomain, the subdomain should own the live or staged proof.

Boundaries

Discord helps people find the right public proof. It does not replace proof.

No entitlement

Membership, roles, testing, reports, node interest, or code contributions do not create allocation, rewards, governance rights, leverage, or future privilege.

No private support promise

Public chat can route issues. Sensitive reports must wait for an official private disclosure path when published.

No wallet pressure

Viewing QUAD pages does not require a wallet connection, signature, seed phrase, or payment.

No authority inheritance

A Discord message, role, crawler summary, listing, receipt, route, or public link does not override the owning surface.