rsnrdk

Id argue float alone would be enough and pattern id makes it bulletproof. But I guess your addition wont hurt. 
 
I think you don't need all that. Same applies for cases and stickers, they are all identical. If you have 5 vanilla BFK from 5 diff users and one withdraws it does not matter which one you return. Or if someone buys/withdraws a case or vanilla knife you can send whichever one of the tradable stock. All you need to store is the class_id, the count and ownership. Exact unit is irrelevant. 
Ye thats exactly why I suggested that. No possibility of any gaps no additional requests needed no need to implement caps on bots. Its a stopgap/workaround but what can you do when they pull shit like that.

You are right, thats actually doesn`t matter)
 
Thank you for your answers!
 

Just Use proxies for any kind of ratelimits steam ithink now applies dynamic ratelimits dont know for sure by yeah.
Use proxies 

yes after the trade the new asset id is visible so just set up a inventory poll and u should be good any steam trading bot does inventory poll but be careful not to set the poll too frequent u can get ratelimited very fast.
the old asset id is still in the event handler response so u have both the new id and the old one how i do it is i store a template of the doc in db then use a backfill script to fill in the new asset id.
Hope that helps
Regards

Just asked steam about this - w8ing for thier respond

I faced with this change on 22.04 first time. And there're still no new_assetid, new_contextid for trades from 22.04. The hold ended a long time ago