Aleo.store is a NFT marketplace using the Aleo blockchain. For now, it is mainly a proof of concept that aims at helping build a standard for NFTs on Aleo, while taking advantage of its unique ZKP capabilities.
aleo-store-db-sync
Next priority is developing an open source program syncronising the chain with a PostgreSQL database of data relevant to (collections, tokens, listings, mints etc...) on top of Heraku's explorer. Currently some functions require to load all entries from a mapping and then filter the entries based on a key or a value. An Postgre database will make the frontend scalable.
It will make building a volume explorer possible, allowing to see the volume of transactions for each collection and assets individualy. This will allow to see the most popular collections and assets, by following "accept_listing" transactions.
It will also enable to implement Search engine. It's not currently possible to search for a specific asset or collection. It is a high priority feature for the marketplace frontend.
Alias redirection
Allow entering an Alias instead of an address when using transfer token and transfer collection features. Check with Leo wallet team if Aliases can be integrated in the wallet. Add Alias research to previously cited search engine.
Coin selection
A credits record consolidation program is also being written. A third program, importing aleo.store program and consolidation program, will wrap transitions that use credits.aleo records (mint_public and accept_listing) as inputs and allow to use several records instead of just one. It will allow coin selection on the front end and execution of intended program, in only one transaction.
NFT CLI
A CLI for manipulating ARC721 tokens/Advanced token features is in the pipe as well. It will allow to handle big collections more easily. Initialize collections, public mints, public tokens, and mint tokens as well as transfering tokens A documentation for this tool will also be necessary.
Bugs
There is a bug when a record has just been consumed by a transaction it sometimes still appears in Leo request records list, while new created record appears as well. This causes associated private token or collection to appear twice (only one id spendable of course). This issue form Leo wallet could be solved on my side if block height was included in the record, by filtering doubles with the same id, ignoring the one with the lowest block height.
Auctions, offers should be implemented. This is not possible for now as credits cannot be owned by contracts. Bundles and mutli-sweep could be implemented as well but are not a priority.
Feedbacks
You can write an email to contact@aleo.store or join the Discord and Twitter. Community management is not my best quality though, but I would be glad to hear your feedbacks.
