ckBTC: a canister-issued bitcoin twin token on the IC, 1:1-backed by BTC

General
111

This means that your Bitcoin transaction is still pending, you can check on a Block explorer like https://blockstream.info/ how many confirmations your transaction has (it needs 12 confirmations to be considered valid).

112

it shows 961 CONFIRMATIONS as the link

113

Do you mind giving me the principal you are using so that I can try to see what is going on?

114

yes, just DM you, thanks!

115

How to get information on bitcoin deposited to the bitcoin address assigned by the ckbtc minter? Eg. sender address, amount (utxos), time and fees deducted?

116

https://637g5-siaaa-aaaaj-aasja-cai.raw.ic0.app/token/mxzaz-hqaaa-aaaar-qaada-cai

117

@Jonathan the issue with this is that the ledger only shows ckbtc transfers (i.e from - to principal IDs). The scenario I’m describing is when you receive real btc to the btc address assigned by the ckbtc minter and you want to fetch details of this transaction (e.g sender btc address). Querying the ledger canister only returns information about the corresponding ckbtc tokens that were minted. Does the IC Bitcoin API give information on the actual btc transaction that received to the assigned btc address?

118

Do you want to get this information programatically from canister code or manually? Manually you can look at a Bitcoin blockchain explorer to get the information. The IC Bitcoin API gives access to the Bitcoin canister and the Bitcoin canister only stores the UTXO set, not the entire Bitcoin blockchain data. So that creates two problems for the information you are seeking. a) The UTXO set consists of just txid and vout. That doesn’t tell you anything about the sender. b) Once the ckBTC canister has spent a deposit to satisfy a withdrawal, the output is no longer in the the UTXO set and you won’t even get the txid anymore from the Bitcoin canister. So I believe you can’t get the information you want programatically from a canister. Unless with an http outcall to a third-party Bitcoin blockchain explorer.

In the long run a canister (or a set of canisters) can be created that stores the entire Bitcoin blockchain, but nobody has written that yet.

2 Likes
119

What is the relation between this code ic/main.rs at master · dfinity/ic · GitHub and the one that is deployed as the minter mqygn-kiaaa-aaaar-qaadq-cai?

Where do I find the deployed code? Some other branch?

120

You can still get that information from the ckBTC index and archive canisters. The ckBTC minting transactions contain the corresponding Bitcoin txid in their memo field. Just be careful with the byte order which is opposite to what common Bitcoin block explorers expect in their UI. Though this is probably Bitcoin’s fault, not ckBTC’s.

1 Like
121

Thanks I think I will get the information I need from the block explorers using the txid from the ckbtc minting transactions.

122

You can derive this from the NNS proposals. The last ckBTC minter upgrade proposal was Proposal: 115473 - IC Dashboard, which states that this release is built from git hash d21c69ba055489905bf801a4aea7145f545c9ff8, so the code at ic/rs/bitcoin/ckbtc/minter at d21c69ba055489905bf801a4aea7145f545c9ff8 · dfinity/ic · GitHub should be the currently deployed version.

After proposal Proposal: 118485 - IC Dashboard passes, it would be ic/rs/bitcoin/ckbtc/minter at 3440457faa3b162d9e1877aaad91ce563c964a25 · dfinity/ic · GitHub.

1 Like
123

Why has ckBTC not implemented ICRC-2 standards, bro? It can make ckBTC used easily in other canisters (Dapps)

124

The ICRC-2 design was finalized this week and will be up for an approval vote on the NNS soon. It will be implemented for ckbtc and SNS ledger after that vote happens.

8 Likes
125

What’s the latest story on working with ckBTC/ICRC locally? Is there any easy solution like dfx pull yet?

2 Likes
126

What about the ICP ledger?

2 Likes
127

Is there a way to browse what’s in this directory? How did you know to find the Wasm binary there with its specific name?

128

Is there a guide to getting ckBTC with the minter setup locally? Is there any kind of development mode on the minter canister locally that allows you to turn off the KYT checks? I have the ckBTC ledger and minter deployed locally, but trying to use the functionality is giving me BUG: upgrade procedure must ensure that the KYT principal is set and now I’m afraid I’ll have to setup an entire KYT local story.

2 Likes
129

Yeah this little ckBTC example that I’m doing for Azle is getting quite complicated, I don’t understand how a beginner would ever be able to figure this stuff out. There’s got to be a better way to setup these canisters locally, I’m thinking dfx pull is going to do that right?

2 Likes
130

I accidentally posted this elsewhere, thus I need to write something to distinguish from that message…

I have the kyt canister deployed with the following command:

dfx deploy kyt --specified-id bkyz2-fmaaa-aaaaa-qaaaq-cai --argument '(variant { InitArg = record { minter_id = principal "bd3sg-teaaa-aaaaa-qaaba-cai"; maintainers = vec {}; mode = variant { AcceptAll } } })'

I would expect that in mode AcceptAll that I wouldn’t have to provide an API key, but I’m getting the error:

(
  variant {
    Err = variant {
      TemporarilyUnavailable = "The KYT provider is temporarily unavailable: No valid API keys"
    }
  },
)

This error goes away when I set an empty “” as the api key, but this shouldn’t be necessary IMO.

3 Likes