Pages:
Author

Topic: Version 0.3.18 - page 3. (Read 27005 times)

legendary
Activity: 938
Merit: 1001
bitcoin - the aerogel of money
December 09, 2010, 10:27:10 AM
#40
Just wait until somebody encodes kiddie porn into the chain - it would stay there forever.

It is impossible to completely prevent that kind of abuse unfortunately.

For example, someone could encode information in the decimal figures of amount sent, or in a "vanity plate" Bitcoin address.

Probably not practical for jpeg or mpeg files, but for other low-bandwidth "illegal data" such as Blu-Ray keys, this is bound to happen sooner or later.

Even "low bandwidth kiddie porn" could create big problems for us one day. All over the world, legislation is becoming more draconian every year and in some countries even the "wrong" kind of fiction and poetry is now considered kiddie porn by the courts and thus illegal.
founder
Activity: 364
Merit: 7065
December 09, 2010, 10:17:53 AM
#39
I came to agree with Gavin about whitelisting when I realized how quickly new transaction types can be added.

why not make it easier on everyone and just allow say, 64 or 128 bytes of random data in a transaction?
That's already possible.   OP_CHECKSIG.   can be 33 to 120 bytes.

I also support a third transaction type for timestamp hash sized arbitrary data.  There's no point not having one since you can already do it anyway.  It would tell nodes they don't need to bother to index it.
legendary
Activity: 1652
Merit: 2301
Chief Scientist
December 09, 2010, 09:51:07 AM
#38
by default disallow non-standard transactions that exceed 128 bytes (or whatever threshold is agreeable)?

I would like to hear why the above option was thrown out by the developers.

Several months ago, around the time when the 0.3.9 bugs were found, I privately told Satoshi that I thought whitelisting acceptable transaction types was a better way to go, rather than blacklisting transaction types that we find out cause problems.

The danger is similar websites that try to blacklist