Assessment reportsPublic findings
Back to Zellic site
↗
Assessment reports>Radix>Threat Model>Liquidity pools
GeneralOverview
Findings
High (1)
Medium (2)
Low (2)
Informational (1)
DiscussionUnique Characteristics of Radix
Threat ModelWhat are threat models?
1-native-blueprintsModule: Resource blueprintsResourcesConsensus managerFungible and nonfungible proofsAuthorization zonePackageFungible bucketsFungible vaultsFungible resource managersValidatorAccount lockerWorktopAccountLiquidity poolsAccess controller
2-runtime3-transactions4-kernel
Audit ResultsAssessment Results

Liquidity pools

The Radix engine has three native blueprints for liquidity pools. These are the one, two, and multiresource pools.

The functionality of all three pools are mostly the same. Every blueprint has an instantiate() function, which is intended to be used to create a pool component. The pool component then contains methods that allow the pool-manager role to contribute resources to the pool. The pool then returns a resource bucket that contains the equivalent of LP tokens. These LP tokens can then be used to redeem the pool resources back at a later time.

Typically, the pool-manager role would be assigned to an exchange blueprint. The exchange blueprint would allow users to swap resources within the pool or even between multiple pools.

There are also publicly accessible redeem functions that can be used to redeem pool resources using buckets of LP resources. These are intended to be used by normal users, while the protected deposit and withdraw methods are intended to be used by the pool manager.

Zellic © 2025Back to top ↑