---
# System prepended metadata

title: Untitled

---

---
Governance Committee Issue #14
---

<!--### Before raising a Topic of Discussion (ToD)

<!--Candidate topics of discussion should first be discussed with other members so that there has been a degree of peer review before invoking this formal process.  Discussion can take place in any appropriate collaboration channel or tool.  Members must make reasonable effort to reach out to and at least inform all parties impacted in the candidate ToD.

<!--Topics of discussion are normally raised in ‘business as usual’ agenda-setting process for the governance body relevant to the topic.  Each committee, body or business unit has a membership representative who may be contacted in order to table the item in the agenda/decision-making process operated by that unit. 

<!--### When to Raise a Formal ToD

<!--ToD’s may be raised where:
<!--*   there is no obvious accountable/responsible body already in existing co-op governance to address the candidate topic, <!--or
<!--*   the ToD is deemed to be of ‘board level significance’<sup>[3](#myfootnote1)</sup> and is not already on the Co-op Board agenda, or
<!--*   the topic has already been submitted, but the proposer and a significant number of peers feel that the topic has not been properly addressed and requires escalation as a dispute or unresolved matter for arbitration and final settlement.

**Title:** <!--short (50 char max) but informative -->
**Description** <!--of ToD (no more than 1 page) -->
Contractor attempted to deposit REV into the Co-op staking pool, but mistakenly sent to an address with no know private key. 

**Context**:  <!--link to previous discussion / documents and history of previous submission and outcomes. -->

- Block Explorer (revdefine.io) shows the errant [transaction](https://revdefine.io/#/blocks/393850c323279f68b999901db14d3a10837bbc2dbecfbb819bc3081e80180fd6/deploy/8dc6edec4c3572fb5fedcb74c7c9aeafad1802a11496073dbfff25adc5eb65ea2e6f84477375c912135dd1cade362b6cf60fa9920f2db37e7eb05b969d11bef91b) being sent to address 1111rsk1gRf3HJeon9kdndvJ5WQGqxmuRzfjBn8eTtxz5U9E1Yke6 instead of Co-op Staking pool 11112PvkcBG2NYXheMA3g8E6xiTNhBJguT9TncZPPmNfXg2Npb1kRU.
- Screenshot of my Discord communication with the contractor, where we caught the error:
![Gov-Cmte-issue14-recover-stake](https://user-images.githubusercontent.com/3330502/125884892-b5167ff3-c138-42a1-a742-ea368e8378f7.png)
- Block Explorer (revdefine.io) [history](https://revdefine.io/#/revaccounts/1111rsk1gRf3HJeon9kdndvJ5WQGqxmuRzfjBn8eTtxz5U9E1Yke6) of the wallet receiving the errant transaction. Note that the balance has remain constant since the transaction and that the tokens were sent only 33 blocks before the contractor [successfully](https://revdefine.io/#/blocks/7312d312cff17c627889ba9cd32b221b75c1c8b767d70fa55580677f158dfbbe/deploy/37d2e131edf5f14ab8abbac4c0c4c7636fb24b3cbe458c31b84b5cbd95f1070b523f4dfff6f1b0c31acfd99f42e284c83d9ca66cf3812edd324da6bed7c124fe1c) deposited to the Co-op staking pool.

**Impact statement**: <!-- on co-op ongoing costs, effort, third party / external impact, reputation, external valuation etc.  (Must include timing of impacts, quantified wherever possible - link) -->
Moving REV from the errant wallet to the Co-op staking pool will not affect any other wallets.

**Benefits statement** <!--(Must include timing of benefits, quantified wherever possible - link) -->
Restoring the errant REV to the Co-op staking pool will recover REV which would otherwise remain unusable because the wallet private key is unknown.

**Implementation** <!--Costs, Plan and Risk Assessment  (links) -->
Adjust the hard fork balances to debit 3499999.5 REV from 1111rsk1gRf3HJeon9kdndvJ5WQGqxmuRzfjBn8eTtxz5U9E1Yke6 REV and credit 3499999.5 REV to the Co-op staking pool 1111YVVUNB3VXV1VuJr1cQstfpP6CcCgaEDL6Vyordn5ynHTxiVEe will have no impact on other REV addresses.

**Time frame** <!--for discussion - allowing reasonable time to adjust the ToD, if necessary, and for the proposed consultation _mechanism_ -->
To be implemented during Hard Fork 1

**Governance Bodies** to be advised:  e.g. Board, Finance and Audit, or Governance (in the case of a governance change)
Governance Committee

<!--**Mechanism** proposed for expressing collective sentiment / making decision, including pre and post consultation.  (This should be discussed with the Governance Committee) -->
<!--**Change Log** to record any significant changes to the ToD  (what, who, why, when etc) -->
