Implement ZapsRegistry contract for ID-based address and merchant resolution - #28
Merged
Conversation
ONEONUORA
approved these changes
Jan 23, 2026
ONEONUORA
left a comment
ONEONUORA
left a comment
Contributor
There was a problem hiding this comment.
Nice implementation @Akshola00
Contributor
|
Fix merge conflicts, please @Akshola00 |
Contributor
Author
|
done
|
anonfedora
approved these changes
Jan 25, 2026
anonfedora
left a comment
anonfedora
left a comment
Contributor
There was a problem hiding this comment.
lgtm 🚀... Merging now
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the ZapsRegistry Soroban contract to map human-readable user and merchant IDs to Stellar addresses and settlement metadata. This contract replaces raw address usage with deterministic ID resolution, enforces strict access control, emits auditable events, and prevents spoofing or unauthorized updates. It serves as the canonical registry for user wallets and merchant payment routing while supporting merchant upgradeability and immutable audit guarantees.
closes #10