Sometimes, different records have the same field values. We encountered this in #318 where separate EconomicResources might be created by associated EconomicEvents but end up with the same EntryHash, causing uniqueness problems that can affect indexing and other relationships between different bits of data.
To work around this, we should insert some random bytes into an internal storage field upon creating new records, and persist the same value between updates. These values should not be returned in any response data- they are purely for internal use.
This will apply to all record types except ProposedIntent and ProposedTo, which are idempotent entries in that they merely hold values to associate other record types.
Sometimes, different records have the same field values. We encountered this in #318 where separate
EconomicResourcesmight be created by associatedEconomicEventsbut end up with the sameEntryHash, causing uniqueness problems that can affect indexing and other relationships between different bits of data.To work around this, we should insert some random bytes into an internal storage field upon creating new records, and persist the same value between updates. These values should not be returned in any response data- they are purely for internal use.
This will apply to all record types except
ProposedIntentandProposedTo, which are idempotent entries in that they merely hold values to associate other record types.