I really enjoyed reading, thanks for writing this!
I have some minor comments (feel free to ignore them)
who told the foundations of Grin’s consensus Mimblewimble.
MW isn’t a consensus, it’s a blockchain format/design.
I think Jedusor made a mistake in his whitepaper when calculating the chain size. At that time, the chain would be slightly larger than Bitcoin because the rangeproofs were quite bigger. I’d need to verify this though. With today’s rangeproofs, we are about 1/4 of Bitcoin size.
There’s a typo in Shiba Inu.
Are the yearly inflation numbers for Bitcoin correct? The first 4 years should be the same as Grin’s.
if the Grin sent to the wrong address, since the signature of the recipient’s wallet is needed, the Grins sent to the wrong address will not be lost because the signature will not be received.
This is confusing because there are no addresses on Grin/MW. The Tor address is an offchain way to transport a slate from one person to another. The reason why you can’t lose Grin is because the receiver explicitly accepts the coins in a transaction. Unlike on other chains, every Grin transaction has a “proof the receiver claimed the coins” or whatever we would call this.
I think the name letters part about the number 15 could be dropped.
Again, good job writing this, it’s great seeing energy put in the posts.
I think it’s important to state that you can send to the wrong address in grin (ofc we are talking about the “contact” address, not btc-like address). I can always make a SRS where i accidently pick the wrong receiver. What you can’t do is send to an address not owned by anyone because nobody will respond to it (if it’s encrypted). To avoid sending to the wrong address we have the invoice flow and here’s why invoices are great. With standard flow you can make a mistake and put the wrong receiver, the receiver has incentive to not reveal the mistake and sign the transaction to receive the money. With invoice flow you can make a mistake and put the wrong sender, the sender (very likely) has no incentive to pay, so the tx won’t be completed.
as content for a book, i think it could work. but as a standalone article, i think you could cut out half of the content. make it more to the point or on-topic.
It was just something unique to this article. The format of the book will be different and I will not add the story part. Instead of this Instead, there will be more detailed technical information.