MSU Builder Forum — Community Guidelines

[msu_admin]

Guidelines for Q&A, collaboration, and knowledge sharing across the MSU Builder ecosystem. These guidelines apply alongside the Builder Code of Conduct.

---

1. Forum member level system

Trust Levels are assigned based on participation and activity. Each level unlocks additional capabilities.

Level	Name	Capabilities
TL 0	New user	1. Reply only 2. Cannot create topics 3. 1 link per post 4. No image uploads 5. No DMs
TL 1	Basic user	1. Create topics 2. Upload images 3. 1 link per post 4. Send DMs 5. Flag posts
TL 2	Member	1. All TL 1 capabilities 2. No link limit 3. Send invites 4. Ignore users
TL 3	Regular	1. Recategorize topics 2. Edit topic titles 3. Instantly hide TL 0 spam 4. Edit other’s posts
TL 4	Leader	1. Full TL 3 access 2. Delete posts 3. All moderation

• Level thresholds (how we use Trust Levels)
  • TL 1 is the baseline verified member tier. It unlocks features that require higher accountability (e.g., creating topics, sending DMs, sharing richer content).
    • Members below TL 1 cannot:
      • Create topics
      • Add external links
      • Upload images
      • Create topic on the Showcase category
  • TL 3 is a moderation-capable tier. It grants limited operational permissions needed to help maintain forum quality.
    • Members below TL 3 cannot:
      • Move miscategorized topics
      • Edit topic titles when necessary
      • Immediately hide obvious spam

---

2. Member moderation policy

A. Enforcement (details)

• Scope: Posts, replies, DMs sent via the forum, tagging, categorization, content shared in the forum, conduct toward other members on the board

• Severity

  Severity level	Description	Example
  Minor	Low impact · Easily corrected · Likely unintentional	Wrong category, missing tags, no code block
  Major	Clear rule breach · Repeated minor offenses · Intentional	harassment, IP infringement post, repeated spam
  Dangerous	Harmful to users or platform · Legal risk	scam links, hate speech, doxxing, credential exposure

When a violation in the forum reaches a certain threshold, the team refers the case to the Builder Program. From that point, the full Builder Terms enforcement ladder governs the outcome, including app-level and account-level sanctions on your MSU Builder account.

• Dangerous violation → Referred immediately

• Major violation unresolved after Enforcement Step2 → Referred

• Step 3 reached → referred; Step 4 applied in parallel on the board

• Any violation with legal or compliance implications → Referred immediately

• Enforcement Steps

Steps	Trigger	Enforcement Action	Relief
Step 1: Correction Request	- Post in wrong category - Missing required tags - No code block used for code - Accidental brand guideline slip	- Private DM with guidance - Post flagged for editing if needed - No formal warning recorded	- Corrected → no further action - Ignored → Step 2
Step 2: Posting suspended	- Harassment or abusive replies - Investment solicitation - IP infringement post - Reward manipulation discussion - Repeated Step 1 without improvement	- Formal warning via private DM - Discourse Silence (up to 7 days) - Offending posts hidden - Member can still read — cannot post	- Appeal within 7 days - Violation resolved → Silence lifted - No response or repeat → Step 3 - Pattern identified → referred to Builder Program
Step 3: Account Suspension	- Hate speech or religious disparagement - Scam or phishing post - Doxxing another member - Sharing credentials or exploits - Step 2 unresolved or repeated	- Discourse Suspend applied - All posts hidden pending review - Case referred to Builder Program team - Platform-level sanctions governed by Builder Terms from this point	- Appeal within 7 days via contact_builder@nexpace.io - Internal review → reinstatement possible - No appeal or repeat → permanent ban - Builder Terms sanctions may apply independently
Step 4: Permanent Account suspension	- Step 3 with no response within 7-day appeal window - Step 3 accumulated 2 or more times - Same dangerous violation repeated after reinstatement - Circumventing a Step 3 suspension (new account, etc.)	- Discourse account permanently suspended - All posts removed - IP and device block applied - Re-registration attempts blocked - Builder Program team notified for platform-level action	- No appeal available - No reinstatement under any circumstances - New account identified as same builder → Step 4 applied immediately - Platform-level consequences governed separately by Builder Terms
Fast Track: Immediate Enforcement	- Active scam or phishing link live on the board - Private keys or credentials visibly posted - Confirmed bot account or coordinated spam - Content with legal or compliance implications	- Post removed immediately - Account suspended without prior warning - IP blocked applied - Referred to Builder Program team in parallel	- The team may act immediately at its discretion when urgent response is needed

Note: Steps are not always applied in sequence. A first-time dangerous violation goes directly to Step 3 or fast track. The team exercises judgment based on severity, impact, and whether harm is ongoing.

B. Appeal

• Appeal window is valid for 7 days from the DM with violation was sent. Appeals apply to Steps 2 and 3 only. Step 4 is permanent and not subject to appeal.

Escalation Rules

• Same violation repeated 3× → automatic escalation to the next step

• No response to a formal notice within 7 days → escalates to the next step

• Step 3 accumulated 2× or more → automatic Step 4, no further notice required

• Appeal Process

  

• Reversal after appeal

  • Step 2 reversal
    • Discourse Silence lifted immediately
    • Hidden posts reviewed and restored
    • Normal posting privileges reinstated
  • Step 3 reversal
    • Board account reinstated
    • Builder Program reversed
    • Platform-level sanctions reviewed separately under Builder Terms

C. Flag types and handling

Severity	Flag Types	Description	Immediate Action	Enforcement Type
Minor	Low posting quality	- Wrong category , Missing required tags, No code block for code, Unsolicited promotional post outside Showcase (e.g. Q&A post filed under Resources · code pasted as plain text)	Correction Request Sent	Step 1
Minor	Attribution / branding (minor)	- 3rd-party content shared without attribution (first time, non-malicious), Accidental MSU branding guideline slip (e.g. Reposting without crediting the author)	Correction Request Sent	Step 1
Major	Abusive conduct	- Single abusive or disrespectful reply, Coordinated downvote campaigns, Personal attacks framed as technical criticism	(e.g. insulting a builder’s competence in a personal way · mass-flagging a specific user’s posts)	Warning Issued + Post deleted if necessary
Major	Platform integrity	- Promoting reward manipulation, fake traffic methods, or self-purchase schemes - Discussing Earned NESO abuse techniques	(e.g. “how I farmed NESO with fake clicks” · sharing scripts that simulate transactions)	Post deleted + Posting silenced + Builder Program referred
Major	IP infringement / branding misuse	- Confirmed 3rd-party IP infringement, MSU trademark misuse, Sharing reverse-engineered or tampered MSU assets (e.g. posting unlicensed MSU artwork · using MSU logo in misleading ways)	Post deleted + Posting silenced + Builder Program referred	Step 2 + Refer to the Builder Program
Major	Investment solicitation / external campaigns	- Token price predictions - Financial service promotions, etc (e.g. “This token will 10x” · linking to unlicensed financial services)	Warning Issued + post deleted if necessary	Step 1
Major	Content harmful to the MSU ecosystem	- Misinformation about the ecosystem or other builders (e.g. fabricated security incidents · false statements about another builder’s app)	Post deleted + warning issued	Step 2
Dangerous	Spam/bot generated posts	- Any detected bot generated posts or spam posts - Any duplicated posts (e.g. identical replies in multiple threads · AI-generated spam flooding Q&A)	Post deleted + Account suspended	Fast Track
Dangerous	Scam / phishing/fraudulent links	- Fake token drops - Wallet connection prompts, etc (e.g. “Connect your wallet to claim 1000 NESO” · fake team DM links)	Post deleted + Account suspended + Builder Program referred	Fast Track
Dangerous	Inappropriate	- Contents that include harmful, unsafe, or inappropriate content, including but not limited to gambling, adult, exploitative, or discriminatory materials (e.g. links to unlicensed gambling services · explicit imagery · content targeting vulnerable groups)	Post deleted + Account suspended	Fast Track
Dangerous	Harassment / hate speech	- Slurs or targeted insults - Religious mockery / denigration - Repeated misgendering	Post deleted + Warning issued	Fast Track
Dangerous	Security — credentials / exploits	- Posting private keys, Seed phrases, API keys, Internal endpoints - Sharing exploit code or attack vectors (e.g. accidental or intentional key exposure · PoC exploit for MSU contracts)	Post deleted + Warning issued(with requesting rotate key) + Builder Program referred	Fast Track
Review	Others	2 or more TL 3 flags		Team review

Still allowed: factual and respectful criticism of religious doctrine, academic discussion of discrimination, quoting offensive content to report or condemn it, and satire that clearly does not demean any individual or group. When intent is ambiguous, the moderation team reviews the full context before taking action.

---

3. Code of conduct

• Builder Code of Conduct always applies. Violations on this Forum may also constitute a CoC breach and can result in restrictions on your Builder Program participation, up to and including permanent exclusion.
• Encouraged
  • Constructive criticism of code, architecture, and design (ideally paired with an alternative suggestion)
  • Participating under a pseudonym (disclosing your real identity is entirely optional)
  • Sharing failure cases: “Here’s what didn’t work and why” is valuable signal for the whole ecosystem
  • Fact-based comparison and discussion of other projects or tools
• Prohibited
  • Bot-generated or automated posts: Posts created via bots, automated scripts, or injected tools are removed immediately and the account suspended.
  • Spreading misinformation about the MSU ecosystem: Deliberate false claims about the ecosystem, Nexpace, or other builders. Technical disagreements are welcome — misinformation is not.
  • Sharing transaction manipulation methods: Discussing or promoting self-purchases, fake traffic, forced clicks, or any technique to artificially inflate token rewards.
  • Investment solicitation or external financial promotions: Token price predictions, unverified “alpha”, and promotions for unrelated financial products or campaigns.
  • Copyright infringement or unauthorized IP use: Posting others’ work without attribution, or using MSU brand assets in ways that violate the MSU Branding Guidelines.
  • Harassment, discrimination, or abusive language directed at any builder, user, or the team: Technical disagreements must be grounded in data and reasoning, not personal attacks.
  • Doxxing: Publishing another member’s real name, wallet address, or personal information without their explicit consent. Even your own personal information including wallet address is not allowed.

---

4. Posting categories and rules

A. Posting categories

Category	Purpose	Access	Note
Notice	Official announcements on forum operations and the Builder Program	The Team ONLY
General	Introductions, off-topic, casual chat	TL 1+ write	minimum 1 tag required
Ask & Help	Technical questions and answers	TL 1+ write	minimum 1 tag required
Showcase	Synergy App launches, demos, project intros	TL 1+ write	minimum 1 tag required
Prompt tips	Tips and prompt patterns for vibe coding and AI agents in Synergy App development	TL 1+ write	minimum 1 tag required

Note: The category structure may change over time. New categories may be added, and existing ones may be renamed, merged, or removed as the forum’s needs evolve.

B. Posting rules

• Ask & Help
  • Search before you post
    • Use the Discourse search (shortcut /) to check for existing topics before creating a new one. Duplicate topics will be merged into the original thread.
  • Write a descriptive title
    • Do not post with title such as “Please help”, “Getting an error”. Be specific about your issue.
  • Use code blocks for all code and logs
    • Wrap all code snippets, error logs, and transaction data in `\```` fenced code blocks. Plain-text pastes make posts hard to read and answer.
  • Add at least one tag
    • Tag your post with the relevant stack or domain
  • Mark a solution when resolved
    • Click ✓ Solution on the answer that solved your issue. If you figured it out yourself, post your solution as a reply and mark it — this helps future builders with the same problem.
  • Share your progress
    • If you’ve made progress or changed your approach, update the thread with a reply. Open-ended posts with no updates are harder for others to build on.
• General
  • Attribute third-party content
    • When sharing code, libraries, or content created by others, always credit the original source and include the applicable license. Omitting authorship or presenting others’ work as your own is strictly prohibited.
  • Follow MSU branding guidelines
    • Any use of MSU logos, trademarks, or brand assets in posts must comply with the official MSU Branding Guidelines. Unauthorized or misleading use of MSU intellectual property is prohibited.
• Showcase
  • Keep promotions ONLY in the Showcase category
    • Project announcements, launch posts, and demos belong in 🚀 Showcase. Promotional posts in other categories will be moved without notice.