## Title Lack of Flexibility in Payment Tokens for Registration Costs

[hats-bug-reporter[bot]]

Github username: @0xmahdirostami Twitter username: 0xmahdirostami Submission hash (on-chain): 0x391c0468be449c6921a7586f7d7d9052037ba27074fe637ad3c3712aa543951b Severity: low

Description:

Vulnerability Detail

The current implementation of the contract restricts inviters or mitigators to pay the registration cost with wrap tokens or any other circle tokens. The contract doesn't provide an option to pay with other Circle tokens or wrapped Circle tokens, limiting flexibility for users who hold alternative Circle tokens.

Impact

This restriction makes it inconvenient for users who have other Circle tokens or wrap tokens.

Mitigation

Allow the inviter or mitigator to specify which Circle token or wrapped Circle token they would like to use for paying the registration cost.

[benjaminbollen]

Thank you for your report on the lack of flexibility in payment tokens for registration costs. After careful review, we've determined that this is not an issue.

The requirement to pay known amounts in specific Circles is an intentional design choice in our system. There is no provision for users to choose alternative payment tokens for registration costs.

We appreciate your attention to the payment mechanics of our platform. While this limitation is by design, your report helps ensure our system's features and constraints are clearly understood. Thank you for contributing to the ongoing discussion about our platform's architecture.