found it here:
https://docs.internetcomputer.org/languages/motoko/reference/changelog/#0130-2024-09-17
https://github.com/caffeinelabs/motoko/pull/4690
I suppose it’s like a “Buy Me a Coffee” button but in cycles ![]()
No, but more seriously, maybe you manage a fleet of canisters for testing and they all have similar but slightly different cycles - then you can shave some of them off to all be the same - perhaps that’s a legitimate use case..
Who’s buying whom coffee here, @Dionysus ?? ![]()
I’m getting confused about who owes who now!
I’m not sure why I was summoned here, mate.
I quite enjoyed that little joke I did.
I make my own coffee, mate.
Sometimes the wife makes it for me if she’s in a good mood.
Lmao, @WebTreeSoftwareSolut , your alt account has been working overtime.
This was put in when bob was burning cycles by actually doing real PoW. It was killing the network topology so they gave them a cheat code. It got hand-wavy, and there wasn’t really any PoW going on. It was just Proof of Burn. I may be misremembering, but that is close to right.
interesting.. who is “Me” here if im the one burning my own cycles? haha
hmm interesting
… but how to prove the cycles burn happened tho
i mean, if the burner rly wanna flex
thanks for the history. so as i thought then; there’s no rly good use case so far to use cyclesBurn ![]()
![]()
Why would a dev use Prim.cyclesBurn?
Shits and gigs, much like sending ICP (or any other token) directly to the burn account