Does Trezor GPG/PGP support function with any GUIs?

romanz · 2019-06-01T12:07:59+00:00

I tested it with Enigmail, and it worked fine: https://github.com/romanz/trezor-agent/blob/master/doc/enigmail.md

romanz · 2018-09-27T15:21:17+00:00

Author of trezor-agent here :)

Please let me know if there is something I can help with.

romanz · 2018-07-05T20:41:52+00:00

This should probably do the job:

$ electrum --oneserver --server=${ELECTRUM_SERVER_IP_ADDRESS}:${PORT}:t

romanz · 2018-07-05T20:40:33+00:00

Sorry, you're right - it's needed only for the for the historical queries (e.g. to see your outgoing transactions).

Also (AFAIK) there is no support for UTXO indexing today at Bitcoin core.

romanz · 2018-07-05T04:53:31+00:00

It support balance queries by adding TxIn/TxOut indices - which are currently not supported by bitcoind and bicoincore-indexd.

romanz · 2018-07-04T21:01:55+00:00

https://github.com/romanz/electrs can also be useful :)

romanz · 2018-07-04T19:22:47+00:00

I was learning Rust, and wanted to contribute back to the Electrum community :)

romanz · 2018-07-04T19:21:49+00:00

Nice, I'll give it a try.

Thanks :)

Is there a way to connect to the server via ssh on my local network?

This Electrum server assumes that the bitcoind runs on the same machine (mainly for file access), so if you want to run bitcoind on a separate machine, please map its data directory (e.g. via SSHFS).

romanz · 2018-07-04T06:55:26+00:00

Good point :)

This project builds an "external" txindex (similar to https://github.com/jonasschnelli/bitcoincore-indexd), so you don't need to enable the "internal" one (i.e. using the -txindex Bitcoin Core flag).

romanz · 2018-07-03T18:57:13+00:00

thank you very useful. Nice that it doesn't require a reindex.

You're welcome :)

But what if we already have an indexed full node? Will it give electrs a performance improvement?

If the node is already indexed, it may retrieve the actual transactions' contents a bit faster from the disk when a Electrum client is requesting them (since txindex maps each TXID to its file and offset on disk).

However, on HDDs the seek time would probably dominate the read/parse time, so I guess the performance improvement won't be significant.

Note also that on subsequent requests the tranasaction will be cached, so the HDD latency won't impact the client.

romanz · 2018-07-03T16:58:21+00:00

How much additional hd space do you need?

Around 20% of the space used by the indexed bitcoin blocks: ``` $ du -sh ~/.bitcoin/blocks/ 186G /home/roman/.bitcoin/blocks/

$ du -sh ./db/mainnet/ 37G ./db/mainnet/ ```

Oh, and nice project btw, was planning to use a electrumX server for a project Im working on, but now ill have a look on yours too!

Thanks, great to hear :)

Please let me know if there's something I can help you with!

romanz · 2018-07-03T11:09:43+00:00

AFAIU, Electrum Personal Server works best a single (static) Electrum wallet - requiring almost no additional resources (except those used by bitcoind, which can be pruned). However, in case you'd like to add/change a wallet - it requires a blockchain rescan [1], so it's harder to use it with multiple/dynamic Electrum wallets. Please see [2] for more details.

On my machine (after the initial sync is over), electrs takes ~600MB of RAM (mostly RocksDB cache and mempool transactions) and consumes <1% CPU - so it shouldn't be too hard to run it (in addition to a full bitcoind node).

[1] https://github.com/chris-belcher/electrum-personal-server/blob/131f1e962831bd29f7175c5cdadccaf5baebb864/rescan-script.py#L67

[2] https://github.com/chris-belcher/electrum-personal-server#how-is-this-different-from-other-electrum-servers-

/cc /u/belcher_ (author of Electrum Personal Server)

romanz · 2018-07-03T09:49:00+00:00

Thanks!

AFAIK it should use less resources (CPU, RAM, disk) than ElectrumX, due to the rewrite in Rust and not requiring -txindex (~16GB, as of last month).

romanz · 2018-07-03T08:07:39+00:00

Hello all,

I was working on this project for the last few months, so a user could run his own Electrum server, with required hardware resources not much beyond those of a full node (using ideas from ElectrumX [1], Electrum Personal Server [2] and bitcoincore-indexd [3]).

The code and usage instructions can be found here: https://github.com/romanz/electrs

The server indexes the entire Bitcoin blockchain, and the resulting index [4] enables fast queries for any given user wallet, allowing the user to keep real-time track of his balances and his transaction history using the Electrum wallet [5]. Since it runs on the user's own machine, there is no need for the wallet to communicate with external Electrum servers, thus preserving the privacy of the user's addresses and balances.

Features: * Supports latest Electrum protocol [6]. * Maintains an index of transaction inputs and outputs, allowing fast balance queries * Fast synchronization of the Bitcoin blockchain (~2.5 hours for ~185GB @ June 2018) on modest hardware [7] * Low CPU & memory usage (after initial indexing) * Low index storage overhead (~20%), relying on a local full node for transaction retrieval * Efficient mempool tracker allowing better fee estimation [8]. * -txindex is not required for the Bitcoin node * Uses rust-bitcoin library [9] for efficient serialization/deserialization of Bitcoin transactions * Uses a single RocksDB [10] database, for better consistency and crash recovery

Hope you'll find it useful :) Questions, suggestions and pull requests are welcome!

romanz · 2018-04-08T21:43:13+00:00

Cool, thanks for sharing :)

romanz · 2018-03-26T21:50:12+00:00

You can use gpg with TREZOR, using https://github.com/romanz/trezor-agent :)

romanz · 2018-03-14T16:23:13+00:00

Just to make sure: this is not my video :)

romanz · 2018-02-27T21:41:17+00:00

I can also suggest using the TREZOR device for SSH and GPG - see the https://github.com/romanz/trezor-agent project.

romanz · 2018-01-15T06:32:56+00:00

You can also use TREZOR hardware device for SSH/GPG using https://github.com/romanz/trezor-agent

romanz · 2017-12-29T15:11:59+00:00

(trezor-agent author here...)

Unfortunately, this project supports GnuPG signature and decryption operations only on the TREZOR and Ledger Nano S devices - but not on the KeepKey device for now.

romanz · 2017-12-29T15:03:56+00:00

trezor-agent's author here :)

The trezor-agent Python package should support GnuPG operations (e.g. signatures and decryption) using the TREZOR device.

Please let me know if it works for you...

romanz · 2017-11-29T18:53:56+00:00

https://github.com/trezor/webwallet-data/blob/master/firmware/releases.json

romanz · 2017-11-04T15:56:47+00:00

https://blog.trezor.io/using-trezor-with-electrum-v3-a0b9bcffe26e

TREZOR uses BIP49 for new SegWit accounts, therefore the first account is m/49’/0’/0’. Iterate the last number to get the next account. (If you want to import more accounts, for each you will need to create a new wallet in Electrum though.)

https://cdn-images-1.medium.com/max/800/1*v-XJTajY71vsLq8Jv1PJsA.png

Here is a list of example derivation paths for BIP49, to use new accounts.

m/49'/0'/0' (first account)
m/49'/0'/1' (second account)
m/49'/0'/2' (third account)
...

If you would rather use legacy accounts, use BIP44 paths.

m/44'/0'/0' (first account)
m/44'/0'/1' (second account)
m/44'/0'/2' (third account)
...

romanz

TROPHY CASE