At AVM in Austin two weeks ago, they said it will happen this summer.

Hello @jeapostrophe , just hoping onto this thread as I asked a similar question just today. Since the box storage feature for Maps is not available on Algo yet, what are the best data structure alternatives to use to counter this? Tried with my team to think around that limitation and no luck until now(at least the 2nd week on the problem). I remember you advising Maps are the best for use cases like NFT data, are there anything else someone can use that has the best traits or close to Maps? Thanks.

There is also an issue where when you add new values to a Map in consensus, it overwrites the previous entry you added if it came from the same address

I answered on the other thread. Specifically on the question of NFT attributes, suppose I have the NFT "Jay McCarthy" and I want to extend it with "height" and "charm". One design is to have the "Jay McCarthy" contract have a map of these attributes and an external agent set them. Alternatively, I could launch a new contract called "Jay McCarthy's charm" and then a client will search the set of all contracts for ones that mention "Jay McCarthy" when they get displayed. That will be tedious and more expensive, but it will work, if you can't wait for more Algorand features.

I think I'd rather wait @jeapostrophe for the update, thanks for the explanation, let me try comprehending to depth the Map's explanation you gave. Thanks again.