Simply Staking Community

25 Jan 2023 11:06

ok got it to work, had to update the IP address again in the .env file, might want to update the docs there

Simply Staking Community

25 Jan 2023 10:52

getting this after upgrade to 1.3.0:

Simply Staking Community

24 Jan 2023 15:17

Hi guys! Pleased to announce that we have had our first contribution from the community! :rocket:

PANIC now supports the configuration of two new alerts for when a node/validator is peered with sentinel. Thanks to @nikhilvasan and the rest of the team at Skip for this.

Should you wish to contribute, do not hesitate to reach out to us and we will assist you accordingly.

Release v1.3.1 along with all upgrade instructions can be found through this link:

https://github.com/SimplyVC/panic/releases/tag/v1.3.1

Simply Staking Community

23 Jan 2023 10:08

I had a friend with a similar problem, I advised him to write a sweeper script using a lot of gas for the tx and send the coins to another wallet, and run it immediately after the unstaking. It worked, he was faster than the evil script

Simply Staking Community

23 Jan 2023 08:49

1. Take note of your recovery phrase
2. Turn off your compromised devices
3. Setup metamask with your recovery phrase on an uncompromised device
4. Withdraw your staking funds
5. Transfer your funds to an uncompromised wallet

Simply Staking Community

20 Jan 2023 20:25

I updated the polkadot api version in the package.json. do u know the latest version I should have there?

Simply Staking Community

20 Jan 2023 15:46

hello! Question... while updating my validators I did not turn off alerting.
I brought down all of them (KSM), got all of them as warning in the docker logs, which is fine, but the CRITICAL ones were only 20% of the total, and only 20% of the 20% got sent to opsgenie: why not all the critical ones?

Simply Staking Community

12 Jan 2023 13:21

Hi Guys ! I’ve seen some news about you discontinuing your validator services on some chains. Nothing like that on moonbeam ?

Simply Staking Community

12 Jan 2023 10:05

Give it a restart like I explained in the pin.

Simply Staking Community

10 Jan 2023 12:16

Following these steps should fix your PANIC alerting for Substrate-based chains by upgrading the Substrate API:

1) In you PANIC directory, find substrate-api/package.json
2) Change the value of "@polkadot/api": to the latest version of Substrate API.
3) Restart the substrate-api container by executing:

docker-compose kill substrate-api
docker-compose up --build -d substrate-api

Simply Staking Community

10 Jan 2023 12:02

PANIC - SubstrateApiIsNotReachableAlert

Simply Staking Community

10 Jan 2023 12:01

What alert are you receiving on opsgenie?

Simply Staking Community

10 Jan 2023 12:00

I use it for dot and ksm

Simply Staking Community

10 Jan 2023 11:59

in this page I don't see anything related to substrate

Simply Staking Community

10 Jan 2023 11:58

but I can't find anything with "substrate"

Simply Staking Community

25 Jan 2023 10:52

tried to restart it and remove orphans as well and it did nto help

Simply Staking Community

25 Jan 2023 10:24

do i need to upgrade to 1.3.0 before i can upgrade to this version?

Simply Staking Community

24 Jan 2023 13:26

Dear PANIC users, gm! as it was announced on the Bare Metal Podcast, for the time being you won't see many updates coming your way as the team is focused on other exciting projects. That being said, we've built a solid working foundation throughout these 2 years that the community can pick up on if deemed useful, therefore if anyone wishes to contribute they are welcome to do so.

We will be assisting along the way, therefore if you have any questions or willing to contribute kindly reach out to @itsciccioo or @dylan_galea

Bare Metal Podcast: Improved Cosmos Governance & Power of Panic | Francesco | Simply Staking https://www.youtube.com/watch?v=J_oKQNTdcWE&t=98s

Simply Staking Community

23 Jan 2023 08:51

This would work assuming that the sweeper script is running on your compromised device

Simply Staking Community

23 Jan 2023 01:09

Hi! I have my metamask account compromised with a sweeper bot and I have 800 glmr staking on simply staking 3. If I withdraw my staking funds the bot will send them to another wallet. Is there any way you can help me? please.

Simply Staking Community

20 Jan 2023 19:01

It depends on whether the configuration is right and whether panic is actually managing to get data. Its important to note that we have not updated the polkadotjs api libraries for a while, so it might be that panic is not compatible any more with Substrate

Simply Staking Community

12 Jan 2023 13:24

Hey, Moonbeam definitely not affected!

Simply Staking Community

12 Jan 2023 10:06

It should work, let me know tho

Simply Staking Community

11 Jan 2023 21:02

Please can any one help me resolve why I keep getting missing blocks here started noticing this recently keeps missing blocks at intervals thereby reducing my uptime

Simply Staking Community

10 Jan 2023 12:15

@Eleuname84 you are in fact right. That alert is non-configurable since it an error alert designed to indicate an error internal to PANIC, and not regarding your node.

Simply Staking Community

10 Jan 2023 12:01

I have 15 threshold alerts and 11 severity alerts.. no substrate

Simply Staking Community

10 Jan 2023 12:00

The alert config should show up in that list

Simply Staking Community

10 Jan 2023 12:00

Are you editing the configuration of a substrate-based chain?

Simply Staking Community

10 Jan 2023 11:59

In what way can't you find it? Is it not visible?

Simply Staking Community

10 Jan 2023 11:55

You can amend alert configurations via the PANIC UI, given that you are using the most recent PANIC version.