We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
null
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.
POW field is always null, in stagnet. BE is running the same version in both networks
POW is populated.
Use the URLs above
0.73.1
No response
The text was updated successfully, but these errors were encountered:
This is no longer true. Either they were TXs that do not require POW, or I was mistaken.
Sorry, something went wrong.
gordsport
No branches or pull requests
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 networksExpected behaviour
POW is populated.
Steps to reproduce
Software version
0.73.1
Failing test
No response
Jenkins run
No response
Configuration used
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: