Yellow Network and Nitrolite (ERC-7824) development best practices for building state channel applications. Use when building apps with Yellow SDK, implementing state channels, connecting to ClearNodes, managing off-chain transactions, or working with application sessions.
86
Quality
81%
Does it follow best practices?
Impact
91%
1.82xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
ClearNode connection and reconnection
Correct WSS URL
0%
100%
Secure scheme only
100%
100%
Exponential backoff formula
41%
100%
Max reconnect attempts: 5
0%
100%
Base reconnect interval: 3000ms
0%
100%
Reset on successful reconnect
100%
100%
Async timeout implementation
0%
100%
Listener cleanup
60%
70%
WebSocket error handling
100%
100%
Nitrolite package used
0%
0%
Without context: $0.2646 · 1m 24s · 14 turns · 21 in / 5,139 out tokens
With context: $0.4060 · 1m 40s · 20 turns · 276 in / 5,726 out tokens
Authentication flow and message signing
Nitrolite package
0%
100%
createAuthRequestMessage used
0%
100%
createAuthVerifyMessage used
0%
100%
Session key passed as session_key
50%
100%
Separate signing key generated
100%
100%
Plain JSON signing — no EIP-191
0%
100%
JWT token returned/stored
100%
100%
Auth error handling
75%
100%
No private key in logs
100%
100%
Auth timeout
0%
100%
Without context: $0.5443 · 2m 28s · 28 turns · 34 in / 8,605 out tokens
With context: $1.2271 · 4m 41s · 46 turns · 48 in / 16,257 out tokens
Application session lifecycle management
Nitrolite package
100%
100%
createAppSessionMessage used
100%
100%
Protocol: nitroliterpc
50%
0%
Weights [100, 0]
0%
100%
Quorum: 100
0%
100%
Challenge: 0
0%
100%
Nonce: Date.now()
100%
100%
Allocation asset: usdc
100%
100%
Amount as string
100%
100%
createCloseAppSessionMessage used
100%
100%
createGetLedgerBalancesMessage used
100%
100%
Session closed in demo
100%
100%
Without context: $3.5452 · 9m 39s · 92 turns · 195 in / 35,036 out tokens
With context: $2.3828 · 6m 8s · 78 turns · 81 in / 21,562 out tokens
5342bca
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.