Program Rules
These rules keep rewards flowing to builders who bring real traders. Breaking them can lead to clawback of rewards and removal from the program.
Partnership standards
- Real user activity. Trading volume from self-owned or linked wallets, or self-matched trades, does not qualify for commissions, points or tier credit.
- One entity, one account. All builder addresses controlled by the same entity are treated as a single builder.
- Entity verification. Required for the Partner and Strategic tiers.
- Ecosystem listing. Official partner listings on txflow.com require BD approval, based on brand recognition and user volume.
Fee rules
- Builder fees must not exceed the market cap or the user's approved rate. If either limit is exceeded, the order still fills, but no builder fee is charged.
- No builder fees apply to liquidation or ADL fills.
- On spot, builder fees are charged on sell fills only. Buy fills carry no builder fee, whatever
fthe order sets. - Fee credits cover TxFlow trading fees only and do not cover builder fees.
- Fee caps are set by the platform. Changes are announced in advance with a transition period. Builder fees already accrued are unaffected.
Reward conditions
- Referral commissions are calculated on TxFlow fees after trader discounts and fee credits. Builder fees are excluded from commission and points calculations.
- Volume flagged by risk controls is not eligible for points.
- Points and pool rewards are subject to the TxFlow Points Program Terms, including anti-farming and anti-sybil reviews.
User consent
Users must explicitly approve builder fees. Before the user signs approveBuilderFee, your interface must display your app name, builder address, maximum fee rate, trading permissions and authorization duration.
Silent approvals, pre-selected referral binding, and approval requests above the fee rate you charge are prohibited.
Risk control
- TxFlow monitors builder activity and may restrict addresses that show abnormal behavior.
- Builder addresses cannot be used as trading addresses, which prevents self-approval at the protocol level.
- Front-running, or trading ahead of routed order flow, is prohibited.
- Report suspected abuse to your BD contact.