Certificate Renewal but Why?! about sdk

[ayasuda2OO3]

Thanks for the inquiry.

The chain of EC trust hierarchy (x509) is what internally make EC stand out as an invulnerable streaming channel in servicing network-to-network connectivity today.

Beginning #203+, agents have been forming a chain of trust by checking their issuer, expiration date, role, scope, licensing, etc, in a self-validity process, a technique which employees a series of RSA cryptography, and a nounce-driven token-validation in runtime.

#202 and older releases in the nutshell, 1) are lack of the validation process, 2) contain unverifiable intermediate certs from its issuer, hence the incompatible. and because of this incompatibility, 3) the connections generated from 202- are not trusted and are excluded from the current chain of EC connectivity, it would burden us in maintaining two hierarchies for future expiry, 4) lack of performance/communication enhancements.

The replacement of the #202 and older releases would 1) introduce the current security model into associated usage, 2) increase performance/compatibility for future releases, and 3) help reduce the cost of maintaining a separated hierarchy.