Hi Dan,
I'm deploying a React app (~1.3MB total, 14 files) using react-onchain with a WoC+ARC adapter (GorillaPool's ordinals indexer has been down for 2+ days). Small files (< 50KB each) inscribe and mine fine — 12 out of 14 consistently get MINED status. But the two large bundles (308KB JS + 918KB Three.js chunk) always end up as SEEN_IN_ORPHAN_MEMPOOL on ARC.
What I've tried:
Multiple payment keys (fresh UTXOs, no mempool conflicts)
Sequential broadcasting with 10-15s delays between transactions
15s wait after the UTXO split tx before broadcasting inscriptions
Verified the split tx is MINED before inscriptions broadcast
Confirmed ARC policy shows maxtxsizepolicy: 100000000
Fixed broadcast to use raw hex with Content-Type: text/plain (was incorrectly JSON-wrapped initially)
The small inscriptions all spend from the same split tx outputs and mine fine. The large ones also spend from the same split tx but consistently orphan. This reproduces across 5+ deploy attempts.
Questions:
Is there a practical relay size limit for individual inscription transactions that ARC or BSV mining nodes enforce, separate from the advertised policy?
Does react-onchain build large inscription transactions differently from small ones (e.g. chaining vs parallel split outputs)?
Have you seen this issue before with large file inscriptions?
Using react-onchain v1.2.2 with a custom WoC+ARC indexer adapter. Happy to share the fork if helpful.
Thanks!
BSVanon
Hi Dan,
I'm deploying a React app (~1.3MB total, 14 files) using react-onchain with a WoC+ARC adapter (GorillaPool's ordinals indexer has been down for 2+ days). Small files (< 50KB each) inscribe and mine fine — 12 out of 14 consistently get MINED status. But the two large bundles (308KB JS + 918KB Three.js chunk) always end up as SEEN_IN_ORPHAN_MEMPOOL on ARC.
What I've tried:
Multiple payment keys (fresh UTXOs, no mempool conflicts)
Sequential broadcasting with 10-15s delays between transactions
15s wait after the UTXO split tx before broadcasting inscriptions
Verified the split tx is MINED before inscriptions broadcast
Confirmed ARC policy shows maxtxsizepolicy: 100000000
Fixed broadcast to use raw hex with Content-Type: text/plain (was incorrectly JSON-wrapped initially)
The small inscriptions all spend from the same split tx outputs and mine fine. The large ones also spend from the same split tx but consistently orphan. This reproduces across 5+ deploy attempts.
Questions:
Is there a practical relay size limit for individual inscription transactions that ARC or BSV mining nodes enforce, separate from the advertised policy?
Does react-onchain build large inscription transactions differently from small ones (e.g. chaining vs parallel split outputs)?
Have you seen this issue before with large file inscriptions?
Using react-onchain v1.2.2 with a custom WoC+ARC indexer adapter. Happy to share the fork if helpful.
Thanks!
BSVanon