<p>Bitcore fork from SatoshiLabs is indeed available only for 64-bit linux.</p>

<p>You can try to build the necessary binaries yourself and then update the npm install scripts in bitcore, but that is very hard.</p>

<p>I would not recommend you to run bitcore on a personal computer, since it adds additional 200GB data, so you will end up with about half a terabyte of data. Also, because of some performance issues in the bitcore code, the address database synchs for days (around a week), where you cannot use the computer for anything else. (Also the disk SHOULD be SSD, or the syncing is even longer.)</p>

<p>If you want your own backend, I would recommend paying for a Linux server (but it's hard to find a reasonably priced VPS/hosted server with 500GB disk).</p>

<p>All in all, it is not easy to use Trezor with your own full node, unfortunately.</p>

<hr>

<p>I am actually working for SatoshiLabs, on the backends, right now :) and we don't have plans to make the builds on OS X, since we won't be able to test them anyway.</p>

CC BY-SA 3.0
2017-11-09T01:17:23.497Z
Thanks for your detailed answer. :-) Not the answer I wanted but I understand.
Adam Millerchip
CC BY-SA 3.0
2017-11-09T14:41:34.243Z
Long term, we are planning to move away from bitcore to something simplier, but we are just exploring that right now
Karel Bílek
CC BY-SA 3.0
2017-11-08T18:58:48.713Z
2017-11-08T18:58:48.713Z
Karel Bílek
<p>I want to point <a href="https://wallet.trezor.io" rel="nofollow noreferrer">Trezor Wallet</a> at my own local node. I'm already running Bitcoin Core, but Trezor Wallet requires Bitcore.</p>
<h1>What I have tried:</h1>
<h2>1. Installing the latest bitcore version according to <a href="https://bitcore.io/guides/full-node" rel="nofollow noreferrer">the guide</a>.</h2>
<p>This doesn't install <a href="https://github.com/bitpay/bitcore/issues/1454" rel="nofollow noreferrer">due to a bug</a>, but after working around it I got it running. But unfortunately it then <a href="https://github.com/bitpay/bitcore-node/issues/463" rel="nofollow noreferrer">crashes during indexing</a>, so is unusable.</p>
<h2>2. Use SatoshiLabs's bitcore fork</h2>
<p>SatoshiLabs have made <a href="https://github.com/satoshilabs/bitcore" rel="nofollow noreferrer">a fork</a> of bitcore for use with Trezor Wallet. This looks very promising, especially as it is designed to work with Trezor Wallet, they have fixed the bug in the Bitpay version, and also added better fee estimates. However it also fails to install on OSX, because the embedded Bitcoin Core build <a href="https://github.com/satoshilabs/bitcoin/releases/tag/v0.15.0" rel="nofollow noreferrer">is only packaged for Linux</a>.</p>
<h1>Next steps</h1>
<p>I can see four options:</p>
<ol>
<li>Go back to trying to get vanilla bitcore working. Find the cause of the crash and fix / workaround.</li>
<li>Try to get SatoshiLabs' fork working on OSX. Maybe I can use a vanilla Bitcoin Core build instead of the bundled one? Although I'd probably have to spend a lot of time investigating how to set up the dependencies and run the install correctly.</li>
<li>Forget about OSX and set up a simple Linux server and try again.</li>
<li>Give up and just let Trezor Wallet use its defaults.</li>
</ol>
<p>Can I get a working bitcore node on my OSX machine for use with Trezor Wallet? Preferably I'd like to do it without hacking the default config or source code too much.</p>

CC BY-SA 3.0
2017-11-15T04:43:20.643Z
A nice article about some merits for being able to validate against our own full node: https://medium.com/@lopp/securing-your-financial-sovereignty-3af6fe834603
Adam Millerchip
<mac><full-node><trezor><bitcore>
Can I run Trezor Wallet against my own local node on OSX?
Adam Millerchip
# Can I run Trezor Wallet against my own local node on OSX?

(Asked by: username_0 on 2017-11-08)

I want to point [Trezor Wallet](https://wallet.trezor.io) at my own local node. I'm already running Bitcoin Core, but Trezor Wallet requires Bitcore.

# What I have tried:

## 1. Installing the latest bitcore version according to [the guide](https://bitcore.io/guides/full-node).

This doesn't install [due to a bug](https://github.com/bitpay/bitcore/issues/1454), but after working around it I got it running. But unfortunately it then [crashes during indexing](https://github.com/bitpay/bitcore-node/issues/463), so is unusable.

## 2. Use SatoshiLabs's bitcore fork

SatoshiLabs have made [a fork](https://github.com/satoshilabs/bitcore) of bitcore for use with Trezor Wallet. This looks very promising, especially as it is designed to work with Trezor Wallet, they have fixed the bug in the Bitpay version, and also added better fee estimates. However it also fails to install on OSX, because the embedded Bitcoin Core build [is only packaged for Linux](https://github.com/satoshilabs/bitcoin/releases/tag/v0.15.0).

# Next steps

I can see four options:

1. Go back to trying to get vanilla bitcore working. Find the cause of the crash and fix / workaround.
2. Try to get SatoshiLabs' fork working on OSX. Maybe I can use a vanilla Bitcoin Core build instead of the bundled one? Although I'd probably have to spend a lot of time investigating how to set up the dependencies and run the install correctly.
3. Forget about OSX and set up a simple Linux server and try again.
4. Give up and just let Trezor Wallet use its defaults.

Can I get a working bitcore node on my OSX machine for use with Trezor Wallet? Preferably I'd like to do it without hacking the default config or source code too much.

**Tags:** mac, full-node, trezor, bitcore

> **Comments:**
> **username_0**: A nice article about some merits for being able to validate against our own full node: https://medium.com/@lopp/securing-your-financial-sovereignty-3af6fe834603  

---

## 1 answers

### Answer by username_1 on 2017-11-08. Score: 3 | Accepted answer

Bitcore fork from SatoshiLabs is indeed available only for 64-bit linux.

You can try to build the necessary binaries yourself and then update the npm install scripts in bitcore, but that is very hard.

I would not recommend you to run bitcore on a personal computer, since it adds additional 200GB data, so you will end up with about half a terabyte of data. Also, because of some performance issues in the bitcore code, the address database synchs for days (around a week), where you cannot use the computer for anything else. (Also the disk SHOULD be SSD, or the syncing is even longer.)

If you want your own backend, I would recommend paying for a Linux server (but it's hard to find a reasonably priced VPS/hosted server with 500GB disk).

All in all, it is not easy to use Trezor with your own full node, unfortunately.

---

I am actually working for SatoshiLabs, on the backends, right now :) and we don't have plans to make the builds on OS X, since we won't be able to test them anyway.

> **Comments:**
> **username_0**: Thanks for your detailed answer. :-) Not the answer I wanted but I understand.  
> **username_1**: Long term, we are planning to move away from bitcore to something simplier, but we are just exploring that right now  

---

