← All work

Web3

Engineering on the NEAR Protocol ecosystem

Protocol-level and tooling work on a sharded, proof-of-stake network.

Client
NEAR Protocol ecosystem
Field
Web3
Our part
Part of a wider engineering effort
Stack
RustWebAssemblyTypeScriptPostgreSQLDocker
shard 0shard 1shard 2shard 3cross-shard receiptIndexerchain state, queryableRPC · applicationsepoch nepoch n+4 · validator rotation

The problem

A sharded chain moves the hard problems from the contract to the infrastructure: cross-shard receipts, state that lives in many places, tooling that has to hide all of that from a developer who just wants to deploy.

What we built

  • Contributions to node and infrastructure components on the network’s Rust codebase
  • Indexing and RPC tooling that lets applications read chain state without running their own node
  • Smart contracts and SDK-level utilities for teams building on the network
  • Test harnesses and load tooling used to exercise changes before they reached mainnet

What it changed

  • The same engineers now design chain infrastructure for client products: indexers, relayers and wallets that stay up
  • Hands-on knowledge of a production sharded network, which is rare and shows in estimates