This week we released an update to the Staking Data API that affects users looking to query Staking Provider data.
The update includes the addition of the isApproved field, which signifies a staking provider has passed a preliminary checking process by the Staking Rewards team, but not yet part of our Verified Staking Provider program.
We have also depreciated some unused fields and relations in GraphQL connected to the provider endpoint, and removed the following from the order and where entities, as listed below:
where:
order:
Verified Staking Provider (vsp) fields in the Staking Data API are now maintained in the vsp metric with the following variation format.
{
"verificationScore": {
"ls": {
"bizOpsScore": null,
"operatorSetScore": null,
"pro": false,
"securitySetUpScore": null,
"totalScore": null,
"verified": false,
"verifiedSince": ""
},
"pos": {
"bizOpsScore": 100,
"pro": false,
"reliabilityScore": 100,
"securitySetUpScore": 100,
"totalScore": 100,
"verified": true,
"verifiedSince": "2024-04-01T00:00:00.000"
},
"valueAdded": {
"score": 100,
"text": [
{
"description": "They do great things.",
"link": "href=\\\"https://great.things\\",
"title": "Great Things"
}
]
}
}
}Join 12,000 institutional allocators worldwide. No spam, unsubscribe anytime.
