PLEASE READ - Effective 2300 UTC 6/9, we will begin the process of removing all self stake from our nodes. We will become inactive. Please redelegate ASAP.

Joined March 2022
28 Photos and videos
95% of funds returned; remaining 5% will be sent today. Tx hashes are in this thread. Utilizing the LP bug was done using the public user interface of app.osmosis.zone/pools. No unauthorized access to systems was used. Our team member learned of the LP bug from Reddit.

2
84CDA57157C05835C2F4117DAA4474E2954DF555A9B82E0A4CD4C9F1923DA13C
1
We have never been a validator on Osmosis, and had no part in the v9 Nitrogen upgrade, including any development of code. In 72 hours, we will be closing this account.
1
1
FireStake | Validator retweeted
Want to say huge thank you to the @stake_fire team for being the first exploiters to come forward on their own accord and cooperate to return funds to the Osmosis community. I believe their action inspired further exploiters to pursue the similar line of action.
Once again, we are actively working with @sunnya97 to return all funds. The process has already begun.
33
20
218
We have begun the unbonding process. Working through nodes now. Please redelegate.
9
2
18
We have been removing our self stake on our Sifchain, Provenance, and Evmos nodes, but for some reason it doesn't seem to throw us into inactive. Will continue to do the others. mintscan.io/evmos/validators…
2
4
Our understanding was that removing out self stake below the min required would put us inactive. It appears that isn't happening. Is anybody familiar with this?
2
5
FireStake | Validator retweeted
Notional still believes that @stake_fire team committed a terrible wrong - this is undoubtably the case. But they do appear to be committed to returning all stolen funds and removing all self stake from their nodes. This is the right move.
1
1
12
Once again, we are actively working with @sunnya97 to return all funds. The process has already begun.
They stepped forward themselves.
7
26
Dear @osmosis community, many of you know about the Osmosis LP bug that occurred yesterday. In disbelief of it being real, two members of @fire_stake started testing to see if the bug existed, testing grew into a temporary lapse in good judgment, and...
154
100
581
to return the funds as soon as possible. We’re also working with the Osmosis team to encourage anyone else who took advantage of this situation to please come forward and return funds. You’re welcome to come to us, and we can help act as a liaison. We need to make this right.
19
8
199
Please see here for an update. We will be removing all self stake at 2300 UTC today. We will become inactive. Please redelegate ASAP. We will NOT be in cosmos ecosystem x.com/stake_fire/status/1534…

We will NOT move forward with the xfer of key ownership based on @ConsensusOne suggestion. Effective 2300 UTC 6/9, we will begin the process of removing all self stake from our nodes. We will become inactive. Please redelegate ASAP.
7
Replying to @osmosis @fire_stake
Please see here for update. We will be removing all self stake from nodes at 2300 UTC today. x.com/stake_fire/status/1534…

We will NOT move forward with the xfer of key ownership based on @ConsensusOne suggestion. Effective 2300 UTC 6/9, we will begin the process of removing all self stake from our nodes. We will become inactive. Please redelegate ASAP.
1
1
We will NOT move forward with the xfer of key ownership based on @ConsensusOne suggestion. Effective 2300 UTC 6/9, we will begin the process of removing all self stake from our nodes. We will become inactive. Please redelegate ASAP.
2
4
13
Per @ConsensusOne suggestion, we will not continue with the transfer to @AbraTusz and @kadabra_moon We will begin unbonding our nodes soon. Will update with timeline. Please redelegate ASAP.
Replying to @gadikian
We believe that @stake_fire should immediately remove their self-stake from all validators they operate, this would immediately remove their nodes from the active set without a slashing event.
1
3
We will be transferring validator ownership to @Kadabra_Moon effective immediately. FireStake will no longer operate in the Cosmos ecosystem. Here is the formal agreement: gateway.pinata.cloud/ipfs/Qm…

15
6
36
Hi all, we’ve heard your feedback. We plan to exit operations in one of two ways: 1) Transition our nodes to trusted providers via key exchange 2) Start the unbonding process We will update once the plan is finalized.
18
5
65
FireStake | Validator retweeted
They stepped forward themselves.
19
10
282