Create endpoint that receives a schema of verifiable randomness

[azixus]

Is there a use case for me wanting an 8 bit unsigned, and an 8 bit signed in the same request?

It seems that batching supports getting an arbitrary number of the same type, but perhaps that's not the most common use case?

Consider an alternative where we could ask for arbitrary quantities of different types in the same request.

In this fantasy land, I might make a request where I specify my requirements in json:

{
  "api": "v1",
  "seed": "xyz",
  "request": [
    {
      "type": "uint8",
      "count": 5
    },
    {
      "type": "int16",
      "count": 2
    },
    ...
  ]
}

And receive a response like:

{
  "results": [
    {
      "type": "uint8",
      "data": [1,2,3,4,5]
    },
    {
      "type": "int16",
      "data": [6,7]
    },
    ...
  ]
}

If that's a reasonable use case, it might reduce our traffic, and therefore our firewall work + egressed data somewhat

Originally posted by @GlacierWalrus in #2 (comment)

[azixus]

This is actually very similar to an idea I had a while back. We could have some sort of specification for a "schema of verifiable randomness".

Essentially, this would be a user-readable file that describes how the randomness is derived from the randomness beacon.

By sending this file to the server, the server could output something to the like of a "certificate of verifiable randomness" that includes the round, the signature and all the information necessary to independently verify that the random values were fairly derived.