Module: Metadata Registry (URI & Hash Storage)

[memplethee-lab]

Create a Metadata Registry module to manage on-chain metadata for contracts, modules, and entities.

Direction:

• Provide a registry that maps identifiers to metadata URIs and supports updatable entries with access control.
• Support verifiable on-chain hashes and optional immutability flags.
• Offer read-helpers for common metadata consumption patterns.

Acceptance criteria:

• Metadata Registry contract added with create/update/get functions and appropriate access controls.
• Metadata entries can include on-chain hash verification and URI storage.
• Tests cover lifecycle, immutability flag behavior, and access restrictions.
• Documentation shows examples for registering contract metadata and using off-chain resolvers.

[midenotch]

Hi Maintainer,
Interested in working on this issue. I'll implement the requested changes and ensure everything is properly tested before submission.

Payout wallet (Stellar): GBLT6QSRPF7YGSCOWEOGBXKS2DRKOPBLF6QHJAD6QCNCWWQ54E2NJ4AB
GrantFox OSS campaign — smart escrow payout on merge.

[Jaamaldeen]

Let me do this:

Approach:

Contract Design: Define MetadataRegistry with entries: Map<identifier, Entry> where Entry { uri, hash, immutable, owner, createdAt, updatedAt }. Use Bytes32 or String identifiers. Emit events for create/update.

Core Functions:

create(identifier, uri, hash, immutable): Store entry, set owner to caller. Require identifier unused.

update(identifier, newUri, newHash): Only callable by owner if immutable == false. Update timestamp.

get(identifier): Return full entry. Optional resolve helper returns (uri, hash).

Access control via owner field or role-based modifiers.

Verification: Store keccak256(metadata) hash alongside URI. Consumers can fetch off-chain data and verify against on-chain hash—ensuring integrity without storing full blob.

Immutability: If immutable == true, reject update() after creation. Useful for permanent records (audit logs, core specs).

Read Helpers: Add getAllByOwner(owner), exists(identifier), getHash(identifier) for common patterns.

Testing:

Create entry → retrieve → verify fields.
Update by owner (immutable = false).
Update rejected for non-owner or immutable entries.
Hash verification (off-chain + on-chain match).
Access control failure scenarios.
Documentation: Include examples for registering contract metadata (ABIs, source verification) and off-chain resolvers (IPFS, HTTPS, Arweave).

Gas-optimized storage using Vec or maps, with benchmarks included.

[grantfox-oss]

🦊 GrantFox — @Jaamaldeen has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #43)
2. Your PR will be reviewed by the SourceXXL maintainers

Good luck! Track your progress on GrantFox.