Velodrome Locks
Base Code
SELECT *, CONCAT('0x', SUBSTR(topics [1] :: STRING, 27, 42)) AS provider, ethereum.public.udf_hex_to_int( topics [2] :: STRING ) :: DATE AS locked_date, regexp_substr_all(SUBSTR(DATA, 3, len(DATA)), '.{64}') AS segmented_data, ethereum.public.udf_hex_to_int( segmented_data [0] :: STRING ) AS tokenID, ethereum.public.udf_hex_to_int( segmented_data [1] :: STRING )/pow(10,18) AS VALUE, ethereum.public.udf_hex_to_int( segmented_data [2] :: STRING ) AS deposit_type, ethereum.public.udf_hex_to_int( segmented_data [3] :: STRING ) AS TIMESTAMP FROM optimism.core.fact_event_logs WHERE topics [0] :: STRING = '0xff04ccafc360e16b67d682d17bd9503c4c6b9a131f6be6325762dc9ffc7de624'
For this analysis, some items have been prepared with the help of the base code prepared above, and the main challenges of the analysis have been answered. The output of this code can be seen in the table opposite
Important points of the table
- This table has two time columns, one for the time of transaction registration and the other for the time of prioritization, both of which I have analyzed in the next part.
- This table has about 5,000 rows, which means that in general 5,000 transactions have been registered for locking.
- You can get the information you need for each part with appropriate categories and fulfilling the required conditions of each part
The time when the transactions are recorded is almost a fixed graph and it means that every day fixed transactions are done in this protocol. But the locking time is not like that, it seems that 4 locking times are more popular than others
End of July 2022 End of December 2022 Early January 2023 Late January 2026
For this part, two concepts will be taken First, which wallets had the highest number of transactions Or Which wallets have the most transactions?
Since the amount of transactions was a more important factor for me SO
In the table below, you can see the top 10 wallets in terms of transaction volume