[Utility] Design how Chain/Service IDs should be described - Githubissues

pokt-network / pocket

Official implementation of the Pocket Network Protocol v1

https://pokt.network

MIT License

61 stars 33 forks source link

[Utility] Design how Chain/Service IDs should be described #831

Open adshmh opened 1 year ago

adshmh commented 1 year ago

Objective

Design how Chain/Service IDs are

Origin Document

Part of work on #754

Goals

Clear definition of what a Chain/Service ID is

Deliverable

[ ] Updated README and all other documentation
[ ] Resolve all TODO comments related to this issue
[ ] Enable chain specific rewards & configurations

Non-goals / Non-deliverables

General issue deliverables

[ ] Update any relevant local/global README(s)
[ ] Update relevant source code tree explanations
[ ] Add or update any relevant or supporting mermaid diagrams

Testing Methodology

[ ] Task specific tests or benchmarks: make ...
[ ] New tests or benchmarks: make ...
[ ] All tests: make test_all
[ ] LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md
[ ] k8s LocalNet: verify a k8s LocalNet is still functioning correctly by following the instructions here

Creator: @adshmh Co-Owners: @Olshansk

Olshansk commented 1 year ago

@adshmh We'll do this one together and I also added this deliverable:

- [ ] Enable chain specific rewards & configurations