# Non replicated HTTPS outcalls

**URL:** <https://forum.dfinity.org/t/non-replicated-https-outcalls/26627>\
**Category:** Developers\
**Created:** [January 13, 2024, 10:27pm UTC](https://forum.dfinity.org/t/non-replicated-https-outcalls/26627 "2024-01-13T22:27:51Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![skilesare](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/skilesare/32/5609_2.png) [@skilesare](https://forum.dfinity.org/u/skilesare)\
**Post date:** [January 15, 2024, 2:26pm UTC](https://forum.dfinity.org/t/non-replicated-https-outcalls/26627/9 "2024-01-15T14:26:30Z")

</div>

This is very cool and I can see a thousand use cases. I will make the following cautionary note:

WARNING: If you use outcalls(other than fire and forget) you may be abandoning the cryptographic guarantees and deterministic guarantees that most expect from ‘classic’ crypto dapps.

These may not be necessary for your canister, and if not, then carry on, but if they are, then just keep in mind there is a bunch you’ll need to consider and plan for if you want to keep those properties.

I’ve written in more detail here:

> [@The Double-Edged Sword of HTTP Outcalls in Internet Computer Smart Contracts](https://forum.dfinity.org/t/the-double-edged-sword-of-http-outcalls-in-internet-computer-smart-contracts/19196):
>
> TL;DR: HTTP outcalls in smart contracts have potential benefits, like event alerts and trusted data provision, but can lead to fragile, centralized systems. Weighing mitigation strategies against simpler, economic incentivization methods is crucial. The community should develop guidelines and best practices for HTTP outcalls, while exploring alternatives to ensure a robust, decentralized ecosystem on the Internet Computer platform. As we continue to build and improve the Internet Computer ecosy…

and here:

> [@Oracles. I’m suspicious. - re: coming http requests](https://forum.dfinity.org/t/oracles-i-m-suspicious-re-coming-http-requests/14360):
>
> Maybe I’m just a math nerd, but I like determinism. I like my contract inputs to be replayable and to end up with the same thing at the end of every run. Everyone is looking forward to outgoing http requests and all I see are foot guns. I’ll try to explain my position and hopefully, by the end you at least have a better idea of the kind of issues you are going to have if you try to pull data from the internet into your IC canister and what price you will pay to do so. TLDR: Oracles push data …

---

_[View the full topic](https://forum.dfinity.org/t/non-replicated-https-outcalls/26627)._
