Troubleshooting for Nibiru EVM Testnet 2

Find the failure before asking for help.

Check the network, inspect a public address or transaction, then export a clean report for a maintainer or community channel.

Read-only by designNever enter a seed phrase or private key.

Network health

Live data from the official Nibiru Testnet 2 EVM RPC.

RPC statusChecking…Try again shortly.

Latest block—— sec old

Latency— msCheck again

Chain ID—Expected 6911

Inspect public chain data

No wallet connection or signature required.

Address inspector

Verify balance, nonce, and account type.

Wallet or contract address

Transaction debugger

Read inclusion, receipt, cost, and likely state.

Transaction hash

Issue guide

Choose the closest symptom and work through the checks.

What are you seeing?

Share public addresses and transaction hashes only. Support staff never need your seed phrase or private key.

1
Confirm the wallet network is Nibiru Testnet 2.
2
Use EVM chain ID 6911 (hex 0x1AFF).
3
Replace any deprecated testnet RPC with the current official endpoint.
4
Reload the dApp after switching networks.

Build a support report

Turn checks into a reproducible, maintainer-friendly report.

What happened?Steps to reproduce

# Nibiru Testnet 2 support report

Network checked: Run the network check to capture a timestamp
Issue: Wallet shows the wrong network

## Network
- RPC reachable: No
- Chain ID: Unavailable (expected 6911)
- Latest block: Unavailable
- Block age: Unavailable seconds
- RPC latency: Unavailable ms
- Client: Unavailable

## What happened
Not provided

## Steps to reproduce
Not provided

## Safety
- No seed phrase, private key, or secret was included.

_Prepared with Nibiru Debug Desk, an independent community utility._

Open community pilot

Test the workflow in 15 minutes.

Run one real diagnostic from start to finish. Your checklist stays in this browser; only the feedback you choose to post is shared.

0/5steps complete

00–02 minConfirm the safety boundaryUse Testnet 2 and public chain data only. Never paste a seed phrase, private key, personal identifier, or mainnet funds.
02–05 minVerify the networkRefresh Network health. Confirm that the endpoint responds and that the chain ID is 6911 before diagnosing anything else.
05–09 minInspect one public recordCheck a public Testnet 2 address or transaction hash. Note whether the result is understandable and technically useful.
09–12 minCreate a support reportDescribe what happened and the reproduction steps, then copy or download the generated Markdown report.
12–15 minSubmit honest feedbackReport what worked, what failed, and one improvement. A completed checklist is not counted as success without evidence.

Pilot evidence

Turn a session into verifiable proof.

Capture aggregate outcomes, catch inconsistent counts, and export a public retrospective. No participant identities or wallet data are collected.

Private working draftAutosaved only in this browser. Nothing is submitted to a server.

Session title

Reporting status

Session date

City or format

RegisteredValid registrations before the session

AttendedPeople present for a meaningful portion

Correct networkParticipants who verified Testnet 2

Public transactionParticipants with a confirmed public tx

Public repositoryParticipants or teams with a public repo

Documented blockerDistinct reproducible blockers captured

Peer helpersParticipants who helped another builder

Day-7 returnsAttendees completing a follow-up action

Recurring blockers

Public evidence links

Notes and next iteration

Community field kit

Designed to work beyond the demo.

A public, reviewable pilot for helping an India-based cohort complete a first Testnet 2 action. The materials are ready; results will be added only after a real session.

Run the session60-minute first-build workshopRoles, timing, challenge cards, and follow-up Make onboarding clearerEnglish + Hindi quick startSafety, network checks, and support vocabulary Review the complete kitContent, care, and measurementTransparent templates with no invented outcomes