Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • Minds Backend - Engine Minds Backend - Engine
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 282
    • Issues 282
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 16
    • Merge requests 16
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • MindsMinds
  • Minds Backend - EngineMinds Backend - Engine
  • Issues
  • #2397
Closed
Open
Issue created Jul 29, 2022 by Ben@benhayward.benDeveloper

Set up SKALE mirror in staging

Goal

Have SKALE mirror running in staging.

What needs to be done

  • Config values need to be set up.
  • Alter Cassandra table (do we want to alter views too?).
  • Users will need to be decided/set up
  • A sufficient supply of tokens and sFuel will need to be sent to the users configured for:
    • balance_sync_user_guid - Needs to be able to sync the entire network worth of offchain tokens.
    • sfuel_distributor_user_guid - Needs to have enough sFuel to distribute when requested by all custodial user wallets.
    • boost_escrow_user_guid - Needs enough balance to cover existing boosts in queue .
    • withdrawal_escrow_user_guid - Needs enough balance to cover existing withdrawals in the queue.
    • rewards_distributor_user_guid - Needs enough balance to cover Rewards
  • Bootstapping development env docs should be followed as it's more or less the same process for production.
  • Cronjob / runner needs deploying for the balance sync job.
  • When running balance sync job - it WILL take a significant amount of time (possibly up to 24 hours).

Everything will need thorough testing, balance sync stream will need checking periodically.

QA

Test SKALE mirror in staging - there's guidance of testing functionality on sandboxes here !1083 (closed)

UX/Design

N/A

Personas

Internal use presently so we can monitor and assess.

Experiments

No experiments, but 2 feat flags to control envs

  • engine-2350-skale-mirror
  • engine-2360-skale-balance-sync

Acceptance Criteria

  • SKALE mirror running in production.
  • Configured correctly.
  • Balances staying in sync.

Definition of Ready Checklist

  • Definition Of Done (DoD)
  • Acceptance criteria
  • Weighted
  • QA
  • UX/Design
  • Personas
  • Experiments
Edited Jul 29, 2022 by Ben
Assignee
Assign to
Time tracking