+ THE NETWORK REMEMBERS
FOLLOW
THE SHADOW
Words shape perception
Actions leave a digital trace
A shadow inside BNB Chain
Everything here is run by JEV
01 / JEV
Talk to
the shadow
Type a command
JEV answers with live chain data
Nothing is signed
02 / TRACE ENGINE
Follow what
moves beneath
One address opens the network
Follow the route, inspect the connections
Make sense of what remains
THE EVIDENCE LAYER
Every connection has a receipt
| LEG | TIME / BLOCK | FROM → TO | TYPE | VALUE | TRANSACTION |
|---|
The graph, tape and ledger share the same records · type an address in the workspace for a live trace
03 / INFRASTRUCTURE
Own node
JEV on the wire
SHADOW does not borrow an index or a public RPC
JEV reads BNB Chain from a node the team runs
When shared endpoints throttle or lag, the trace keeps moving
No shared rate limits
Public endpoints ration requests across everyone who uses them; JEV answers only from our node
Every block indexed from our node
The index is built block by block from what the node sees, not backfilled from a feed that may have missed one
Read by JEV, not relayed
What you see on the map was read from the chain by JEV on our process; no third party sits between the block and the trace
04 / INTEGRATION
Application filed
with BNB Chain
SHADOW has submitted an application to integrate with BNB Chain
Until it is reviewed, everything here runs independently
on our own node, under JEV
Integration application filed
The request and the supporting material are with BNB Chain
✓ DoneAwaiting BNB Chain's review
Nothing changes on this side until the review comes back
In progressAppears when approved
The integration shows up here only once it is approved
PendingBUILT IN PUBLIC
What is done
What is next
Short list, kept honest
Items move left only when they are running
Block propagation
Branching capital paths
Event indexing / live
Read-only HTTP / JEV
- ✓Own BNB Chain node
- ✓JEV on the terminal, the trace and the index
- ✓Read-only trace engine
- ✓Live indexer behind the terminal
- ✓Read-only HTTP API at /api
- ✓Time window, depth 2 and token filters
- ✓Path finder between two addresses
- ✓Ledger with transaction hashes (cursor paging)
- ✓Receipts export (CSV / JSON)
- ✓Pixel terminal
- ○Native ETH and ERC-1155 flows
- ○BNB Chain integration (pending review)
- ○$SHADOW contract announcement
05 / THE SHADOW IN THE NETWORK
The story changes
The trace stays
In a digital world where information has long outgrown our ability to make sense of it, attention fragments and consciousness overloads
Familiar voices become trusted voices; repetition becomes confirmation; someone else's interpretation quietly replaces our own understanding
Blockchains are open to everyone, but transparency does not guarantee clarity; among millions of transactions, connections disappear into the noise
Words shape perception
Actions leave a digital trace
SHADOW follows the impulses of capital inside BNB Chain, through wallets, contracts and liquidity pools, revealing where positions form, where liquidity moves and where exits begin. JEV runs that read — every command, every route, every receipt
One address opens a path through the network; follow the connections until the story becomes something you can examine for yourself
Find the point of entry
Start with an address or a transaction and identify the first connection
Move through the network
Follow the transfers through contracts, liquidity pools and bridge exits
Read what remains
Inspect amounts, assets and transaction records behind each connection
DEVELOPER INTERFACE
The same trace
Another interface
Inspect and export the structured records behind the current example
Live read-only API at /api · every 200 is {data, meta:{dataset_head, took_ms}}
Swagger at /api/docs · the sample below replays a guided scenario
/graph?address={address}&depth=1SCENARIO REPLAY06 / NATIVE TO THE NARRATIVE
$SHADOW
The shadow has a name
The network keeps its trace
The verified contract address will appear here when it is available
KNOW WHAT YOU ARE LOOKING AT
Keep your
eyes open
A visible connection deserves a closer look
A label is only as strong as its source
Is this live BNB Chain data?+
Yes; JEV reads the live shadowflow API at /api on our own node for search, the trace command, the workspace and the infrastructure box (read only, every 200 is {data, meta:{dataset_head, took_ms}}); the three guided cases on this page are illustrative scenarios
Do I need to connect a wallet?+
No, the interface is read only; it never requests a private key, wallet connection or signature
Does a connection prove shared ownership?+
No, a transfer or a sequence of trades does not establish common ownership or intent; unlabelled entities remain unlabelled
What happens at a bridge?+
The trace ends at the observed boundary; this view does not imply that funds have been followed across every network
Can I keep the results?+
Export the selected trace as CSV or JSON; watchlist choices stay on this device; queries are not stored on a server
Do you run your own node?+
Yes; the chain is read from a node the team operates, which removes third-party rate limits and gaps
What is JEV?+
JEV is the model that runs this page: the terminal, the trace engine and the index; it answers commands against live chain data on our node, read only, nothing signed
Are you integrated with BNB Chain?+
Not yet; an integration application has been submitted and is awaiting review; SHADOW stays independent and unaffiliated until then
END OF TRANSMISSION / JEV IS ON THE WIRE