Skip to content
Black Relay Docs

Frontier Development Notes

Practical notes for building around EVE Frontier public data, Sui reads, wallet identity, static client data and the Black Relay API.

The Black Relay API is one tool in that stack. It is useful when you need source-labelled public read data; it is not a replacement for official contracts, EVE Vault, direct Sui reads, dApp Kit, local tests or pre-transaction validation.

Start with the boundary

Section titled “Start with the boundary”

Before choosing a tool, decide what kind of problem you are solving:

Problem Primary tooling
Learn the world and object model. Official docs, world contracts, Sui docs.
Build or publish Move logic. Builder scaffold, Sui CLI, world contracts.
Connect a player wallet. EVE Vault, dApp Kit, server-side nonce flow if needed.
Inspect exact current object state. Sui CLI, GraphQL, gRPC or SDK reads.
Ask a player to sign. Wallet/dApp flow with fresh object state.
Show public names, systems, events or sources. Black Relay API, Registry explorer or Registry exports.
Reproduce the canonical import pipeline. blackrelay/registry tooling.

If the next action can move assets, change infrastructure or spend gas, use direct sources and live reads. If the next action is display, exploration, lookup or provenance, a public read layer may be the right shortcut.

Builder map

Section titled “Builder map”

For Frontier development, these docs focus on boundaries that usually cost builders time:

Problem Where to start
Setting up tools, wallets and dApp sessions Environment and identity
Planning a tool or dApp workflow Development workflows
Keeping IDs, names and objects straight Identifiers and data model
Understanding the world model World, chain and client
Handling world package upgrades World upgrades
Inspecting objects and events directly Sui CLI and GraphQL
Indexing public chain events Events and indexing
Building around smart assemblies Smart Assemblies
Designing a programmable storage unit Programmable SSUs
Working with routes, gates and systems Gates, turrets and routes
Handling rift and location evidence Rifts and locations
Understanding static-client data Static client data
Finding the right upstream tool or endpoint Reference links
Testing safely before live use Testing and localnet
Designing the frontend/server split dApp Architecture
Running a tool after launch Deployment and operations
Debugging environment or transaction errors Debugging and help
Reviewing extension safety Move security checklist
Tracking stale examples and patch drift Known stale assumptions
Deciding when the public read layer helps Why use Black Relay

Where Black Relay fits

Section titled “Where Black Relay fits”

Black Relay maintains a Registry pipeline that combines public Sui data, World API snapshots, static-client extraction and reviewed source evidence into export bundles. The public API serves those bundles from Cloudflare.

Use it for public read-side work:

  • lookup and search
  • public current-state tables
  • source and confidence display
  • killmail and event browsing
  • static-client labels and type metadata
  • export freshness checks
  • bulk public exports

Black Relay indexes public or source-labelled data only. It does not publish private Discord intel, real-world identity claims, wallet secrets or unverifiable alt accusations.

Do not use it as transaction authority. A dApp that signs, sponsors, deploys, mutates or spends should re-read live state through direct Frontier and Sui tooling before asking a player to sign.

Frontier data can change after patches or cycle resets. Check source, cycle and timestamp before relying on a record.

API reference

Section titled “API reference”

If the API is the right tool for your use case, start with API quickstart or Runnable examples.

API base URL:

https://api.blackrelay.network

Current defaults:

Setting Value
Environment stillness
Current cycle 6
API version v1
Access model Public read-only
CORS Access-Control-Allow-Origin: *
Methods GET, HEAD, OPTIONS

The API does not create canonical records, index Sui directly, call the World API, sign transactions or mutate Registry state. Use the operations routes to check freshness and source gaps before treating data as complete.

Section titled “Main links”