You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lumos supports chained transactions, which can effectively increase the flow of transactions.
However, considering the issue of censorship, transactions signed by users should be sent from wallets to CKB nodes directly. This makes it difficult to efficiently arrange the inputs and outputs of transactions in sequential order on the dapp service to leverage the features of chained transactions.
To integrate this advantage as much as possible, it is hoped that projects of Kuai can provide an optional feature by exposing a hook to obtain the transactions submitted by wallets. These transactions can be used on the server side as a reference for chained transactions.
This proposal should include a development paradigm about the chained transactions and a spec of the hook to sync pending transactions
The text was updated successfully, but these errors were encountered:
Lumos supports chained transactions, which can effectively increase the flow of transactions.
However, considering the issue of censorship, transactions signed by users should be sent from wallets to CKB nodes directly. This makes it difficult to efficiently arrange the inputs and outputs of transactions in sequential order on the dapp service to leverage the features of chained transactions.
To integrate this advantage as much as possible, it is hoped that projects of Kuai can provide an optional feature by exposing a hook to obtain the transactions submitted by wallets. These transactions can be used on the server side as a reference for chained transactions.
This proposal should include a development paradigm about the chained transactions and a spec of the hook to sync pending transactions
The text was updated successfully, but these errors were encountered: