Our Web Interface and Dev Bounty Program

We recently released the first version of a web interface for our dApp and we are currently testing it on Jungle Testnet. We are going to run an extended testing session from the 6th until 13th of August and we are launching a Dev Bounty Program to encourage the EOS Developers community to participate in this session.

UNICO is looking for you!

We are recruiting 5 testers for each of these two groups:

1. Basic Tester We expect you to explore our web interface and report any bugs or suggestions for improvements. The reward for this activity is 20.000 UNI once accepted in the group, plus 20.000 UNI for each significant bug reported or improvement suggestion.
2. Advanced Tester We expect you to explore our web interface as well as our smart contract (with cleos commands, v.1.1.0 is needed) and report bugs or suggestions for improvements. The reward for this activity is 40.000 UNI once accepted in the group, plus 40.000 UNI for each significant bug reported or improvement suggestion.

In both cases, the focus is on functionalities and functions, as the graphics will be designed by professionals.

You can apply for this program by contacting me on Telegram (https://t.me/@Ivand83). As soon as the teams are formed, we will soon set up a dedicated telegram group to communicate and cooperate.

Below you can watch our web interface in action, linked to Scatter, which enables interactions with our dApp in a user-friendly way.

In this Beta release we have enabled functions for the “primary market” (i.e. collectibles being sold by the UNICO account) such as:

1. List → Acomplete list of all collectibles. For each collectible we have:

1a. ID → A unique identifier for each collectible. You can get a complete list with cleos command:

cleos -u http://dev.cryptolions.io:38888 get table unico unico unicollects

1b. Name → Collectible’s name

1c. Author → Collectible’s author. This account receives revenue from primary and secondary market sales declared in “author revenue” and “author revenue Secondary Market”

1d. Unico Revenue → Revenue from primary and secondary market to reward RAM and Platform maintenance by Unico Team

1e. Charity → This account can collect a fraction of revenues from primary and secondary market sales if the author so wishes

1f. Max Supply → The maximum number of licenses that can be issued on the market

1g. Current Supply → The number of licenses currently issued on the market

1h. Price → The starting price of licenses issued on the market. Price can be set in different currencies such as EOS, UNI, etc. You can get a complete price list with cleos command:

cleos -u http://dev.cryptolions.io:38888 get table unico unico prices

1i. My Licenses → The number of licenses owned by the user logged on Scatter. You can see all issued licenses with cleos command:

cleos -u http://dev.cryptolions.io:38888 get table eosionft eosionft token

and licenses for a given account with:

cleos -u http://dev.cryptolions.io:38888 get table -L “account_name” eosionft eosionft token — index 2 — key-type i64 (https://github.com/EOSIO/eos/pull/4053)

and token balance for a given account with:

cleos -u http://dev.cryptolions.io:38888 get table eosionft account_name accounts

2. Buy → Each license can be bought by a user with sufficient EOS and RAM resources. For each collectible, EOS price is set by author and RAM needed is around 548 bytes. You can perform this operation on EOSIO blockchain directly with cleos command:

cleos -u http://dev.cryptolions.io:38888 push action unico buy ‘[“account”, “EOS”, number_of_license]’ -p account_name

3. History → It shows the transaction history for a license, including sellers and buyers, price and date. We will later release an API for other platforms to access these data in order to increase the visibility of UNICO’s collectibles market.

In this Beta release we have enabled also basic functions for the “secondary market” (i.e. trades between collectors) such as:

1. SellTo → Each license can be sold to a specific user. EOS price is set by the owner and RAM needed is around 545 bytes. You can perform this operation on EOSIO blockchain directly with the cleos command:

cleos -u http://dev.cryptolions.io:38888 push action unico sellto ‘[“seller_account”, “buyer_account”, “102.0000 EOS”, license_number]’ -p seller

You can check the market status in the “secondary market” tab. You can also perform this operation on EOSIO blockchain directly with cleos command:

cleos -u http://dev.cryptolions.io:38888 get table unico unico markets

1. CancelSell → It could happen that a buyer is no longer interested to buy a license; then “sell” status can be revoked by the owner account. With this operation owner also recovers the RAM used in the “SellTo” action. We can perform this operation on EOSIO blockchain directly with cleos command:

cleos -u http://dev.cryptolions.io:38888 push action unico cancelsell ‘[“seller_account”, “buyer_account”, license_number]’ -p seller_account

1. BuyFrom → A license can be bought by a user with EOS and RAM availability from another user after “Sellto” is invoked. For this action RAM needed for the buyer is around 548 bytes and seller recovers “Buy” + “SellTo” costs . You can perform this operation on EOSIO blockchain directly with cleos command:

cleos -u http://dev.cryptolions.io:38888 push action unico buyfrom ‘[“buyer_account”, “seller_account”, license_number]’ -p buyer_account

Below you can see a summary of all operations and their RAM costs:

RAM costs

Subscribe to our newsletter to stay informed on the project’s progress and latest developments.

Follow us on:

Website: https://www.unico.global

Telegram: https://t.me/unicoglobal

Twitter: https://twitter.com/unico_global

Facebook: https://business.facebook.com/unico.fans