-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Leverage deployed gnosis auction vs fork #42
Comments
This comment was marked as resolved.
This comment was marked as resolved.
Interesting, the fee for Gnosis auction is paid in the token the auctioneer is selling, not the bidding token: |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
RusseII
changed the title
Leverage deployed gnosis auction vs fork (draft)
Leverage deployed gnosis auction vs fork
Feb 11, 2022
agree with auction recommendation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Interaction with Gnosis Auction
Options
We have three main options on how to interface with Gnosis auction
Use the contract as-is from the deployed address (recommended)
Fork the contract and redeploy without changing the source code
Fork and edit source code for a custom use case
Add's more auditing overhead, protocol risk, and complexity. Avoid if possible.
Questions
There are a few different ways we can handle this:
borrower
.Broker
- it will be theauctioneer
. It would receive theborrowingToken
upon the settlement of the auction and could keep 2% them and send the rest to theborrower
(recommended)@Namaskar-1F64F please correct me if I missed anything
The text was updated successfully, but these errors were encountered: