nspcc-dev/neofs-dev-env

Actualize wallets

Open

#267 opened on Jun 19, 2023

View on GitHubContributor guide
 (3 comments) (1 reaction) (0 assignees)Makefile (25 forks)auto 404
I4S3U4discussiondocumentationhelp wanted

Repository metrics

Stars
 (10 stars)
PR merge metrics
 (PR metrics pending)

Description

As I understand we have some copypasted accounts for years (https://github.com/nspcc-dev/neofs-dev-env/blob/9e092f3f8e0b27d4cbf67aaf53137f61ccb276b6/services/chain/node-wallet.json#L23-L48? multi-sig? what? @roman-khimov, @AnnaShaleva).

Also, some of them have labels while some do not. I would expect a perfect repo with wallets to be fully labeled. Wallet naming also bothers me (node-wallet.json (what wallet? neo-go? neofs-node?)/wallet.json).

Contributor guide

Research direction
Examine the wallet files in the repository, identify inconsistencies in labeling and naming, and propose a standardized format.
Tech stack
goshell
Domain
backendinfrastructure
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitNeoFS basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60