# CKB Tx Builder 意见收集 ## Metadata **Status**:: #x **Zettel**:: #zettel/permanent **Created**:: [[2023-07-17]] **Topic**:: [[♯ CKB]] ## Synopsis 1. 对于 tx builder 接口有什么改进建议？有没有参考项目推荐？ 2. 目前 SDKs 只对 system scripts 和某些我们挑选的 scripts 作了封装，对于其它 scripts 则缺少支持，也没法去全部支持，那如何才能简化应用间的交互呢？ 3. 目前我们 SDKs 走的多语言路线，那是不是 dApps 想被集成，也得维护多语言的 SDK 呢？ 4. 我的想法是需要有一个语言无关的关于交易构建的标准，这样只需要输入一些参数就能创建出一个其它 dApp 的合法交易出来。对于这样的标准，有没有什么想法？ 5. 除开交易构建标准，有其它的办法能解决 Scripts 互操作的问题吗？ > [!bot] Translation > 1. Do you have any suggestions for improving the tx builder interface? Do you have any recommended reference projects? > 2. Currently, the SDKs only encapsulate system scripts and some scripts we have selected, while lacking support for other scripts. It is not feasible to support all scripts. So, how can we simplify the interaction between dApps? > 3. Currently, our SDK follows a multi-language route. Does that mean dApps developers who want to be integrated also need to maintain SDKs for multiple languages? > 4. My idea is that there needs to be a language-independent standard for transaction construction, so that a legitimate transaction for another dApp can be created by simply entering some parameters. Do you have any thoughts on such a standard? > 5. Aside from the transaction construction standard, are there any other ways to solve the problem of script interoperability?