Pesquisa verificada por fontes: Binance Signed Endpoint Percent

Decision Matrix

Source Map

• Binance Developer Documentation: Spot Block Matching Change Log (binance-spot-block-matching-changelog)
• Binance Developer Documentation: General REST API Information (binance-spot-rest-api)
• Binance Developer Documentation: Rebate Change Log (binance-rebate-changelog)

Control Notes

1. Affected signing path

Affected signing path is the decision point where public documentation must become an operating rule. In this package, it means the risk sits in payload construction before cryptographic signing. The practical action is to inventory every internal client that builds signed Binance requests. The unresolved edge is undocumented third-party wrappers that reserialize payloads, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

2. Fixture coverage

Fixture coverage is the decision point where public documentation must become an operating rule. In this package, it means ASCII-only examples can miss encoding defects. The practical action is to test ASCII, non-ASCII, query-only and body-plus-query payloads. The unresolved edge is symbols or parameters not present in test fixtures, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

3. Timing controls

Timing controls is the decision point where public documentation must become an operating rule. In this package, it means timestamp and recvWindow still decide whether signed requests are accepted in time. The practical action is to avoid changing time windows while changing encoding. The unresolved edge is clock skew during deployment, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

4. Product scope

Product scope is the decision point where public documentation must become an operating rule. In this package, it means Binance product-family changelogs may surface the same signing requirement in different places. The practical action is to verify every product family used by the bot before production rollout. The unresolved edge is private endpoints not covered by public examples, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

5. Failure evidence

Failure evidence is the decision point where public documentation must become an operating rule. In this package, it means INVALID_SIGNATURE can come from multiple signing defects. The practical action is to log non-secret payload-shape hashes and error labels, not secrets. The unresolved edge is whether support can distinguish encoding failure from key misuse, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

6. Rollback

Rollback is the decision point where public documentation must become an operating rule. In this package, it means a signing migration should be reversible until all endpoints pass. The practical action is to keep old and new signer paths behind a controlled release flag. The unresolved edge is whether historical orders need replay or only future requests change, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

7. Commercial boundary

Commercial boundary is the decision point where public documentation must become an operating rule. In this package, it means API compatibility does not prove better execution, lower fees or account eligibility. The practical action is to report it as operational readiness only. The unresolved edge is future exchange-side changes after the documented date, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

Known Unknowns

• undocumented third-party wrappers that reserialize payloads
• symbols or parameters not present in test fixtures
• clock skew during deployment
• private endpoints not covered by public examples
• whether support can distinguish encoding failure from key misuse
• whether historical orders need replay or only future requests change
• future exchange-side changes after the documented date

Practical Takeaway

Binance developer documentation now makes percent-encoding part of the signed-payload control surface for affected REST examples, and the Spot Block Matching changelog warns that requests not following the order will be rejected with INVALID_SIGNATURE from the stated effective time. The decision outcome is to test signing libraries with ASCII and non-ASCII payload fixtures, keep timestamp and recvWindow handling unchanged, and verify every affected product family before rotating production keys or changing bot order flow. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, callback, policy framework, settlement route or liquidity position will work under every future condition.