YouthChain

What is YouthChain?

YouthChain is a Layer 1 blockchain built around Proof of Engagement (PoE) — a consensus design where on-chain user engagement, alongside stake, shapes who produces blocks and how the community governs itself. Every like, comment, share, post, and watch performed inside integrated social apps is recorded on-chain via the EngagementOracle contract. The aggregated Engagement Score (ES) already drives quadratic-voting DAO power today, and feeds a small engagement multiplier (β=0.10) on top of stake-weighted leader selection. On the 4-node testnet, validators are foundation-operated servers, so stake is the real differentiator; full ES-weighted selection and engagement-proportional rewards ship post-testnet, once validator identities map to real engaged accounts.

Mobile team — start here

10 numbered steps from zero to first on-chain engagement in 30 minutes. Copy, paste, run.

Quickstart

Connect MetaMask and submit your first engagement transaction in 5 minutes.

Architecture

Understand the 5 Rust crates, revm-based EVM, and the PoE-FireDAG consensus.

Mobile API

27 REST endpoints — register, engage, read profile, leaderboard, faucet, attestations.

ABIs

All 8 contract ABIs as downloadable JSON, CORS-enabled.

Testnet at a glance

Chain ID

7717

Block time

~1 second

Validators

4 nodes

Consensus

PoE + BFT (⌊2N/3⌋+1)

EVM

revm 14 · EIP-1559-style base fee

Finality

~2s (1 BFT round)

Key features

  • Stake-weighted leader selection with an engagement multiplier — leader probability is stake × (1 + β·ES) with β=0.10. On the 4-node testnet the engagement term is inert (validators aren’t content creators), so stake is the real differentiator; genuine ES-weighting activates post-testnet. See Engagement Score.
  • DAG-ready block structure — blocks carry a parent_hashes vector and verifiers accept up to 4 parents, but the live network runs single-leader-per-round (k=1). Parallel DAG production is implemented and tested on a branch and ships once the certified-DAG fork-choice is enabled.
  • BLS12-381 aggregate signatures — block commits are a single aggregated signature over the validator set.
  • Full EVM compatibility — deploy any Solidity contract, use any Ethereum wallet.
  • Native mobile integration — no wallet SDK required for MVP; the mobile API handles signing server-side (see the security note).

Where to go next

1

Read the quickstart

Set up MetaMask and push your first transaction.
2

Pick an integration path

Building a mobile app? Start with the Mobile API. Building a dApp? Start with the JSON-RPC reference.
3

Explore contracts

The 5 core contracts (YCEToken, EngagementOracle, StakingJars, QuadraticVoting, ValidatorRegistry) are live on testnet.