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

Integrate Akash Network as a Payment Provider #37

Open
jay-dee7 opened this issue Sep 27, 2021 · 0 comments
Open

Integrate Akash Network as a Payment Provider #37

jay-dee7 opened this issue Sep 27, 2021 · 0 comments
Labels
enhancement New feature or request needs-triage This label refers to a non-final decision on implementation, when an important feature/bug is added P1 P1 label is used for this that we see of highest priority. Critical bugs, security issues, etc

Comments

@jay-dee7
Copy link
Member

jay-dee7 commented Sep 27, 2021

Since we deploy our backend on Akash, it would be nice to have Akash Network as one of our payment methods. Users should be able to pay for container image hosting using Akash, which would cover their storage costs as well. It's easy enough to enable transactions on a cosmos based project (which Akash is), however there might be few challenges:

  • What kind of wallet to choose (single or multi-sig)
  • How do we keep the recipient wallet secure
  • How do we make it more transparent (revenue/burn will be publicly available)
  • How do we setup an automated job (to some degree) so that we can co-operate between multiple blockchains (like Sia, Akash, IPFS, etc)

Reference Documentation:

@jay-dee7 jay-dee7 added enhancement New feature or request P1 P1 label is used for this that we see of highest priority. Critical bugs, security issues, etc labels Sep 27, 2021
@jay-dee7 jay-dee7 added this to To do in OpenRegistry - Roadmap via automation Sep 27, 2021
@jay-dee7 jay-dee7 added the needs-triage This label refers to a non-final decision on implementation, when an important feature/bug is added label Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs-triage This label refers to a non-final decision on implementation, when an important feature/bug is added P1 P1 label is used for this that we see of highest priority. Critical bugs, security issues, etc
Projects
Status: Backlog
Development

No branches or pull requests

1 participant