Awarded: Bounty #43 - Pipelinify Updates - $4,000

Pipelinify Updates - Motoko - #43

Current Status: Discussion

  • Discussion (01/09/2023)
  • Ratification: (01/09/2023)
  • Open for application: (01/09/2023)
  • Assigned
  • In Review
  • Closed

Official Link

Bounty Details

  • Bounty Amount: $4,000 USD of ICP at award date.
  • Bounty Acceleration: For each 1 ICP sent to 269b560f921487247b75d5507c9af250af3a932c372111fa5fbb66eba64354c5, will add .25 ICP to this issue and .75 ICP to fund other initiatives.
  • Project Type: Individual
  • Opened: 01/09/2023
  • Time Commitment: Days
  • Project Type: Library
  • Experience Type: Beginner - Motoko;

Description is a utility library that allows for a number of automation tasks in motoko, including moving data between canisters.

In this bounty you will:

  1. Add documention about how pipelinify works.
  2. Create examples for:
    • Moving a file from one server to another
    • Extending a process to run across multiple rounds
  3. Add the timer API to automate the execution of multi-round tasks.
  4. Update from Hashmap to Map v0.7.0
  5. Configure for vessel and MOPs.

This bounty gives the opportunity to

  • learn about Motoko
  • learn about async message flow
  • learn about timers

To apply for this bounty you should:

  • Include links to previous work writing tutorials and any other open-source contributions(ie. your github).
  • Include a brief overview of how you will complete the task. This can include things like which dependencies you will use, how you will make it self-contained, the sacrifices you would have to make to achieve that, or how you will make it simple. Anything that can convince us you are taking a thoughtful and expert approach to this design.
  • Give an estimated timeline on completing the task.
  • Post your application text to the Bounty Thread

Selection Process

The developer’s advisors will propose a vote to award the bounty and the Developer Advisors will vote.

Bounty Completion

Please keep your ongoing code in a public repository(fork or branch is ok). Please provide regular (at least weekly) updates. Code commits count as updates if you link to your branch/fork from the bounty thread. We just need to be able to see that you are making progress.

The balance of the bounty will be paid out at completion.

Once you have finished, please alert the dev forum thread that you have completed work and where we can find that work. We will review and award the bounty reward if the terms have been met. If there is any coordination work(like a pull request) or additional documentation needed we will inform you of what is needed before we can award the reward.

Bounty Abandonment and Re-awarding

If you cease work on the bounty for a prolonged(at the Developer Advisory Board’s discretion) or if the quality of work degrades to the point that we think someone else should be working on the bounty we may re-award it. We will be transparent about this and try to work with you to push through and complete the project, but sometimes, it may be necessary to move on or to augment your contribution with another resource which would result in a split bounty.


The bounty was generously funded by the DFINITY Foundation. If you would like to turbocharge this bounty you can seed additional donations of ICP to 269b560f921487247b75d5507c9af250af3a932c372111fa5fbb66eba64354c5. ICDevs will match the bounty $40:1 ICP for the first 50 ICP out of the DFINITY grant and then 0.25:1. All donations will be tax deductible for US Citizens and Corporations. If you send a donation and need a donation receipt, please email the hash of your donation transaction, physical address, and name to More information about how you can contribute can be found at our donations page.

FYI: General Bounty Process


The draft bounty is posted to the DFINITY developer’s forum for discussion

Ratification: (01/09/2023)

The developer advisor’s board will propose a bounty be ratified and a vote will take place to ratify the bounty. Until a bounty is ratified by the Dev it hasn’t been officially adopted. Please take this into consideration if you are considering starting early.

Open for application

Developers can submit applications to the Dev Forum post. The council will consider these as they come in and propose a vote to award the bounty to one of the applicants. If you would like to apply anonymously you can send an email to austin at icdevs dot org or sending a PM on the dev forum.


A developer is currently working on this bounty, you are free to contribute, but any splitting of the award will need to be discussed with the currently assigned developer.

In Review

The Dev Council is reviewing the submission


The award has been given and the bounty is closed.

Other Bounties


Hi, I can complete this task. I’m admittedly new to ICP and Motoko, however I’ve been programming for 8+ years on many different stacks. This bounty seems like a great entry point into Motoko, inter-Canister communication, and ICP in general.

First, as I learn and test the tool, I can create the necessary documentation for it. Next, I can make it vessel and MOP compatible. My first contribution to the code will be upgrading it to use Map. Lastly, and at the point I have the most familiarity with the code, I’ll extend its functionality to automate the execution of multi-round tasks as is required.

I can post here or elsewhere frequent updates (every 3 days maybe?).

Happy to chat further about implementation details or my qualifications.


I’ll submit it to the board, but you should feel free to get started:

@icme, @aiv, @quint, @mparikh, please vote :slight_smile:

1 Like

Hey @relaxed04 … interested in picking this one up now that you are done with RLP?

Likely yes. I’ll first take a quick look at what else is available and get back to you later today.

Hey @skilesare. Happy to get started on this one.
I’m not fully aware of the bounty process here, can I get a rough idea of next steps and timelines for review and payment of RLP, thanks!

I’m working on it. I need to send a report to DFINITY with the completed tasks an obtain payment from them. What ever the price is on the day they pay out the grant payment is the price I use to pay out to you after the board approves the pay out. I’m trying to get it done for you guys as we have 4 that are pending review.

Sounds good to me, thanks. I’ll get started on this one.

I noticed this was reopened. Life got in the way a bit, and I’ve been delayed. I’ll be free to re-start this in about a week if anyone hasn’t jumped on it by then. Thanks.

1 Like

I’ve submitted a proposal for you to take this one on.

Please coordinate with @piens as he has been looking at the pipelinify stuff a good bit and may have some commentary. Profile - piens - Internet Computer Developer Forum

@icme, @aiv, @quint, @mparikh, @cryptoschindler please vote :slight_smile:


@skilesare @relaxed04 Is this up for grabs? If yes, I would like to take it up.

I’ve started working on this over the weekend. I’ll post an update here in the next couple days




Im currently in the process of extending and refactoring current test cases - these will be referenced when creating documentation of example use cases.

1 Like

This bounty has been retired. More Bounties Soon!

1 Like