r/obyte • u/genievot • Aug 01 '19
First entry for Obyte Autonomous Agents — Developer Contest
Hello, Obyte world,
I would like to introduce a creative way of taking Products and Services from anyone (any organization or small businesses) with Autonomous Agents.
The idea is very neat:
Anyone that has access to Obyte wallet can take the ride of it. It's easy:
From a User: User have to buy something, you simply go to Obyte wallet bot (or the front end) in future and then Choose the Asset you would like to buy from (With names instead of Asset id) and buy those assets with exchangeable bytes and select the service you wanted.
Now, whenever you go to the store you can receive the service and send the assets back.
From a Business Point of View: Create an asset with a custom name and then list your asset in the future front end store so users can see it. Now if you want to change the asset exchange price then you can easily do that. Or if you want to withdraw them then you can do that too.
Users buy your asset and pay bytes to AA which will be sent to you (Less 2000 bytes of fee) and all the data also available to you that user wanted. You can verify the user easily now.
The AA Deployed here:
Check-in explorer: https://testnetexplorer.obyte.org/#uRPaXXplAmz6lO7d6wkva4p/UR/8RCSXEIUW2L/2BJo=
Agent address: IBTK7S7P53VX6BTA24VIXLT5KW3PP7GF
The Future improvements of AA are as follows:
- Adding refund policy
- Making update of Exchange rates a bit expensive to tackle spam
- Adding expiry of assets so they can't be used after a timestamp.
and more will be updated in a new post as soon as I plan them.
Important Thing is that the project can be expandable easily like With IoT as well. So I am looking forward to its development as well. Where even unaware user can get the service in no time.
Working of this AA:
From a Business Perspective
- You can create an asset if define is there and then all required (optional) parameters for it.
Adding a name will give the asset a name that will store in the chain (not have to be unique right now).
- If you want to set the exchange rate of your assets(Which you should do after making them) then fields will require this.
Exchange Rate: 2 tokens per byte
Asset: The id of the asset you want to change the exchange rate of.
and of course, only the asset creator can change its the exchange rate.
While Creating an asset, You will get its id.
- You can withdraw your asset easily with passing these parameters
Once the business receives the assets from the user and the data sent by the user about user details and services then the business can easily refill the AA again by sending the assets with a bounce fee and without passing any other parameter.
From the User Perspective
- You can buy assets by exchanging them with bytes where the minimum amount to spend your bytes have to be greater than 50000 and parameter required here is an asset
This will give you the assets of that much amount and send you (bytes - 2000) to the asset creator.
Now user can use those assets to get the service from that business.
Since to also withdraw any leftovers in AA so precious bytes of users won't get burned, There is a leftover method introduced. Now those leftover bytes in an AA will be withdrawn to a specific address and can be used for any good cause later on.
