Start at the source.
Block height, gas, wallet balances and contract data are read from BNB Chain. The observation record preserves the source and time of the read.
BNB RPC documentation ↗An agent that reads BNB Chain with you. Ask a question. Inspect its path. Follow every answer back to its evidence.
Talk to WRAITH ↗From your question
to a verifiable observation.
Talk to WRAITH about BNB Chain. Inspect a wallet, a transaction or a token. Chain observations appear beside the answer.
Select a component. See what it does, what it can access, and where the boundary lies.
Step through a research request. This walkthrough explains the sequence; live reads are shown in the chat above.
Choose a scenario and follow the request, one step at a time.
DEMONSTRATION · NO FUNDS OR TRANSACTIONSInspect a BNB Mainnet address or transaction. Every result links to BscScan for an independent view.
An address is the beginning of a story.
See what is actually recorded.
Know what the system can establish before you rely on an answer.
Block height, gas, wallet balances and contract data are read from BNB Chain. The observation record preserves the source and time of the read.
BNB RPC documentation ↗WRAITH has no access to a private key. Its tools cannot send a transaction, approve a token, move a balance or request a wallet signature.
Follow the permissions ↗Language reasoning runs on a server-side model. Chain reads are real; model inference is not executed by BNB validators.
Read an answer with its evidence ↗No token address is configured for this release. This site does not ask you to buy a token or fund an inference deposit.
The execution theatre is an interactive explanation. Actual RPC observations appear in the chat record and the explorer, with links to BscScan.
No. An address, bytecode and ERC-20 metadata cannot prove a token is safe. WRAITH reports the data it can read and leaves unsupported conclusions unresolved.
The current conversation stays in this browser tab. Requests are processed by the configured model provider. Do not send private keys, recovery phrases or other secrets.