<p>No such support exists in the bitcoin protocol. Use a different receiving address for every transaction to uniquely identify them, if you do this correctly then no external labels are necessary. </p>

CC BY-SA 3.0
2014-04-02T19:16:36.067Z
This isn't strictly true, is it? For example, you could embed arbitrary data in a custom output script. But it would be more a kludge than an intended feature, and since the transaction would be nonstandard you'd have extra trouble getting it transmitted and confirmed. But people have included data in the block chain this way before.
Nate Eldredge
CC BY-SA 3.0
2014-04-02T19:29:40.117Z
we have prunable outputs as of Bitcoin core 0.9
Mark S.
CC BY-SA 3.0
2014-03-03T17:38:08.757Z
2014-03-03T17:38:08.757Z
user13413
<p>I'm not too sure how I can expand on this. </p>

<p>Let's say that you want to tag the actual transaction with 'Rent' or 'Bill'. </p>

<p>Is there a field where I can insert a string for the other party? Note that this doesn't need to be hashed, it can be clear text.</p>

<transactions>
Can a bitcoin transaction hold an arbitrary string or strings for reference?
TheMightyLlama
# Can a bitcoin transaction hold an arbitrary string or strings for reference?

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

I'm not too sure how I can expand on this.

Let's say that you want to tag the actual transaction with 'Rent' or 'Bill'.

Is there a field where I can insert a string for the other party? Note that this doesn't need to be hashed, it can be clear text.

**Tags:** transactions


---

## 1 answers

### Answer by username_1 on 2014-03-03. Score: -2

No such support exists in the bitcoin protocol. Use a different receiving address for every transaction to uniquely identify them, if you do this correctly then no external labels are necessary.

> **Comments:**
> **username_2**: This isn't strictly true, is it? For example, you could embed arbitrary data in a custom output script. But it would be more a kludge than an intended feature, and since the transaction would be nonstandard you'd have extra trouble getting it transmitted and confirmed. But people have included data in the block chain this way before.  
> **username_3**: we have prunable outputs as of Bitcoin core 0.9  

---

