Skip to content
SineraDocs

Network and lookup

Find contract addresses, tokens and fees for a network, and look up Atoms, sessions, transactions and addresses in the Developer Portal.

Two pages under Developers in the Developer Portal work whether or not you are signed in: Network and Lookup.

For a public, read-only view of ATP state with no sign-in, see the ATP Explorer. If the portal operator has linked an explorer, Lookup opens it instead of the portal's own pages.

Network

Network is the reference for the network selected in the header. Use it when you configure your integration.

SectionWhat it shows
ConnectionThe chain id and where the portal reads the network from.
ContractsThe address of each protocol module, with a copy button.
Admission configThe config id that every new Atom and delegation session must carry.
TokensThe settlement tokens the deployment admits, with their decimals and fee class. Test tokens are marked.
Fee ratesThe protocol fee for each case. The rate is fixed on an Atom when it is created and does not change afterwards.
SDK quickstartA short example that reads one Atom on this network, ready to copy.

A network marked Not deployed has no contracts to show. Nothing can be read or created there until a deployment is recorded. Today, BSC Testnet is the only public deployment.

Lookup

Paste an identifier and the portal works out what it is.

You pasteYou get
An Atom idThe Atom's detail page: lifecycle, deadlines, settlement and disputes.
A delegation session idThe session, opened in Delegations.
A transaction hashWhat the transaction did.
An addressWhat the address is (a protocol contract, a settlement token or an ordinary address), how many Atoms and sessions involve it, and a link to the block explorer.

The examples under the search field are real records on the selected network.

Read a transaction

The transaction page is decoded from the transaction and its receipt.

PartMeaning
StatusSuccess, reverted or pending. A pending transaction has been seen by the node but is not in a block yet.
What it didA sentence, for example that it created an Atom with its id and amount, or that it created a delegation session.
ATP eventsEvery event of the deployment that the transaction emitted, in order, with the module that emitted it.
Revert reasonShown for reverted transactions when the network returns one, with an explanation.

A transaction that did not call the deployment and emitted none of its events is reported as not an ATP transaction.

Lookup is the first place to check after you create an Atom or a delegation session. Paste the transaction hash to see whether it succeeded and what it created.

Things to remember

  • Lookup reads the selected network only. An id from another network is not found.
  • The address page gives counts only. To list the Atoms and sessions of an address, sign in with it.
  • Any Atom can be opened by its id. Chain data is public. Signing in only decides which records the portal lists as yours.
  • Records are read at a recent finalized block, so something mined moments ago may take a short while to appear.