It's not just privacy that appealing about Grin, it's designed to scale based on usage. Grin is designed so that its network doesn’t get dragged to a standstill when transaction volume increases. This was the core issue in the Bitcoin block-size debate: there were more transactions than could fit into a 1Mb block. As long as there’s a restrictive block size limit, there will be a capacity issue. A dirty little secret is that to get around scalability issues, almost all payment processors and exchanges do off-chain transactions. Which begs the question: why bother using a cryptocurrency with blockchain? It’s a slippery slope. Increasing usage will of course increase transaction volume. To ensure that a block size can continue to accommodate volume increases, you have to streamlining each block by trimming transactions. MimbleWimble/Grin maintains that if an output spends an input, you no longer have to keep them because they cancel each other out. This greatly cuts down the amount of data you have to store and process. The only data that nodes keep is unspent outputs and block headers. Instead of thinking of blockchain capacity in terms of number of transactions, MimbleWimble/Grin is designed to grow with the number of users using cut-through. The streamlined blocks make growth sustainable over time as the transaction data set does not continue to get bigger. This increases privacy since transaction data gets removed and it also enables fungibility. That's the scalability answer Grin brings, in addition to privacy by default.
Grin is an implementation of the Mimblewimble protocol. 100% open-source and community-driven. There's no ICO, no pre-mine, and no founder's reward. Repo at https://github.com/mimblewimble/grin and more info available at http://grin-tech.org/
Someone can also break into your servers and manipulate your transactions. It's our business to run a secure and reliable service. Bitcoin infrastructure is fairly complex and so the probably that you'll miss something are pretty high. Isn't it better to focus on your own business rather that spend all your time and money building and maintaining the backend piece?
You don't have to trust our data - you can check it against the multitude of block explorers available in the market. However, if you use blockchain.info to check, be aware that they do not support pay-to-script transactions and will not show the transaction until it's confirmed. And you can easily check the received data.
The security of our APIs lies in the fact we don't store private keys - the user signs their own transaction.
I have a stronger opinion for those who live in safe countries and have no concern for the people who keep them safe and comfortable. The fact that everyone on this thread can voice their opinion freely, criticize openly, and play armchair quarterback on something they may know nothing about should speak volumes. Today and tomorrow is the time for grace for those who have laid down their life in service to our country. US Navy Seals are an elite group who undertake incredibly dangerous missions. They deserve nothing but respect on this Memorial Day. Freedom is never free.
This made me chuckle because I tease the devs I work with about this all the time: I call them artists. It's the BA vs BS. Devs have the freedom to be much more creative than engineers. I think of devs in a similar way to architects - as in a design a building kind. Btw, I am a licensed engineers. =)
The Navy Seals I have known in my life have been the most honest, bravest, and intelligent people I have ever known. I'm grateful people like this exist in the world.
Thanks! Yes, for test =). At the BoostVC Hackathon yesterday, the team that won, CoinViz, used one of our APIs to do a visual representation of the blockchain: 110k requests in 5hrs and our infrastructure was still bored.