# Community Call July/August 2021

**URL:** <https://research.rsk.dev/t/community-call-july-august-2021/204>\
**Category:** Uncategorized\
**Created:** [July 16, 2021, 3:54am UTC](https://research.rsk.dev/t/community-call-july-august-2021/204 "2021-07-16T03:54:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![bguiz](https://avatars.discourse-cdn.com/v4/letter/b/fbc32d/32.png) [@bguiz](https://research.rsk.dev/u/bguiz)\
**Post date:** [August 3, 2021, 3:56am UTC](https://research.rsk.dev/t/community-call-july-august-2021/204/2 "2021-08-03T03:56:21Z")

</div>

Proposed topic from @SergioDemianLerner → RSKIP-241, User triggered peg-out fee-bumping

> [@RSKIP-241 User-triggered peg-out tx fee-bumping](https://research.rsk.dev/t/rskip-241-user-triggered-peg-out-tx-fee-bumping/213):
>
> Hi! I would like the community to review this change to the bride contract to enable fee bumping of peg-out transactions. One of the reasons peg-out transactions are expensive is because the fee/kilobyte (which is not frequently updated) must be set high to accommodate the varying fees of Bitcoin. with a fee bumping mechanism, the default fee/kilobyte could be set to a lower value, and users would be able to bump the peg-out transactions if they get stuck. You can read the whole proposal here:…

---

_[View the full topic](https://research.rsk.dev/t/community-call-july-august-2021/204)._