-
Notifications
You must be signed in to change notification settings - Fork 29
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
deploy next lower range for univ3 tcl #32
Comments
Waiting for funds to reach on treasury ops once nonce 6 executes, awaiting signers |
think this can be closed for now, no? good to have #100 merged and ready, but this ticket is not needed for now..? |
we could close it, but it will be just to open again in the future the same, right? depending on market conditions at the end till it becomes relevant again, but not see damage on leaving it open |
snap:
|
Execed at 100 gwei. May take a while. Ping me for a speedup. https://etherscan.io/tx/0xe7405ac5e024a368cb261b9628c066fc0dd2b92949ba9acaa1fbb783b7dd46da |
NFT transfer to vault tx: https://etherscan.io/tx/0x75dea1ce080a0aed2ce8a246073883e19b56f41760794b44f93cdf1088d1fdec |
Reminder:
|
nonce 49, top-ups missing part on the lowest range snap:
|
the
.000063 - .000125
range has to be deployed according to bip-74: https://forum.badger.finance/t/bip-74-treasury-controlled-liquidity-for-badger/5082/requires 57.74 wbtc, which needs to be funded from vault, but nft position itself could be created on treasury ops i guess.
lowest range deployed is currently in range: https://app.uniswap.org/#/pool/167046
pool: https://info.uniswap.org/#/pools/0xe15e6583425700993bd08f51bf6e7b73cd5da91b
The text was updated successfully, but these errors were encountered: