Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[Feature request] Cap "select all" coin selection at 256 inputs (the per-transaction maximum)

オープン
  • 何か問題がありますか？
#316 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
android, kotlin
領域
mobile

調査の方向性

Start by locating the Android send flow’s coin control screen and the code that handles “Select all” for manually selected UTXOs. Trace how that selection reaches transaction building, and check whether an existing coin selection rule sets the input order or limit. Done means selection is capped at 256, the UI reports how many remain, and the large manual selection failure is investigated.

索引モデルが issue の本文から書いたものです。

説明

Title: Cap "select all" coin selection at 256 inputs (the per-transaction maximum)

Description

When a wallet has more than 256 UTXOs, the "select all" option in manual coin control currently tries to include every input. Since a single transaction supports at most 256 inputs, this results in an invalid or failing transaction rather than a usable one.

Expected behaviour

"Select all" should select the top 256 UTXOs (e.g. largest-value first, or whatever ordering coin selection already uses), filling the transaction to its maximum input count instead of exceeding it. The UI should make it clear that the selection has been capped and how many UTXOs remain unselected.

Current behaviour

All UTXOs are selected regardless of count, so wallets with >256 UTXOs cannot use "select all" to build a valid transaction.

Steps to reproduce

  1. Use a wallet (mainnet, testnet, or Liquid) holding more than 256 UTXOs.
  2. Open Send → coin control / manual UTXO selection.
  3. Tap "Select all".
  4. Attempt to build or sign the transaction.

Proposed solution

  • Change "Select all" to select min(total_utxos, 256) inputs, ordered by value descending (or by the existing coin-selection heuristic).
  • Show a notice such as "256 of N UTXOs selected (transaction limit)".
  • Optionally offer a "Select next 256" action so users can consolidate large UTXO sets across several transactions.

Related: sending 255 manually selected inputs fails

Even staying under the limit, building a transaction with 255 manually selected UTXOs fails with:

Made one or multiple attempts, all errored:
	- EOF while parsing a value at line 1 column 0

This looks like a serde_json error from GDK receiving an empty response from a backend call (fee estimation, UTXO fetch, or broadcast) rather than a transaction-construction error. Possibly a request timeout or payload size limit when the input set is large.

Steps to reproduce

  1. Open Send → coin control.
  2. Manually select 255 UTXOs.
  3. Enter a recipient and amount, continue to review/sign.
  4. Error above is shown; the transaction is never built.

Questions for maintainers

  • Is there a practical input limit below 256 that the app enforces or should enforce?
  • Does the same happen with a smaller selection (e.g. 100 inputs)? (fill in if you've tested)
主要言語
Kotlin
スター
272
フォーク
110
30日以内にマージされた PR はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Blockstream/green_android のほかの issue

Blockstream/green_android の issue をすべて見る

似ている issue

Kotlin の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。