Not only speed, what is @SeiNetwork capable of when replacing the old fashion SWIFT payment rail? fyi, SWIFT stands for Society for Worldwide Interbank Financial Telecommunication, is born with the major use case of securing cross-border financial messaging for banks and institutions. imo, the cases of using SWIFT hints the possibilities: + large-volume transactions between aprox 11,500 institutions + cross-border transfer across over 200 territories + adopting emerging recent needs of digital trades, atomic payments and tokenizations Thus, if Sei (and upcoming Sei GIGA) should be handling all these use case much better, they may support even more use cases: + micro payments between platforms (including Web2 and Web3) leveraging x402 + automated payroll with AI-assisted features + accessible to common financial products Yet, when the settlement layer of Sei is able to go this far, it may become a much better version of SWIFT.

in Sei we trust