# Looking for Core 30/31 peers that relay \>83-byte OP\_RETURN transactions

**URL:** <https://community.start9.com/t/looking-for-core-30-31-peers-that-relay-83-byte-op-return-transactions/5710>\
**Category:** StartOS Support\
**Created:** [September 5, 2026, 9:46pm UTC](https://community.start9.com/t/looking-for-core-30-31-peers-that-relay-83-byte-op-return-transactions/5710 "2026-09-05T21:46:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![degard](https://community.start9.com/letter_avatar_proxy/v4/letter/d/9dc877/32.png) [@degard](https://community.start9.com/u/degard)\
**Post date:** [September 5, 2026, 9:46pm UTC](https://community.start9.com/t/looking-for-core-30-31-peers-that-relay-83-byte-op-return-transactions/5710/1 "2026-09-05T21:46:20Z")

</div>

**Hi,**

I’m looking for one or more known-good Bitcoin P2P peers for a coin-splitting/replay-protection setup on StartOS.

I am using the oversized-OP\_RETURN method demonstrated by Bitcoin University: an Electrum self-send containing an OP\_RETURN larger than 83 bytes, intended to provide replay protection against the BIP110 chain.

My StartOS Bitcoin node is configured to relay OP\_RETURN transactions with the current default maximum size of `100000 bytes`.

I initially broadcast a test transaction through my own node. It entered my local mempool successfully, and:

`getmempoolentry <txid>` returned `unbroadcast: false`.

However, even after several hours the transaction was not visible on either Blockstream Explorer or mempool.space.

I then inspected my peers. I have roughly ten outbound peers; almost all report `/Satoshi:29.x/` or older, with only one `/Satoshi:31.0.0/` `outbound-full-relay` peer.

**The decisive test:** I connected Electrum to the public server

`bitcoin.mullvad.net:5010`

and rebroadcast the **exact same signed transaction** — same raw transaction, same TXID, no RBF and no modification.

The transaction then appeared on Blockstream Explorer almost immediately.

This strongly suggests that the transaction itself is fine and that the remaining problem is the **relay path through my current Bitcoin P2P peers**.

### What I’m looking for

Does anyone know one or more **publicly reachable Bitcoin Core 30/31 P2P nodes that are known to relay \>83-byte OP\_RETURN transactions** , ideally using the Core 30+ `datacarriersize=100000` default?

I would like to add them as **additional `addnode` peers** to my StartOS Bitcoin node, without replacing normal peer discovery, and then repeat the propagation test.

In particular, I’m looking for:

- a known-good `host:port` P2P endpoint;
- a way to identify or verify peers that actually relay oversized OP\_RETURN transactions;
- or any Start9-recommended peers/settings for this particular Core 30+ relay-policy situation.

The objective is to perform the actual coin split through **my own Electrum → my own StartOS/Bitcoin node → suitable P2P peers** , rather than relying on a third-party Electrum server for the final transaction.

Also, if StartOS provides a preferred way to configure persistent `addnode` peers through the Bitcoin service UI rather than `bitcoin-cli addnode`, I’d appreciate the exact setting.

Thanks!

_[This post was created with the help of ChatGPT and fine-tuned by me._ 🙂 _]_