Supported networks & standards

Networks

Steady is currently available on two networks: Ethereum (Layer 1) and Arbitrum (Layer 2).

Ethereum provides the deepest liquidity, the broadest institutional infrastructure support, and the security guarantees that matter for large institutional flows. Arbitrum extends those same security guarantees to a Layer 2 environment with significantly lower transaction costs, making it the right network for high-frequency activity, DeFi integration, and applications where Layer 1 gas fees would be prohibitive.

Token Standards

Both STDY and wSTDY are standard ERC-20 tokens.

For most purposes, STDY behaves exactly like any other ERC-20:

• Standard transfer, approval, and allowance methods
• Compatible with any ERC-20-aware wallet, custodian, or analytics tool
• Native support across the entire EVM ecosystem

The one "non-standard" behavior is the rebase itself: STDY's balanceOf returns the current rebased balance at every block, which means balances can change without an explicit transfer transaction. This is important to know if you're building infrastructure that assumes balances only change on transfers (in which case wSTDY is the cleaner choice).

Each Network is Independent, there is No Bridge

There is no bridge between Steady's network deployments, and no bridge is planned. STDY exists as separate, fully native deployments on Ethereum and Arbitrum, not as a wrapped or bridged token on one of them.

In practice, each network is its own self-contained Steady ecosystem. To move value between Ethereum and Arbitrum, onboarded investors can redeem STDY on one network and mint on the other through the primary market.

Official Contract Addresses

Ethereum Mainnet

• STDY: 0xe5F26fdBc375f75A5F4BDE3049DC2E0dd93a95b9
• wSTDY: 0xf131f35702b6Ad5c40fF1363224A3828938192DB

Arbitrum

• STDY: 0xe5F26fdBc375f75A5F4BDE3049DC2E0dd93a95b9
• wSTDY: 0xf131f35702b6Ad5c40fF1363224A3828938192DB

Always verify contract addresses against our official channels before transacting. Anything found on third-party sources should be cross-checked against the addresses published on steadyprotocol.io and in our official documentation.