642cb3bdf5
typing error in readme regitstry -> registry |
||
---|---|---|
.github | ||
chains | ||
public | ||
src | ||
.gitignore | ||
.prettierrc.json | ||
auto-imports.d.ts | ||
components.d.ts | ||
env.d.ts | ||
index.html | ||
installation.md | ||
LICENSE | ||
package.json | ||
postcss.config.js | ||
README.md | ||
tailwind.config.js | ||
tsconfig.config.json | ||
tsconfig.json | ||
vite.config.ts | ||
yarn.lock |
Ping Dashboard
is a light explorer for Cosmos-based Blockchains. https://ping.pub .
What sets Ping Dashboard apart from other explorers?
Ping Dashboard stands out by providing a real-time exploration of blockchain data without relying on caching or pre-processing. It exclusively fetches data from the Cosmos full node via LCD/RPC endpoints, ensuring a truly authentic experience. This approach is referred to as the "Light Explorer."
Are you interested in listing your blockchain on Ping Dashboard?
Initially, Ping Dashboard offers free listing for the first 100 blockchains. However, starting from the 101st blockchain, there will be associated fees.
Why does Ping Dashboard rely on official/trusted third-party public LCD/RPC servers?
There are two primary reasons for this choice:
- Trust: In a decentralized system, it is crucial to avoid relying solely on a single entity. By utilizing official/trusted third-party public LCD/RPC servers, Ping Dashboard ensures that the data is sourced from a network of trusted participants.
- Limited Resources: As Ping Dashboard plans to list hundreds of Cosmos-based blockchains in the future, it is impractical for the Ping team to operate validators or full nodes for all of them. Leveraging trusted third-party servers allows for more efficient resource allocation.
Donation
Your donation will help us make better products. Thanks in advance.
- Address for ERC20: USDC, USDT, ETH
0x88BFec573Dd3E4b7d2E6BfD4D0D6B11F843F8aa1
Donations from project
- Point Network: 1000USDC and $1000 worth of POINT
- Bitsong: 50k BTSG
- IRISnet: 100k IRIS
Hire us
You can hire us by submiting an issue and fund the issue on IssueHunter
Contributors
Developers: @liangping @dingyiming