Topic: CryptoGraffiti - Block Chain Message Encoder & Decoder - page 7. (Read 35470 times)

A minor bug fix: yesterday bitikunn fixed the bug that caused newlines to disappear when displaying messages on the read tab.

Just to let you know, I've been working on automated message encoding lately and soon it will go live, so you no longer need to import addresses into your wallet manually in order to save your message in the block chain. when my automated encoder goes online, you can save your text even with wallet software that does not allow multisend.

this is amazing man
thankyou 

Sad news, both of the new Graphical User Interface developers quitted after failing to complete the new version in 2 months. They worked 5 hours per week and were offered 25% share (per face) of the donations/profit the site generated. One said "Right now it's difficult to work assuming that one day Bitcoin may become SOMETHING."

Seems like a plausible idea. If the same computer network secures sidechains too then it will probably work out pretty well.

edit: But... that still does not stop people from encoding messages into Bitcoin's block chain.

Shouldn't CryptoGraffiti be implemented as a sidechain, with the option to make as many changes to Bitcoin Core as the application needs? I started a related thread here. https://bitcointalksearch.org/topic/web-on-a-sidechain-838813

It can but that does not stop people from encoding messages into transaction outputs. The current approach allows free, manual and immediate message storing while OP_RETURN would require a payment proxy that would make the actual transaction. The GUI of a typical bitcoin wallet such as Bitcoin-core does not let you to play around with OP_RETURN.


Thanks for the info, I created an issue for the UI developers about that.

iPhone is not a meangiful Platform.  You must turn to Android ones for better. 

FYI, the site does not work on the iPhone.

Could this service be changed so it uses recommended OP_RETURN outputs for messages? This would then keep these outputs out of UXTO.

Thanks for pointing that out. I haven't actually used any other bitcoin wallet than Bitcoin-core and Electrum. However, now that I know some wallets haven't implemented multisend I must raise the priority of getting automated message writing implemented soon. The latter would allow you to write a message by making a transaction with a single output to our to-be-developed message encoder which would in turn make the real multi-output transaction for you. The drawback of such a payment proxy would be waiting for confirmations.

Thanks.  I am using MultiBit which doesn't support the send-to-many.

Service is free. It is currently hardcoded to the user interface to have 5500 satoshis per output address as it was the minimum amount some time ago. However, right now the Bitcoin-core wallet lets you send 1500 satoshis to a single output at minimum. The CryptoGraffiti decoder does not care about the number of satoshis sent to an address, all it cares about is whether the address contains human readable text or not.

edit 2:
I locate messages by attempting to decode every BTC transaction that has been included in a new block. If I find any human readable text then I will store the transaction hash as a pointer to an "interesting" transaction. I haven't approached Google.


1. This is a typo that will be fixed in the next release.
2. Under normal conditions the message should show on CryptoGraffiti.info instantly (3-10 seconds). Heavy load or network lag could cause it to take longer.

Wrong, when instant is selected it will appear on CryptoGraffiti.info in 3-10 seconds.
edit: However, due to the bug in the current UI you would need to refresh the page yourself though.


CryptoGraffiti.info considers 1 message to be encoded in a single bitcoin transaction. If you're using some other message writing service then it can happen that a single message gets written into multiple bitcoin transactions. Such messages cannot be intuitively extracted because there is no known standard to determine the order of those messages.

What might also be the case is that you failed to make a send-to-many bitcoin transaction.

Answer to #2 is after 1 confirmation.

Answer to #1 is it appears to be a programming typo.

New question:
I posted a message to the blockchain and it broke it into 4 separate messages.  Why?

Two questions:
1. The date/time stamp on the latest messages on your site shows 2014/09/24.  It is 10/24.  Is this a programming typo?

2. If instant is selected, how long does it take for it to show on your website (assuming Blockchain.info shows the transaction)?

The service is free?  Or 5500 Satoshi's per message block?

For locating the messages, do you search for your Bitcoin address?  Or is it a pre-pended identifier in the Blockchain?

Have you considered approaching Google to index the Blockchain?

I think it must be implemented in the BTC wallets, as option 

Thank you for your idea. We have these features in our TODO list but at the moment we are working on a new framework which is a prerequisite for all these advanced use cases.

Feature request:
It is currently really difficult to find one's graffitis after a while. I propose a search function for btc address or transaction, or maybe even part of the text of the graffiti!

I don't know about that site, but when I did "proof of existence" for some casascius coins, the process was different:

proof of existence doesn't necessarily have to store the data in a readable form in the blockchain. In my case I just used the hash of an image as a private key and published a transaction to the respective address. This has the advantage that I can remove the money again from that address so I'm not polluting the unspent transaction output list with dust. It has the disadvantage of not actually having the data in publicly readable form in the blockchain (the private key (data) cannot be derived from the address).

example:

click for larger version

the proof can still be conducted, but only with an unpruned full blockchain available.

That's a nice idea, thank you! I could implement a possibility for the message's creator to remove the message from my database. The message will still be in the block chain but my service would not display it any more. The process would require the user to prove ownership over one of the input addresses that were used to make the transaction. The latter is easily done with the signature functionality that comes with Bitcoin's private keys.