1995 offchain voting json

[Cmdv]

This PR implements graceful handling of off-chain voting anchor metadata based on parsing success.
fixes #1995
When the anchor hash matches, data is stored with an is_valid flag indicating:

• TRUE: Valid JSON conforming to CIP-100 → all related tables populated
• FALSE: Valid JSON not conforming to CIP-100 → JSON stored, related tables empty
• NULL: Invalid JSON → error message in json column, raw bytes preserved

Hash mismatches continue to go to the error table for retry. Tests and documentation updated accordingly.

[kderme]

Just a small code reduction

[rdlrt]

• FALSE: Valid JSON not conforming to CIP-100 → JSON stored, related tables empty

Wasnt the issue about storing data if hash matches regardless of whether it conforms to a standard or not (as there will be multiple standards) leaving conformance to consumers?

This does not sound like it is exactly addressing the request

[kderme]

• FALSE: Valid JSON not conforming to CIP-100 → JSON stored, related tables empty

Wasnt the issue about storing data if hash matches regardless of whether it conforms to a standard or not (as there will be multiple standards) leaving conformance to consumers?

This does not sound like it is exactly addressing the request

Note that we already store bytes in off_chain_vote_data.bytes for metadata. You can get the original text using

select convert_from(bytes, 'utf-8') from off_chain_vote_data limit 1;

After this pr this is always included as long as the bytes hash match the expected (and the http header is reasonable)

[rdlrt]

• FALSE: Valid JSON not conforming to CIP-100 → JSON stored, related tables empty

Wasnt the issue about storing data if hash matches regardless of whether it conforms to a standard or not (as there will be multiple standards) leaving conformance to consumers?
This does not sound like it is exactly addressing the request

Note that we already store bytes in off_chain_vote_data.bytes for metadata. You can get the original text using

select convert_from(bytes, 'utf-8') from off_chain_vote_data limit 1;

After this pr this is always included as long as the bytes hash match the expected (and the http header is reasonable)

It is only stored if metadata returned is considered valid/parsable (atleast before), glad if that's changing now

[kderme]

After this pr this is always included as long as the bytes hash match the expected (and the http header is reasonable)

It is only stored if metadata returned is considered valid/parsable (atleast before), glad if that's changing now

This changes with this pr. The offchain and the byte will exist even if the json parsing fails. A separate field will annotate that parsing failed