Search content
Sort by

Showing 7 of 7 results by menkaur
Post
Topic
Board Armory
Re: Transaction has 7 confirmations but doesn't show as confirmed in armory
by
menkaur
on 16/09/2017, 17:06:13 UTC
ok, apparently I needed to rebuild and re-scan databases
Post
Topic
Board Armory
Re: Transaction has 7 confirmations but doesn't show as confirmed in armory
by
menkaur
on 16/09/2017, 16:34:51 UTC
I just checked Armory block number, and it shows 480828,  while on core client it shows 485592, however, Armory shows that it's connected and synced
Post
Topic
Board Armory
Transaction has 7 confirmations but doesn't show as confirmed in armory
by
menkaur
on 16/09/2017, 15:55:25 UTC
I'm using bitcoincore 0.15.0.0 and Armory 0.96.

I have sent money to a P2SH-P2PK address in my armory wallet.

Checking the transaction on blockchain.info shows 7 confirmations. Armory shows the transaction with 0 confirmations and last block received 7 minutes ago.

I have tried making it re-scan balances, but it still doesn't see the transaction as confirmed

How can I fix this?
Post
Topic
Board Development & Technical Discussion
Re: Blockchain size proposal - Very Slow Voted Changes
by
menkaur
on 30/03/2017, 12:56:55 UTC
I don't like proposals which involve "voting" of any sort.

I think that the blocksize should be controlled by people who generate transactions

And the best way to achieve it would be like follows:

1. Set unlimited blocksize limit
2. Calculate average block size over past 20k blocks
3. If a miner wants to create a block larger than the average, he'll have to solve a puzzle with exponentially higher difficulty. Something like Exp[(new_block_size/average_block_size -1)]*difficulty


This setup increases probability that the miners will attempt to create larger blocks only if consumers (e.g. people who create transactions) actually need them and signal that the larger blocks are needed by posting transactions with larger fees
Post
Topic
Board Armory
Topic OP
DB crashes after some time working
by
menkaur
on 30/03/2017, 10:10:13 UTC
I'm running core .14 and armory .95.1

The Armory starts and works fine, but after a while, the console crashes

Here's the dblog.txt:

https://pastebin.com/VHF3F1Lh

Is this a bug, or should I update/change configuration?
Post
Topic
Board Armory
Re: v95.1 raw data does not match expected block hash
by
menkaur
on 24/03/2017, 08:30:43 UTC
That fixed it

Thank you
Post
Topic
Board Armory
Re: v95.1 raw data does not match expected block hash
by
menkaur
on 23/03/2017, 23:07:51 UTC
Having the same issue. Armory .95.1 and core .14.0.

armorylog http://pastebin.com/WX10R51S
dblog: http://pastebin.com/LVcaq3Y0