<feed xmlns='http://www.w3.org/2005/Atom'>
<title>digiid-ts/examples/verify-callback.ts, branch v2.0.4</title>
<subtitle>[MIRROR] A modern TypeScript implementation of the Digi-ID authentication protocol</subtitle>
<id>https://git.zelu.dev/digiid-ts/atom?h=v2.0.4</id>
<link rel='self' href='https://git.zelu.dev/digiid-ts/atom?h=v2.0.4'/>
<link rel='alternate' type='text/html' href='https://git.zelu.dev/digiid-ts/'/>
<updated>2025-04-14T08:30:43Z</updated>
<entry>
<title>fix: Correct Bech32 address verification via dependency change</title>
<updated>2025-04-14T08:30:43Z</updated>
<author>
<name>Pawel Zelawski</name>
<email>pawel.zelawski@outlook.com</email>
</author>
<published>2025-04-14T08:30:43Z</published>
<link rel='alternate' type='text/html' href='https://git.zelu.dev/digiid-ts/commit/?id=b354d96163e2ba2103f7d8b101dae547eb4747fa'/>
<id>urn:sha1:b354d96163e2ba2103f7d8b101dae547eb4747fa</id>
<content type='text'>
- Replaced faulty 'digibyte-message' dependency with 'bitcoinjs-message'.
- This resolves a critical bug where signatures from DigiByte Bech32 addresses (dgb1...) could not be verified due to issues in the old dependency chain.
- digiid-ts now correctly handles Legacy (D...), SegWit (S...), and Bech32 (dgb1...) address signature verification.
- Updated build configurations and addressed related linting issues revealed during testing.
</content>
</entry>
<entry>
<title>docs: update terminology in documentation</title>
<updated>2025-04-10T14:11:37Z</updated>
<author>
<name>Pawel Zelawski</name>
<email>pawel.zelawski@outlook.com</email>
</author>
<published>2025-04-10T14:11:37Z</published>
<link rel='alternate' type='text/html' href='https://git.zelu.dev/digiid-ts/commit/?id=0eacb0babaf1d0aca9771662bcba6aef3f795eaa'/>
<id>urn:sha1:0eacb0babaf1d0aca9771662bcba6aef3f795eaa</id>
<content type='text'>
- Update documentation to use "Digi-ID" instead of "DigiID" in user-facing text
- Maintain internal code using 'DigiID' for consistency with original implementation

The changes improve documentation clarity while maintaining full functionality.
</content>
</entry>
</feed>
