I’m following the 3.2 Using HTTPS outcalls GET demonstration, the code deploys but in candid my call gets rejected for not having cycles…But i’ve got enough? no?
main.mo code example:
Cycles.add(20_949_972_000);
I would assume too that 3T is plenty. Can you check with debug-prints that it is actually Cycles.add that traps? Or is it in the await where the call fails?
1 Like
Okay, I think i got i working. Is the coinbase API deprecated now?
I got back this response:
("{"message":"Coinbase Pro API is deprecated."}")
Also whats this ‘aaaaa-aa’?
let ic : Types.IC = actor ("aaaaa-aa");
Do failed requests burn more cycles?
Reason im asking this is because previously when the req failed the func took out 3T cycles out of my wallet, but now its not even noticeable.
I did some reading and i stumbled on a post where someone mentioned that i can exceed the cycle amount that is actually used and rest of it will be returned. yes? no?
Yes, it’s deprecated. We just updated the example, it’s a very easy fix: fix: coinbase API · dfinity/examples@1ef48a7 · GitHub
aaaaa-aa is the management canister. You can read more about it here: The Internet Computer Interface Specification | Internet Computer
I don’t think so, but if you try multiple times and don’t provide a max response byte number then it gets expensive-ish pretty quickly
Yes, that’s correct
3T sounds suspiciously like the amount of cycles dfx uses by default to create a canister. How did you arrive at the 3T number? Did you use dfx cycles balance?