archethic-foundation / aeip Goto Github PK

Is your feature request related to a problem?

In order to insure the operability, additional metadata must be described to avoid that people use different terms for same item
Need also to indicate what's required or not, limit etc..

Describe the solution you'd like

For example:

In addition of the Name it will be nice to have a dedicated attribute for a short name/code (should be required)
Not required attributes such as

• Author
• Description

For Token, need a specific the number of decimals (should be managed by the blockchain during transfer)

Images for Tokens must be named with the size etc.. in order to facilitate the representation of the token in Dapp

If you think that this proposal is interesting, I can work on a more detailed description. let me know

Additional context

No response

This is discussion about the AEIP3 https://github.com/archethic-foundation/aeip/blob/main/AEIP-3.md

We need to create the AEIP relative to the Archethic token standard to describe the goals, and the way it's managed by the network.

So the standard will define:

• What Archethic tokens are (NFT, ERC20 like)
• How to create them and use them
• Format standardisation

This is discussion for the AEIP4 located at: https://github.com/archethic-foundation/aeip/blob/main/AEIP-4.md

Is your feature request related to a problem?

I am sorry I have other concerns about the Properties, hope that will help to progress.

• Seems that there are 2 roles in properties;
  one is to define some metadata of the token (parent) and to define a list of NFT instances (children). It will be nicer to separate these 2 items in different attributes, on an object and another one a collection.
  metadata:{} & instances: []. (didn't find a better word than instances)

• Metadata are defined by an item with 2 attributes key/value, as JSON is based on "key:value", it is more efficient (size, implementation to find the value etc..) to use the native approach. example:
  [
  { "key": "origin", "value": "France"},
  { "key": "organism", "value": "DG" }
  ]
  should be
  {
  "origin": "France",
  "organism": "DG
  }

• For NFT instance, the id should be mandatory and controlled by the developer, I will not recommended to have the index based on the position in a collection (mix representation & business)

Describe the solution you'd like

No response

Additional context

No response

Is the aeip3 related to something like https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki ? @redDwarf03

This is discussion for the AEIP5 located at: https://github.com/archethic-foundation/aeip/blob/main/AEIP-5.md

Is your feature request related to a problem?

Actually, the definition of properties inside a token is free.

Describe the solution you'd like

I suggest to share a property dictionary to define some specific properties to facilitate the interoperability between DApps.

Additional context

In the wallet app, i manage for the moment inside a property of an NFT:

• "name": the creator can specify a name
• "description": the creator can specify a description to promote or define his token
• "file": contains in base 64 the file attached in the NFT (image, pdf, etc...)
• "type/mime": contains the type/mime from IANA Database

This AEIP proposes a URI scheme for making Archethic payments and deeplinking with the mobile applications by specifying a custom URL scheme