Skip to content
This repository has been archived by the owner on Aug 24, 2023. It is now read-only.

Deciding Benchmark: TPS & Bandwidth #99

Open
fuxingloh opened this issue Sep 14, 2022 · 1 comment
Open

Deciding Benchmark: TPS & Bandwidth #99

fuxingloh opened this issue Sep 14, 2022 · 1 comment
Labels
area/ain issues/pr that requires changes on the DeFiCh/ain codebase. area/meta kind/feature New feature request needs/triage Waiting for triage to be accepted

Comments

@fuxingloh
Copy link
Contributor

What is the TPS we want to establish for Meta Chain? What kind of network bandwidth is required to run the chain? Or network growth rate. Since we're using Native Chain validators, the decision has to be made as a whole and consider Native Chain stats and chain parameters.

@fuxingloh fuxingloh added kind/feature New feature request area/meta area/ain issues/pr that requires changes on the DeFiCh/ain codebase. labels Sep 14, 2022
@defichain-bot
Copy link
Member

@fuxingloh: Thanks for opening an issue, it is currently awaiting triage.

The triage/accepted label can be added by foundation members by writing /triage accepted in a comment.

Details

I am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

@defichain-bot defichain-bot added the needs/triage Waiting for triage to be accepted label Sep 14, 2022
@fuxingloh fuxingloh changed the title Deciding Benchmark: TPM & Bandwidth Deciding Benchmark: TPS & Bandwidth Sep 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/ain issues/pr that requires changes on the DeFiCh/ain codebase. area/meta kind/feature New feature request needs/triage Waiting for triage to be accepted
Projects
None yet
Development

No branches or pull requests

2 participants