Hey Curve Dev Team, I hope you're all doing well! I

have a few questions and some clarifications I need regarding the get_pool_asset_type function in the MetaRegistry. Here’s the function I’m referring to:

@external
@view
def get_pool_asset_type(_pool: address, _handler_id: uint256 = 0) -> uint256:
"""
@notice Query the asset type of `_pool`
@param _pool Pool Address
@return The asset type as an unstripped string
@dev 0 : USD, 1: ETH, 2: BTC, 3: Other, 4: CryptoSwap
"""
return RegistryHandler(self._get_registry_handlers_from_pool(_pool)[_handler_id]).get_pool_asset_type(_pool)


MetaRegistry Address: 0xF98B45FA17DE75FB1aD0e7aFD971b0ca00e379fC

### Questions and Clarifications

1. Unexpected Return Values:
- When passing 0x1F71f05CF491595652378Fe94B7820344A551B8E to get_pool_asset_type, it returns 99. Any idea why?
- Passing 0x2889302a794dA87fBF1D6Db415C1492194663D13 returns 3, even though it looks like a CryptoSwap pool. Can you clarify?
2. Understanding Pool Types:
- Could you confirm if pool type 3 means it's a mix between stablecoins and other cryptos?
- We can't find any Meta Crypto Pools. Could you point us to an example?
3. LP Exchange Support:
- It seems only stable swap pools support LP exchange. Is that correct?
4. Interface Consistency:
- From an interface perspective, do all pools with asset types 0, 1, and 2 use int128 input parameters for indexes in the exchange function?
- And do all pools with asset types 3 and 4 use uint256 input parameters for indexes in the exchange function?
5. Future Pools:
- If the above points are correct, will this distinction hold true for pools deployed in the future as well?

Thanks a lot for your help! These details are super important for us to get everything right in our integration.

check this https://docs.curve.fi/registry/MetaRegistryAPI/

0x1F71f05CF491595652378Fe94B7820344A551B8E is an old stableswap pool btw, not cryptoswap