Thanks for the proposal! We’re a little concerned about the technical feasibility of the project and would like to address them with you here before making a determination on this proposal.
One issue brought up by the committee is where your Sia node will be running - are you planning to run a central node for sake of ease (while sacrificing a bit of decentralization), or force a user to download and run a full node to power the extension? If the user is connecting to a central node how will your service preserve privacy for its users?
We’re a little confused as to your budget request. The full term of the project appears to be three months, while one year of infrastructure is mentioned. Is this to keep the project online beyond the grant duration? Additionally, you mentioned the project will be supported by two developers, but it looks like you mention requiring 6-8 full-time personnel. Please clarify those points.
Finally, as mentioned in the forum thread, renterd would be the choice here as siad has been/is being deprecated. Thanks!
Regards,
Kino on behalf of the Sia Foundation and Grants Committee
For now we plan to install our node and let all users use it. For this reason we added 1-year budget for infrastructure rent - to support this solution after delivery. In future we plan to add functionality to switch a node and connect to any other particular node, chosen by a user. In all our Web3 projects we proceed from the fact that one of the main principles should be decentralization, therefore we plan to work on this issue in the future.
Privacy will be preserved by encrypting uploaded files with user’s key in the extension and these files will be received by a node already encrypted.
Explanations of the FTE parameter - both developers will work full time + partially PO, QA and management, so we got 6,8 man-months in total that fit in 3 calendar months due to the team of several developers.
Renterd seems ok, we are learning it’s API and everything seems good for our task now.
This is a reminder that your October progress report is now late.
Progress reports are expected to be posted by the end of the 2nd day of the next month, in this instance your October progress report was due on November 2nd.
Please be sure to follow the Progress Report Template and submit your progress report so we may continue funding your grant.
Regards,
Kino on behalf of the Sia Foundation and Grants Committee
I’m sorry, didn’t get the reminder on mail. Just switched on the notifications not to miss the new ones.
Here’s the report with demo video and you can also use the extension in the test net:
This is a reminder that your January progress report is now late.
Progress reports are expected to be posted by the end of the 2nd day of the next month, in this instance your January progress report was due on February 2nd.
Please be sure to follow the Progress Report Template and submit your progress report so we may continue funding your grant.
Regards,
Kino on behalf of the Sia Foundation and Grants Committee
What progress was made on your grant this month?
Please summarize your progress in 3-5 sentences or bullet points:
To increase throughput and lower the gateway resources consuption when uploading large files we have changed the intermediate storage which is used to store client’s files while uploading them to the network - now the disk space is used. The files are deleted as soon as they are uploaded to the network.
All tariffs shown in the extension are now tied to the current SC/USD exchange rate according to USD prices shown on the Tiri web site.
We have added the dapp version notification for users to update the dapp when a new version is published. Also, some manipulations with tariffs were made.
Here’s the last updated repo: GitHub - bsn-si/sia-datawallet-gateway
Hello! In March we didn’t make a lot. We are working with billing: have changed some tariffs mechanics and fixed a few minor problems, but still have to execute tests. We will push the new version till Tuesday, I think, and I’ll comment here when done.
We have worked with billing and tariffs, fixed different issues, for example - the free “disk” space indicator now correctly considers deleted files and tariff change.
Current version of the extension is 1.0.1: Releases · bsn-si/sia-datawallet-extension · GitHub .
Hello! Sorry for silence, we’ve got national holidays in Slovenia, as well as in Serbia the whole last week and the team is out till tomorrow. From the code perspective we’ve just added a “support” form, so users could request support if they agree to reveal an email for messaging. I’ll push the update to Git asap and put a report form here.
In April we were working on the Tiri concept that will help to gain mass adoption. The Tiri dapp shows that a user can easily, yet privately and securely store data on-chain, but using a browser extension fits only archive storage tasks and users need an operational storage like Dropbox - this is the main feedback that we’ve got from our test and first users. So we are developing a technical description for using Tiri as a remote virtual disk storage.
We’ve added a user support form, so users could request support if they agree to reveal an email for messaging.
As we have fulfilled all the planned deliverables, the current work on the project is mostly focused on the product concept, model and technical design of the needed features.
Summarize any problems that you ran into this month and how you’ll be solving them.
I see these main tasks with additional features:
Adding integration with local file system, so users could work with their files locally. This feature is quiet clear and we don’t see technical constraints. The tech description is prepared.
File sharing. If we want to stay as decentralized as possible, this feature could be solved with an access list smart contract like here, for example, but smart contracts are not available at the moment. So this feature is something that requires contemplation over its concept.
The HTLC would be a great feature for SIA mass adoption and for all projects on SIA as well, so we are eagerly monitoring the progress of the Komodo team’s work on this task. This should allow payments for SIA services from different networks.