docs: add a short glossary of ZK/Stellar terms for new contributors

[tech-adrian]

Area
repo root or docs/

Problem
DESIGN.md and README.md use terms like nullifier, commitment, Merkle root, UltraHonk, keccak transform, and Poseidon2 throughout, assuming ZK familiarity. This raises the bar for new contributors who understand Stellar/Soroban but not zero-knowledge cryptography, or vice versa.

Proposed change
Add a short GLOSSARY.md defining the ~15 most-used domain terms in the codebase in one or two plain-English sentences each, linked from README/CONTRIBUTING.

Acceptance Criteria

• GLOSSARY.md covers the core terms used across README/DESIGN.md (nullifier, commitment, Merkle root, recipient binding, UltraHonk, Poseidon2, selective disclosure, relayer, etc.)
• Linked from README.md and/or CONTRIBUTING.md
• Relevant tests (just test, pnpm test, cargo test, or nargo test as applicable) pass locally and in CI
• A screenshot or short screen recording is attached to the PR showing the change working (the rendered glossary) — required before this can be merged.

Open your PR against the dev branch, not main. All active development merges into dev.

Discuss this issue / coordinate work: join the DShield contributor Telegram group: https://t.me/+SiGHH24No9U2MDJk

[yusufmuhammadayodeji-netizen]

Hello, this issue aligns well with my skill set and I’m confident I can resolve it properly. Please assign it to me.

[Lspnjr1]

Hello maintainers,

I’d like to take on this issue. I’ve gone through the issue details and believe I can implement the required changes effectively. I’ll ensure the solution is properly tested, follows the project’s conventions, and submit a pull request as soon as it’s ready.

Please assign this issue to me if it’s available. Thank you!

[Lspnjr1]

Hello maintainers,

I’d like to take on this issue. I’ve gone through the issue details and believe I can implement the required changes effectively. I’ll ensure the solution is properly tested, follows the project’s conventions, and submit a pull request as soon as it’s ready.

Please assign this issue to me if it’s available. Thank you!

[Lspnjr1]

Hello maintainers,

I’d like to take on this issue. I’ve gone through the issue details and believe I can implement the required changes effectively. I’ll ensure the solution is properly tested, follows the project’s conventions, and submit a pull request as soon as it’s ready.

Please assign this issue to me if it’s available. Thank you!

[ShantelPeters]

Hi! I’d like to work on this issue. I have experience writing and improving technical documentation for developer-focused projects. I’ll review the existing README and DESIGN docs, identify the most commonly used ZK/Stellar terms, and create a concise GLOSSARY.md with clear, beginner-friendly definitions. I’ll also link the glossary from the README and CONTRIBUTING documentation to make onboarding easier for new contributors. I can submit a well-organized PR within 1–2 days.

[grantfox-oss]

🦊 GrantFox — @ShantelPeters has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@ShantelPeters's PR #50 was approved and merged by @tech-adrian.

🏆 @ShantelPeters: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (83 total points). Track your full progress on GrantFox.

👏 Great work, @ShantelPeters! Keep contributing to Dshield-xyz.