Can a general-purpose chain be scoped down to fit a single community, and become the substrate for consumer products whose users never have to learn what gas is?
NERA is an EVM-compatible blockchain network built by the studio as the substrate for community-scale consumer products. Frontier testnet is live, the public block explorer runs at scan.nerachain.io, and the NNS (Nera Name Service) identity layer is in production. My Bridge, the studio's hyperlocal social-commerce platform, is the first end-to-end consumer product running on top of NERA, using its wallets, identity, on-chain tipping, and event-attendance NFTs in production in Lethbridge.
Mainnet chains optimize for global throughput and global liquidity. Their fee curves, finality assumptions, and operating costs are tuned for that ambition, not for a single city's social app or a regional loyalty program.
Closed permissioned chains solve the cost problem but stall on governance. Who decides what gets deployed, who can validate, who pays for what? Without a public answer, partner adoption stalls.
Consumer Web3 onboarding is broken. Asking a new user to manage a seed phrase before they can sign up is a hard filter against everyone who doesn't already think in crypto.
Platform-owned identity ports the same problem from Web2 to Web3. A handle owned by a single app is no more durable than @username. Losing the account means losing the identity.
Most chains do not ship explorer, identity, and wallet tooling that a small studio can integrate in a single product cycle. The infrastructure exists in fragments; integrating them all is its own engineering project.
Tune gas economics for sub-cent consumer transactions. Pick finality and throughput parameters that fit civic, event, and commerce workloads, not global DeFi. Run testnet open and public so partners can validate independently.
EVM compatibility means the dev tooling is the dev tooling everyone already uses: Solidity, Foundry, Hardhat, MetaMask. The consensus layer is built on Tendermint-style BFT with hot-swappability, so the chain can evolve its agreement model without forking off its history.
Nera Name Service gives users a portable name backed by a wallet address. Apps can resolve names but cannot own them. If a consumer leaves a product, their identity goes with them.
For consumer products like My Bridge, NERA supports custodial wallet flows at signup. The user never sees a seed phrase. Self-custody is available later, when the user actually wants it. The friction lives in the right place: not the front door.
scan.nerachain.io is live as a first-party explorer. Block production, transactions, NNS lookups, and wallet activity are public and inspectable. The integration story for a partner product is one stack, not five.
My Bridge is in production in Lethbridge. Wallets, NNS identity, on-chain tipping, and event-attendance NFTs are all served from NERA in front of real users. The thesis that a small chain can host a real consumer product is no longer hypothetical.
Every event check-in, peer scan, tip, and reward redemption inside My Bridge is a NERA transaction. Holding fees at consumer-product levels through that activity is one of the substrate-thesis bets, and the bet is currently holding.
The MyBridge field deployment makes the case starkly: a non-custodial-only product would have lost most signups at the seed-phrase step. Custodial-by-default with optional self-custody is the only sign-up flow that respects both crypto-native and crypto-naive users.
scan.nerachain.io being live means a prospective partner can verify chain liveness, transaction volume, and product activity themselves, without a sales call. The explorer is documentation that updates itself.
EVM-compatible execution layer. Standard Solidity tooling (Foundry, Hardhat) targets NERA without modification.
Tendermint-derived BFT consensus with hot-swappable mechanisms. The chain can adopt new consensus parameters without breaking history.
1,247 TPS measured on Frontier testnet with sub-second finality. Numbers tuned for consumer/community workloads, not maximum global throughput.
Native NNS (Nera Name Service) identity layer. Wallet-backed portable names, resolvable by any app, owned by none.
Custodial wallet integration surface for partner products. Sign-up flows skip seed-phrase prompts; self-custody migration is an opt-in path, not a required one.
Built-in cross-chain bridge infrastructure for moving assets to and from EVM mainnets when partner products need it.
First-party public block explorer at scan.nerachain.io. Block production, transactions, NNS lookups, and contract activity are inspectable without a backend.
Move from Frontier testnet to mainnet with the My Bridge production load as the canonical workload to size against.
Publish gas economics in detail: the curve, the assumptions, and where the model breaks if community workloads exceed projections.
Open NNS to second-product adoption. The thesis is only proven if a chain-native identity layer serves more than one consumer product.
Document the custodial-to-self-custody migration UX as a reference flow for other consumer Web3 builders.
Field-test secondary deployments. If MyBridge generalizes to a second city, NERA inherits the same generalization question: does a second community workload fit the same chain, or does each community want its own?