[Bitcoin-development] Help with PR 3845

2014-04-06 Thread Daniel Newton
https://github.com/bitcoin/bitcoin/pull/3845 (Add a method for removing a single wallet tx) Hi All, I am hoping there are some who would like to review/test this pull request. Basically it enables a user to zap individually those pesky zombie transactions that were popping up a couple of months a

Re: [Bitcoin-development] Feedback request: colored coins protocol

2014-04-06 Thread Mark Friedenbach
On 04/06/2014 01:59 PM, Flavien Charlon wrote: > Do you think this is the right approach? No, I'm afraid it has significant flaws. The two chief flaws are (1) there is absolutely no reason to include asset tagging information if it is not validated - that just bloats the block chain, and (2) you s

[Bitcoin-development] Feedback request: colored coins protocol

2014-04-06 Thread Flavien Charlon
Hi, I am the lead developer of Coinprism , the new colored coins web wallet. After some discussions with the other people involved with colored coins, I wrote a specification document describing the colored coins protocol that we are using in coinprism. I am looking fo

Re: [Bitcoin-development] Standardizing OP_RETURN message format

2014-04-06 Thread Peter Todd
On Sun, Apr 06, 2014 at 09:35:20AM +0200, Maciej Trebacz wrote: > So, OP_RETURN is here and there is no coming back. So if we have it, it > would be nice to actually make use of it in a good way. I would like to > write a process BIP with a proposal for standardizing OP_RETURN > transactions for be

Re: [Bitcoin-development] Standardizing OP_RETURN message format

2014-04-06 Thread Gregory Maxwell
On Sun, Apr 6, 2014 at 12:35 AM, Maciej Trebacz wrote: > 00 01 | none | Proof of burn transaction. Use it if you want to effectively > destroy coins (by sending it all as fees to miners) For just having a dummy output for an all fee transaction you do not need to have a PUSH at all.

[Bitcoin-development] Standardizing OP_RETURN message format

2014-04-06 Thread Maciej Trebacz
So, OP_RETURN is here and there is no coming back. So if we have it, it would be nice to actually make use of it in a good way. I would like to write a process BIP with a proposal for standardizing OP_RETURN transactions for better interoperability between services. Right now there are no guideline