Description
The backend needs an exact, agreed-upon algorithm (hash function, normalization, optional salt) for turning a WhatsApp phone number into the BytesN<32> this contract expects — otherwise two services could hash the same number differently.
Deliverables
- A section in
docs/INTEGRATION.md specifying the exact hashing approach (e.g. SHA-256 of a normalized E.164 phone number, with or without a salt) so any client computes the same hash for the same number.
Depends on
Write docs/INTEGRATION.md describing how the backend should call this contract over Soroban RPC
Description
The backend needs an exact, agreed-upon algorithm (hash function, normalization, optional salt) for turning a WhatsApp phone number into the
BytesN<32>this contract expects — otherwise two services could hash the same number differently.Deliverables
docs/INTEGRATION.mdspecifying the exact hashing approach (e.g. SHA-256 of a normalized E.164 phone number, with or without a salt) so any client computes the same hash for the same number.Depends on
Write docs/INTEGRATION.md describing how the backend should call this contract over Soroban RPC