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
for a more robust alternative. The `FILTERED_G_ADDRESSES` configuration
299
+
option is likewise deprecated and has no effect.
300
+
301
+
***unbanaccounts** (deprecated)
302
+
Account banning has been removed; this endpoint is kept for backwards
303
+
compatibility and only returns a deprecation warning.
315
304
316
305
***checkdb**
317
306
Triggers the instance to perform a background check of the database's state.
@@ -399,10 +388,9 @@ Most commands return their results in JSON format.
399
388
* "FILTERED" - transaction rejected because it contains an operation type that Stellar Core filters out. See Stellar Core configuration `EXCLUDE_TRANSACTIONS_CONTAINING_OPERATION_TYPE` for more details.
400
389
401
390
Optional parameters:
402
-
*`force=true` - bypasses banned account filtering (see `banaccounts`),
403
-
allowing the transaction into the mempool even if its source account or
404
-
fee source is on the ban list. Other filtering (operation type, Soroban
405
-
key filtering) still applies. Example: `tx?blob=Base64&force=true`
391
+
*`force=true` - deprecated and has no effect (it used to bypass
392
+
banned account filtering, which has been removed). Accepted for
393
+
backwards compatibility; the response includes a deprecation warning.
0 commit comments