Hey! We would use abstraction across the codebase to cover fallbacks/upgradability and any changes under the hood. You would still be able to use the method, but the method (code) can change over time. The methods of authentication are quite solidified, so I don’t see breaking changes often. We would also make the bridge configurable to use XXX version of the framework for instance. The first two months would involve close cooperation with Cartesi Team to work out flexible abstractions for the Identity system. The adoption across different web2frameworks can be community-led (i.e. nodejs community-led) if the bridge catches on. We would provide guidelines on how to create and maintain the bridge.