The Office of Inspector General (OIG) is a neutral third-party role designed to evaluate WAX Guild Candidates' contribution to the ecosystem and provide ongoing transparency for the community. The office is designed as a committee with 3 inspector generals who will standardize WAX Guild evaluations, and properly recognise those WAX Guilds making valuable contributions to the WAX ecosystem.

Guilds that failed the previous evaluation and don't submit an update will not be reviewed, marked as Failed Core and moved to Retired Guilds table.

Green text represents additions / modifications.

~~Red text with strikethrough represents removals.~~

Orange text represents proposed changes that have not reached consensus yet.

Major Changes 4.5 - 2022 (October 2022)

Technical Requirements

We are announcing a restructuring of tech-ops criteria when scoring history solutions. See the following table for an overview of points.

TX history APIs eligible for points:

solution	criteria	points
v1 native	Nodeos Chain API	0
hyperion-partial	(chain + v1 + v2) & partial history available	up to 2
hyperion-full	(chain + v1 + v2) & full history available	+2
dfuse	dfuse	3

Scoring of history solutions happens based on the following criteria:

Guilds can only score points in this category for ONE history solution. (e.g. hyperion OR dfuse) Additional APIs (e.g. Light API) can be scored under the category ‘useful APIs’), if usage metrics are provided and support a scoring.
Partial Hyperion history needs to cover at least the last 6 weeks of data. [≥95% uptime 2p, 95%→70% 1p]
Full history bonus is only granted on high availability. [≥95% uptime 4p, 95%→70% 1p]
Guilds are responsible to ensure their history solutions uptime and performance is successfully tracked by the majority of monitoring systems (https://tools.ledgerwise.io/, https://wax.validationcore.io/stats/guild, https://oig.sentnl.io/, https://wax.stats.eosusa.news/). Failing to do so can result in a loss of points. This means guilds need to ensure their bp.json is available and updated and their rate limits are tolerant enough to allow the fulfilment of all checks. If tracking fails and the situation can not be resolved in a timely manner Guilds should provide an explanation and the measures taken with their next report.

Hyperion features needed to apply scoring for hyperion based solutions:

index_transfer_memo: true