<p>When using a third party, you will be trusting them to give you correct information. This is not just about being dishonest but also about not having bugs. </p>

<p>For instance consider the recent cve-2010-5141 vulnerability. If you are running a full node on your own, you can know what is going on and you can upgrade when you find out about it. But if you rely on a third party you have to trust that they upgrade and are aware of it.</p>

<p>As a matter of fact they apparently have not yet upgraded and on TestNet they are showing a block with exploiting transaction as valid. So theoretically you, as an exchange, can lose money if you were relying on them and if this was MainNet.</p>

CC BY-SA 4.0
2018-09-29T04:16:11.933Z
2018-09-29T04:16:11.933Z
Coding Enthusiast
<p>I am working on an exchange platform with users having separate pair of public and private keys using blockcypher api. I encountered <a href="https://www.blockcypher.com/dev/bitcoin/?php#using-wallets" rel="nofollow noreferrer">Blockcypher Wallet API</a>, and it seems its a pleasant way of collating Set of Public Addresses to Query Together. For some reasons, i intend to add all new generated public addresses created by any user under a single wallet name (the site name) using the "Wallet API", this will come in handy in the case where by i need to filter all incoming transactions webhook to only the public addresses under the site name into a callback url. So i needed to confirm if this is a secure way to handle it. I would appreciate if an elegant way to handle this can be suggested.</p>

CC BY-SA 4.0
2018-09-28T19:55:30.560Z
If you’re building an exchange, and want ‘a secure way to handle things’, you should consider running your own node, not trusting a third party.
chytrik
<blockchain><blockcypher>
Is it secure to collect common public addresses under a wallet using BlockCypher Wallet API
HolluwaTosin360
# Is it secure to collect common public addresses under a wallet using BlockCypher Wallet API

(Asked by: username_0 on 2018-09-28)

I am working on an exchange platform with users having separate pair of public and private keys using blockcypher api. I encountered [Blockcypher Wallet API](https://www.blockcypher.com/dev/bitcoin/?php#using-wallets), and it seems its a pleasant way of collating Set of Public Addresses to Query Together. For some reasons, i intend to add all new generated public addresses created by any user under a single wallet name (the site name) using the "Wallet API", this will come in handy in the case where by i need to filter all incoming transactions webhook to only the public addresses under the site name into a callback url. So i needed to confirm if this is a secure way to handle it. I would appreciate if an elegant way to handle this can be suggested.

**Tags:** blockchain, blockcypher

> **Comments:**
> **username_1**: If you’re building an exchange, and want ‘a secure way to handle things’, you should consider running your own node, not trusting a third party.  

---

## 1 answers

### Answer by username_2 on 2018-09-29. Score: 1

When using a third party, you will be trusting them to give you correct information. This is not just about being dishonest but also about not having bugs.

For instance consider the recent cve-2010-5141 vulnerability. If you are running a full node on your own, you can know what is going on and you can upgrade when you find out about it. But if you rely on a third party you have to trust that they upgrade and are aware of it.

As a matter of fact they apparently have not yet upgraded and on TestNet they are showing a block with exploiting transaction as valid. So theoretically you, as an exchange, can lose money if you were relying on them and if this was MainNet.


---

