이준범
We will use a [heimdall](https://github.com/it-chain/heimdall). We plan to use the functions of heimdall to generate private and public keys and to generate id based keys.
And add test cases for this
We will use viper as config library! same as it-chain!
Count me in — I’d love to help with the v2 implementation. I have been working on https://github.com/coinbase/x402/pull/454, https://github.com/coinbase/x402/issues/439
🚀 Proposal: exact+jwt-access[draft] Idea (1-liner): After an exact on-chain payment finalizes, the server issues a short-lived JWT. The token includes req = keccak256(canonicalized PaymentRequirements), so verification is stateless: recompute requirements...
An additional suggestion: In the current draft we only embed the hash of the canonicalized PaymentRequirements (req). One concern is that this by itself represents requirements but not the fact...
@notorious-d-e-v Thank you for referring this issue. I want to move on this part. I would appreciate if you could guide me where and how to start?!