Ubiquity contest details

• Join Sherlock Discord
• Submit findings using the issue page in your private contest repo (label issues as med or high)
• Read for more details

Q&A

Q: On what chains are the smart contracts going to be deployed?

Mainnet

---

Q: Which ERC20 tokens do you expect will interact with the smart contracts?

LUSD, DAI

---

Q: Which ERC721 tokens do you expect will interact with the smart contracts?

None

---

Q: Do you plan to support ERC1155?

No

---

Q: Which ERC777 tokens do you expect will interact with the smart contracts?

None

---

Q: Are there any FEE-ON-TRANSFER tokens interacting with the smart contracts?

No

---

Q: Are there any REBASING tokens interacting with the smart contracts?

No

---

Q: Are the admins of the protocols your contracts integrate with (if any) TRUSTED or RESTRICTED?

TRUSTED

---

Q: Is the admin/owner of the protocol/contracts TRUSTED or RESTRICTED?

TRUSTED

---

Q: Are there any additional protocol roles? If yes, please explain in detail:

DOLLAR_TOKEN_MINTER_ROLE: can only mint Dollar tokens DOLLAR_TOKEN_BURNER_ROLE: can only burn Dollar tokens PAUSER_ROLE: can only pause/unpause contracts

---

Q: Is the code/contract expected to comply with any EIPs? Are there specific assumptions around adhering to those EIPs that Watsons should be aware of?

Is the code/contract expected to comply with any EIPs?

Yes

Are there specific assumptions around adhering to those EIPs that Watsons should be aware of?

No

---

Q: Please list any known issues/acceptable risks that should not result in a valid finding.

None

---

Q: Please provide links to previous audits (if any).

None

---

Q: Are there any off-chain mechanisms or off-chain procedures for the protocol (keeper bots, input validation expectations, etc)?

No

---

Q: In case of external protocol integrations, are the risks of external contracts pausing or executing an emergency withdrawal acceptable? If not, Watsons will submit issues related to these situations that can harm your protocol's functionality.

No, the risks of external contracts pausing or executing an emergency withdrawal are not acceptable.

---

Q: Do you expect to use any of the following tokens with non-standard behaviour with the smart contracts?

No

---

Q: Add links to relevant protocol resources

Audit notes: ubiquity/ubiquity-dollar#846 Architecture: https://github.com/ubiquity/ubiquity-dollar/wiki/23.-Smart-Contracts-Architecture Docs from natspec: https://github.com/ubiquity/ubiquity-dollar/wiki/22.-Smart-Contract-API

---

Q: On what chains are the smart contracts going to be deployed?

Mainnet

---

Q: Which ERC20 tokens do you expect will interact with the smart contracts?

LUSD, DAI

---

Q: Which ERC721 tokens do you expect will interact with the smart contracts?

None

---

Q: Do you plan to support ERC1155?

No

---

Q: Which ERC777 tokens do you expect will interact with the smart contracts?

None

---

Q: Are there any FEE-ON-TRANSFER tokens interacting with the smart contracts?

No

---

Q: Are there any REBASING tokens interacting with the smart contracts?

No

---

Q: Are the admins of the protocols your contracts integrate with (if any) TRUSTED or RESTRICTED?

TRUSTED

---

Q: Is the admin/owner of the protocol/contracts TRUSTED or RESTRICTED?

TRUSTED

---

Q: Are there any additional protocol roles? If yes, please explain in detail:

DOLLAR_TOKEN_MINTER_ROLE: can only mint Dollar tokens DOLLAR_TOKEN_BURNER_ROLE: can only burn Dollar tokens PAUSER_ROLE: can only pause/unpause contracts

---

Q: Is the code/contract expected to comply with any EIPs? Are there specific assumptions around adhering to those EIPs that Watsons should be aware of?

Is the code/contract expected to comply with any EIPs?

Yes

Are there specific assumptions around adhering to those EIPs that Watsons should be aware of?

No

---

Q: Please list any known issues/acceptable risks that should not result in a valid finding.

None

---

Q: Please provide links to previous audits (if any).

None

---

Q: Are there any off-chain mechanisms or off-chain procedures for the protocol (keeper bots, input validation expectations, etc)?

No

---

Q: In case of external protocol integrations, are the risks of external contracts pausing or executing an emergency withdrawal acceptable? If not, Watsons will submit issues related to these situations that can harm your protocol's functionality.

No, the risks of external contracts pausing or executing an emergency withdrawal are not acceptable.

---

Q: Do you expect to use any of the following tokens with non-standard behaviour with the smart contracts?

No

---

Q: Add links to relevant protocol resources

Audit notes: ubiquity/ubiquity-dollar#846 Architecture: https://github.com/ubiquity/ubiquity-dollar/wiki/23.-Smart-Contracts-Architecture Docs from natspec: https://github.com/ubiquity/ubiquity-dollar/wiki/22.-Smart-Contract-API

---

Q: On what chains are the smart contracts going to be deployed?

Mainnet

---

Q: Which ERC20 tokens do you expect will interact with the smart contracts?

LUSD, DAI

---

Q: Which ERC721 tokens do you expect will interact with the smart contracts?

None

---

Q: Do you plan to support ERC1155?

No

---

Q: Which ERC777 tokens do you expect will interact with the smart contracts?

None

---

Q: Are there any FEE-ON-TRANSFER tokens interacting with the smart contracts?

No

---

Q: Are there any REBASING tokens interacting with the smart contracts?

No

---

Q: Are the admins of the protocols your contracts integrate with (if any) TRUSTED or RESTRICTED?

TRUSTED

---

Q: Is the admin/owner of the protocol/contracts TRUSTED or RESTRICTED?

TRUSTED

---

Q: Are there any additional protocol roles? If yes, please explain in detail:

DOLLAR_TOKEN_MINTER_ROLE: can only mint Dollar tokens DOLLAR_TOKEN_BURNER_ROLE: can only burn Dollar tokens PAUSER_ROLE: can only pause/unpause contracts

---

Q: Is the code/contract expected to comply with any EIPs? Are there specific assumptions around adhering to those EIPs that Watsons should be aware of?

Is the code/contract expected to comply with any EIPs?

Yes

Are there specific assumptions around adhering to those EIPs that Watsons should be aware of?

No

---

Q: Please list any known issues/acceptable risks that should not result in a valid finding.

None

---

Q: Please provide links to previous audits (if any).

None

---

Q: Are there any off-chain mechanisms or off-chain procedures for the protocol (keeper bots, input validation expectations, etc)?

No

---

Q: In case of external protocol integrations, are the risks of external contracts pausing or executing an emergency withdrawal acceptable? If not, Watsons will submit issues related to these situations that can harm your protocol's functionality.

No, the risks of external contracts pausing or executing an emergency withdrawal are not acceptable.

---

Q: Do you expect to use any of the following tokens with non-standard behaviour with the smart contracts?

No

---

Q: Add links to relevant protocol resources

Audit notes: ubiquity/ubiquity-dollar#846 Architecture: https://github.com/ubiquity/ubiquity-dollar/wiki/23.-Smart-Contracts-Architecture Docs from natspec: https://github.com/ubiquity/ubiquity-dollar/wiki/22.-Smart-Contract-API

---

Audit scope

ubiquity-dollar @ 2d1cfeb7178481138e820a8f22405ddaff6e4975

• ubiquity-dollar/packages/contracts/src/dollar/Diamond.sol
• ubiquity-dollar/packages/contracts/src/dollar/access/AccessControlInternal.sol
• ubiquity-dollar/packages/contracts/src/dollar/core/ERC20Ubiquity.sol
• ubiquity-dollar/packages/contracts/src/dollar/core/UbiquityDollarToken.sol
• ubiquity-dollar/packages/contracts/src/dollar/facets/AccessControlFacet.sol
• ubiquity-dollar/packages/contracts/src/dollar/facets/DiamondCutFacet.sol
• ubiquity-dollar/packages/contracts/src/dollar/facets/OwnershipFacet.sol
• ubiquity-dollar/packages/contracts/src/dollar/facets/TWAPOracleDollar3poolFacet.sol
• ubiquity-dollar/packages/contracts/src/dollar/facets/UbiquityPoolFacet.sol
• ubiquity-dollar/packages/contracts/src/dollar/libraries/LibAccessControl.sol
• ubiquity-dollar/packages/contracts/src/dollar/libraries/LibAppStorage.sol
• ubiquity-dollar/packages/contracts/src/dollar/libraries/LibDiamond.sol
• ubiquity-dollar/packages/contracts/src/dollar/libraries/LibTWAPOracle.sol
• ubiquity-dollar/packages/contracts/src/dollar/libraries/LibUbiquityPool.sol

ubiquity-dollar @ 2d1cfeb7178481138e820a8f22405ddaff6e4975

• ubiquity-dollar/packages/contracts/src/dollar/Diamond.sol
• ubiquity-dollar/packages/contracts/src/dollar/access/AccessControlInternal.sol
• ubiquity-dollar/packages/contracts/src/dollar/core/ERC20Ubiquity.sol
• ubiquity-dollar/packages/contracts/src/dollar/core/UbiquityDollarToken.sol
• ubiquity-dollar/packages/contracts/src/dollar/facets/AccessControlFacet.sol
• ubiquity-dollar/packages/contracts/src/dollar/facets/DiamondCutFacet.sol
• ubiquity-dollar/packages/contracts/src/dollar/facets/OwnershipFacet.sol
• ubiquity-dollar/packages/contracts/src/dollar/facets/TWAPOracleDollar3poolFacet.sol
• ubiquity-dollar/packages/contracts/src/dollar/facets/UbiquityPoolFacet.sol
• ubiquity-dollar/packages/contracts/src/dollar/libraries/LibAccessControl.sol
• ubiquity-dollar/packages/contracts/src/dollar/libraries/LibAppStorage.sol
• ubiquity-dollar/packages/contracts/src/dollar/libraries/LibDiamond.sol
• ubiquity-dollar/packages/contracts/src/dollar/libraries/LibTWAPOracle.sol
• ubiquity-dollar/packages/contracts/src/dollar/libraries/LibUbiquityPool.sol