Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • B BotC Overview
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 47
    • Issues 47
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • faircoop
  • BankOfTheCommons
  • BotC Overview
  • Issues
  • #107
Closed
Open
Created Feb 04, 2021 by Ramaxx@ramaOwner

Continuity of Ethereum operations

Ethereum operations require manually recharging the payout address (incorrectly called "hot-wallet") each time a user needs to cashout.

As announced on #106 (closed), I'm dropping responsibility of manually moving funds to payout address.

There is a proposal of having @santi take care of these recharges.

This will break the proposed transition steps which would guarantee a smooth hand-over to the new role as described on the wiki page: BotC-Tech-role-description

It must be decided by the assembly, or whoever wants to make him/herself responsible for taking this step.

From my side, I can guarantee I won't touch the cryptoservers or their wallets anymore unless there is any technical issue on the server side which could produce downtime, which will be properly notified in advance to the relevant teams (probably core and imMunitech). That is, I will only take care of the servers and daemons to remain running until my credentials get finally removed. Of course backups are part of the sysadmin responsibility which I will take care of.

The assembly can only trust my word that I don't keep a copy of any private keys anywere else other than the cryptonodes and the backup server, infrastructure belonging to BotC, under administrative access by @enric. After the private keys get regenerated (as explained on #108), it will be 100% guaranteed that any unauthorized movement of funds couldn't be linked to the leaving admin.

In other case, from the moment it's decided that someone else (in this case @santi) will become ETH node operator, I will automatically become exempt of any responsibility related to any sort of issues with funds (blocked, lost or stolen) from any of the cryptonodes.

Edited Feb 04, 2021 by Ramaxx
Assignee
Assign to
Time tracking

gitlab project and software management by fairkom.eu - more open source web apps at fairapps.net