pokt-network / explorer Goto Github PK

Create the following data models:

1. Account
2. Block
3. Transaction

https://explorer.testnet.pokt.network/, click ADDITIONAL INFORMATION:

TX NUMBER 0

If this is Number of Transactions then consider rewording, else could remove this field

Implement navigation with the following routes:

1. Home
2. Account Detail
3. Transaction Detail
4. Block Detail

Describe the bug
When i try to run explorer locally, it fails with error Allocation failed - JavaScript heap out of memory

To Reproduce
Steps to reproduce the behavior:

1. Git clone
2. npm i
3. npm run start -- --max_old_size_space=8912

Expected behavior
The explorer should start on localhost:3000

Logs

➜  pocker-explorer git:(develop) 
<--- Last few GCs --->

[109854:0x49cd020]    36138 ms: Mark-sweep 2022.3 (2051.0) -> 2021.3 (2051.0) MB, 1079.7 / 0.0 ms  (average mu = 0.198, current mu = 0.116) allocation failure scavenge might not succeed
[109854:0x49cd020]    37650 ms: Mark-sweep 2022.7 (2051.5) -> 2021.7 (2051.5) MB, 1376.6 / 0.0 ms  (average mu = 0.146, current mu = 0.089) allocation failure scavenge might not succeed


<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0x140e819]
Security context: 0x222e91c808d1 <JSObject>
    1: append [0xeccf744bc21] [/home/tim/workspace/chainstack/pocker-explorer/node_modules/@babel/generator/lib/buffer.js:~61] [pc=0x26749017d3dc](this=0x0042e12c0219 <Buffer map = 0x1f156aba8029>,0x2a94782c6d31 <String[#1]: ,>)
    2: commaSeparator [0xeccf7455b21] [/home/tim/workspace/chainstack/pocker-explorer/node_modules/@babel/generator/lib/printer.js:~499]...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xa1ae50 node::Abort() [node]
 2: 0xa1b25c node::OnFatalError(char const*, char const*) [node]
 3: 0xb9b20e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xb9b589 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xd58815  [node]
 6: 0xd58ea6 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [node]
 7: 0xd65765 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [node]
 8: 0xd66615 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 9: 0xd690cc v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
10: 0xd2faeb v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
11: 0x107221c v8::internal::Runtime_AllocateInOldGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
12: 0x140e819  [node]

Desktop (please complete the following information):

• Node.JS: v12.22.12
• Version [latest develop]

Both the Previous and Next block buttons are not working, they are also in the wrong location in the view (inverted).

When sending a normal TX using the wallet, it was noticed that instead of 0.01, it was costing 0.1.

Currently the Homepage has 2 widgets showing wrong information:

• Total Staked Nodes
• Total Staked

message | "Relay attempts exhausted"

The portal API is failing with both the network and the altruists on this query. Something probably changed between pocket-core versions and the response.

https://mainnet.gateway.pokt.network/v1/lb/60a2ac11b1747c6552385c61/v1/query/nodes

Integrate the datasource in the following screens:

1. Home and Search
2. Account Detail
3. Transaction Detail
4. Block Detail

Tx fee of 0.01 POKT should be visible when viewing the details of a tx

This issue was automatically created by Allstar.

Security Policy Violation
Security policy not enabled.
A SECURITY.md file can give users information about what constitutes a vulnerability and how to report one securely so that information about a bug is not publicly visible. Examples of secure reporting methods include using an issue tracker with private issue support, or encrypted email with a published key.

To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/pokt-foundation/explorer/security/policy to enable.

For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository.

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

When clicking on the "next block" button, the previous block is showed; and viceversa.

Also, when clicking on "previous block", nothing happens.

Evidence:
https://www.loom.com/share/f245f2cb898640488222f76ddb5512f3

and params

Basically, we can link the claims to their respective Proofs in the transactions that have the message type Proof. This would in turn require us to query the claims relative to a proof in the transaction page where a transaction has a message of type Proof.

Closes #8

Change dispatcher list to new PNF nodes:

mainnet-1.nodes.pokt.network to mainnet-24

Seems like this isn't querying the amount of staked POKT correctly

On https://explorer.testnet.pokt.network/ under the total staked field

Initial project setup + initial components + Search component

Closes #4

https://explorer.testnet.pokt.network/ is using mainnet

After having implemented the QoS over the gateway feature, we were stuck using the mainnet endpoint through the gateway because there was no app staked for testnet.

Make sure to use a testnet endpoint for testnet deployments

Block time should be set to 15 mins for testnet

Create a generic interface to be able to retrieve data from the selected network. The following methods should be contained:

getHeight()
getAccount(id)
getTransaction(id)
getBlock(id)
getLatestBlocks(count)
getLatestTransactions(count)

Closes #6

Explorer testnet:

Come and help us grow the POKT community alongside the protocol. Join our social media cannels.
cannels should be channels

FAQ// DEV PORTAL should be FAQ / Dev Portal

Road Map? should be Road Map

remove:
iOS SDK
Android SDK

Hook up footer links where obvious