Bitcoin Forum
April 26, 2024, 12:31:12 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Armory / 4 general questions to Armory on: January 07, 2014, 01:59:12 PM
Hello everyone,

I am currently using Armory for my cold storage. The hot wallet never saw an internet connection and was backuped to a paper wallet. Everything was done with the 0.90 Ubuntu version.

I also created a watch only copy of my wallet to see my balance.

I currently don't have any problems but still would like to know how Armory works in detail.

First, this is how I understood Armory works (correct me if I'm wrong):

Armory has a deterministic way to create new keys based on a seed. All public keys are the same no matter if they are created from the hot wallet or the watch only wallet (I actually tested this, just generating a few new keys in both wallets).

OK now to my questions:
1. If the private keys are not stored in the watch only wallet, how can a new public key be created, that maps to the new private key in the hot wallet?
2. Is the seed of the wallet also stored in the watch only copy?
3. If one of my private key will be compromised, will an attacker be able to generate all following private keys (for example if he has the watch only copy)?
4. Will an attacker have any use for the watch only wallet (other than seeing my BTC balance)?

hope these questions make sense
2  Other / Beginners & Help / Re: phoenix miner runs out of work on slush on: July 02, 2011, 04:05:35 PM
I once had this issue, restarted the miner and it was working again just fine. Have tried that?

yes, happens again and again
3  Other / Beginners & Help / phoenix miner runs out of work on slush on: July 02, 2011, 03:48:49 PM
hello everyone,

I'm currently mining on 2 pools (eligius and slush).

As a miner I use phoenix with the phatk kernel.

the commands are the same:

Code:
python phoenix.py -u http://<user>:<pass>@<server>:<port> -k phatk DEVICE=0 VECTORS AGGRESSION=13 WORKSIZE=128 BFI_INT FASTLOOP=false 2>&1 > <log> &

After some hours, the following message appears in the logs:

Code:
Warning: work queue empty, miner is idle

On eligius, this is not a problem, as the mining continues several seconds later. But If this happens on the slush pool, the mining just stops.

Is anybody familiar with such a problem and knows how to solve it?

regards
Leif
4  Bitcoin / Mining / Mining on two pools as a load balancer on: June 08, 2011, 11:38:31 AM
Hello everyone,

as the us server of eligius is currently down, I was thinking about what the best way is to implement a load balancer.

I thought the easiest way would be to start 2 mining tools on 2 different pools. The hashrate per miner would then equally distributed on two pools, but as one pool goes offline, the hashrate on the other pool would then go to 100%.

Is there anything wrong with that approach. Are there any other advantages of multiple mining (I currently only have one gpu) or am I missing something and that is actually a really bad idea?
5  Bitcoin / Mining / Re: Mining on small/large pool. Any difference on: June 07, 2011, 06:38:52 PM
OK I get the theory. But consider this (and correct me if I'm wrong).

- A lot of different independet people (or pools) are trying to generate blocks
- blocks are chained together
- the longest block chain is the valid one

consider the scenario:

I'm on my own. I generate a block. Now another block is created by someone else. Doesn't that make my block usesless as I have to add my block to the just generated block?

If so: the longer it takes to create a block (i.e. the smaller the pool is), the more likely it is that I do a lot of useless work I do an the lesser profit I get.

I most certainly missing something, but in my head this example makes sense.

Not quite. Each block relies on inputs from the previous block.

That way you can't 'work ahead', so to speak. As soon as someone else finds a block, the whole network learns, and starts over on a brand new block.

On the off chance two blocks are found simultaneously, two block chains are started. Next block will make one block chain longer, and thus winning.

OK so regarding this example, wouldn't working on a larger pool make more sense as the chances are higher that another block is discovered during the calculations?
6  Bitcoin / Mining / Re: Mining on small/large pool. Any difference on: June 07, 2011, 05:42:20 PM
OK I get the theory. But consider this (and correct me if I'm wrong).

- A lot of different independet people (or pools) are trying to generate blocks
- blocks are chained together
- the longest block chain is the valid one

consider the scenario:

I'm on my own. I generate a block. Now another block is created by someone else. Doesn't that make my block usesless as I have to add my block to the just generated block?

If so: the longer it takes to create a block (i.e. the smaller the pool is), the more likely it is that I do a lot of useless work I do an the lesser profit I get.

I most certainly missing something, but in my head this example makes sense.
7  Bitcoin / Mining / Mining on small/large pool. Any difference on: June 07, 2011, 01:31:07 PM
I'm currently looking for a pool to mine on (currently I'm using the EU-pool from eligius). My hash rate is ~300M.

So I was wondering if it makes any difference, whether I mine on a large pool (discovery of new blocks every 2-5 hours) or if I mine on a small pool.

From what I understand: if mining on a large pool, I will receive (or at least promised to receive) BTC more frequently.

Are there any other differences/advantages/disadvantages of mining on a small or large pool?
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!