mint_token lacks encryption/auth and is forgeable

Hi team,

I noticed that the current *mint_token* implementation is unencrypted and unauthenticated. This makes the tokens easily forgeable by attackers and exposes client IPs in plaintext.

Due to these security risks, this feature essentially cannot be enabled in real-world production environments (such as Cloudflare's own live websites).

Could you share your considerations regarding this design? Are there plans to provide a secure, production-ready implementation in the future?

Thanks!

Start by reviewing the mint_token implementation and its token format, focusing on the lack of encryption and authentication and the plaintext client IP exposure described here. The issue does not identify files, tests, or a concrete protocol design; a maintainer decision on the secure production-ready requirements is needed before implementation can be considered done.

Written by the indexing model from the issue text.