Sia Bounties: Duplicati Integration

Welcome to Sia Bounties! Learn more about the program at our blog.

We are excited to announce a bounty for Duplicati, an open source backup app, for 400,000 SC. Based on today's exchange rate, that's worth about $3200.

Why Duplicati? Duplicati is a popular backup application that stores backups online with strong encryption, and works with FTP, SSH, WebDAV, OneDrive, Amazon S3, Google Drive and many others.

In their 2.0 version, which is currently in beta, Duplicati provides a friendly in-browser UI that allows users to easily create automated backup tasks. Combined with Sia-UI, a Duplicati integration will mean that even nontechnical users can use Sia for backups.

Crucially, Duplicati compresses files into a series of zipped folders. In tests, we were able to backup a 5.82 GB directory with 43,000 files into a 3.34 GB Duplicati backup with 139 zipped folders. Sia would struggle with so many files, so Duplicati's compression is a huge benefit.

Duplicati does offer optional encryption, but it is not needed with a Sia integration, since all files on Sia are split apart, encrypted, and stored across dozens of worldwide nodes.

A Sia + Duplicati integration means that users will be able to backup their computers directly to Sia's cheap, secure, and redundant storage network without having to rely on centralized parties like Amazon.

If you are interested in building this integration, please review the below requirements and the blog post. All Sia-related discussion should take place here or on the bounties channel in our Discord.

If you have questions for Duplicati, you can reach them on their Forum or submit an issue on their Github.

For reference, our API docs are found here, and Duplicati's wiki is here.

Good luck! This bounty expires on September 29, 2017.

Minimum Bounty Requirements

• Must deliver a working integration between Sia and Duplicati.
• Must allow users to choose Sia as an option in the Duplicati's Storage Type dropdown, and backup their files to Sia through Duplicati.
• Duplicati must be given full control over file-related functions; users must be able to use Duplicati to upload/download Sia files.
• Can assume that the Sia node is already unlocked, funded, and has contracts on the same computer.
• Must agree to work with the community to test the integration and maintain it on an ongoing basis.
• Code quality must meet approval from the Sia Core developers and Duplicati developers.
• Duplicati must agree to merge the integration into their upstream code.

General Bounty Rules

• Best place to discuss bounties is #bounties in our Discord.
• Every Bounty Project will be clearly specified, with specific requirements for bounty payout. Now, knowing the Sia community, we are aware that by simply meeting some minimum requirement, you won’t stop developing. But meeting ALL the minimums is when a bounty will get paid.
• Certain bounties are expected to be quite large in scope (and payout) and thus likely require formation of a team. In these instances the team is responsible for providing an agreed statement as part of their bounty submission for how the bounty will be distributed along with the necessary Siacoin addresses to distribute the funds across.
• A bounty will only be paid once to one submission and, unless specified otherwise, it will be paid to the first individual or team to meet ALL the criteria set out for the bounty. This may be changed in special cases for larger bounties.
• All projects have a time period where they are useful to the development and growth of Sia and likewise all bounties will have an expiration date. Submissions will not be accepted after the expiration date, unless the bounty is renewed.
• In the event of multiple submissions in the same time period, Sia and the Donors will evaluate each submission and serve as tiebreakers.
• Sia and the Donors reserves the right to modify/clarify/expand any bounty requirements and payouts. We will keep this honest and transparent, and the reasons for any and all changes and ultimately bounty awards will be published.
• When paying a bounty, the winning individual or team transfers all rights to the code to Sia, if not already open source (though we will of course make it open source).