Consistent reference to content hash in data module #1006
Labels
Scope: x/data
Issues that update the x/data module
Type: Refactor
A code change that neither fixes a bug nor adds a feature
Milestone
Summary
When anchoring and attesting to data, the messages require
Hash
andHashes
as an input. When registering data to a resolver, the message requiresData
. Each field represents one or more content hashes. A content hash also includes aHash
field. We should use consistent and more descriptive field names.Problem Definition
Inconsistent use of field names in the data module when referring to a content hash.
Proposal
Update
hash
tocontent_hash
,hashes
tocontent_hashes
, anddata
tocontent_hashes
.For Admin Use
The text was updated successfully, but these errors were encountered: