#3: Cryptographic verification

[azazellj]

Description

Cryptographic verification.

Related Issue

Closes #

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test addition or update

Platform Support

• Android
• iOS
• Both platforms

Testing

• Unit tests pass
• Integration tests pass
• Manual testing completed
• Cross-platform compatibility verified
• Performance benchmarks updated (if applicable)
• API compatibility checked

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have updated the version number if needed
• I have checked for any breaking changes

Breaking Changes

• changed JWT parsing & decoding mechanism

Migration Guide

• JWT.parse -> JWT.decode

Performance Impact

• going to be measured with benchmark

Additional Notes

Screenshots (if applicable)

Checklist for Breaking Changes

• Breaking change is clearly documented
• Migration guide is provided
• Version number is incremented appropriately
• Deprecation warnings are added for old APIs
• Backward compatibility is maintained where possible