The key insight is that you design a cryptographic algorithm that will preserve addition between amounts, even when encrypted but you need to also provide some encrypted data that will allow an independent verifier to validate the whole transaction.
The problem is more nuanced because you need to guarantee that coins aren't produced from thin air.
The problem of the approach in the linked article is that proofs are large. To support encrypted verification (there is no need to decrypt anything in any step of the process) you need thousands of bytes for verifying a 32-bit amount.
Bulletproofs reduced the proof size significantly. There are then additional approaches like MimbleWimble where the proofs on the ledger can be discarded to make it even smaller.
To be honest, I don't see any maths. I see a document titled "investigation" which contains a bibliography consisting of a single forum post from 2013 by someone named Adam, and then the author goes on saying that he has invented some maths that allegedly would allow confidential transactions. Forgive me if I'm a bit sceptical... better wait until some experts review this material.
The key insight is that you design a cryptographic algorithm that will preserve addition between amounts, even when encrypted but you need to also provide some encrypted data that will allow an independent verifier to validate the whole transaction.
The problem is more nuanced because you need to guarantee that coins aren't produced from thin air.
The problem of the approach in the linked article is that proofs are large. To support encrypted verification (there is no need to decrypt anything in any step of the process) you need thousands of bytes for verifying a 32-bit amount.
Bulletproofs reduced the proof size significantly. There are then additional approaches like MimbleWimble where the proofs on the ledger can be discarded to make it even smaller.