-
Notifications
You must be signed in to change notification settings - Fork 91
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
Security monitoring #927
Comments
Hi rndqnuu there is another potential monitor solution available at mainnet, https://cyvers.ai/ |
Updated description |
/help |
Available Commands
|
@0xJoichiro I received the notification, can you please add a comment with |
/start |
# Skipping to register a wallet address because both address/ens doesn't exist |
/query @0xJoichiro |
! action has an uncaught error |
@0xJoichiro could you please try to register your wallet address for payouts using |
yes sir,I'll create a wallet and try this asap |
/wallet 0x2C35d567b68Adf4FcE2b89e9c0aE70Ea119C209A |
+ Successfully registered wallet address |
/start |
Tips:
|
@gitcoindev does this work as a draft PR #938? Yes, please mark it as ready for review when it will be ready. |
@0xJoichiro the message it's not clear do you think the PR is ready to review? |
@gentlementlegen can you trim and parse commands so they execute even with the |
@0x4007 yes I opened a ticket on |
@alexandr-masl the deadline is at Mon, Sep 9, 8:42 AM UTC |
@alexandr-masl, this task has been idle for a while. Please provide an update. |
@alexandr-masl The point regarding telegram notifications is not mandatory if some other notification method (email?) is available on the monitoring platform. If https://www.openzeppelin.com/defender supports setting up telegram notification in few clicks then it's fine. Otherwise if it only supports email notifications then it's also fine. There's no need to overengineer, just select a notification solution which can be set up in a couple of clicks (and we'll add telegram notifcations later). |
Got it! I was deciding between Chainlink and OpenZeppelin, but I’m leaning towards implementing OpenZeppelin Defender since it offers built-in notifications like Slack, Telegram, and email right out of the box, plus it supports webhooks, allowing to send notifications to any external service or platform |
@alexandr-masl, this task has been idle for a while. Please provide an update. |
4 similar comments
@alexandr-masl, this task has been idle for a while. Please provide an update. |
@alexandr-masl, this task has been idle for a while. Please provide an update. |
@alexandr-masl, this task has been idle for a while. Please provide an update. |
@alexandr-masl, this task has been idle for a while. Please provide an update. |
Hey @rndquu, can you please reassign me? Also, I'm still waiting for your review on this pull request. Let me know if there's anything I can help with, as I haven't seen any updates in a while |
@alexandr-masl the deadline is at Tue, Oct 22, 8:15 AM UTC |
Passed the deadline and no activity is detected, removing assignees: @alexandr-masl. |
/query |
|
/query @alexandr-masl |
|
/wallet 0x37Dd2F550E177F753d4b383dA86010e5Ad58C16c |
+ Successfully registered wallet address |
/query @alexandr-masl |
|
@alexandr-masl the deadline is at Sat, Dec 14, 5:02 PM UTC |
In case of a security incident we should:
Possible solutions for monitoring:
What should be done:
a) Pause the UbiquityDollarToken
b) Pause LibUbiquityPool by disabling collateral
Dollar monitoring
)P.S. Mainnet contract addresses can be found here
The text was updated successfully, but these errors were encountered: