How to get that trusted validator hash?

[ethanfrey]

What are best practices for out-of-bound verification?

It would be good to add documentation here? Maybe some tools/mneumonics?

At least a way to calculate the validator hash from the genesis block when bootstrapping. And easily list the current validator hash/height I trust to share with a friend.

Comments on how to make this more user-friendly are most welcome.

[ethanfrey]

I'm guessing we will want some gpg signed key (or binary seed), we can check and download

[adrianbrink]

I think a good way could be to have the core dev's all sign the initially trusted validator set. Also I think we should write extensive documentation about how we arrived at the initial validator set and how people can compute the hash for themselves.

[ethanfrey]

For now, I think I will add a --genesis flag that takes a genesis file and populates chain-id and valhash from those computer values.

Thus, if you know you have the proper genesis file, you can safely attach to a network (at least until the first unbonding period has passed).

[ethanfrey]

There is also already a --seed flag you can use to accept a seed file from a trusted source, which is the block header, signatures, and validator set at any point in time. Assuming you trust the source.

[ethanfrey]

Resolved with #36