Private sets is a self-serve feature designed to enable organizations to curate a set of validators, each marked with a unique tag. This tag, carrying an identifier specific to your organization, ensures that only you can view the performance and rewards metrics for it. Displayed within your console, these tags streamline analysis processes and let you perform A/B testing on your node setup or group together validators for a specific customer confidentially.
Getting Started
Build and Growth API users can create private sets. Build tier comes with max 4 sets while Growth comes with 20.
Step 1: Creating a Tag and associating validators to it
To call a set's effectiveness, you must first create a tag which acts as a unique identifier for the set.
Using the id that you get in the response above, call the following endpoint to associate validators with the tag
POST/v1/tags/{id}/validators
Body parameters (Required)
Response
{"tag":"string","pubkeysAdded": integer}
Once you have a tag with validator mappings, you can move to Step 2.
To add more validators to a tag, call POST/v1/tags/{id}/validators with the new keys you'd like to add. Similarly, to remove a pubkey from an existing tag, callDELETE/v1/tags/{id}/validators/{pubkey}.
NOTE: Removing keys from a tag doesn't erase their impact on historical performance ie performance of a removed pubkey continues to impact the all-time performance of a set.
Step 2: Calling the performance and rewards endpoints for your set
Using the tag's ID, call the sets endpoints to retrieve performance and rewards metrics. These endpoints operate similar to the /operators/ endpoints with similar granularities and refresh windows.
