Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Utility][Documentation] Add a README section on how to use the portal as a servicer #962

Open
5 tasks
adshmh opened this issue Aug 2, 2023 · 0 comments
Open
5 tasks
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@adshmh
Copy link
Contributor

adshmh commented Aug 2, 2023

Objective

Add a section to the documentation (in utility and/or localnet docs) to describe how to create a Pocket Portal account and use it as a servicer for sending relays as part of development/testing.

Origin Document

Remove the need for running an Ethereum (or any other relay chain) node when sending relays and verifying the results as part of development/testing work.

Config section from #869 shows the need for this:

image

Goals

  • Streamline development/testing process by following a a simple set of instructions.

Deliverable

  • Updated documentation and/or a short video

Non-goals / Non-deliverables

  • Instructions/support on running an Ethereum (or any other relay chain) node.

General issue deliverables

  • Update the appropriate CHANGELOG(s)
  • Update any relevant local/global README(s)
  • Update relevant source code tree explanations
  • Add or update any relevant or supporting mermaid diagrams

Creator: [@adshmh]
Co-Owners: [@Olshansk]

@adshmh adshmh added the documentation Improvements or additions to documentation label Aug 2, 2023
@adshmh adshmh added this to the M3: Pocket RoS (Relay or Slash) milestone Aug 2, 2023
@adshmh adshmh self-assigned this Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: Backlog
Development

No branches or pull requests

1 participant