-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anagolay project Idiyanale phase 1 (Nr. 1) #719
Conversation
grant ready Signed-off-by: Daniel Maricic <daniel@woss.io>
Hi Daniel, thank you for your application. We will look into it as soon as possible. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the application and sorry for the late reply. I have a few questions: It currently says “Manifest is ......”. Is this on purpose? Regarding multihash, are you referring to https://multiformats.io/multihash/? Do you already have some initial mockups regarding the Demo web app? How are you planning to integrate Filecoin? Are you aware of https://github.com/ChainSafe/filecoindot?
Nope, that was 100% accidental and I'll update it today, I was sure I finished that part :) Thanks for pointing it out.
Yes, more accurately the official rust version
The plan is to have the Operation source code (Operation Version) as resilient as possible. By that I mean is, once it's stored on the IPFS it's close to impossible to un-store them( delete, remove, hunt for existing copies, etc ... ). Any technology that can provide will be considered and implemented. For now, we are going to store all the Operations on the public IPFS cluster we host, and on Filecoin using the web3.storage. If there is a better way, I am open to suggestions. We do not want to run our Filecoin node, well, at least not yet. It requires quite beefy machines :)
Yes, the reason why we are not using it ATM is that I would like to create something that works, then later we can improve and add additional layers for Filecoin, or Crust Network. |
Signed-off-by: Daniel Maricic <daniel@woss.io>
@Noc2 description updated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update. Regarding “it's close to impossible to un-store them”, I guess if you don’t have an incentive for keeping files stored, they might disappear in the long run. Also running your own cluster is highly centralized. In general, I know that decentralized storage is a very difficult problem, but it would be nice if you at least work on solving this as part of the grant. Maybe include a research report regarding the potential existing solutions for decentralized storage and their advantages and disadvantages as part of milestone 1 or 2.
Regarding milestone 3, we usually require teams to have at least some mockups for the UI. If you don’t have any at this stage, I simply suggest removing milestone 3 for now and we sign potentially a follow-up grant in the future.
* change the md headers for better reading and clearer structure Signed-off-by: Daniel Maricic <daniel@woss.io>
Signed-off-by: Daniel Maricic <daniel@woss.io>
I don't know exactly what you want me to do here so I updated the grant where I outline how we are planning to use decentralized storage. I don't see why any of the milestones need to be changed.
I provided a UI mock, hopefully, that will be enough. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the reply. Are you aware that Subspace Labs Acqui-Hired canyon network? See https://medium.com/subspace-network/subspace-labs-acqui-hires-team-from-canyon-network-to-bring-decentralized-storage-to-polkadot-89ad488964d5 So you probably won’t be able to use Canyon. Apart from this, I have one last question: would you be willing to reduce the price a little bit? This way it will be easier to accept by the rest of the committee.
Signed-off-by: Daniel Maricic <daniel@woss.io>
Thanks for the quick reply.
Nope, I didn't know that, and it's funny that it doesn't show up in DDG for the first 20 results. This changes only the future evaluations for the permanent storage, but not the current implementations.
It depends on what you define by |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It’s hard to define, since I also don’t know what the rest of the committee thinks is reasonable for this kind of work. But I personally think that the grant at the moment is a little bit expensive, also given that the deliveries are mostly useful for your own project and grant teams that working on potential start-ups ideally shouldn’t cover 100% of their initial funding via grants.
Thank you for the reply.
by implementing the proposed logic in Substrate, it's inherently available to the entire ecosystem, including all the existing and still emerging NFT projects to which it's highly relevant as it solves the obvious shortcomings of the current approach. Here is the example I wrote in the grant. Besides, Anagolay's implementation will lay the ground for the whole new type of applications in the creators and sharing economy, making the Substrate highly relevant outside of the DeFi domain and bringing new users to the ecosystem.
The project as a whole has started in 2019 and was mostly self-funded since then. The total investment to the date is 280k EUR with which we have created a proof of concept and a verified use-case (first of many) and did a lot of research in both tech and market domains. The aforementioned use-case for the photography market - Kelp.Digital - got validation and support from the European Union’s Horizon 2020 research innovation program NGI TRUST and was selected by Media Motor Europe among 20 high-potential European deep-tech startups in the media sector. The PoC demo you can see here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the reply. In this case, I will share the application with the rest of the team. However, I have to say that I’m not fully convinced of it at the moment. On the one hand, I’m not convinced about the business case, and on the hand I don’t think that the tools, which you develop as part of the grant, will be used by a lot of other projects (to justify the 45k). But that doesn’t mean that the rest of the committee won’t approve it.
thank you for passing the application forward and sorry for not replying earlier, had a pretty crazy day yesterday at IGF with our presentation. Looking forward to seeing what the rest of the committee thinks about this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that, if enough people publish code on IPFS and enough people depend on it, there will also be automation built around fetching the latest version and updating automatically (re: npm), which means the issue of bad actors is not solved. Still, I think this is an interesting project, and the price is, I believe, what the missing part of your previous grant was.
Signed-off-by: Daniel Maricic <daniel@woss.io>
The experience of your team with PolkaMusic is unfortunately rather a negative sign (you can check my evaluation of their milestone) and I would be thus wary of the final outcome of your project - that's of course just personal experience. Overall, I am not convinced by the application and since we haven't seen any interest from other Grant Committee members within the last 2 weeks, I will close it, as per our standard policies. |
@mmagician I'm genuinely sorry to hear about your bad experience with PolkaMusic but then again there was just one junior from their team which we decided to let go week ago and i didn't update the grant since I didn't think you guys will do anything during the Xmass holidays. The update also reduces the cost and the milestones.
How come? This is essentially the base for the proof generation off-chain and on-chain(if needed). Also, it is a base for the Rights Management and Licensing of multimedia. The reason why you don't see a big picture is that it is not obvious from this grant, and this is intentional since the grant covers only a small part if you wish to know everything about this let me know and I will be glad to explain you or provide with documentation which is still in the R&D stage and not published.
I really don't understand the lack of interest. I've spent days reading the applications that are less attractive and solve nothing of the real-world problems which you (plural) choose to finance, whereas us are trying to fix the copyrights and ownerships of digital media so ALL creators can benefit. How that is not interesting to you I cannot understand. I suggest we reopen this PR and i commit updated grant proposal. Then you can review it again and make your decision. If you want me to explain the big picture (which is not part of the grant) let me know and we can set up the call. |
Ok, you can let us know once you have updated the proposal. |
Signed-off-by: Daniel Maricic <daniel@woss.io>
@mmagician proposal updated. I hope it will be satisfactory and enough for you to make a decision. I would like to remind you, if you would like to know more about the project ( more than this grant tells ) let me know. |
Thanks for the update. Please bear in mind, that as my colleagues have mentioned, the decision to award a grant is made by a committee and for your price level you need 3 approvals. Everyone will have a different perspective, background and priorities when making the decision. I will try to review it again in the coming days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m happy to go ahead with it at this price. Sorry for the late reply here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still have my doubts regarding practicality of your solution, even after I've browser through your docs, which I assume contains at least some portion of the R&D you mentioned.
That said, I am not the one bringing this solution to market. At the current reduced price, I am willing to support the application - I can see you've done the necessary research regarding substrate and aim for decentralisation as much as possible.
Congratulations and welcome to the Web3 Foundation Grants Program! Please refer to our Milestone Delivery repository for instructions on how to submit milestones and invoices, our FAQ for frequently asked questions and the support section of our README for more ways to find answers to your questions. |
Project Abstract
Anagolay is a peer-to-peer network that stores records of Rights (Copyright, Licenses, and Ownership), Restrictions, and Proofs of any digital content. It empowers the users to store, claim, sell, and rent their work with the correct transfer of Rights and usage of Licenses. Actual digital data is never stored on the chain, only the respective cryptographic proof. As such, it acts as an identifier, verifiable by users who have access to that same data without disclosing it in the process.
We applied for a grant in 2020 and got approved under the name Sensio Network. Since then we did a lot of research and improved the approach. We did rebranding; SensioPhoto is Kelp Digital and SensioNetwork is Anagolay Network.
For which grant level are you applying?
Application Checklist
project_name.md
) and updated.