Documentation: randomness-agent

[web3-nomad]

is it possible to show an example configuration for the committee.toml file that is required to pass in on runtime
and ideally a simple README on how to get this started?

Thanks in advance

[CluEleSsUK]

Hello there! Your best bet is to run a distributed key generation as per the README in the adkg-cli.
There are a few runbooks available in the dcipher ceremonies repo too, as well as sample inputs and outputs from real ceremonies (not including the secret key material ofc!!).

Happy to help you if you get stuck, and I'd love to know what you're building so we can help support you!

[web3-nomad]

Thanks.. I'll check out the ceremonies repo.

as for what i'm building.. it's going to be a card game initially. (simple one to demonstrate VRF at first, then a more complex variant using some kind of conditional/time lock encryption to keep the deck/cards private.

It's just a toy app for my own enjoyment for now.

[web3-nomad]

Hi @CluEleSsUK.
I spoke too soon. for the randomness one I am trying to call it via

../target/release/examples/randomness \
  --chain-id 296 \
  --committee-config committee.toml \
  --rpc-url https://testnet.hashio.io/api \
  --tx-private-key $PRIV_KEY \
  --signature-sender-addr $ADDRESS \
  --randomness-sender-addr $ADDRESS

the contents of the committee.toml are a mystery still.
I have the following

member_id=1
secret_key="xxxx"
n=1
signing_threshold=1
adkg_public="xxx"
adkg_secret="xxx"
[group]
n=1
t=1
t_reconstruction = 4
start_time = "2025-07-24T16:25:30Z"

[[nodes]]
member_id=1
address="/ip4/127.0.0.1/9991"
bls_pk="6xxxxx4="
peer_id="12D3xxxxxgQ"

I tried the group/final group toml files you pointed too with no joy either