Social / Messaging·EVM
Cyber
Cyber is an OP-stack EVM L2 (chain id 7560) purpose-built for social and consumer apps, with native account abstraction, session keys, paymasters, and the CyberConnect social graph (W3PP profiles, follows, posts) onchain. Use it when you want gasless follows/posts and a portable social graph that any dapp can read.
- 01onchain social graphs (follows, posts, profiles)
- 02gasless social actions via paymaster
- 03consumer apps on a social-native L2
- 04ERC-4337 smart accounts with session keys
- 05portable identity across dapps
- pnpm add @cyberlab/cyber-account viem
- pnpm add wagmi @wagmi/connectors # if using wagmi
| Variable | Scope | Description |
|---|---|---|
| NEXT_PUBLIC_CYBER_RPC_URL | Client | Cyber mainnet RPC URL (chain id 7560). Defaults to https://cyber.alt.technology if unset. |
| CYBER_PAYMASTER_API_KEY | Server | Server-only key for Cyber's ERC-4337 paymaster, used to sponsor user-op gas for social actions. |
Use Cyber as the EVM L2 for onchain social. Add chain id 7560 to your viem/wagmi config with `defineChain({ id: 7560, name: 'Cyber', rpcUrls: { default: { http: [process.env.NEXT_PUBLIC_CYBER_RPC_URL] } } })`. For account abstraction, instantiate `new CyberAccount({ chain, owner, paymaster })` from `@cyberlab/cyber-account` and submit user-ops with `cyberAccount.sendTransaction({ to, data, value })`. Read the social graph (W3PP profiles, follows, content) via the CyberConnect indexer GraphQL endpoint, and write follows/posts by calling the protocol contracts through your CyberAccount. Sponsor gas by attaching a paymaster context to every user-op.
- ⚑Cyber is an OP-stack EVM L2 with chain id 7560 — not Ethereum mainnet, not Base. Configure RPC, bridge, and explorer URLs explicitly or wallets will silently fall back to the wrong chain.
- ⚑Onchain vs offchain content: profile metadata and post bodies are stored on IPFS/Arweave with only the content hash on Cyber — broken pinning produces ghost posts that resolve to nothing.
- ⚑Content moderation is per-app: the protocol does not filter posts, so each frontend must run its own block/mute/report layer. Plan a moderation queue before launch.
- ⚑Paymaster sponsorship requires server-issued signatures — never ship `CYBER_PAYMASTER_API_KEY` to the browser, or attackers can drain your gas budget.
- ⚑Session keys expire and are scoped to specific selectors/contracts; failing to rotate them leaves users stranded mid-session.
- ⚑ERC-4337 user-ops settle in seconds but are not free — bundler/paymaster downtime will block writes even when the L2 is healthy.