We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
对于RGB交易,多数情况Output 中含有 RGB++ Lock,这是因为在转账的时候通常会有找零到原地址的情况。 当一笔L1->L1交易 Input的BTC地址 转完所有的XUDT的时候,就会出现 Output中只有BTC Time Lock 的交易,对于这种交易,应该也进行类型判断。因此,对当前的RGB++ 交易作出如下调整:
The text was updated successfully, but these errors were encountered:
Leave a message and attach Btc time lock data information. https://ckb-explorer-frontend-in-magickbase-repo-okomdwwgi-magickbase.vercel.app/transaction/0x57872f2f13d1b0e583d66d5c2ee5b9ce10d775427eddcc988d413e6a873ec72f
Btc time lock
https://ckb-explorer-frontend-in-magickbase-repo-okomdwwgi-magickbase.vercel.app/transaction/0x3068a4b4a57941ac41f120de3d831c8402f2a83800eebfe6dcba174e4850e1d0
Sorry, something went wrong.
rabbitz
No branches or pull requests
对于RGB交易,多数情况Output 中含有 RGB++ Lock,这是因为在转账的时候通常会有找零到原地址的情况。
当一笔L1->L1交易 Input的BTC地址 转完所有的XUDT的时候,就会出现 Output中只有BTC Time Lock 的交易,对于这种交易,应该也进行类型判断。因此,对当前的RGB++ 交易作出如下调整:
The text was updated successfully, but these errors were encountered: