search

goatpig / armoryd

JSON-RPC daemon for BitcoinArmory
Other
6 stars 5 forks source link

An external bitcoin wallet system needed #8

Open albabosh opened 6 years ago

albabosh commented 6 years ago

Hello, I run an altcoin node (an old bitcoind port with a compartible PRC API) and a wallet-as-a-service web application whitch used an internal bitcoin accounting system. As soon as it gets deprecated I am searching for a replacement. Is this project a thing I could use for external wallets & accounting ?

goatpig commented 6 years ago

This a JSON-RPC daemon that interfaces for a Bitcoin blockchain indexing database operating behind a network node. There's also a GUI counterpart that operates on top of the same database and wallet format (i.e. you can use that offline sign transactions generated by the daemon).

If what you are looking for is to monitor and manage assets on the Bitcoin chain, this stack is for you. It does not do altcoins. Also, it requires its own local full network node.

albabosh commented 6 years ago

I used a coin daemon (with bitcoin rpc json api) for wallet management & p2p networking and I coded a web GUI (user profile management, etc). After a recent daemon update accounting was completely broken. Now I need some sort of "middleware" to handle "user accounts". If armoryd can do this then was api does it provide and how does it interact with the coin daemon ? Sorry for my bad English.

goatpig commented 6 years ago

I don't know what the "coin daemon" is. Armory works off Bitcoin Core nodes only.

albabosh commented 6 years ago

"Coin daemon" is a Bitcoin Core.

вт, 6 февр. 2018 г. в 21:37, goatpig notifications@github.com:

I don't know what the "coin daemon" is. Armory works off Bitcoin Core nodes only.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/goatpig/armoryd/issues/8#issuecomment-363521339, or mute the thread https://github.com/notifications/unsubscribe-auth/AF7WPNPYeDjsMs07pIH49BbQ4-KMjl5uks5tSJvqgaJpZM4R6tZh .

albabosh commented 6 years ago

I wonder if it reads blocks from disk or uses Bitcoin core rpc ?

вт, 6 февр. 2018 г. в 21:42, Александр Бабошин albabosh82@gmail.com:

"Coin daemon" is a Bitcoin Core.

вт, 6 февр. 2018 г. в 21:37, goatpig notifications@github.com:

I don't know what the "coin daemon" is. Armory works off Bitcoin Core nodes only.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/goatpig/armoryd/issues/8#issuecomment-363521339, or mute the thread https://github.com/notifications/unsubscribe-auth/AF7WPNPYeDjsMs07pIH49BbQ4-KMjl5uks5tSJvqgaJpZM4R6tZh .

goatpig commented 6 years ago

It reads blocks from disk. Later this year it will migrate to grabbing block data over the node P2P.

albabosh commented 6 years ago

Will it write the whole blockchain into its own DB ?

вт, 6 февр. 2018 г. в 22:17, goatpig notifications@github.com:

It reads blocks from disk. Later this year it will migrate to grabbing block data over the node P2P.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/goatpig/armoryd/issues/8#issuecomment-363533638, or mute the thread https://github.com/notifications/unsubscribe-auth/AF7WPCAZIDfYrufHPuv8HwmYVu2urgf1ks5tSKU5gaJpZM4R6tZh .

goatpig commented 6 years ago

Depends of what mode of operation you are going to use. There are 3:

DB_BARE: ~200MB, only keeps track of addresses you register with the DB. Cannot resolve arbitrary tx hashes, i.e. it cannot tell resolve the txhash for inputs in transactions that pay you, which means you can't figure out what fee they pay nor what block the paying outputs where from.

DB_FULL: ~1.5GB. Same as DB_BARE but has the dataset to resolve any txhash, meaning it does not have the limitations of DB_BARE, at the cost of a longer setup and bigger database.

DB_SUPER: ~2.5x blockchain. This keeps track of all blockchain history, basically a blockchain explorer.

DB_BARE/FULL only tracks addresses you register with it. If you register an address with that kind of DB, it has to rescan the blockchain in full to get its history (unless the address is flagged as new, in which case it assumes the address has no history).

DB_SUPER tracks all blockchain history at all times, it can return history for arbitrary addresses quasi instantly.

The sizes are only indicative of the Armory's own DB. You still need a Core fullnode along side that, on the same system.