Official Plugins strategies

[xellos00]

• Parents: Release Planing & Managements #207

---

Checklist

• New Feature for the SVC/Plugin
• New Feature for CI/CD
• Enhancement on Vatz
• Others(etc. e.g, documentation,...)

---

Please describe, what it's about or related Problem with

A clear description of what feature need to be developed or enhanced in Vatz

as we discussed earlier in previous meeting
we need to establish our official plugins to have following responsibilities

• Description for VATZ official plugins
• VATZ dev team's policies on official plugins
• Which plugins will be our officials.

Describe the output that you are expecting for above

A clear and concise description of what you expect to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Let's have each poll to find right direction.

[xellos00]

VATZ dev team's policies on official plugins

[xellos00]

Which plugins will be our officials.

• excel

num in Cap	Candidate	CAP (by 8/10/2022)	Number of Validator	Assignee
1	Bitcoin (BTC)	$464,094,999,077
2	Ethereum(ETH	$229,085,667,636
3	Tether(USDT)	$66,778,180,270
4	USD Coin(USDC)	$53,931,533,227
5	BNB(BNB)	$53,324,486,110
6	XRP(XRP)	$18,700,890,949
7	Cardano(ADA)	$18,211,393,037
8	Binance USD(BUSD)	$17,790,529,997
9	Solana(SOL)	$14,962,674,781
10	Polkadot(DOT)	$10,492,023,456
11	Dogecoin(DOGE)	$9,483,973,046
12	Avalanche(AVAX)	$8,290,676,349
13	Dai(DAI)	$7,579,824,198
14	Polygon(MATIC)	$7,537,831,026
15	Uniswap(UNI)	$6,916,746,185
16	Shiba Inu(SHIB)	$6,817,060,297
17	TRON(TRX)	$6,541,524,208
18	Wrapped Bitcoin(WBTC)	$5,927,450,330
19	Ethereum Classic(ETC)	$5,267,576,609
20	UNUS SED LEO(LEO)	$4,503,457,498
21	NEAR Protocol(NEAR)	$4,420,425,735
22	Litecoin(LTC)	$4,385,852,278
23	Chainlink(LINK)	$4,285,579,785
24	FTX Token(FTT)	$4,272,245,704
25	Cronos(CRO)	$3,865,904,709
26	Cosmos(ATOM)	$3,412,149,117
27	Stellar(XLM)	$3,169,779,777
28	Flow(FLOW)	$3,136,225,894
29	Monero(XMR)	$3,025,297,370
30	Bitcoin Cash(BCH)	$2,743,558,783
31	Algorand(ALGO)	$2,539,920,513
32	VeChain(VET)	$2,392,085,857
33	ApeCoin(APE)	$2,183,648,900
34	Filecoin(FIL)	$2,172,457,201
35	Internet Computer(ICP)	$2,161,005,409
36	Decentraland(MANA)	$1,992,705,025
37	The Sandbox(SAND)	$1,738,464,180
38	Tezos(XTZ)	$1,716,088,232
39	Hedera(HBAR)	$1,680,061,929
40	Theta Network(THETA)	$1,610,761,718
41	Aave(AAVE)	$1,579,533,290
42	Elrond(EGLD)	$1,551,470,254
43	Axie Infinity(AXS)	$1,550,226,072
44	Quant(QNT)	$1,548,771,180
45	EOS(EOS)	$1,294,701,647
46	TrueUSD(TUSD)	$1,217,862,058
47	Bitcoin SV(BSV)	$1,192,326,469
48	Zcash(ZEC)	$1,175,557,026
49	OKB(OKB)	$1,150,053,749
50	Helium(HNT)	$1,081,380,701
51	Maker(MKR)	$1,071,219,164
52	KuCoin Token(KCS)	$1,058,527,919
53	Fantom(FTM)	$1,033,504,194
54	The Graph(GRT)	$1,002,699,620
55	IOTA(MIOTA)	$987,072,437
56	THORChain(RUNE)	$978,428,454
57	BitTorrent-New(BTT)	$951,083,926
58	Pax Dollar(USDP)	$944,725,411
59	Chiliz(CHZ)	$913,239,196
60	eCash(XEC)	$908,220,150
61	Klaytn(KLAY)	$875,509,140
62	Lido DAO(LDO)	$863,512,897
63	Neo(NEO)	$828,251,048
64	USDD(USDD)	$745,042,714
65	Curve DAO Token(CRV)	$729,506,942
66	Neutrino USD(USDN)	$698,263,835
67	Basic Attention Token(BAT)	$686,360,296
68	Huobi Token(HT)	$678,845,897
69	Waves(WAVES)	$669,657,855
70	Stacks(STX)	$656,307,973

[xellos00]

Official plugin
@skonhwang @meetrick @Choi-Jinhong @heejin-github
COSMOS- Main assignee who take all responsibility for this plugin.

Please, put a vote or select assignees for this plugin by end of this week by 2022-08-22.

[heejin-github]

Cosmos Plugin

• maintainer : @heejin-github

• monitoring item

  • chain dependency : up, block height, peer count
  • hwstat : cpu, mem, disk

• module : one module or separated module.

  • separated module based on Vatz SDK.

• Build and Running

  • Build : Make
  • Running : pm2

• github repo : https://github.com/dsrvlabs/vatz-plugin-cosmos

  • grab current development in this repo.

• additional item

  • integrate official plugin into vatz
  • initialize vatz plugin with vatz cli command
    • ex. ) vatz plugin init name port -> make initial plugin with given name and port.

[xellos00]

Cosmos Plugin

• maintainer : @heejin-github

• monitoring item

  • chain dependency : up, block height, peer count
  • hwstat : cpu, mem, disk

• module : one module or separated module.

  • separated module based on Vatz SDK.

• Build and Running

  • Build : Make
  • Running : pm2

• github repo : https://github.com/dsrvlabs/vatz-plugin-cosmos

  • grap current development in this repo.

• additional item

  • integrate official plugin into vatz

  • initialize vatz plugin with vatz cli command

    • ex. ) vatz plugin init name port -> make initial plugin with given name and port.

@heejin-github
Let's have a meeting to settle all the details how we are going to manage those repos in common in this week.

[heejin-github]

Cosmos Plugin

• maintainer : @heejin-github

• monitoring item

  • chain dependency : up, block height, peer count
  • hwstat : cpu, mem, disk

• module : one module or separated module.

  • separated module based on Vatz SDK.

• Build and Running

  • Build : Make
  • Running : pm2

• github repo : https://github.com/dsrvlabs/vatz-plugin-cosmos

  • grap current development in this repo.

• additional item

  • integrate official plugin into vatz

  • initialize vatz plugin with vatz cli command

    • ex. ) vatz plugin init name port -> make initial plugin with given name and port.

@heejin-github Let's have a meeting to settle all the details how we are going to manage those repos in common in this week.

OK! Let me summarize my opinion for cosmos plugin.
please let me know your question or any opinion for cosmos plugin first.
then, I'll setup the meeting and prepare these items for our meeting.

Basically, I'm going to start cosmos plugin maintaining as below.

use already existed plugins, method, or systems first.

1. Create new repo for vatz-plugin-cosmos
2. Collect developed plugins into vatz-plugin-cosmos
   • exist one : up, block-height, hwstat(cpu, mem, disk)
   • need develop : peer count
3. All plugins will be based on the Vatz SDK and have its own module.
4. Build all plugins with make
5. Run and manage plugins with pm2

I'll proceed to the next step when all of the above items are completed.

Find improvements and newly developments, if needed.

1. Check any problem to monitor cosmos node with current plugins.
2. Check if any further monitoring items required.
3. Check for unnecessary monitoring items in current plugins.
4. Find enhancement for Build and Run.
5. Decide whether cosmos plugin integrate into Vatz and CLI interaction.

[xellos00]

@heejin-github
I would like to have a meeting for following agenda
I have questions

• who are the main assignee(code owner) for 2 repos?
  • COSMOS
  • Linux or Machine checker
• How to Guide & documents
• Release Plan & version planning
• CI /CD

Are you available for next Monday 1:00 PM?

[heejin-github]

@heejin-github I would like to have a meeting for following agenda I have questions

• who are the main assignee(code owner) for 2 repos?

  • COSMOS
  • Linux or Machine checker

• How to Guide & documents

• Release Plan & version planning

• CI /CD

Are you available for next Monday 1:00 PM?

OK, I'll send meeting invitation for you.

[xellos00]

#Agenda & Post Actions

1. Repos, Code-Owner @heejin-github

(same code hierarchy)

• (SDK) COSMOS Hub (vatz-plugin-cosmoshub)
• (SDK) Linux (hd-common)

2. Documentation (TODOs)

• How to guide, e.g. install, start, end.
• How to communicate VATZ
  • proper work
  • error
    • troubleshoot

3. Release Plan & Version planning

(TBD)
Release

v1.0.x
1 => v1 or v2
0 => 2 ,3,4,
x => hot fix

--

VATZ | cosmos | linux

• 1.0 1.0. 1.0

---

• 2.0 2.0. 2.0

4. CI

• When PR raised
  • Test
  • Build
• Release
  • Release tag

[xellos00]

5. Run and manage plugins with pm2

@heejin-github
Can you create a issue with above or group with single tag

[heejin-github]

5. Run and manage plugins with pm2

@heejin-github Can you create a issue with above or group with single tag

I will create issues for each task, as a child issue of #236

[xellos00]

Everything tasks are transferred to

• Vatz Official Plugins Developments & Managements #241