<p>There is [old] bitcoin version by Lukejr
<a href="http://eligius.st/~luke-jr/programs/bitcoin/files/bitcoin-qt/next/test/20130721/" rel="nofollow">http://eligius.st/~luke-jr/programs/bitcoin/files/bitcoin-qt/next/test/20130721/</a>
It accepts and relays non-standard transactions running with commandline option "-acceptnonstdtxn"</p>

<p>It is very unstable program, use it with separate database and empty wallet.dat
But it definetely works.</p>

<p>There is at least one pool, which accepts non-standard transactions
It is eligius.st
Its public IP-address is 192.3.11.20
Just add option "connect=192.3.11.20" in your conf file or commandline param and you are a part of "non-standard relaying network"</p>

<p>for more information refer to
<a href="https://bitcointalk.org/?topic=260749" rel="nofollow">https://bitcointalk.org/?topic=260749</a></p>

CC BY-SA 3.0
2014-05-14T08:06:27.893Z
yesterday i've sent tx with non-standard input script https://blockchain.info/ru/tx/6cbca41fcb4d3fdbc900be4a1e7225cfbf929cae61686e0fa42a9ed521648894 and my transacton was successfully included into the next Eligius block #300598
amaclin
CC BY-SA 3.0
2015-05-11T00:10:21.680Z
As of May 2015 the only Eligius node IP I can find that's accepting connections is 68.168.105.168.
Max Kaye
CC BY-SA 3.0
2014-05-12T19:19:54.880Z
2014-05-12T19:19:54.880Z
amaclin
<p>0.8.6 still relays transactions with malleable signatures. This fix has been implemented in 0.9.x. However, only a very few percentage actually runs 0.9.x because it's not yet officially released. It's still a release candidate (RC), i.e. feature-complete but not widely tested yet.</p>

CC BY-SA 3.0
2014-03-13T02:38:03.170Z
I don't think the question is about malleable signatures but about nonstandard scripts.
Nate Eldredge
CC BY-SA 3.0
2014-03-12T20:45:37.707Z
2014-03-12T20:45:37.707Z
Luca Matteis
<p>Which Bitcoin node implementations, if any, currently relay valid transactions that use so-called 'non-standard' scripts? What proportion of the network is made up of these implementations? What proportion of the network's hashing power will include transactions with valid but 'non-standard' scripts in their blocks?</p>

<p>To clarify the term 'non-standard', I'm referring to the function <a href="https://github.com/bitcoin/bitcoin/blob/master/src/script.cpp#L1414" rel="nofollow"><code>IsStandard()</code></a>, and the following <a href="https://en.bitcoin.it/wiki/Script#Scripts" rel="nofollow">comment on the Bitcoin Wiki</a>:</p>

<blockquote>
  <p>non-standard scripts are accepted if they are in a block, but nodes will not relay them.</p>
</blockquote>

CC BY-SA 3.0
2014-03-12T23:19:16.777Z
If non-standard scripts were included in blocks that don't validate with standard nodes you wouldn't be mining Bitcoin anymore, but a fork from Bitcoin that no Bitcoin miner will accept and mine on top of.
John T
CC BY-SA 3.0
2014-03-13T01:38:23.573Z
@JacobTorba I'm only talking about valid scripts that _do_ validate with normal nodes. The question is about what implementations _relay_ non-standard scripts.
bames53
<script><nodes><non-standard-transaction><relay><transaction-propagation>
What node implementations and mining pools relay and process 'non-standard' scripts?
bames53
# What node implementations and mining pools relay and process 'non-standard' scripts?

(Asked by: username_0 on 2014-03-12)

Which Bitcoin node implementations, if any, currently relay valid transactions that use so-called 'non-standard' scripts? What proportion of the network is made up of these implementations? What proportion of the network's hashing power will include transactions with valid but 'non-standard' scripts in their blocks?

To clarify the term 'non-standard', I'm referring to the function [`IsStandard()`](https://github.com/bitcoin/bitcoin/blob/master/src/script.cpp#L1414), and the following [comment on the Bitcoin Wiki](https://en.bitcoin.it/wiki/Script#Scripts):

> non-standard scripts are accepted if they are in a block, but nodes will not relay them.

**Tags:** script, nodes, non-standard-transaction, relay, transaction-propagation

> **Comments:**
> **username_1**: If non-standard scripts were included in blocks that don't validate with standard nodes you wouldn't be mining Bitcoin anymore, but a fork from Bitcoin that no Bitcoin miner will accept and mine on top of.  
> **username_0**: @JacobTorba I'm only talking about valid scripts that _do_ validate with normal nodes. The question is about what implementations _relay_ non-standard scripts.  

---

## 2 answers

### Answer by username_2 on 2014-05-12. Score: 1

There is [old] bitcoin version by Lukejr
<http://eligius.st/~luke-jr/programs/bitcoin/files/bitcoin-qt/next/test/20130721/>
It accepts and relays non-standard transactions running with commandline option "-acceptnonstdtxn"

It is very unstable program, use it with separate database and empty wallet.dat
But it definetely works.

There is at least one pool, which accepts non-standard transactions
It is eligius.st
Its public IP-address is 192.3.11.20
Just add option "connect=192.3.11.20" in your conf file or commandline param and you are a part of "non-standard relaying network"

for more information refer to
<https://bitcointalk.org/?topic=260749>

> **Comments:**
> **username_2**: yesterday i've sent tx with non-standard input script https://blockchain.info/ru/tx/6cbca41fcb4d3fdbc900be4a1e7225cfbf929cae61686e0fa42a9ed521648894 and my transacton was successfully included into the next Eligius block #300598  
> **username_3**: As of May 2015 the only Eligius node IP I can find that's accepting connections is 68.168.105.168.  

---

### Answer by username_4 on 2014-03-12. Score: 0

0.8.6 still relays transactions with malleable signatures. This fix has been implemented in 0.9.x. However, only a very few percentage actually runs 0.9.x because it's not yet officially released. It's still a release candidate (RC), i.e. feature-complete but not widely tested yet.

> **Comments:**
> **username_5**: I don't think the question is about malleable signatures but about nonstandard scripts.  

---

