Awarded: Bounty #60 - Stable Buffer Motoko Upgrade - $1,000 StableBuffer Motoko Library - #60

Current Status: Discussion

  • Discussion (03/24/2023)
  • Ratification: (TBD)
  • Open for application: (TBD)
  • Assigned (TBD)
  • In Review
  • Closed

Official Link

Bounty Details

  • Bounty Amount: $1,000 USD of ICP at award date.
  • Bounty Acceleration: For each 1 ICP sent to e156fe180f0f6deffa87344390dc45b2e6d4483d4007f6ea8f3f4d89e56fa5d2, will add .25 ICP to this issue and .75 ICP to fund other initiatives.
  • Developer Type: Individual
  • Opened: TBD
  • Time Commitment: Days
  • Project Type: Motoko
  • Experience Type: Beginner - Motoko


The proposed project aims to bring the StableBuffer library(GitHub - canscale/StableBuffer: Stable Buffers in Motoko) up to parity with the recent improvements made to in the base library(motoko-base/src/ at master · dfinity/motoko-base · GitHub). StableBuffer is a Motoko library that provides a reliable way to manage byte arrays, while is a built-in Motoko module that provides similar functionality.

By updating the StableBuffer library to be consistent with the improvements made to, developers will be able to use the two libraries interchangeably, which will improve code compatibility and reduce the potential for errors.

To complete the StableBuffer library update, the project will require an experienced developer who is proficient in Motoko and has a strong understanding of byte arrays. The developer will work closely with the Motoko community to ensure that the updated library meets the needs of developers working on the Internet Computer.

This should be a straightforward port of each function from a class based format to a functional based format.

This bounty gives the opportunity to

  • learn about Motoko
  • learn about Social on the IC
  • Dapp development

To apply for this bounty you should:

  • Include links to previous work building web applications and any other open-source contributions (i.e., your Github).
  • Provide 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 e156fe180f0f6deffa87344390dc45b2e6d4483d4007f6ea8f3f4d89e56fa5d2. ICDevs will add .25 for every 1 token donated to the bounty. 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


I updated the code to be equivalent to version 0.8.7 of the base library. Also updated the test cases to match the new capacity calculation.

The comments are not updated yet and still contain usage examples from the base/Buffer.
When this is done, I’ll create a PR for the original repo.

The documentation is updated and a PR has been created: Update to base/Buffer version 0.8.7 by f0i · Pull Request #10 · canscale/StableBuffer · GitHub

1 Like

Thanks for all the great work. Responded to your PR with two different options moving forwards to protect backwards compatibility for those who are currently using this package.