Proposal

[Frenkiee]

For the following tasks, we suggest the following implementations:

• Checksum all EVM addresses (now they are retrieved as lowercased)
• Pool tracking table
• EVM Event table for both verified and unverified EVM events
• Track ReefswapFactory PairCreated event, create a new contract for newly created Pair and verify contract
• Track ReefswapPair events: Mint (add liquidity), Burn (remove liquidity), Swap (on swap), Sync (called after every event)
• Crawler backtracking of unverified EVM events (once a new verified contract is detected, go through its old unverified events and verify them)
• NFT and NFTs page
• FE navigation bar - group Contracts, Tokens, and NFTs under Contracts dropdown
• FE navigation bar - group Blocks, Extrinsics, Events under Blocks dropdown
• Style dropdown
• Pool and Pools page?

Pool DB schematic:

• token address 1 (foreign key on contract)
• token address 2 (foreign key on contract)
• pool address (foreign key on contract)
• fee
• volume
• block id?
• decimals
• timestamp
• current price
• token amount 1
• token amount 2
• tvl (total value locked)
• reserve amount for token 1
• reserve amount for token 2
• event type (Mint, Burn, Swap)

[Netherdrake]

I think leaving addresses as lowercase in database is fine. From usability perspective, this is more convenient, because every language including SQL has a string.to_lower_case() type of function, while the reverse is not true (need special library to generate checksum addresses).

The checksum addresses are mostly to be used in UI's to prevent some class of copy/paste errors (all addresses in Reefscan UI should be ckecksum cased)