feat: bump affiliate fees to 60 bps

[gomes-bot]

Description

Does what it says on the box. DEFAULT_FEE_BPS and the public API's DEFAULT_AFFILIATE_BPS now surface 60 so every swapper, rate, and quote consumer sees the same bump.

Issue

closes #11919

Risk

Low - static constants only, no protocol logic touched.

Testing

Engineering

• Request any swap quote (web or public API) and confirm affiliate bps surfaces as 60

Operations

• 🏁 My feature is behind a flag and doesn't require operations testing (yet)

Screenshots (if applicable)

n/a

Summary by CodeRabbit

• Chores
  • Default affiliate fee rates have been increased from 55 to 60 basis points across the platform. This adjustment impacts all commission and fee calculations throughout the system. Platform configuration, mock API responses, and automated tests have been synchronized to reflect the new rates and maintain consistent behavior.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

The pull request updates the default affiliate fee basis points from 55 to 60 across configuration constants and test expectations. Changes are applied consistently to config files, mock API responses, and test assertions with no modifications to logic or control flow.

Changes

Cohort / File(s)	Summary
Configuration Constants packages/public-api/src/config.ts, src/lib/fees/constant.ts	Updated DEFAULT_AFFILIATE_BPS and DEFAULT_FEE_BPS exported constants from '55' to '60'.
Mock Responses & Tests packages/public-api/src/server-standalone.ts, src/lib/fees/utils.test.ts	Updated affiliateBps values in mock API responses (3 entries) and test expectation from '55' to '60'.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• feat: remove affiliate fees for related asset bridging #11509: Directly affected by the DEFAULT_FEE_BPS change (55→60), which alters the fallback value used by getAffiliateBps logic.
• feat: near affiliate fees #11164: Related to affiliateBps consumption for NEAR appFees configuration, impacted by the default fee basis points update.

Suggested reviewers

• gomesalexandre
• premiumjibles

Poem

🐰 From fifty-five to sixty hops we bound,
Fee basis points leaping all around,
The DFC voted, unanimous and clear,
More revenue blooms in the newborn year! 📈

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat: bump affiliate fees to 60 bps' accurately and concisely summarizes the main change: updating affiliate fee constants from 55 to 60 basis points across the codebase.
Linked Issues check	✅ Passed	The pull request successfully addresses issue #11919 by updating DEFAULT_FEE_BPS and DEFAULT_AFFILIATE_BPS constants to 60 bps across all relevant files and test expectations.
Out of Scope Changes check	✅ Passed	All changes are directly related to the objective of bumping affiliate fees to 60 bps; no unrelated or out-of-scope modifications are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[firebomb1]

For posterity, this is following DFC's vote to increase fees here: https://discord.com/channels/554694662431178782/920449863408287855/1460829229561151790

And within their mission granted by SCP-170.

[0xApotheosis]

gm