Feature: velocore adapter

[velocore]

Description

Velocore is a veDEX with real-time voting.

Website: https://velocore.xyz
App: https://linea.velocore.xyz
Docs: https://docs.velocore.xyz
Contracts: https://docs.velocore.xyz/security-and-contract-address/linea-contracts

We have a different architecture to the Uniswap forks.
For example, we have a singleton vault structure for all kinds of interactions, erc-1155 LPs for stable pools, and a gauge contract for each LP.
So we implemented VelocorePoolAdapter based on the IProtocolAdapter class rather than SimplePoolAdapter.

Please note that we used gauge address instead of pool address as the key of the metadata object.
Because of our structure, a stable pool can have multiple LPs in a pool, each LP is an erc-1155 token, distinguished by tokenId, and each LP has one gauge associated with it.
Therefore, we used the gauge address as the key of the metadata object for a one-to-one mapping of protocolToken and key.

The rest of the VelocorePoolAdapter is nothing special. We used the Lens contract to get the data for the gauges and pools.

Pre-merge author checklist

• A brief description of the protocol and adapters is added to the PR
• Files outside the protocol folder are not being edited and, if they are, it's clearly explained why in the PR
• update me comments are removed
• Contracts used are verified for that chain block explorer
• Test cases with a block number have been added to the testCases.ts file for every relevant method that has been implemented
  • positions
  • prices
  • deposits
  • withdrawals
  • profits
  • tvl
  • apr
  • apy
• getAddress from ethers
  • Is used to parse hardcoded addresses
  • Is used to parse addresses that come from contract calls when it is not clear they'll be in checksum format
  • It is NOT used to parse addresses from input methods
  • It is NOT used to parse addresses from metadata
• For every adapter that extends SimplePoolAdapter
  • getPositions is not overwritten and, if it is, it's clearly explained why in the PR
  • unwrap is not overwritten and, if it is, it's clearly explained why in the PR
• If the adapters requires to fetch static data on-chain (e.g. pool ids, token metadata, etc)
  • The adapter implements IMetadataBuilder
  • The buildMetadata method is implemented with the @CacheToFile decorator
  • All the static data is stored within the metadata JSON file

[velocore]

We found that the defiProvider.unwrap function doesn't accept filterTokenId, even though the TestCase type has the filterTokenId property.

mmi-defi-adapters/src/types/testCase.ts

Lines 73 to 78 in 1c5bdab

	| {
	method: 'prices'
	blockNumber?: number
	filterProtocolToken?: string
	filterTokenId?: string
	}

Also, the adapter.unwrap function has tokenId as a parameter.

mmi-defi-adapters/src/types/adapter.ts

Lines 56 to 70 in 1c5bdab

	export type UnwrapInput = {
	/**
	* Optional override param
	*/
	blockNumber?: number
	/**
	* Protocol token address (LP token address).
	*/
	protocolTokenAddress: string
	/**
	* Optional filter for pools that will be queried by an ID
	*/
	tokenId?: string
	}

We need tokenId to handle our stable pool LPs (erc-1155) correctly, so we decided to add tokenId as params.

It is outside of our adapter implementation, so please let me know if it is not acceptable.