Open miohtama opened 2 years ago
I'd really like to see an update on this! Seems pretty important to me as a developer!
Hello! Thank you for your suggestion. The tokens page only describes the transactions' format. It can be easily integrated into any script by simply converting the input parameters into valid hex. I will leave this issue open for future references
I also think it is something that could improve the docs a lot. The ones with transaction schemas. For example, for a developer who lands on docs first time, this doesn't tell much at first sight:
IssuanceTransaction {
Sender: <account address of the token manager>
Receiver: erd1qqqqqqqqqqqqqqqpqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzllls8a5w6u
Value: 50000000000000000 # (0.05 EGLD)
GasLimit: 60000000
Data: "issue" +
"@" + <token name in hexadecimal encoding> +
"@" + <token ticker in hexadecimal encoding> +
"@" + <initial supply in hexadecimal encoding> +
"@" + <number of decimals in hexadecimal encoding>
}
IMO, they usually want tabs with examples of such transactions in JS SDK, Python SDK, and maybe others too. With a clear description of what should be imported from which library, with the link to the GitHub repository. Plus, to the examples repository.
The ESDT tokens chapter details how to issue out a new token.
https://docs.elrond.com/developers/esdt-tokens/#issuance-of-fungible-esdt-tokens
This documentation is very outlining and is not helpful enough for outside readers - as it has gaps to let the user to understand the complete steps to issue and manage tokens.
It does not cross-reference to any tooling (JavaScript, Python erdpy, Rust, how to issue out a token)
It does not refer to have source code, or related, how the tokens are managed, or any detailed discussion about token standards - for example it asks to community feedback, but does not discuss how to give such feedback and where relevant discussion should take a place