Allocyn
Studionet. Network details
Wallet not connected
Live dataStudionet · Allocyn contract0xA2aB…fFc7Explorer

Network

Allocyn works on GenLayer Studionet. Connect a wallet and check that everything lines up.

Network

StudionetGenLayer Studio network for development and testing.Chain ID 61999

Studionet is the only network Allocyn uses for now. Other GenLayer networks may come in a future update. Allocyn never changes your wallet’s network without your approval.

RPC https://studio.genlayer.com/api · Studionet explorer

Wallet

Disconnect clears Allocyn’s own state only. It does not revoke this site’s permission in your wallet; do that in the wallet’s connected-sites settings.

Diagnostics

Each row is checked on its own. A problem in one row does not hide the others.

  • Wallet provider
    Checking: Checking…
  • Connected address
    None
    Not connected.
  • Wallet chain ID
    Unknown
    The wallet has not reported a chain.
  • Selected network (Allocyn)
    Studionet
    Expected chain ID 61999.
  • Expected vs actual chain ID
    61999 vs unknown
  • GenLayerJS client
    Not created
    A client is created when a wallet is connected.
  • SDK preset vs expected
    Warning: Chain ID and RPC match
    SDK chain 61999, RPC https://studio.genlayer.com/api. SDK explorer is https://genlayer-explorer.vercel.app; Allocyn links to https://explorer-studio.genlayer.com.
  • GenLayer Snap
    Unknown
    Checked after a wallet is connected.
  • RPC connection
    Not checked
    https://studio.genlayer.com/api
  • Allocyn contract
    OK: 0xA2aB53A024278Af37f6209735affEDf60A85fFc7
    Official Allocyn deployment on Studionet.

Allocyn contract

0xA2aB53A024278Af37f6209735affEDf60A85fFc7

View in explorer

Official Allocyn deployment on Studionet.

Live mode reads and writes this contract. Reading needs no wallet; writing needs a connected wallet on Studionet.

Check this is the contract the app was written for

The app’s rules (limits, link checks, hashes) are copied from one version of the contract, whose source file has the SHA-256 below. To compare it with what is deployed, run genlayer code 0xA2aB53A024278Af37f6209735affEDf60A85fFc7 with the GenLayer CLI, save the output to a file and hash it.

14d94364fe24ff5511d6ec1ab5bc35635aabc0470efc9c81d45ad4748b94b51a

Showing: Live data

Demo data