Skip to content

Conversation

@otaviovin
Copy link
Contributor

This Pull Request improves the examples/issue_asset.py example by making it more educational, consistent with the existing examples, and aligned with the official Stellar Python SDK documentation.

Summary of Changes:

  • Added a comprehensive header docstring describing the purpose and workflow of asset issuance on the Stellar Testnet.
  • Included installation and execution instructions for running the example (pip install stellar-sdk and python issue_asset.py).
  • Added detailed step-by-step comments explaining how to create, trust, and distribute a custom asset.
  • Documented the expected output to help developers verify successful trustline creation and asset transfer.
  • Improved readability, formatting, and consistency with other examples in the repository.
  • Added guidance and best practices about separating issuing and distribution accounts for better security.

Purpose:

This enhancement helps developers understand how to:

  1. Connect to the Stellar Testnet using the Python SDK.
  2. Create and define a new custom asset with the Asset class.
  3. Establish a trustline between the issuing and distribution accounts.
  4. Send the newly issued asset from the issuer to the distributor.
  5. Follow Stellar’s recommended asset issuance model for secure token management.
    By following this example, developers can easily learn the full process of issuing, distributing, and managing assets on the Stellar network.

References:

These changes make the issue_asset.py example self-contained, easy to follow, and consistent with other educational examples in the py-stellar-base repository.
It serves as a practical guide for developers learning how to create and distribute custom assets securely using the Stellar Python SDK on the Testnet.

@codecov
Copy link

codecov bot commented Nov 12, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.97%. Comparing base (fba85a5) to head (93bf895).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1099   +/-   ##
=======================================
  Coverage   97.97%   97.97%           
=======================================
  Files         262      262           
  Lines       14799    14799           
=======================================
  Hits        14499    14499           
  Misses        300      300           
Flag Coverage Δ
unittests 97.97% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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

Successfully merging this pull request may close these issues.

1 participant