I am considering this sIgn protocol to create an audit package, and to be honest, I like the idea and its implementation, but only if it is truly effective and not too complicated. To me, the simple thing is that I sign something, and it should leave a clear trace, not too many tools and messy logs. Just a neat package declaration, payment references, and the version of the rules that were used, that's it.
The statement needs to clearly show what has happened, with no estimation. References to the settlement agreement? That is evidence that everything has truly ended and is not just in the process of being resolved forever, and the version of the rules is more important than people think. If the rules change later, I still want to know which rules were used at that time, not rewriting old history...
I have seen systems where everything is scattered everywhere, and when something goes wrong, everyone blames each other. That’s why I like the idea of packaging everything together in one package...
I like the idea of packaging goods because it includes everything, signed and sealed. I have no argument about that, just checking.
But I am also careful; if it changes a complicated process or slows down the approval process, it will ruin the whole point. This process should be quick, automated, and boring in a nice way; I shouldn't even think about it unless something is wrong.
I like that but only if it maintains simplicity and honesty, nothing extra, just authentic evidence is enough...
I always keep everything related to technology simple, bringing everything together and not trusting anything that cannot be proven effective later. Always learn, master the basics of technology, and do not forget to cultivate knowledge for yourself as well as for others... @SignOfficial $SIGN #SignDigitalSovereignInfra
