Yesterday's Railway issues, and an increasing stream of cloud provider inciden… · @keoneHD · TwKit

@keoneHD

Yesterday's Railway issues, and an increasing stream of cloud provider incidents, highlight a major issue: decentralized apps have no way of scheduling or automating smart contract calls. Someone needs to run that cron on a server, which are becoming increasingly unreliable in the age of AI. The point of decentralized systems is that we shouldn't need to rely on a single server to maintain an invariant that protects the correctness and solvency of self-sovereign money protocols. Automation needs to move to the blockchain, where a network of distributed nodes brings fault-tolerance and checks-and-balances. Scheduled Transactions are how we accomplish that. Scheduled Transactions are far more than a replacement for keepers. They let users and applications alike set up interactions that recur on a cadence, happen once at a chosen moment, or follow from something that happened earlier. Check out the details below, as well as a few examples of what you can build with Scheduled Transactions, such as on-chain keepers, recurring payments, long-running (asynchronous) computations, automatic refunds in atomic swaps, and order-book cleanup.

曝光 1883 · 评论 6 · 点赞 36 · 书签 1