If you don't have a ToTheBlockchain account before replying to a tweet with #ToTheBlockchain, we'll reply to you telling you to setup your billing information.
Any text after the hashtag is currently ignored but in the future will be used as parameters (writing to different blockchains, copying specific metadata, etc.)
If there's text before the #ToTheBlockchain hashtag, then the archive will not be triggered. This was intentional so people can mention #ToTheBlockchain mid-sentence without triggering an archive.
We write the tweet (in the format below) to a Bitcoin transaction broken up 1 OP_RETURN output and multiple "fake" P2SH outputs. "Fake" because these outputs aren't addresses with known private keys but tweet data disguised to look like a key.
OP_RETURN TTB-T,$AUTHOR_NAME,$TWEET_ID,$TWEET_TIMESTAMP,$ARCHIVE_REQUESTOR_NAME OP_HASH160 TWEET[0..20] OP_EQUAL OP_HASH160 TWEET[21..40] OP_EQUAL OP_HASH160 TWEET[41..60] OP_EQUAL OP_HASH160 TWEET[61..80] OP_EQUAL ...etc
We reply to the tweet asking for an archive with a screenshot of the original tweet being replied to and text saying that it is "on the blockchain" and a link to the transaction
The TTB-T prefix is a convention we're currently using for all Tweets written to blockchains via this service. We may end up removing it.
OP_RETURN TTB-T,bob,986074763394321123,1523996979,alice OP_HASH160 Hello World OP_EQUAL // the tweet's text will be spread across P2SH (pay to script hash) outputs in 20 byte chunks