Determinism before parallelism
Parallel execution produced divergent state roots. I made replay sequential so a user’s engagement score and rewards resolve to the same state on every validator.
Case 05 · Social engagement · Layer 1
A blockchain where activity in social apps becomes rewards and a voice in governance.
YouthChain is an EVM-compatible Layer 1 for social apps. Posts, likes and other activity are recorded on-chain so users can earn YCR rewards and build an engagement score used in governance. I work on its Rust consensus and execution layer, protocol contracts and the path from mobile activity to the chain.
The public testnet (chain ID 7717) runs with four validators and a block explorer. I implemented and exercised consensus, EVM execution and the engagement path, including validator interruption and recovery.
A social app needs a trustworthy record of participation before it can award tokens or use an engagement score for governance. The network also needs to replay that record consistently: divergent state would make balances and scores unreliable.
Co-designed and implemented PoE/FireDAG consensus with BLS signatures. The current testnet uses one block leader per round.
Traced state-root mismatches to transaction execution and made replay deterministic by construction.
Built protocol contracts, JSON-RPC integration and an off-chain sequencer with an engagement rollup.
In an integrated app, a person posts, likes or comments. The integration sends that activity toward YouthChain instead of leaving it only in an app database.
Social action → mobile APIParticipation has a user and an action type.The integration sends a transaction calling EngagementOracle.recordAction with the user and action type. The app waits for confirmation before treating it as recorded.
Post or like → recordAction transactionA submitted action is not yet a confirmed reward.Four testnet validators agree on the transaction, then execute the contract. It updates the engagement score and pending YCR reward; deterministic replay keeps the result consistent.
Confirmed action → score + pending YCREvery validator must compute the same user balance and score.The app can read the score and pending reward; a user can inspect the public chain in the testnet explorer. Claiming turns pending YCR into a token balance.
On-chain record → app view / explorerUsers and developers need a verifiable result.Parallel execution produced divergent state roots. I made replay sequential so a user’s engagement score and rewards resolve to the same state on every validator.
I tested validator interruption and recovery during load because participation records and payouts depend on the chain continuing to agree after a node fails.
Live explorer for testnet chain 7717. It exposes block, transaction and validator data without a wallet.
Public explanation of the social platform and the Proof-of-Engagement project.
Product purpose and engagement mechanics follow the YouthChain documentation. The public explorer and indexer were checked on 30 September 2026; implementation scope follows protocol records and my CV.
Public testnet, not a mainnet claim. Engagement-weighted validator selection is planned beyond the current four-validator phase.