You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, affiliate/referrer fees are defined off-chain within the signed Order object (fields like feeRateBps, referrer, affiliate, affiliatePercentage). The contract only enforces validation and distribution at fill time, respecting the global MAX_FEE_RATE_BIPS.
This design provides flexibility but limits transparency: the wallet that receives fees cannot adjust rates on-chain, and users must rely on new signed orders to reflect different conditions.
Idea:
Introduce optional on-chain configurability for these parameters (similar to how the admin controls forkastFeeReceiver and forkastBaseFeeRate). This would allow forks to:
Register their fee splits publicly, with events for visibility
Prevent silent changes off-chain
Increase trust in white-label forks and their governance
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, affiliate/referrer fees are defined off-chain within the signed Order object (fields like feeRateBps, referrer, affiliate, affiliatePercentage). The contract only enforces validation and distribution at fill time, respecting the global MAX_FEE_RATE_BIPS.
This design provides flexibility but limits transparency: the wallet that receives fees cannot adjust rates on-chain, and users must rely on new signed orders to reflect different conditions.
Idea:
Introduce optional on-chain configurability for these parameters (similar to how the admin controls forkastFeeReceiver and forkastBaseFeeRate). This would allow forks to:
Beta Was this translation helpful? Give feedback.
All reactions