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
Copy file name to clipboardExpand all lines: POLICY.md
+51-1Lines changed: 51 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,17 @@ Accepted values:
110
110
-**A network/chain identifier** — e.g. `"ARBITRUM"`, `"BEP20"`, `"ETH"`, `"SOL"`. The value must match what the exchange uses for that chain.
111
111
-**`"*"`** — wildcard; matches any network.
112
112
113
-
Even if the policy allows a network, the selected exchange must also support that network for the currency or the request will still fail at execution time.
113
+
The broker normalizes common operator aliases before matching policy:
114
+
115
+
| Operator alias | Broker network id |
116
+
|----------------|-------------------|
117
+
|`ARB`, `ARBITRUM`|`ARBITRUM`|
118
+
|`ETH`, `ERC20`, `ETHEREUM`|`ETHEREUM`|
119
+
|`BNB`, `BSC`, `BEP20`|`BNB`|
120
+
121
+
Even if the policy allows a normalized network, the selected exchange must also
122
+
support that network for the currency or the request will still fail at
123
+
execution time.
114
124
115
125
---
116
126
@@ -191,6 +201,46 @@ Common rejection reasons:
191
201
- address not whitelisted
192
202
- token not in `coins` for the matched rule
193
203
204
+
### Narrow Binance/MEXC USDC BEP20 corridor example
205
+
206
+
Use a dedicated policy for treasury corridors instead of relying on broad
207
+
exchange/network rules. The example
208
+
`policy/policy.binance-mexc-usdc-bep20.example.json` permits only USDC over the
209
+
normalized `BNB` network family (`BNB`, `BSC`, or `BEP20`) between Binance and
0 commit comments