Learning Development Concepts on Aptos

I am very curious to learn about the move language, I am really thankful for this guide.

6 Likes

Noted well

9 Likes

it is awesome

7 Likes

Where can I find it

8 Likes

thats interesing! Thank you for sharing this buddy!

6 Likes

A good work thank s sir

6 Likes

the Aptos Ecosystem that have focused on education and learning concerning the Aptos Move environment
 aptos is great

9 Likes

I literally thought of learning the move language to contribute to the Aptos ecosystem.
Looking forward to more future potentials.

4 Likes

I’ve learnt HTML, currently learning CSS , Am I on the right track?

1 Like

Of course, yes.

3 Likes

Good information

4 Likes

Hello all,

I’ve recently gravitated to Aptos as a fellow MOVE network (formally developed rather heavily on Sui) and I have some questions regarding the Fungible Asset standard.

In order to effectively create a fungible token (ERC-20 equivalent) my understanding based on the documentation is that you must:

  1. Create an immutable object to “own” the metadata object for the new fungible asset.
  2. Generate any refs you may desire: mint ref being obviously required in order to mint any supply, but others can also be added (i.e. burn & transfer ref)

first question

What is the best way to effectively “freeze” or drop the mint ref after the initial TGE? I do not want to have the ability to mint tokens at a future date, I simply want to mint the total supply upon deployment and then freeze or burn or drop the mint ref and not allow anyone to have the ability to mint any future tokens of my fungible asset—what is the best way to achieve this result? Would I simply create the mint ref in the constructor ref (since they are destroyed upon deployment) and mint the total supply that way?

second question

I have been told by a friend that I need to “register” my fungible asset before it can be visualized by any Aptos wallet or be explorable via Aptos explorers. Is this correct? How do I effectively register my newly created fungible asset? Is this handled in the actual token.move code or is that an external function that happens elsewhere? Or is this what creating the “primary store” effectively does? Unsure exactly what this means and want to be sure that my fungible asset is freely transferable and able to be held by various wallets/viewed on explorers etc—essentially am looking for functional parity with any basic ERC-20 token (discoverable name, symbol, decimals, image, freely tradeable, able to be visualized in any wallet and viewable on any explorer for Aptos, but not able to mint future tokens past initial token genesis event, cannot burn tokens, and cannot control the supply or restrict anyone from trading the token.)

Apologies for the super long post, but it’s of vital importance that I make sure I have all these details properly ironed out and this seems to be the best place. Thank you so much for making it this far and I hope to get some confirmations or pointed in the right direction from this. Cheers!

3 Likes