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

Explain the process of charging Native CSPR Tokens and the role of Session Code #1497

Open
Tracked by #1495
devendran-m opened this issue Dec 19, 2024 · 0 comments
Open
Tracked by #1495

Comments

@devendran-m
Copy link
Contributor

devendran-m commented Dec 19, 2024

User Story:

As a developer working with the Casper Network,
I want a clear and detailed explanation in the documentation on how native CSPR tokens can be charged from one account, including the role of session code in the process,
so that I can implement token transactions accurately and understand the underlying requirements for executing them within an account's context.

Acceptance Criteria:

  • The documentation includes a step-by-step guide on charging native CSPR tokens from one account.
  • The guide explains the prerequisites, such as account setup, permissions, and requirements for session code.
  • The process for using session code within the account’s context to execute token transactions is clearly described.
  • Detailed code snippets and examples demonstrate how to implement the process, with annotations explaining the role of session code.
  • Visual aids, such as flowcharts or diagrams, illustrate the transaction flow, highlighting where and how session code is used.
  • Common issues, best practices, and troubleshooting steps for token charging and session code execution are documented.
  • Developers unfamiliar with the process can successfully implement it by following the documentation without needing additional guidance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant