signature chain just for verification or the docs are also stored on the chain,like IPFS did?
No, nothing gets stored on the blockchain, no one gets to see the content of the files. We work with timestamps and hash ID's.
Each file has its own unique hash ID, when the file gets altered the hash ID changes with it. Combining this with timestamping allows us to certify authenticity of basically anything digital without people actually getting to see the contents of what is being certified.
So,why need a new chain to get hash ID when there were such service based on bitcoin?
http://www.proofofexistence.comMy argument would be because Bitcoin itself is aging. If we ever reach the transaction fees from 2017 again it'll be more expensive than doing centralized certification, in some cases even slower.
With our token based on the Waves Platform we have almost instant transactions, super cheap fees and the added plus of easily making connections with other projects on the Waves Platform. There are a whole lot of reasons why we chose to go this route.
One example of the "easily making connections", not that we expected any of this when starting the project. Our lead developer now has really good connections with the official team of the Waves Platform as he lately joined the official team as lead for the Phillipines. Also Waves Grants has supplied us with two grants for further development. Add to that the two partners we have made on the Waves Platform.
In short, there are a lot of benefits to creating our service with our own token. Simple benefits are cheap fees, fast speeds, connections, support, partnerships etc.
I do ofcourse understand your view as lots of projects do not need their token but could just build it on Bitcoin or Ethereum, but wirh us that simply is not the case. We want to improve upon the current centralized, pricy and slow system.
