Step #2 - Make this so that it write the data in the OP_RETURN, where it's supposed to go for easy debugging purposes (for other developers), or just so that you can leave a message in the way the blockchain in meant to be used for leaving messages.
Love what you guys are doing though, neat project!
Love what you guys are doing though, neat project!
I enabled OP_RETURN decoding for http://cryptograffiti.info/paystamper/ yesterday (refresh the page if you have it in cache, the version in bottom right corner should be 0.93). Just go to the monitor tab and monitor this address: 14E6WJjQbzBgxQ2LhjWehWVF9iNY191SRd. You will see this text "ascribe is hiring! ascribe.io/jobs" which is actually written after OP_RETURN (you can verify it from blockchain.info). However, currently only paystamper part of cryptograffiti is able to decode OP_RETURN messages. I hope bitikunn will implement it to cryptograffiti's read tab soon.
@Hyena:
Have you thought about enabling https?
This would be useful to hide the specific message someone is going to view (because https encrypts everything after the TLD)
Also a Tor hidden service version would be cool. Even cooler would be if that version would use the hidden service of blockchain.info instead of the clearnet version.
Have you thought about enabling https?
This would be useful to hide the specific message someone is going to view (because https encrypts everything after the TLD)
Also a Tor hidden service version would be cool. Even cooler would be if that version would use the hidden service of blockchain.info instead of the clearnet version.
I have thought about enabling https although I'm not a big fan of it. Cryptograffiti actually supports application layer security but we haven't enabled it for the end users yet because it might not be so important. HTTPS could already be used to fetch the web page itself (using a self signed certificate) but for some reason I have made it to automatically switch to http. Perhaps because browsers are quite racist against self signed certificates.
I also support the idea of hosting cryptograffiti as an I2P or Tor hidden service. Alternatively, it could even be hosted in the torrent network, IPFS or Tahoe's P2P data storage platform. Cryptograffiti is already able to detect end decode JPG images from UTXOs so the clearnet cryptograffiti could at some point become controversial if someone decides to store CP images in the block chain. Should such a thing happen we would disable the automatic decoding of foul images. The hidden service version should be free of such censoring but for the clearnet one I'm just worried about my own ass
To look even farther into the future, I would add more coins to the service. For example, a coin such as dogecoin with really cheap TX fees suits better for storing custom data. I would also like to get rid of the blockchain.info API's dependencies at some point to become autonomous.
Speaking of being autonomous, cryptograffiti has the potential to become a DAO (distributed autonomous organization) similarly to NuBits, B&C Exchange and Teehe). It would earn its revenue from the paystamper-like service that encodes your data for you in the block chain for a small fee. With the help of PeerShares it would be easy to distribute dividends and pass motions about how to enhance the services. It's clear that developing it from our free time as a hobby makes things rather slow to progress. If there is enough investor interest, it could be turned into a serious project and I wouldn't be against it. After all, there is a clear need for a service such as cryptograffiti.