Can you elaborate? My thoughts: * Typically, payment issues like this are at small scales - not a massive enterprise website for a multinational corporation,

Can you elaborate? My thoughts: * Typically, payment issues like this are at small scales - not a massive enterprise website for a multinational corporation, but a small businesses that need web presence. * In such cases, scope management is key. Client typically underestimates the work required, so education and clear expectations are both a must and an uphill battle * Anything that expands the scope without clear requirements tracing, risks derailing. Adding "tokens" and crypto, not just as a smart contract between web developer and business users, but with all the customers and users, seems like a huge expansion of scope, and likely orthogonal to the limited "web presence / small eCommerce" requirements * Meanwhile, the traditional/boring commerce and law have this covered - a little bit of work ahead of time by the web developer to draft and sign appropriate contract / payment terms (which can and should be standardized once for all clients), can provide appropriate safety guardrails; in particular, far less overhead than building a whole new (possibly unbilled?) crypto/token facilities. What are your thoughts on A/B comparison here? Thanks for your time!