Table of Contents |
---|
...
...
https://how-to-use-stellar-laboratory.readthedocs.io/en/latest/token.html
Here are the steps involved:
- Step 1: Create 2 accounts (One for Issuance, another for Distribution).
- Step 2: Execute a change of trust transaction from Distribution to Issuance.
- Step 3: Create the token.
Step 1: Create 2 accounts
You will need TWO (2) accounts. One to act as the issuer and one to act as the distributor account.
Create two and save them to your local computer. Make sure you clearly label somehow one as issuer and one as distributor. For me, I saved the data as “issuer-test-account-Stellar.txt” and “distributor-test-account-Stellar.txt”.
Using the testnet faucet and fund both accounts with RIA. Make sure that the slider in the top right is set to “test”.
Go to Create an account for more details.
Step 2: Change the trust between the two accounts.
For us to issue the token, we need to issue a change trust transaction between the distribution account and the issuance account. You can do that through this handy web interface.
Using the accounts you have created, change trust using the distribution account aimed at the issuing account:
Submit this using your private key
And you’ll come to this final screen:
If all goes well, you’ll see a JSON response similar to above.
Step 3: Creating the Actual Token
This step is not intuitive: the token creation is done by sending a payment from the issuing account to the distribution account, denominated in the new token. This is why we had to change trust to begin with — the distribution account issued a statement of trust that this “BLOCKSIMPLE” thing was the real deal.
Go to Transaction Builder, this is what that operation looks like:
If all goes well, you’ll see a successful transaction like so:
Ok, so now we have issued 5000 BLOCKSIMPLE tokens on the test net. Woohoo!
Congratulations! You just issued your first ever custom token!
Source: https://hackernoon.com/how-to-make-a-custom-token-on-stellar-ae5296512a2e
Custom Tokens on HLF example 1 - for ERC20 wallet
...
Digital Assets Ecosystem Will Be Powered By End-To-End Standards Vipin |
---|
These tokens are often marooned in platforms with no way to interwork with other tokens or payment systems or existing financial market infrastructure. Releasing the tokens from their current prisons and allowing them to interoperate will unleash business value. IWA standards are meant to be platform and technology neutral and not limited to blockchain or distributed ledger technologies. IWA focuses on the interoperation of value represented by tokens, by addressing three layers of the problem. Each layer is at a different level in the business stack. Starting from the base,
Token templates can make it easier for business analysts to model tokens and behaviors: For example a token that can be minted and transferred has behaviors like mint and transfer. A business analyst models a token using a graphical front end, which in turn generates artifacts that span business specifications and code. This creates a seamless way to model the token from concept to code. Templates can be developed by domain Multi-party contracts can leverage existing systems like CDM IWA will benefit by looking at work that has already been done in the CDM or the Common Domain Model. CDM although first developed by ISDA, the International Swaps and Derivatives Association is now open source. CDM is being generalized for all types of contracts and is platform neutral. The same model can be used for other domains ISDA CDM fact sheethttps://www.isda.org/a/z8AEE/ISDA-CDM-Factsheet.pdf Create standards for market -driven analysis of contractually shared data for regulatory reporting and extraction of business value. This analysis will use privacy preserving methods. One can assume zero-knowledge proofs or homomorphic techniques. In this too, existing standards need to be looked at and integrated into the IWA. Roles will be mapped to sets of token behaviors identities can be mapped to roles by: automatic or manual assignments |
Monetize and Tokenize Data
...