Hello everyone this is 'Luna' ๐คโค๏ธ๐ Told you I'm rescuing a pitbull pup. ๐ค๐
I just would like to give most sincerest thanks for all the people who contributed towards the '1c_SaveAPup' movement I got going on. Truly from the bottom of my heartโค๏ธ
Iโm looking at this sIgn protocol produce an audIt package thIng, and honestly i lIke the idea and exucation but only if it stays real and not excessIve to me it is sImple i sIgn somethIng, and it should leave behind a clean trail not so many tools disorganized logs Just a tIght package manIfest settlement refs and the rule version that was used that is it. The manIfest should show what happened, plaIn and clear and no estimation. The settlement refs? Thatโs your proof thIngs actually closed not just in progress forever and the rule versIon matters more than people think. If rules change later i stIll want to know what rules were used at the tIme no old rewriting history..... Iโve seen systems where this stuff gets scattered then when somethIng breaks everyone is poInting fingers. That is why I am into the package idea everything is bundled together in the package.... The package idea is what I lIke because it has everything, in the package., signed, and locked i don not argue with it i just check it. But i'm also careful if it changes heavy process or slow approvals, it kIlls the whole poInt. This should be fast, automatic, and borIng in a good way i should not even thInk about it unless something goes wrong. Iโm into it but only if it stays lean and honest no extra layers, just proof that holds up..... i keep tech related thing sImple bundle everything and donโt trust anything that canโt prove itself later and keep learning understand the basIc of tech and don't forget to educate your self and others... @SignOfficial#signdigitalsovereigninfra $SIGN