Skip to content

Conversation

@nicholaspai
Copy link
Member

No description provided.

import "@openzeppelin/contracts/utils/Address.sol";

/**
* @notice Contract deployed on Ethereum that houses L1 token liquidity for all SpokePools. Admin can instruct this
Copy link
Member

Choose a reason for hiding this comment

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

should we say "admin"? this is not really correct, no? it's more that a valid bundle does the action you describe.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, this is definitely not an admin. Anyone can propose these and their validity is validated via the OO.

Copy link
Member Author

Choose a reason for hiding this comment

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

sure


/**
* @notice Contract deployed on Ethereum that houses L1 token liquidity for all SpokePools. Admin can instruct this
* contract to send tokens to L2 SpokePools via "pool rebalances" with which to pay out relayers on those networks.
Copy link
Member

Choose a reason for hiding this comment

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

"with which to pay out relayers" is a bit clunky. can you refactor this sentence a bit?

Copy link
Member Author

Choose a reason for hiding this comment

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

sure

/**
* @notice Contract deployed on Ethereum that houses L1 token liquidity for all SpokePools. Admin can instruct this
* contract to send tokens to L2 SpokePools via "pool rebalances" with which to pay out relayers on those networks.
* Admin also can publish relayer refund and slow relay merkle roots to SpokePools via this contract.
Copy link
Member

Choose a reason for hiding this comment

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

Again, not sure if we should use the Admin word. wdyt?

Copy link
Member Author

Choose a reason for hiding this comment

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

sure changing

mapping(bytes32 => address) private whitelistedRoutes;

// Mapping of L1TokenAddress to the associated Pool information.
// Mapping of L1 token addresses to the associated pool information.
Copy link
Member

Choose a reason for hiding this comment

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

should this comment come after the struct declaration, but before the mapping is defined?

Copy link
Member Author

Choose a reason for hiding this comment

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

sure


function addLiquidity(address l1Token, uint256 l1TokenAmount) public payable {
/**
* @notice Deposit liquidity into this contract to earn LP fees in exchange for backstopping relays on SpokePools.
Copy link
Member

@chrismaree chrismaree Feb 28, 2022

Choose a reason for hiding this comment

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

is backstopping the right word? I get what you're saying; it totally makes sence but is it the most correct word?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, I think funding is probably a more correct word.

Copy link
Member Author

Choose a reason for hiding this comment

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

changed to funding

* refund relayers.
* @param slowRelayRoot Slow relay root to publish to Spoke Pool where a data worker can execute leaves to
* fulfill slow relays.
*/
Copy link
Member

Choose a reason for hiding this comment

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

you are missing a comment on poolRebalanceRoot

Copy link
Member Author

Choose a reason for hiding this comment

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

done

nicholaspai and others added 3 commits February 28, 2022 18:41
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
nicholaspai and others added 14 commits February 28, 2022 18:46
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
Co-authored-by: Chris Maree <christopher.maree@gmail.com>
nit
Signed-off-by: ubuntu <>
Signed-off-by: chrismaree <christopher.maree@gmail.com>
@nicholaspai nicholaspai merged commit bf03255 into master Mar 1, 2022
@nicholaspai nicholaspai deleted the npai/natspec branch March 1, 2022 15:36
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.

4 participants