Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write a CIP to enable RBF #1493

Open
Tracked by #1509
ninabarbakadze opened this issue Sep 17, 2024 · 1 comment
Open
Tracked by #1509

Write a CIP to enable RBF #1493

ninabarbakadze opened this issue Sep 17, 2024 · 1 comment
Assignees

Comments

@ninabarbakadze
Copy link
Member

Description

we want to be able to allow replace-by-fee system where users can override transactions with the same nonce but a higher fee

@ninabarbakadze ninabarbakadze self-assigned this Sep 17, 2024
rootulp pushed a commit to rootulp/celestia-core that referenced this issue Sep 20, 2024
…g (backport celestiaorg#1493) (celestiaorg#1496)

* build(deps): Bump pillow from 9.3.0 to 10.0.1 in /scripts/qa/reporting (celestiaorg#1493)

Bumps [pillow](https:/python-pillow/Pillow) from 9.3.0 to 10.0.1.
- [Release notes](https:/python-pillow/Pillow/releases)
- [Changelog](https:/python-pillow/Pillow/blob/main/CHANGES.rst)
- [Commits](python-pillow/Pillow@9.3.0...10.0.1)

---
updated-dependencies:
- dependency-name: pillow
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
(cherry picked from commit c1abe91f1ba28cdacdb902b2f500512fbfe67b7a)

# Conflicts:
#	scripts/qa/reporting/requirements.txt

* Resolve conflicts

Signed-off-by: Thane Thomson <[email protected]>

---------

Signed-off-by: Thane Thomson <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Thane Thomson <[email protected]>
@rootulp
Copy link
Collaborator

rootulp commented Oct 8, 2024

I have an idea for something to include in the CIP. Apparently Bitcoin's (RBF) enables users to opt-in to RBF.

allowing users to signal explicitly that their transactions could be replaced

But I assume our implementation won't ask users to opt-in to transactions that can be replaced and instead all transactions will be replaceable by default. So the CIP could describe existing RBF implementations and how our's compares.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants