Tydro Docs | Smart Contracts
Tydro's smart-contract architecture is modular, with Pool and L2Pool entry points, configuration and access-control contracts, tokenization, oracles, rate strategies and data-provider helpers.
What this page covers
Tydro's smart-contract architecture is modular, with Pool and L2Pool entry points, configuration and access-control contracts, tokenization, oracles, rate strategies and data-provider helpers.
How it works
Pool is the central interaction point for supplying, borrowing and repaying. L2Pool optimizes calldata for rollups. PoolConfigurator manages reserve configuration, ACLManager controls roles, PoolAddressesProvider tracks core component addresses and aTokens or debt tokens represent user positions.
Reference
Practical usage
Integrators should use the current address book and match each contract to the correct Ink deployment. Read-only data providers are useful for interfaces, while state-changing actions should follow the protocol's Pool or L2Pool pathways.
Risks and operational notes
Using the wrong address, ABI, network or proxy implementation can produce failed or unsafe transactions. Always verify addresses and upgradeability assumptions before deployment.