Binance Square
Duonggg12
1.2k Posts

Duonggg12

2008 tập viết content
Open Trade
Frequent Trader
11.7 Months
34 Following
1.7K+ Followers
1.7K+ Liked
Posts
Portfolio
·
--
#binancep2pantoan @Binance_Vietnam $BTC A merchant who just wants to check the buyer more thoroughly can also accidentally invalidate their own ads. I looked into the Additional Verification section of Binance P2P and found that the issue lies in the timing of the request. In the ad configuration, Binance provides a field called takerAdditionalKycRequired, which allows the merchant to enable additional verification requirements from the very beginning. If the merchant does not enable this condition on the ad, but then later asks the buyer to complete more verification, Binance considers it a violation. Per the Merchant Guidelines, any ads found to be violating may be closed; if further action is taken, the merchant’s P2P activity could be suspended for up to 14 days or disqualified. The part that’s easy to get wrong is that the merchant may think: “I’m only checking the buyer with one extra step.” But for Binance, this is no longer a standalone requirement within the order. It has become a transaction condition that the merchant must declare in the ad itself. So the workaround is quite simple: if the ad needs additional verification, enable it before the buyer enters the order. In return, the merchant must decide this condition when creating the ad instead of waiting until they encounter each buyer and then requesting it. The cost of doing it the right way is almost 0 additional processing time, but the trade-off is that the merchant loses flexibility in changing the conditions midway. And this is where I’ll check before every ad: are the conditions I want the buyer to meet already included on the ad? If not, don’t wait until an order comes in to add the requirement. At that point, the issue is no longer whether the buyer is willing to verify—it could become a problem with the ad itself.
#binancep2pantoan @Binance Vietnam $BTC A merchant who just wants to check the buyer more thoroughly can also accidentally invalidate their own ads.

I looked into the Additional Verification section of Binance P2P and found that the issue lies in the timing of the request. In the ad configuration, Binance provides a field called takerAdditionalKycRequired, which allows the merchant to enable additional verification requirements from the very beginning.

If the merchant does not enable this condition on the ad, but then later asks the buyer to complete more verification, Binance considers it a violation. Per the Merchant Guidelines, any ads found to be violating may be closed; if further action is taken, the merchant’s P2P activity could be suspended for up to 14 days or disqualified.

The part that’s easy to get wrong is that the merchant may think: “I’m only checking the buyer with one extra step.” But for Binance, this is no longer a standalone requirement within the order. It has become a transaction condition that the merchant must declare in the ad itself.

So the workaround is quite simple: if the ad needs additional verification, enable it before the buyer enters the order. In return, the merchant must decide this condition when creating the ad instead of waiting until they encounter each buyer and then requesting it.

The cost of doing it the right way is almost 0 additional processing time, but the trade-off is that the merchant loses flexibility in changing the conditions midway.

And this is where I’ll check before every ad: are the conditions I want the buyer to meet already included on the ad? If not, don’t wait until an order comes in to add the requirement. At that point, the issue is no longer whether the buyer is willing to verify—it could become a problem with the ad itself.
Verified
#dusk $DUSK @Dusk_Foundation $BTC I would have treated a 202 response as acceptance. Then I read Dusk’s transaction flow more carefully. A 202 only means the node accepted the transaction for routing. It does not mean the transaction entered the real mempool, executed, or finalized. A future nonce transaction can sit outside the visible mempool while waiting for the missing nonce. Rusk 1.7.0 added a bounded pre admission retry queue for these non consecutive Moonlight transactions. Instead of rejecting the transaction immediately, the node can defer it and emit a deferred lifecycle event. That creates a practical problem for integrations. If a withdrawal service marks a transaction complete after receiving 202, it can be wrong. Dusk’s exchange documentation says the service should track execution and finality before completing the withdrawal. It also needs to preserve the signed transaction and rebroadcast the same bytes if transport fails. So I would not treat: 202 → done I would treat it as: 202 → keep tracking. The simple test is whether the transaction eventually reaches execution and finality, not whether the first HTTP request succeeded.
#dusk $DUSK @Dusk $BTC I would have treated a 202 response as acceptance.

Then I read Dusk’s transaction flow more carefully.

A 202 only means the node accepted the transaction for routing. It does not mean the transaction entered the real mempool, executed, or finalized. A future nonce transaction can sit outside the visible mempool while waiting for the missing nonce.

Rusk 1.7.0 added a bounded pre admission retry queue for these non consecutive Moonlight transactions. Instead of rejecting the transaction immediately, the node can defer it and emit a deferred lifecycle event.

That creates a practical problem for integrations.

If a withdrawal service marks a transaction complete after receiving 202, it can be wrong. Dusk’s exchange documentation says the service should track execution and finality before completing the withdrawal. It also needs to preserve the signed transaction and rebroadcast the same bytes if transport fails.

So I would not treat:

202 → done

I would treat it as:

202 → keep tracking.

The simple test is whether the transaction eventually reaches execution and finality, not whether the first HTTP request succeeded.
$HOME My view: Bearish, but currently consolidating near 0.0069–0.0070. Heavy liquidity around 0.00715–0.00735 could attract price upward, but I’d need a clean break above that zone before becoming bullish. {future}(HOMEUSDT)
$HOME

My view: Bearish, but currently consolidating near 0.0069–0.0070. Heavy liquidity around 0.00715–0.00735 could attract price upward, but I’d need a clean break above that zone before becoming bullish.
$BLESS My view: Weak structure. Price continues to make lower highs and is now around 0.0083. There is liquidity below around 0.0080–0.0082, while much heavier liquidity sits above 0.0091–0.0095. Short-term bias remains bearish. {future}(BLESSUSDT)
$BLESS

My view: Weak structure. Price continues to make lower highs and is now around 0.0083. There is liquidity below around 0.0080–0.0082, while much heavier liquidity sits above 0.0091–0.0095. Short-term bias remains bearish.
$ACU My view: Bearish overall, but there was a strong rebound from around 0.098 toward 0.113. The 0.119–0.134 region contains heavy liquidity and should be difficult resistance. I’d watch whether price can hold above 0.112. {future}(ACUUSDT)
$ACU

My view: Bearish overall, but there was a strong rebound from around 0.098 toward 0.113. The 0.119–0.134 region contains heavy liquidity and should be difficult resistance. I’d watch whether price can hold above 0.112.
$SPORTFUN My view: Relatively stronger than Q. Price is consolidating around 0.0227 after the earlier drop. Liquidity is dense around 0.0240–0.0254, so a move into that region looks possible if buyers regain momentum. {future}(SPORTFUNUSDT)
$SPORTFUN

My view: Relatively stronger than Q. Price is consolidating around 0.0227 after the earlier drop. Liquidity is dense around 0.0240–0.0254, so a move into that region looks possible if buyers regain momentum.
$Q My view: Clearly bearish. Price has fallen from roughly 0.027–0.028 to around 0.022, with liquidity concentrated above 0.0235–0.0240. I’d treat that area as the first major resistance rather than expecting an immediate reversal. {future}(QUSDT)
$Q

My view: Clearly bearish. Price has fallen from roughly 0.027–0.028 to around 0.022, with liquidity concentrated above 0.0235–0.0240. I’d treat that area as the first major resistance rather than expecting an immediate reversal.
$XPIN My view: Extremely volatile and high-risk. The sharp liquidation wick shows a major liquidity event, followed by a partial recovery. Current price around 0.00135 is weak; 0.00146–0.00157 looks like strong overhead liquidity and resistance. {future}(XPINUSDT)
$XPIN

My view: Extremely volatile and high-risk. The sharp liquidation wick shows a major liquidity event, followed by a partial recovery. Current price around 0.00135 is weak; 0.00146–0.00157 looks like strong overhead liquidity and resistance.
$CYS My view: Bearish but potentially forming a base. Price dropped from around 0.80 toward 0.50, then started stabilizing. Heavy liquidity sits around 0.67–0.75, making that zone a major resistance area. {future}(CYSUSDT)
$CYS

My view: Bearish but potentially forming a base. Price dropped from around 0.80 toward 0.50, then started stabilizing. Heavy liquidity sits around 0.67–0.75, making that zone a major resistance area.
$H My view: More interesting than the others. Price suffered a sharp dump but has started recovering from the 0.10–0.11 area. Liquidity around 0.12–0.15 is much heavier, so I see potential for a relief move higher if momentum continues. {future}(HUSDT)
$H

My view: More interesting than the others. Price suffered a sharp dump but has started recovering from the 0.10–0.11 area. Liquidity around 0.12–0.15 is much heavier, so I see potential for a relief move higher if momentum continues.
$VELVET My view: Very bearish. Price has broken down aggressively and is now near the lower liquidity zone. The main liquidity above around 0.82–0.99 could act as a pullback target, but I would avoid chasing longs here. {future}(VELVETUSDT)
$VELVET

My view: Very bearish. Price has broken down aggressively and is now near the lower liquidity zone. The main liquidity above around 0.82–0.99 could act as a pullback target, but I would avoid chasing longs here.
$BEAT My view: Strong bearish structure. Price is sitting near the lower range after a sharp drop, while major liquidity remains above. I’d expect a short-term bounce, but the overall trend is still bearish. {future}(BEATUSDT)
$BEAT

My view: Strong bearish structure. Price is sitting near the lower range after a sharp drop, while major liquidity remains above. I’d expect a short-term bounce, but the overall trend is still bearish.
$STBL My view: Bearish / neutral * Current price: ~0.0264 * Resistance: 0.0273 → 0.0290 * Support: 0.0256 → 0.0248 * After the rejection from ~0.028, momentum has weakened. I’d watch 0.0256 closely; losing it could expose 0.0248. {future}(STBLUSDT)
$STBL

My view: Bearish / neutral

* Current price: ~0.0264
* Resistance: 0.0273 → 0.0290
* Support: 0.0256 → 0.0248
* After the rejection from ~0.028, momentum has weakened. I’d watch 0.0256 closely; losing it could expose 0.0248.
$ONG My view: Neutral / slightly bullish * Current price: ~0.058 * Resistance: 0.0605 → 0.0628 * Strong support: 0.0559 → 0.0536 * Price is sitting between important zones. A break above 0.0605 would be bullish, while losing 0.0559 would make me expect another move lower. {future}(ONGUSDT)
$ONG

My view: Neutral / slightly bullish

* Current price: ~0.058
* Resistance: 0.0605 → 0.0628
* Strong support: 0.0559 → 0.0536
* Price is sitting between important zones. A break above 0.0605 would be bullish, while losing 0.0559 would make me expect another move lower.
$DIA My view: Bullish, but near resistance * Current price: ~0.144 * Heavy liquidity above: 0.148 → 0.156 * Support: 0.132 → 0.124 * The structure looks strong after the breakout. I think 0.148 is the immediate magnet, with 0.156 possible if momentum remains strong. {future}(DIAUSDT)
$DIA

My view: Bullish, but near resistance

* Current price: ~0.144
* Heavy liquidity above: 0.148 → 0.156
* Support: 0.132 → 0.124
* The structure looks strong after the breakout. I think 0.148 is the immediate magnet, with 0.156 possible if momentum remains strong.
$DODOX My view: Neutral / slightly bullish * Current price: ~0.0224 * Major liquidity above: 0.0236 → 0.0248 * Support: 0.02115 → 0.0199 * There is substantial liquidity above the current price. 0.0236 is the key target, but failure to hold 0.022 could lead to a deeper retracement. {future}(DODOXUSDT)
$DODOX

My view: Neutral / slightly bullish

* Current price: ~0.0224
* Major liquidity above: 0.0236 → 0.0248
* Support: 0.02115 → 0.0199
* There is substantial liquidity above the current price. 0.0236 is the key target, but failure to hold 0.022 could lead to a deeper retracement.
$TAG My view: Bullish bias * Current price: ~0.00104 * Strong liquidity above: 0.00110 → 0.00115 * Support: 0.00098 → 0.00092 * The large cluster around 0.00110 looks like the main price magnet. I’d lean toward another attempt higher as long as 0.00098 holds. {future}(TAGUSDT)
$TAG

My view: Bullish bias

* Current price: ~0.00104
* Strong liquidity above: 0.00110 → 0.00115
* Support: 0.00098 → 0.00092
* The large cluster around 0.00110 looks like the main price magnet. I’d lean toward another attempt higher as long as 0.00098 holds.
$TUT My view: Short-term bullish, but resistance is heavy * Current price: ~0.0384 * Resistance/liquidity: 0.0415 → 0.0447 * Support: 0.0352 → 0.0321 * The chart still has upside potential, but 0.0415 is the key area. A rejection there could bring price back toward 0.0352. {future}(TUTUSDT)
$TUT

My view: Short-term bullish, but resistance is heavy

* Current price: ~0.0384
* Resistance/liquidity: 0.0415 → 0.0447
* Support: 0.0352 → 0.0321
* The chart still has upside potential, but 0.0415 is the key area. A rejection there could bring price back toward 0.0352.
$STAR My view: Volatile bullish / neutral * Current price: ~0.117 * Liquidity above: 0.119 → 0.126 * Strong liquidity below: 0.105 → 0.112 * There is liquidity on both sides, so I expect high volatility and possible sweeps in both directions. Personally, I’d prefer confirmation above 0.119. {future}(STARUSDT)
$STAR

My view: Volatile bullish / neutral

* Current price: ~0.117
* Liquidity above: 0.119 → 0.126
* Strong liquidity below: 0.105 → 0.112
* There is liquidity on both sides, so I expect high volatility and possible sweeps in both directions. Personally, I’d prefer confirmation above 0.119.
$ACE My view: Bullish with resistance nearby * Current price: ~0.165 * Strong liquidity above: 0.166 → 0.176 * Support: 0.154 → 0.142 * Price is approaching a heavy liquidation cluster. Break above 0.166 could trigger another push higher, while rejection could send it back toward 0.154. {future}(ACEUSDT)
$ACE

My view: Bullish with resistance nearby

* Current price: ~0.165
* Strong liquidity above: 0.166 → 0.176
* Support: 0.154 → 0.142
* Price is approaching a heavy liquidation cluster. Break above 0.166 could trigger another push higher, while rejection could send it back toward 0.154.
Log in to explore more content
Join global crypto users on Binance Square
⚡️ Get latest and useful information about crypto.
💬 Trusted by the world’s largest crypto exchange.
👍 Discover real insights from verified creators.
Email / Phone number
Sitemap
Cookie Preferences
Platform T&Cs