[Medium] Implement credential revocation logic

[Josie123-Dev]

Task Description

Add credential revocation logic to contracts:

• Revoke credentials
• Update revocation status
• Maintain revocation list
• Check revocation status
• Emit revocation events

Requirements

• Revocation function
• Status update
• List maintenance
• Status check
• Event emission

Acceptance Criteria

• Revocation works
• Status is updated
• List is maintained
• Check works
• Events are emitted

[meshackyaro]

Hi,

I came across this issue and would love to implement the credential revocation system. Providing a secure, gas-efficient way to revoke, track, and check the status of credentials—complete with real-time event logging—is an essential requirement for cryptographic trust architectures.

I have solid experience writing smart contracts (specifically focusing on state optimization and secure administrative access controls). I am highly familiar with:

Implementing identity/credential registry structures.

Building zero-cost lookup states using persistent mappings.

Developing robust event emission patterns for off-chain indexing services.

State Organization: Define a structured layout using an optimized registry mapping (e.g., matching a cryptographic credential_id or hash to a deterministic status struct or boolean flag).

Access Control & Revocation: Build the core revoke_credential function, ensuring it includes proper validation (e.g., checking if the caller is the original issuer) and handles status updates atomically.

Status Check Engine: Provide a gas-optimized, read-only validation hook allowing internal codebases and external integrators to verify live statuses dynamically.

Event Logging: Integrate structural event emissions containing relevant context keys (credential_id, issuer, timestamp) to facilitate straightforward downstream indexing.

Please assign this issue to me, and I’ll get started on drafting the implementation

[grantfox-oss]

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

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #91)
2. Your PR will be reviewed by the GuardZero144 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 campaign!

@meshackyaro's PR #110 was approved and merged by @Josie123-Dev.

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

👏 Great work, @meshackyaro! Keep contributing to GuardZero144.