-
Notifications
You must be signed in to change notification settings - Fork 624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow multiple addresses to incentivize a packet #761
Comments
What happens if the same funder tries to incentivize a packet but specifies a different relayer list? If we wanted to allow this, we should be mapping to a slice of identified packet fees, but then I'm wondering why we don't just map from Was there a security concern with not including the refund address in the key? |
Do we want the refund addr in the key or identified fee struct? It shouldn't be both. It is convenient for it to be in the mapping, but you can filter based on incentivizer if it is in the key |
I think the map from I don't think it's that important to additionally key on refund address, especially if the first prefix is packetID |
closed by #915 |
packetID + refund_addr
->accumulated fees escrowed by this sender for this packetID + relayer list
The text was updated successfully, but these errors were encountered: