Repository navigation
Description
Expected Behavior
An asset lock that is already mined and chain-locked should be creditable with a chain asset lock proof, including when the Core transaction has more than 100 inputs. A chain proof carries only the outpoint and a height, so the input cap that exists to keep an instant proof under the 20 KB state-transition limit does not apply to it.
Please say when this will be accepted. Is the change in protocol version 15 / Platform v5.1, before the protocol 15 tables are frozen? If it is not, which protocol version will include it, and when does that release ship?
Current Behavior
Finish of a shielded transfer funded by a mined asset lock fails on every attempt:
shielded resume fund-from-asset-lock failed: SDK error: Protocol error: Asset lock transaction has too many inputs: 303 (max 100). Consolidate UTXOs before creating the asset lock.
That is consensus error 10534 (IdentityAssetLockTransactionTooManyInputsError, max_asset_lock_transaction_inputs = 100). The Core transaction is already confirmed and chain-locked. Its only output is an unspendable OP_RETURN (6a00), so the Dash is in the credit pool and cannot be spent back on L1. Platform has not credited it. The value is available on neither chain.
Mainnet transaction:
- TXID:
e3e7bc269314a6520c031f256da73d047c890d3d3e5e6195a13ec1fa5295cd6e - Block 2568139, mined 2026-11-07 05:16:57 UTC
- 303 inputs, 44,753 bytes, no InstantSend lock
- Credit / OP_RETURN output: 200.00212852 DASH
- Fee: 0.00044955 DASH
Dash Core treats more than 100 inputs as non-standard, not as invalid, so a miner on an older node included this lock. Rescan, dropping unconfirmed transactions, restarting, and Finish now all hit 10534 again. Consolidating the remaining UTXOs does not apply: the lock is already mined.
Possible Solution
#5682 (fix(dpp)!: hold only an instant asset lock proof to the asset lock input cap (PV15)) is the change that does this: from protocol version 15, count inputs only on an instant proof, and keep every other asset-lock check. It was closed on 2026-10-30 without an explanation, and the branch was deleted.
#5714 already notes that a lock mined by a pre-v23.1.7 node leaves funds in a credit output Platform refuses, and that this case needs its own handling (same situation as support ticket 32104, there with 121 inputs). #5759, merged 2026-11-06, refuses to resume an oversized lock. That is right for a lock Core will not relay. It does not credit one that is already mined. Its description says a row the local record already proves final is completed from that proof, while a mined lock with no usable proof still ends in the input-cap error.
Please reopen #5682 or land the same consensus change before the protocol 15 freeze. The next chance after that is protocol 16.
After activation, recovery should be an app update and Finish Transfers using the chain asset lock proof for this outpoint. The mined lock has no expiry. No further action is possible on the wallet side until the protocol accepts the proof.
Steps to Reproduce (for bugs)
- From DashPay for iOS on mainnet, move Dash from the transparent balance to the shielded balance while the wallet holds only small UTXOs, on a build that still assembles an asset lock of more than 100 inputs.
- Have that asset lock mined (a node older than the
assetlocktx-too-many-inputsrelay rule can include it). Confirmed example:e3e7bc269314a6520c031f256da73d047c890d3d3e5e6195a13ec1fa5295cd6e, 303 inputs, block 2568139. - Open the pending transfer and tap Finish now / Finish Transfers.
- Platform returns 10534. The 200.00212852 DASH credit output stays unclaimed.
Context
This is a mainnet case of 200.00212852 DASH locked by a wallet build that Platform consensus now rejects. The wallet fixes that stop new oversized locks (#5712, #5759, dashpay/rust-dashcore#1191, dashpay/dashwallet-ios#1221) cannot credit a lock that is already in a chain-locked block. Only a protocol change can.
The question this report needs answered is when that change ships, and whether it is still planned for protocol 15 / Platform v5.1.
Your Environment
- Version used: Dash Platform mainnet consensus (error 10534). Wallet: DashPay for iOS, mainnet. App build number was not recorded.
- Environment name and version: mainnet, block 2568139
- Operating System and version: iOS
- Link to your project: fix(dpp)!: hold only an instant asset lock proof to the asset lock input cap (PV15) #5682
Activity
shumkov commentedon Nov 10, 2026
Thanks for the detailed report. The consensus change landed in #5825, merged into
v5.1-dev.What changed: from protocol version 15, Platform no longer holds a chain asset lock proof to the 100-input cap. The cap exists so that an instant proof, which carries the whole transaction inside the state transition, stays under the 20 KiB limit. A chain proof carries only the outpoint and a height, so the cap now applies to instant proofs only. All other asset lock checks are unchanged.
When it applies: it ships in Platform v5.1 and takes effect once protocol version 15 is active on mainnet. Mainnet currently runs protocol 14, so until activation every Finish attempt still returns 10534.
What you need to do: once protocol 15 is active on mainnet, update DashPay to a build based on Platform v5.1 and tap Finish Transfers. The 10534 you see is Platform refusing a chain proof your wallet already submitted for this lock, so the wallet already has everything it needs, and the same Finish should go through after activation. The lock does not expire, and the failed attempts change nothing on either chain. Each shielded Finish builds a new transition, so earlier rejections will not get in the way of the attempt after activation.
I'm leaving this issue open for a related wallet-side case. A lock over 100 inputs whose wallet record hasn't yet seen the lock mined (for example right after a restore) can still be refused by the wallet itself, before any chain proof is tried. That case doesn't apply to your transfer: your wallet already has the proof.