[Active] Wrapping AENS names into AEX-141 NFTs

aeternity Foundation Grant Applications
16

Hey everybody,

I just published a page where you will be able to track the progress of this grant:

Right now the most important thing for me is to clarify the scope. We can consider A LOT of stuff which might be cool, but to achieve it the right way I need to get as much feedback as possible. Otherwise I will probably have to stick to a minimalistic approach to avoid unnecessary overcomplication of tasks.

I created an Ideation Mindmap (Source: aens-nfts/ideation-mindmap-source.md at master · marc0olo/aens-nfts · GitHub) where I noted down all of my initial thoughts.

I will shortly summarize the most important questions to address and discuss:

  • Do we want to introduce a mechanism to reward other users for extending AENS names of others? Personally I think this would be cool and this has always been in my mind :slight_smile:
  • What reward-mechanism do we prefer?
    • NFT owners define their own reward (in Æ coins) for users
    • We create an AEX-9 token (e.g. AENS DAO) which rewards users based on various criteria (to be defined)
      • I already noted some ideas in the mindmap about the AEX-9 token, but if we create such token we should also discuss its utilities (e.g. voting, staking, …)
    • Both?! → IMO, if we decide to introduce an AEX-9 token, we should focus on that
  • Do we want to allow transfers of AENS names between NFTs? Shall this only be possible if the user is owner of both NFTs? I would say yes
  • Logic for extending AENS names wrapped in NFTs (and possibly corresponding reward-payout logic)
    • Always extend all names? (most simple solution, especially when it comes to rewards. but not really efficient)
    • Select a set of names to extend?
    • Select a single name to extend?
  • Do we want to limit the amount of AENS names that can be wrapped into NFTs to ensure that batch-updates & batch-transfers are always possible for all wrapped names? Or should we allow an unlimited amount of names to be wrapped where users/devs would have to take care to not exceed limits in batch updates?
  • How to deal with “spent” or “accidentially received” AENS names? The Smart Contract would not be able to know who sent the AENS name to its account, so there are following options:
    • Sell
      • who should receive the sale proceeds?
      • Listing vs. auction
      • Fixed price vs. dynamic price
    • Make claimable by anybody (first to claim gets the name)
    • Let expire

In case we decide to introduce an AEX-9 token we will have to discuss a lot more details. But these are the “big questions” I have currently in mind which I want to discuss with you.

Can’t wait to get some feedback! :slight_smile:

3 Likes