Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Enforce Core-compatible OP_RETURN / datacarrier and standard tx-size limits in create_tx

未关闭
#339 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 3 天内回复

@tvpeter 已经在做这个了。

开始于 2026年9月26日。

评估

这个 Issue 还没有评估数据。

描述

enhancement

Describe the enhancement

wallet create_tx can attach an OP_RETURN via --add_string / --add_data, but does not implement Bitcoin Core relay policy for:
how large that OP_RETURN script may be (datacarrier)
how large the resulting transaction may be (MAX_STANDARD_TX_WEIGHT)

The documentation says “max 80 bytes”, which matches the pre-v30 Core default. That limit is not actually enforced, and it is no longer the Core default.
A tx that create_tx successfully creates can be non-standard and fail at broadcast against default Core / most public relays.

Use case

Anyone embedding data with --add_string or --add_data currently will discover the problem only at broadcast, after building and signing. Failing at build time with a clear error about the tx weight and the limit will make it easier for users to reconstruct a transaction that can be relayed on the network.

The same check protects bump_fee, where a fee bump can push an already-large transaction over the limit, and any command whose inputs grow the witness.

Additional context
Split out of #326, which fixed the create_tx/bump_fee panics and --fee_rate truncation.

主要语言
Rust
星标
143
派生
98
平均合并
5 天 21 小时
30 天内合并 PR
4

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

bitcoindevkit/bdk-cli 的其他 Issue

查看 bitcoindevkit/bdk-cli 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。