on the Fetch.ai network, protecting chunks of data required for our apps to function and reward you in FET.
All possible by using your Digital Twin.
Link: https://helios.codes/fetch_ai/proposal/?c=AllowForFetchAiTeam
Yooo
okay quick question: Critters do not monetize digital twin data right? It has nothing to do with this right? A Twin ID seems to function as a data storage for third parties, right?
Previously, the idea was for Digital Twin owners to "lend" their storage, for us to be able to work with. Data of our clients would be uploaded to your Digital Twin, although heavily obfuscated. What would look gibberish to one, would make sense to our platform. We would reward you everytime our clients stores data to your Digital Twin in FET. However, this concept was perhaps a bit too ambitious, as it would require a ton of workload for the coming years, since we'd need to build Software on top of the platform (which I'm fine with though). Since then, we've went another direction and focussed more on the Quests part of the Digital Twin API. You see, we're able to open a whole new world for those completing quests on a daily basis. The goal with the revised concept is for users to give extra motivation to complete and host quests by providing rewards in FET, and to make it more fun. It would also raise awareness to Fetch.ai in general. The proposal will be updated. I'm working on a MVP, because I'm able to express my idea better that way. I'll keep you updated. Thanks everyone.
Thank you for the update. And great to see you're moving at the speed at which you are.
Hey Helios. Read (skimmed) through your proposal before it was taken down for revision so i might not remember the numbers accurately. First, great idea and as a long Fet fan i'm always excited to see outside attempts at growing the network (speaks to more decentralization), so kudos to you for fronting this 😊 Issues i had 1) Creation of Data critters with 1K FET fee. It was a bit worrying on the front of the deployment of these "critters" (thousands of them) would require about 1000 FET each. 2) Vault (we all know the risks) The FET is locked in a vault to which "your" tokens are issued in place to the now "owner" of the said data critter. I'm personally not too big on untested synthetic/mirror assets since the FET network is still so new. I feel that the users of the fetch network still deserve the right to focus on securing the network first as opposed to "spilling" out all their resources to something completely new and potentially risky to both them and the network? Do you think it might be better to create a test environment first, (A simulation of some sorts), run your idea extensively to the point of justifying the valuations and then come back with a proposal that all of us will be eager to back?
Обсуждают сегодня