Skip to content

Conversation

@EndymionJkb
Copy link
Collaborator

@EndymionJkb EndymionJkb commented Dec 19, 2025

I used to maintain this manually (Excalidraw), but there are so many things to track now! There's now an easy way to generate a diagram of whatever subset of deployments we want; here I have V3 pools and routers. We can also do V2, mix V2 and V3, etc.

This is an example; see the generator in PR #336 in the deployments repo.

@vercel
Copy link

vercel bot commented Dec 19, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
docs-v3 Ready Ready Preview, Comment Jan 7, 2026 1:16am

Copy link
Collaborator

@mkflow27 mkflow27 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the graphics that are added. They certainly provide helpful visual information about what contract version are the most current one. What do you think about:

  • Adding a reference link to the deployments repo so that readers can navigate there easily?
  • somehow linking or at least making it clear what the relationship between factory and pool is? As a reader I know that V3 ReClamm Pool V2 is the latest Reclamm pool, but the factory that deploys this pool is also relevant for me if I want to make sure I know the right contract to create the pool from, right?

# Conflicts:
#	docs/developer-reference/contracts/buffer-router-api.md
#	docs/developer-reference/contracts/composite-liquidity-router-api.md
@EndymionJkb
Copy link
Collaborator Author

I like the graphics that are added. They certainly provide helpful visual information about what contract version are the most current one. What do you think about:

  • Adding a reference link to the deployments repo so that readers can navigate there easily?
    It's an image now, so I can't really put a link in it. It does have the version and date, so people can go to the deployments repo section and find it by the date.

We also have the contract registry, which lets you look up the current standard factory for "WeightedPool," (or one for a particular version), which is an on-chain way to do that (which a UI could also call).

  • somehow linking or at least making it clear what the relationship between factory and pool is? As a reader I know that V3 ReClamm Pool V2 is the latest Reclamm pool, but the factory that deploys this pool is also relevant for me if I want to make sure I know the right contract to create the pool from, right?

See the comment above, plus it is pretty much always Factory, by convention.

I can add comments and more explanation, vs. just having the raw images.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants