GithubHelp home page GithubHelp logo

ping-pub / explorer Goto Github PK

View Code? Open in Web Editor NEW
321.0 321.0 1.0K 33.21 MB

A light explorer for Cosmos-based Blockchains.

Home Page: https://ping.pub

License: GNU General Public License v2.0

JavaScript 0.18% HTML 0.44% CSS 0.46% Vue 66.62% TypeScript 32.30%
blockchain

explorer's People

Contributors

alisaweb3 avatar dpdanpittman avatar ecoxvague avatar ertemann avatar fadeev avatar fl-y avatar freak12techno avatar george-aj avatar golden-ratio-staking avatar hexskrt avatar ivivanov avatar jarnek73 avatar josietyleung avatar kamikaza731 avatar kioqq avatar liangping avatar mengjay710 avatar nodestake avatar omahs avatar pablin-10 avatar qubelabsio avatar shidiqmuh0 avatar showzyl avatar staketake avatar sxlmnwb avatar uptsmart avatar xiphiar avatar xlightwaverx avatar zenodeapp avatar zreohup avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

explorer's Issues

The query results of denoms_metadata and chain info in json files do not match.

As shown in the picture below, in the result of querying through denoms_metadata, there are display and symbol values, respectively, and for the explanation of swagger, display is the recommended value to be shown to the user. However, in many chain info json files, the display and symbol values ​​are mixed and used. For example, in the case of omniflix chain, in denoms_metadata, the display is flix and the symbol is uflix, but in the chain info json file, the symbol is FLIX. But in the terra chain, the denoms_metadata display is usd, the symbol is UST, and in the json file, the symbol is also UST.

Sometimes the display value is used and sometimes the symbol value is used and it is not unified.
Can you tell me what criteria you used?

스크린샷 2022-05-24 오후 3 09 06

스크린샷 2022-05-24 오후 3 09 27

스크린샷 2022-05-24 오후 3 17 03

스크린샷 2022-05-24 오후 3 17 24

How to set default chain

I only have one blockchain, how can I automatically choose our blockchain when I go to the homepage?
image

I tried to find a way, but it failed :(

License / Usage Check

Hello, Ping.pub team.

I was learning how your software worked and experimenting with recommending validators.

I noticed there is no license / usage guideline published for your repository.

Am I free to modify your software and deploy it on my website for others to use?

error : not matching between denim and amount in Summary asset view.

Hi, I found that denom and amount is not matching in summary asset view.
for example, in AGORIC-3, supply query says that there is 1000000000000000 ubld, but in pingpub explorer assets view shows 1,000,000,000 ubld.
This happens because the denom is left as it is in the assets view, but the amount is changed to the upper denom.

스크린샷 2022-05-20 오후 5 30 34

스크린샷 2022-05-20 오후 5 30 44

propose feature : Respond when other asset types not listed in chain info json are added.

There is no function that can respond when new assets that are not currently listed in the chain info json are added and used.

When pingpub encounter a new asset type, pingpub can use an inappropriate name if it is not recorded in chain info json. Below pingpub use the denom as it is if pingpub can't find the symbol in the chain info.
https://github.com/ping-pub/explorer/blob/master/src/libs/utils.js#L369

Similarly for amount, if exponent cannot be found from chain info, exponent will be 18 or 6, which may be an incorrect value. For example, when a specific asset uses 9 instead of 6 as exponent.
https://github.com/ping-pub/explorer/blob/master/src/libs/utils.js#L401

To solve this, how about querying the denoms_metadata and putting it into the chain info? Of course, this may not apply immediately, as many chains don't provide denoms_metadata. But if you have this feature, the chain doesn't send PR to modify the chain info json, just edit the denoms_metadata.
스크린샷 2022-05-26 오후 5 01 49
https://emoney.validator.network/api/cosmos/bank/v1beta1/denoms_metadata

Validator not visible when jailed

Like asked, here is the issue on git like be discussed on telegram.
On the Sentinel Explorer it was visible that a validator (DragonStake) was jailed for 8 hours since block 312008.
On ping.pub explorer it was not visible that this validator was jailed on the Inactive tab and the validator even disappeared on the Uptime page list. Also in history before block 312008 the validator was not visible anymore and disappeared completely from the list.
Strangely enough another validator named BigCat is visible Jailed and inactive?!
On telegram ping.pub received some prove by pictures.

prettierjs settings / code formatting

Hi Ping Team!

If you use prettierjs to format your code, could you share your settings?

Maybe share a .prettierrc.json file?

It will make it easier for me to share back some changes :)

Followed README but no data showing for my chain

I am trying to run my own instance of the explorer.

I configured it all according to the docs, unless I missed something.

First of all, I do not have a mainnet. So if I do not put a config in src/chains/mainnet, it seems my network does not even show up. So what do I do here -- put in a bogus mainnet entry?

Secondly, for the testnet version, I am not seeing any data showing for my chain. All empty.

Here is my bluzelle.json file in src/chains/testnet:

{
    "chain_name": "bluzelle",
    "api": ["http://localhost:1327"], 
    "rpc": ["http://localhost:26667"],
    "sdk_version": "0.42.6",
    "coin_type": "483",
    "min_tx_fee": "800",
    "assets": [{
        "base": "ubnt",
        "symbol": "BNT",
        "exponent": "6",
        "coingecko_id": "bluzelle", 
        "logo": "https://dl.airtable.com/.attachments/e54f814bba8c0f9af8a3056020210de0/2d1155fb/cosmos-hub.svg"
    }],
    "addr_prefix": "bluzelle",
    "logo": "https://dl.airtable.com/.attachments/e54f814bba8c0f9af8a3056020210de0/2d1155fb/cosmos-hub.svg"
}

Is there some way to see the logs of why this is not working?

Unable to build latest version with yarn

Issue: Yarn fails to build.
Versions:

root@erialos:~/sept-fork-explorer-update# node --version
v16.15.1
root@erialos:~/sept-fork-explorer-update# npm version
y{
  'ping-wallet': '0.1.0',
  npm: '8.11.0',
  node: '16.15.1',
  v8: '9.4.146.24-node.21',
  uv: '1.43.0',
  zlib: '1.2.11',
  brotli: '1.0.9',
  ares: '1.18.1',
  modules: '93',
  nghttp2: '1.47.0',
  napi: '8',
  llhttp: '6.0.4',
  openssl: '1.1.1o+quic',
  cldr: '40.0',
  icu: '70.1',
  tz: '2021a3',
  unicode: '14.0',
  ngtcp2: '0.1.0-DEV',
  nghttp3: '0.1.0-DEV'
}
root@erialos:~/sept-fork-explorer-update# yarn --version
3.2.3

When I run yarn && yarn build, it fails to build with the following output.

root@erialos:~/sept-fork-explorer-update# yarn && yarn build
➤ YN0070: Migrating from Yarn 1; automatically enabling the compatibility node-modules linker 👍

➤ YN0000: ┌ Resolution step
➤ YN0061: │ vue-context@npm:6.0.0 is deprecated: No longer maintained
➤ YN0061: │ uuid@npm:3.4.0 is deprecated: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
➤ YN0061: │ core-js@npm:3.22.5 is deprecated: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
➤ YN0061: │ core-js@npm:2.6.12 is deprecated: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
➤ YN0032: │ eccrypto@npm:1.1.6: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ secp256k1@npm:4.0.3: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ secp256k1@npm:3.7.1: Implicit dependencies on node-gyp are discouraged
➤ YN0061: │ popper.js@npm:1.16.1 is deprecated: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
➤ YN0061: │ querystring@npm:0.2.0 is deprecated: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
➤ YN0061: │ highlight.js@npm:9.18.5 is deprecated: Support has ended for 9.x series. Upgrade to @latest
➤ YN0032: │ nan@npm:2.14.0: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ nan@npm:2.16.0: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ evp_bytestokey@npm:1.0.3: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ node-addon-api@npm:2.0.2: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are discouraged
➤ YN0032: │ keccak@npm:3.0.2: Implicit dependencies on node-gyp are discouraged
➤ YN0061: │ stable@npm:0.1.8 is deprecated: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
➤ YN0002: │ @vue/babel-plugin-jsx@npm:1.1.1 doesn't provide @babel/core (p36aab), requested by @babel/plugin-syntax-jsx
➤ YN0002: │ @vue/cli-service@npm:5.0.4 [2fb66] doesn't provide @babel/core (p1b57a), requested by @babel/helper-compilation-targets
➤ YN0002: │ @vue/eslint-config-airbnb@npm:6.0.0 [2fb66] doesn't provide webpack (pa6ebc), requested by eslint-import-resolver-webpack
➤ YN0002: │ @vue/eslint-config-standard@npm:6.1.0 [2fb66] doesn't provide webpack (p11b8d), requested by eslint-import-resolver-webpack
➤ YN0002: │ @vueuse/core@npm:4.0.0 doesn't provide vue (p71f68), requested by vue-demi
➤ YN0002: │ @vueuse/shared@npm:4.0.0 doesn't provide vue (p70418), requested by vue-demi
➤ YN0002: │ bootstrap-vue@npm:2.21.1 doesn't provide jquery (p68a24), requested by bootstrap
➤ YN0002: │ bootstrap-vue@npm:2.21.1 doesn't provide vue (pa8cbc), requested by portal-vue
➤ YN0002: │ ping-wallet@workspace:. doesn't provide @babel/core (p85d5f), requested by @babel/eslint-parser
➤ YN0002: │ ping-wallet@workspace:. doesn't provide @types/leaflet (p82bb3), requested by vue2-leaflet
➤ YN0060: │ ping-wallet@workspace:. provides apexcharts (pd9bff) with version 3.2.0, which doesn't satisfy what vue-apexcharts requests
➤ YN0002: │ ping-wallet@workspace:. doesn't provide css-loader (p3fbb9), requested by vue-loader
➤ YN0060: │ ping-wallet@workspace:. provides eslint (p4ac6c) with version 8.15.0, which doesn't satisfy what @vue/eslint-config-standard and some of its descendants request
➤ YN0002: │ ping-wallet@workspace:. doesn't provide eslint-plugin-node (p9b947), requested by @vue/eslint-config-standard
➤ YN0002: │ ping-wallet@workspace:. doesn't provide eslint-plugin-promise (pd0be4), requested by @vue/eslint-config-standard
➤ YN0060: │ ping-wallet@workspace:. provides eslint-plugin-vue (pe8a54) with version 9.0.1, which doesn't satisfy what @vue/eslint-config-standard requests
➤ YN0002: │ ping-wallet@workspace:. doesn't provide jquery (p45d43), requested by bootstrap
➤ YN0002: │ ping-wallet@workspace:. doesn't provide popper.js (p882e5), requested by bootstrap
➤ YN0002: │ ping-wallet@workspace:. doesn't provide svelte (p6f170), requested by swiper
➤ YN0060: │ ping-wallet@workspace:. provides swiper (p375f6) with version 6.5.1, which doesn't satisfy what vue-awesome-swiper requests
➤ YN0060: │ ping-wallet@workspace:. provides vue (p165c3) with version 2.6.14, which doesn't satisfy what @intlify/vue-i18n-loader requests
➤ YN0002: │ ping-wallet@workspace:. doesn't provide webpack (p84cf9), requested by compression-webpack-plugin
➤ YN0002: │ ping-wallet@workspace:. doesn't provide webpack (pe80da), requested by node-polyfill-webpack-plugin
➤ YN0002: │ ping-wallet@workspace:. doesn't provide webpack (p79ce6), requested by sass-loader
➤ YN0002: │ ping-wallet@workspace:. doesn't provide webpack (p98593), requested by ts-loader
➤ YN0002: │ ping-wallet@workspace:. doesn't provide webpack (p2d89e), requested by vue-loader
➤ YN0002: │ vue-context@npm:6.0.0 doesn't provide vue (p0d58e), requested by vue-clickaway
➤ YN0002: │ vue-slider-component@npm:3.2.11 doesn't provide vue (p5afb8), requested by vue-property-decorator
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 27s 275ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ yargs-parser@npm:20.2.9 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:16.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yorkie@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ zrender@npm:5.3.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ typescript@npm:4.6.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0000: └ Completed in 2m 4s
➤ YN0000: ┌ Link step
➤ YN0007: │ protobufjs@npm:6.11.2 must be built because it never has been before or the last one failed
➤ YN0007: │ protobufjs@npm:6.10.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @tharsis/address-converter@npm:0.1.8 must be built because it never has been before or the last one failed
➤ YN0007: │ @tharsis/eip712@npm:0.2.4 must be built because it never has been before or the last one failed
➤ YN0007: │ @tharsis/proto@npm:0.1.19 must be built because it never has been before or the last one failed
➤ YN0007: │ @tharsis/eip712@npm:0.2.3 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js@npm:2.6.12 must be built because it never has been before or the last one failed
➤ YN0007: │ bootstrap-vue@npm:2.21.1 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js@npm:3.22.5 must be built because it never has been before or the last one failed
➤ YN0007: │ protobufjs-dbx@npm:7.0.0 must be built because it never has been before or the last one failed
➤ YN0007: │ swiper@npm:6.5.1 [2fb66] must be built because it never has been before or the last one failed
➤ YN0007: │ vue-echarts@npm:6.0.3 [2fb66] must be built because it never has been before or the last one failed
➤ YN0007: │ vue-demi@npm:0.12.5 [293a2] must be built because it never has been before or the last one failed
➤ YN0007: │ secp256k1@npm:3.7.1 must be built because it never has been before or the last one failed
➤ YN0007: │ secp256k1@npm:4.0.3 must be built because it never has been before or the last one failed
➤ YN0007: │ highlight.js@npm:9.18.5 must be built because it never has been before or the last one failed
➤ YN0007: │ yorkie@npm:2.0.0 must be built because it never has been before or the last one failed
➤ YN0007: │ keccak@npm:3.0.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @tharsis/transactions@npm:0.2.5 must be built because it never has been before or the last one failed
➤ YN0007: │ eccrypto@npm:1.1.6 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 1m 1s
➤ YN0000: Done with warnings in 3m 33s

⠦  Building legacy bundle for production...(node:609499) [DEP_WEBPACK_JAVASCRIPT_MODULES_PLUGIN] DeprecationWarning: webpack.JavascriptModulesPlugin has moved to webpack.javascript.JavascriptModulesPlugin
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:609499) [DEP_WEBPACK_LIBRARY_TEMPLATE_PLUGIN] DeprecationWarning: webpack.LibraryTemplatePlugin is deprecated and has been replaced by compilation.outputOptions.library or compilation.addEntry + passing a library option
(node:609499) [DEP_WEBPACK_SINGLE_ENTRY_PLUGIN] DeprecationWarning: SingleEntryPlugin was renamed to EntryPlugin
(node:609499) [DEP_WEBPACK_OPTIONS_DEFAULTER] DeprecationWarning: webpack.WebpackOptionsDefaulter is deprecated and has been replaced by webpack.config.getNormalizedWebpackOptions and webpack.config.applyWebpackOptionsDefaults
(node:609499) [DEP_WEBPACK_AGGRESSIVE_SPLITTING_PLUGIN] DeprecationWarning: AggressiveSplittingPlugin is deprecated in favor of SplitChunksPlugin
(node:609499) [DEP_WEBPACK_COMPILATION_ADDITIONAL_CHUNK_ASSETS] DeprecationWarning: additionalChunkAssets is deprecated (use Compilation.hooks.processAssets instead and use one of Compilation.PROCESS_ASSETS_STAGE_* as stage option)
(node:609499) [DEP_WEBPACK_COMPILATION_AFTER_OPTIMIZE_CHUNK_ASSETS] DeprecationWarning: afterOptimizeChunkAssets is deprecated (use Compilation.hooks.processAssets instead and use one of Compilation.PROCESS_ASSETS_STAGE_* as stage option)
(node:609499) [DEP_WEBPACK_COMPILATION_NORMAL_MODULE_LOADER_HOOK] DeprecationWarning: Compilation.hooks.normalModuleLoader was moved to NormalModule.getCompilationHooks(compilation).loader
(node:609499) [DEP_WEBPACK_COMPILATION_OPTIMIZE_CHUNK_ASSETS] DeprecationWarning: optimizeChunkAssets is deprecated (use Compilation.hooks.processAssets instead and use one of Compilation.PROCESS_ASSETS_STAGE_* as stage option)
(node:609499) [DEP_WEBPACK_CONTEXT_MODULE_FACTORY_ALTERNATIVES] DeprecationWarning: ContextModuleFactory.hooks.alternatives has deprecated in favor of ContextModuleFactory.hooks.alternativeRequests with an additional options argument.
⠋  Building legacy bundle for production...

 ERROR  Failed to compile with 3 errors                                                                                                 7:51:44 AM

 error  in ./src/libs/client/EthereumLedgerSigner.ts

Module parse failed: Unexpected token (29:26)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| }
|
> function toPubkey(keyBytes: Uint8Array): Pubkey {
|   return {
|     type: 'ethermint.crypto.v1.ethsecp256k1.PubKey',

 error  in ./src/libs/client/SigningEthermintClient.ts

Module parse failed: Unexpected token (33:7)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import { defaultMessageAdapter } from './MessageAdapter'
|
> export interface TypedDataField {
|     name: string;
|     type: string;

 error  in ./src/libs/client/SigningKeplrEthermintClient.ts

Module parse failed: Unexpected token (14:10)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|
| export default class SigningKeplerEthermintClient {
>   private signer
|
|   private client

 ERROR  Error: Build failed with errors.
Error: Build failed with errors.
    at /root/sept-fork-explorer-update/node_modules/@vue/cli-service/lib/commands/build/index.js:207:23
    at /root/sept-fork-explorer-update/node_modules/webpack/lib/webpack.js:148:8
    at /root/sept-fork-explorer-update/node_modules/webpack/lib/HookWebpackError.js:68:3
    at Hook.eval [as callAsync] (eval at create (/root/sept-fork-explorer-update/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/root/sept-fork-explorer-update/node_modules/tapable/lib/Hook.js:18:14)
    at Cache.shutdown (/root/sept-fork-explorer-update/node_modules/webpack/lib/Cache.js:150:23)
    at /root/sept-fork-explorer-update/node_modules/webpack/lib/Compiler.js:1225:15
    at Hook.eval [as callAsync] (eval at create (/root/sept-fork-explorer-update/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/root/sept-fork-explorer-update/node_modules/tapable/lib/Hook.js:18:14)
    at Compiler.close (/root/sept-fork-explorer-update/node_modules/webpack/lib/Compiler.js:1218:23)
    at /root/sept-fork-explorer-update/node_modules/webpack/lib/webpack.js:147:16
    at finalCallback (/root/sept-fork-explorer-update/node_modules/webpack/lib/Compiler.js:441:32)
    at /root/sept-fork-explorer-update/node_modules/webpack/lib/Compiler.js:458:13
    at eval (eval at create (/root/sept-fork-explorer-update/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:29:1)
    at done (/root/sept-fork-explorer-update/node_modules/webpack-bundle-analyzer/lib/BundleAnalyzerPlugin.js:80:9)
    at Hook.eval [as callAsync] (eval at create (/root/sept-fork-explorer-update/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:25:1)

Im currently running an older version of ping.pub that I do have working and can currently compile using the nodejs/npm/yarn versions that I have installed.

Is there a specific version of nodejs/npm/yarn that you use/is required?

ki chain tx fees

default tx fee of 800uxki is less than the minimum fee required of 5000uxki

bostrom balances

The balances of $BOOT are off by a factor of 1 million:

image

 cyber q bank balances bostrom1l2ynn9djxrhwr968cwwhugrjugv482ns5pd804
balances:
- amount: "1000000"
  denom: boot
pagination:
  next_key: null
  total: "0"

Let's look at what ping.pub is fetching:

image

{"height":"695395","result":[
  {
    "denom": "boot",
    "amount": "1000000"
  }
]}

I'm guessing that every other asset tends to provide a u<asset> denomination and ping.pub always adjusts by 6 decimals.

build for litespeed

Hello

I built for webserver (yarn && yarn build)
Then i set-up OpenLiteSpeed as webserver.

How should I setup Context/Rewrite rules?
With no setup URIs are server for what they are requested:

if / is called it's okay and I can browse trought the explorer, but if eg. /agoric/ is called a 404 page is returned (cause /agoric/ obv doesn't exist)

So my guess is I should catch every request and redirect to /index.html.
Do you have any pre-built rules to use?

Thanks

desmos mainnet reports no new blocks (since 12/22/2021)

Checked my validator, and blocks are still being produced.

And even /blocks/latest looks like it is also still working:

$ curl -s https://api.mainnet.desmos.network/blocks/latest | jq  .block.header
{
  "version": {
    "block": "11"
  },
  "chain_id": "desmos-mainnet",
  "height": "1566652",
  "time": "2021-12-22T11:17:14.634466845Z",
  "last_block_id": {
    "hash": "84DFF0BD60A0A06FAB8E8C5655AA25EAEFE5DA9253C82B54870181089F1F7186",
    "parts": {
      "total": 1,
      "hash": "2BC0B53EFF774DB6D7AC5BBFD9062F209E116413BD0C4A37A75430A0A62B6FBC"
    }
  },
  "last_commit_hash": "9E502B1CCF4AF6E4BF4E00C53C7DAC36DDA7F8D0244C50417C46DE51997613F2",
  "data_hash": "E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855",
  "validators_hash": "8023116B71FE4D572260C24FACEDCED356B2C52869D2EBB196673B36EF882BD0",
  "next_validators_hash": "8023116B71FE4D572260C24FACEDCED356B2C52869D2EBB196673B36EF882BD0",
  "consensus_hash": "1BF2556CA5D5D7EFFB540F34CB0FFC77A3202E32275557AFBD219882A9E42ACF",
  "app_hash": "C50EE61DF8C223C5D8756418677DB794B6B6EC24D1594110EAA7F0E68E77AB21",
  "last_results_hash": "E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855",
  "evidence_hash": "E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855",
  "proposer_address": "FAC1F8424A4C3807E2CC570C44D41219A15677BA"
}

comdex claiming fails

When trying to claim both commissions and rewards as a validator using ping.pub explorer it fails on Comdex.
(Works fine on other chains)

Withdraw commission (as validator so both commissions and rewards are claimed)
Choose usb ledger
Confirm on ledger

Result is
Error: rpc error: code = InvalidArgument desc = must declare at least one event to search: invalid request
comdexclaim

Please add support of Ethermint based blockchains and types

Hello,
Ethermint has some messages types other than Cosmos, it doesnt allow some default settings transactions to be performed.
For example:
Unsupported type: '/ethermint.types.v1.EthAccount'

As a hints - there are implementations of such:
evmos.me (https://github.com/hanchon-live/evmos.me-frontend, https://github.com/hanchon-live/evmos.me-backend)
explorer.evmos.org/ (which is bdjuno back https://github.com/tharsis/bdjuno and /big-dipper-2.0 base (https://github.com/tharsis/big-dipper-2.0-cosmos)

in above delegation txs are possible => above types included.

This will allow at ping.pub :
New custom ethermint chains
Evmos
genesisL1
crypto.com

Thank you

stuck coins

I can't get my kyve coins back because I don't have tkyve in my hand. Can you help me?

Make default validators sort algorithm randomized

We should consider randomizing validator results in "Staking" tab.
For now, validator sorted by voting power by default. It leads to centralization of networks to top 10 validators.
If we consider doing randomization of results by defaut (you still can sort by voting power when you explicitly want it, via clicking on "Voting power" param), then people who delegate to top 10 will maybe delegate to other validators.
I can make PR, but I need to know thoughts of developers and community about it.

Terra2 LUNA as LUNC

When viewing Terra2 tx fees and tx amounts sent appear as LUNC denom instead of LUNA

display sdk, tendermint, ibc-go versions in the explorer

there are already many useful items displayed in the explorer. however, depending on the target audience of this explorer, it could be useful to query for the sdk, tendermint, and ibc-go versions from the /cosmos/base/tendermint/v1beta1/node_info endpoint so that devs around the interchain can see which versions are deployed on mainnet (and therefore, what cross-version interactions might be happening)

thank you for this contribution to the ecosystem so far!

Incorrect reward amount displayed on all chains

Seems that reward parameter in UI doesn't calculate reward correctly.
It shows too big rewards. Initially thought might be multiplied by 1000, but it seems this is not exactly multiplier of 1000.
Commission has correct value.

image

here is same validator from montscan
image

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.