We offer two types of test vectors:
-
Tiny: designed for quick adjustments and prototyping, with reduced
- validators count: 6
- cores count: 2
- epoch period: 12
- core assignment rotation period: 4
- ticket attempts: 3
-
Full: vectors with production specs
- validators count: 1023
- cores count: 341
- epoch period: 600
- core assignment rotation period: 10
- ticket attempts: 2
For more information refer to the community docs.
Technically, the STF execution process does not inherently produce auxiliary outputs beyond the success or failure result. In this context, we propose an extension to include additional information that may be beneficial for implementors or useful for executing other subsystems reliant on values generated post-STF execution.
When the error or success values are not pertinent to your test vector processing procedures, you may disregard them as necessary.
A mapping of error code semantics is provided within the ASN.1 schema for each specific subsystem.
- Fallback: fallback block authoring, no-safrole, no-work-reports
- Safrole: safrole block authoring, no-work-reports
- Work Reports L0: basic work reports, no-safrole
Validation scripts are included to verify the JSON files against the expected ASN.1 syntax provided with the test vectors. These scripts currently rely on my asn1tools fork.