Opium Network
WebsiteGitHubTelegram
Search…
Opium Documentation
Introduction to Opium
What is Opium
FAQs
Restrictions
Restrictions
Security and Audits
Disclaimer
Audits
Bounty program
Governance
Decentralized setup
Governance flow
$Opium governance token
For users
Opium.Finance
opium.exchange
FOR DEVELOPERS
Deployment Addresses
High-level overview
Opium Protocol V2
Opium Protocol V1
Core
Registry
TokenMinter
TokenSpender
SyntheticAggregator
OracleAggregator
Helpers
Interfaces
Common Errors
oID - Oracle recipe
sID - Derivative recipe
EIP-2547: Composable Multiclass Token
Tutorials
Opium API
SDK
Complex description
Glossary
Opium derivatives
Oracle and derivative recipes
Oracle and derivative registers
Opium margin
Opium swaps (TMtm)
Opium order books
Powered By GitBook
Registry
Registry keeps track of the contracts currently being used in the Opium protocol.
All its user-facing functions are read-only and can be used to fetch the addresses of the contracts currently in use in the Opium Protocol rather than hardcoding them.

changeOpiumAddress() external view returns (address)
It allows to change the address of the recipient of the settlement fees within the Opium Protocol. It can only be called by the current account being the recipient of the settlement fees.
getMinter() external view returns (address)
It returns the current TokenMinter address
getTokenSpender() external view returns (address)
It returns the current TokenSpender address
getOpiumAddress() external view returns (address)
It returns the account that is currently set to receive settlement fees in the Opium Protocol.
getCore() external view returns (address)
It returns the current Core address
getOracleAggregator() external view returns (address)
It returns the current OracleAggregator address
getSyntheticAggregator() external view returns (address)
It returns the current SyntheticAggregator address
Previous
Core
Next
TokenMinter
Last modified 6mo ago
Copy link