Hi!
We’ve developed a game prototype in Algorand two months ago, and we faced a number of challenges.
I want to check what is the state of these challenges today and if there are plans to address them.
-
No float and negative number support in Teal. We used a workaround for float numbers with multiplying every number to 100, but it makes debugging harder. Are there any plans for native support or a standard practice to follow?
-
No support for complex data types. Again we used a workaround to serialize objects to binary and store them and deserialize for reuse. Currently, serialization is not very efficient and uses a lot of gas which makes contract call expensive.
-
Very limited contract cost (execution) budget. Complex contract calls has a lot of computation and although it’s possible to make a group transaction to increase cost budget, it’s not practical to do so. There’s also a limit on program size (max 8 KB). For reference, look here and also here.
-
Mandatory opt-in for receiving every new Token/NFT. As games use a lot of NFTs, it doubles the transaction needed to receive a group of them. For example, 10 transactions are needed for receiving 5 NFTs. Is there a better way to do it?
-
Extremely difficult contract debugging. PyTeal is essentially a wrapper around Teal, and after you go into debugging, you need to face it. You actually need to know Teal inside out in order to effectively debug your contract, which questions the usability of PyTeal.
Thanks in advance.

, which was the program size limit at 2 KB that can increase to 8 KB (still very limited for a game contract).