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
Snapshot bug when changing the sla hystersis network parameter in a batch proposal
*** 424108,424130 **** } }, { "liquidityV2Performances": { "marketId": "de0f57d1ec1e5f7868cc47bcab0aabf896a376e9db1c8bec83d00fda3cd53bd8", "epochStartTime": "1708699245118900603", "performancePerParty": [ { "party": "9b543291a59aaee800300ab0eb55455d5c84b4d0e9ed0f05e6e5bf6dea805690", "commitmentStartTime": "1708699245118900603", - "registeredPenaltiesPerEpoch": [ - "0" - ], "lastEpochFractionOfTimeOnBook": "1", "lastEpochFeePenalty": "0", "lastEpochBondPenalty": "0", "requiredLiquidity": "150000000000", "notionalVolumeBuys": "180668775000", "notionalVolumeSells": "179339920000" } ] } }, --- 424096,424115 ----
.
develop
No response
The text was updated successfully, but these errors were encountered:
karlem
gordsport
Successfully merging a pull request may close this issue.
Problem encountered
Snapshot bug when changing the sla hystersis network parameter in a batch proposal
Observed behaviour
.
Expected behaviour
.
Steps to reproduce
.
Software version
develop
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: