Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Block Explorer API: PoW is always null in stagnet #9954

Closed
edd opened this issue Nov 1, 2023 · 1 comment
Closed

[Bug]: Block Explorer API: PoW is always null in stagnet #9954

edd opened this issue Nov 1, 2023 · 1 comment
Assignees
Labels

Comments

@edd
Copy link
Contributor

edd commented Nov 1, 2023

Problem encountered

For all of the transactions below, the PoW field is present, but null:
https://be.stagnet1.vega.rocks/rest/transactions?limit=25

However in mainnet, it is populated:
https://be.vega.community/rest/transactions?limit=1

Is this correct? Or a bug?

It's possible that POW is not required in stagnet, in which case, this can just be closed.

Observed behaviour

POW field is always null, in stagnet. BE is running the same version in both networks

Expected behaviour

POW is populated.

Steps to reproduce

Use the URLs above

Software version

0.73.1

Failing test

No response

Jenkins run

No response

Configuration used

No response

Relevant log output

No response

@edd
Copy link
Contributor Author

edd commented Nov 2, 2023

This is no longer true. Either they were TXs that do not require POW, or I was mistaken.

@edd edd closed this as completed Nov 2, 2023
@github-project-automation github-project-automation bot moved this to Merged in Core Kanban Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

2 participants