Why separate buy and sell tax
A token can allow both directions but charge very different amounts. A low buy tax does not imply a low sell tax, and transfer behavior can change if contract parameters are mutable.
For trading decisions, the sell side is especially important because a token that can technically be sold may still impose economically damaging exit costs.
How Jepeta represents tax data
Jepeta reads token-security data from GoPlus and exposes buy_tax_percent and sell_tax_percent when available. Missing values remain null and generate warnings rather than being displayed as reassuring zeroes.
The decision policy can warn on elevated taxes. Tax fields sit beside honeypot, mintability, holder concentration, liquidity, and data quality so the user does not over-focus on one number.
Interpretation rule
Use tax as one input. Confirm the token contract, source freshness, liquidity depth, and whether the token has permissions that could change fees later.
A permanent evidence page is useful for seeing what was observed at a published timestamp; run a fresh scan before relying on the current tax state.
Practical checklist
- Check buy and sell separately
- Treat null as unknown
- Watch for asymmetric exit cost
- Check whether fees can change
- Re-scan before execution