SECURITY: Use content checksum to send future objects and receive results #3

Currently, the future UUID is used as the identifier sent to workers. To lower the risk for man-in-the-middle attacks, I think it's better to use a content checksum for the identifier instead. That way the receiving end can validate that the object received is indeed the intended object. For context, the identifier is communicated via the message board.