[Contracts] Add Notification Template Registry

[Abd-Standard]

Description

Introduce an on-chain registry for reusable notification templates. This allows senders to reference predefined templates instead of repeatedly storing identical notification structures.

Tasks
Create template registration functions.
Allow template updates where appropriate.
Emit template registration events.
Validate template existence before use.
Add comprehensive unit tests.

Acceptance Criteria
Templates can be registered successfully.
Invalid template references are rejected.
Events are emitted for template actions.
Tests cover registration and retrieval.

Contributors start work by running:
git checkout -b contracts/template-registry

[Emmanuellsensai]

hi maintainer, i would like to work on this issue

[mrnetwork0001]

I am highly interested in implementing the notification template registry to optimize state usage and prevent redundant data storage.

My background includes writing clean, tested smart contracts, handling template updates securely, and validating references on-chain.

I can begin right away and deliver a thoroughly verified, gas-efficient registry module.

[GBOYEE]

For the notification template registry (#352), I'll add a NotificationTemplateRegistry contract module with:

1. create_template(id, name, template_data) — stores reusable notification structure
2. get_template(id) — retrieves template for reference
3. use_template(notification_id, template_id) — links a notification to a template

Storage pattern follows existing Soroban conventions with DataKey::Templates map. Will include tests for template CRUD and template-linked notification creation. Ready on assignment.

[DjSantech]

Hi! I'm a junior developer with experience in JavaScript, React, Node.js, and Git. I'd like to work on this issue. I'll review the codebase, implement the notification template registration following the project's conventions, test the changes, and submit a clean PR.

[MztaKing]

Dear Team, I will appreciate the opportunity to work on this issue.
Kind Regards

[LuisD-Dev]

Hi, I’d like to work on this issue. I’ve reviewed the description and I believe I can handle the implementation.

Could you please assign it to me? Once it is assigned, I’ll start working on it and submit a pull request with the corresponding changes.

Thank you!

[somotochukwu-dev]

Good day maintainer, please I would like to work on this issue. I will implement the on-chain notification template registry by adding template registration and update functions, validating template references before use, emitting the required events, and writing comprehensive unit tests to cover registration and retrieval. Please I can deliver good clean code please assign this issue to me thank you.

[Purity-Euphemia]

Good Day Maintainer, I have experience and would review the issue, implement a clean solution, test it, and submit a pull request.

[Purity-Euphemia]

Good Day Maintainer, I have experience and would review the issue, implement a clean solution, test it, and submit a pull request.

[maxitalk88-ship-it]

Good Day Maintainer,
I've already built out a working solution for this: a TemplateRegistry.sol contract with registration, owner-gated updates, soft-delete deactivation/reactivation, and an ownership-transfer path, plus a useTemplate() entry point that reverts on missing/inactive templates so consumers can't silently reference bad data. All actions emit events (TemplateRegistered, TemplateUpdated, TemplateDeactivated, TemplateUsed, etc.) for indexers. I've also written a full Foundry test suite covering registration, duplicate/empty-content rejection, update authorization, activation state transitions, and fuzz tests for arbitrary template IDs. I can open a PR against contracts/template-registry within the day.

[CryptoDof]

Hi team,
​I’d love to grab this one. Optimizing on-chain storage is super important, and letting senders reference predefined templates instead of duplicating data every time is a great approach. I've got solid experience building out smart contract architectures in the Web3 space, so setting up this registry is right in my wheelhouse.
​Here’s my plan of attack to get it done:
​Build the registry: I'll write the smart contract functions to handle template registration and allow updates where it makes sense.
​Event emissions: I'll make sure all template actions emit the right events so off-chain services can track them easily.
​Strict validation: I'll put checks in place to automatically reject any transactions trying to reference invalid or non-existent templates.
​Testing: I'll write comprehensive unit tests covering the whole lifecycleregistration, retrieval, and edge casesto ensure everything is bulletproof.
​I'm ready to run git checkout -b contracts/template-registry and start building. Let me know if you're good to assign this to me!
​Cheers,

[VictorEzenma]

Hi! I would love to take on this issue and implement the Notification Template Registry.

I have experience writing secure, optimized smart contracts (Solidity) and writing tests using Foundry. My approach to implementing this registry would be:

1. Contract Design: Design a robust registry contract with an efficient data structure (e.g., using mappings and structs) to store, update, and retrieve notification templates securely.
2. Access Control: Implement proper ownership/access control patterns (like OpenZeppelin's Ownable or custom roles) so only authorized addresses can register or modify templates.
3. Testing: Write comprehensive unit and integration tests in Foundry to ensure 100% test coverage for registration, retrieval, and failure states.

If assigned, I can get to work on this immediately and submit a clean, well-tested PR within 3 to 4 days.