It happened again right now
here's a screenshot with log




dbLog.txt

Log file opened at 1506776459: C:\Users\xxxxxxxx\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1506776459: (..\main.cpp:23) Running on 8 threads
-INFO  - 1506776459: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1506776459: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\xxxxxxxx\AppData\Roaming\Bitcoin\blocks
-INFO  - 1506776459: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\xxxxxxxx\AppData\Roaming\Armory\databases
-INFO  - 1506776459: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1506776460: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 1506776461: (..\BDM_Server.cpp:996) registered bdv: 55fcb76e9fa7b8e8e864
-INFO  - 1506776462: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1506776462: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 1506776464: (..\DatabaseBuilder.cpp:208) Found 487419 headers in db
-INFO  - 1506776466: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1506776469: (..\DatabaseBuilder.cpp:268) parsed block file #969
-INFO  - 1506776470: (..\DatabaseBuilder.cpp:268) parsed block file #970
-INFO  - 1506776471: (..\DatabaseBuilder.cpp:268) parsed block file #971
-DEBUG - 1506776471: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1506776471: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 5.273s
-INFO  - 1506776472: (..\DatabaseBuilder.cpp:106) scanning new blocks from #487313 to #487683
-INFO  - 1506776472: (..\BlockchainScanner.cpp:650) scanned from height #487313 to #487683
-INFO  - 1506776472: (..\BlockchainScanner.cpp:225) scanned transaction history in 0.351s
-INFO  - 1506776472: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.367s
-INFO  - 1506776472: (..\DatabaseBuilder.cpp:160) init db in 10.265s
-INFO  - 1506776472: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN  - 1506776475: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1506776475: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1506776475: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1506776475: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1506776475: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN  - 1506776543: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-INFO  - 1506776592: (..\BDM_Server.cpp:1025) unregistered bdv: 55fcb76e9fa7b8e8e864

armorylog.txt here https://pastebin.com/KJpWqMa9

Thanks

Full log is this, but since then the software has not crashed even once.

Log file opened at 1506448573: C:\Users\xxxxxxxx\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1506448573: (..\main.cpp:23) Running on 8 threads
-INFO  - 1506448573: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1506448573: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\xxxxxxxx\AppData\Roaming\Bitcoin\blocks
-INFO  - 1506448573: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\xxxxxxxx\AppData\Roaming\Armory\databases
-INFO  - 1506448573: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1506448575: (..\BDM_Server.cpp:996) registered bdv: 400f10ecef4f4ef08d8b
-INFO  - 1506448576: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1506448576: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 1506448577: (..\DatabaseBuilder.cpp:208) Found 487169 headers in db
-INFO  - 1506448580: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1506448580: (..\DatabaseBuilder.cpp:477) Found next block after skipping 127256bytes
-INFO  - 1506448580: (..\DatabaseBuilder.cpp:268) parsed block file #967
-DEBUG - 1506448580: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1506448580: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.347s
-INFO  - 1506448580: (..\DatabaseBuilder.cpp:106) scanning new blocks from #487063 to #487064
-INFO  - 1506448580: (..\BlockchainScanner.cpp:650) scanned from height #487063 to #487064
-INFO  - 1506448580: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.048s
-INFO  - 1506448580: (..\DatabaseBuilder.cpp:160) init db in 4.475s
-INFO  - 1506448580: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO  - 1506448591: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-WARN  - 1506448618: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1506448628: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1506448628: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1506448628: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1506448628: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN  - 1506448628: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN  - 1506448656: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN  - 1506448656: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN  - 1506448656: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-WARN  - 1506448701: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN  - 1506448755: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN  - 1506448755: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN  - 1506448755: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-ERROR - 1506449196: (..\SocketObject.cpp:285) POLLERR error in readFromSocketThread
-ERROR - 1506449196: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-INFO  - 1506449196: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node

I updated to last version (0.96-beta-a3d01aa722) but often it crashes with windows 7 64 bit, instead compiling the software with ubuntu 16.04 it works very well (i use online armory with windows and offline armory with ubuntu for signing transactions)

log is this:

-ERROR - 1506449196: (..\SocketObject.cpp:285) POLLERR error in readFromSocketThread
-ERROR - 1506449196: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-INFO  - 1506449196: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node

dunno if this can help but checking task manager the only process that remains open after armoryqt.exe crash is "guardian.exe"

i downgraded bitcoind to v0.15.0 because with v0.15.0.1 armory starts but hangs up indefinitely while checking the database.

any help is appreciated

Thanks

Oh yes, my fault, i need to rest, i'll update to last version, thanks aniway.

I have the same issue of another user with osx but I have windows 7 64 bit, after finished syncing and scanning the blockchain the program (armory 0.93.3)gives me an error and leaves me no choice but to close. It gives me the chance to rebuilt the database the next restart, a procedure already tried twice that has not solved the problem.
I wonder if this is not a problem with folder permissions? i've no clue but with previous armory 0.93.2 the problem was absent.

the error is "The scanning process interrupted unexpectedly, armory will now shutdown. IF the error persist, you will have to rebuilt and rescan your database........"

the log is this (windows username and wallet id censored), i use only watch version of armory for online pc

2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1076 - C++ block utilities loaded successfully
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1186 -
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1187 -
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1188 -
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1189 - ************************************************************
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1190 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1191 - ************************************************************
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1192 - Loading Armory Engine:
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1193 -    Armory Version        : 0.93.3
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1194 -    Armory Build:         : e59e10d38c
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1195 -    PyBtcWallet  Version  : 1.35
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1196 - Detected Operating system: Windows
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1197 -    OS Variant            : 7-6.1.7601-SP1-Multiprocessor Free
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1198 -    User home-directory   : C:\Users\username\AppData\Roaming
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1199 -    Satoshi BTC directory : C:\Users\username\AppData\Roaming\Bitcoin\
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1200 -    Armory home dir       : C:\Users\username\AppData\Roaming\Armory\
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1201 - Detected System Specs    :
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1202 -    Total Available RAM   : 15.94 GB
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1203 -    CPU ID string         : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1204 -    Number of CPU cores   : 8 cores
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1205 -    System is 64-bit      : True
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1206 -    Preferred Encoding    : cp1252
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1207 -    Machine Arch          : amd64
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1208 -    Available HDD (ARM)   : 15 GB
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1209 -    Available HDD (BTC)   : 197 GB
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1210 -
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1211 - Network Name: Main Network
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1212 - Satoshi Port: 8333
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1213 - Do wlt check: True
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1214 - Named options/arguments to armoryengine.py:
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     nettimeout      : 2
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     rescan          : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     ignoreAllZC     : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     enableSupernode : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     disableModules  : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     port            : None
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     interport       : 8223
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     skipStatsReport : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     forceWalletCheck: False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     rebuild         : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     datadir         : DEFAULT
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     clearMempool    : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     offline         : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     coverageOutputDir: None
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     armoryDBDir     : DEFAULT
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     satoshiPort     : DEFAULT
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     useTorSettings  : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     netlog          : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     keypool         : 100
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     coverageInclude : None
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     forceOnline     : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     skipAnnounceCheck: False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     redownload      : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     multisigFile    : DEFAULT
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     disableTorrent  : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     testAnnounceCode: False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     mtdebug         : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     logDisable      : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     settingsPath    : C:\Users\username\AppData\Roaming\Armory\ArmorySettings.txt
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     verbosity       : None
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     doDebug         : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     enableDetSign   : True
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     testnet         : False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     rpcport         : DEFAULT
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     satoshiHome     : DEFAULT
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     satoshiRpcport  : DEFAULT
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     logFile         : C:\Users\username\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1216 -     disableConfPermis: False
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1217 - Other arguments:
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1220 - ************************************************************
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:1620 - C++ block utilities loaded successfully
2017-09-25 20:37 (INFO) -- BDM.pyc:418 - Using the asynchronous/multi-threaded BlockDataManager.
2017-09-25 20:37 (INFO) -- BDM.pyc:419 - Blockchain operations will happen in the background. 
2017-09-25 20:37 (INFO) -- BDM.pyc:420 - Devs: check TheBDM.getState() before asking for data.
2017-09-25 20:37 (INFO) -- BDM.pyc:421 - Registering addresses during rescans will queue them for
2017-09-25 20:37 (INFO) -- BDM.pyc:422 - inclusion after the current scan is completed.
2017-09-25 20:37 (INFO) -- ArmoryUtils.pyc:3531 - Using settings file: C:\Users\username\AppData\Roaming\Armory\ArmorySettings.txt
2017-09-25 20:37 (INFO) -- announcefetch.pyc:95 - Reading files in fetcher directory:
2017-09-25 20:37 (INFO) -- announcefetch.pyc:104 -    announce         : 96f5d5f4253bac5528333c4fef3afd5fa0e931816bfd4c4c8b43d85cee002bb9
2017-09-25 20:37 (INFO) -- announcefetch.pyc:104 -    bootstrap        : b62c08932668ce162d51226135940724e90f4c71704ac936f74cc153b34cc251
2017-09-25 20:37 (INFO) -- announcefetch.pyc:104 -    changelog        : 1c01304b876de3e75672c8b13d9a00157556b86612afac1c88ffc40a8d7dfb90
2017-09-25 20:37 (INFO) -- announcefetch.pyc:104 -    downloads        : 28efee8047ee0a2c26ac9f785d93566fb5a45c20a794da6f972aa48db50ec35a
2017-09-25 20:37 (INFO) -- announcefetch.pyc:104 -    notify           : 87fa1adcd555be83a71b4f5935a6d4f85178ccbf5043531fdd71432b57d127ca
2017-09-25 20:37 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.93.3&id=48039da0
2017-09-25 20:37 (INFO) -- ArmoryQt.py:2736 - loadWalletsAndSettings
2017-09-25 20:37 (INFO) -- ArmoryQt.py:2790 - Loading wallets...
2017-09-25 20:37 (INFO) -- ArmoryQt.py:2849 - Number of wallets read in: 1
2017-09-25 20:37 (INFO) -- ArmoryQt.py:2854 -    Wallet (xxxxxxxxxxx):   "Restored - xxxxxxxxxxx (Watch)    "   (No Encryption)
2017-09-25 20:37 (INFO) -- ArmoryQt.py:2863 - Loading Multisig Lockboxes
2017-09-25 20:37 (INFO) -- ArmoryQt.py:2298 - Setting up networking...
2017-09-25 20:37 (INFO) -- ArmoryQt.py:2327 - Internet status: 2
2017-09-25 20:37 (INFO) -- ArmoryQt.py:2525 - loadBlockchainIfNecessary
2017-09-25 20:37 (INFO) -- ArmoryQt.py:2546 - Setting netmode: 1
2017-09-25 20:37 (INFO) -- ArmoryQt.py:1514 - setupUriRegistration
2017-09-25 20:37 (INFO) -- ArmoryQt.py:1632 - URL-register action: AskUser
2017-09-25 20:37 (INFO) -- ArmoryQt.py:664 - Usermode: Expert
2017-09-25 20:37 (INFO) -- ArmoryQt.py:1810 - Changing usermode:
2017-09-25 20:37 (INFO) -- ArmoryQt.py:1811 -    From: Expert
2017-09-25 20:37 (INFO) -- ArmoryQt.py:1819 -      To: Expert
2017-09-25 20:37 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2017-09-25 20:37 (INFO) -- Networking.pyc:65 - Connection initiated.  Start handshake
2017-09-25 20:37 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2017-09-25 20:37 (INFO) -- Networking.pyc:156 - Received version message from peer:
2017-09-25 20:37 (INFO) -- Networking.pyc:157 -    Version:     70015
2017-09-25 20:37 (INFO) -- Networking.pyc:158 -    SubVersion:  /Satoshi:0.15.0.1/
2017-09-25 20:37 (INFO) -- Networking.pyc:159 -    TimeStamp:   1506364629
2017-09-25 20:37 (INFO) -- Networking.pyc:160 -    StartHeight: 486940
2017-09-25 20:37 (INFO) -- Networking.pyc:350 - Handshake finished, connection open!
2017-09-25 20:37 (WARNING) -- Networking.pyc:222 - received alert: URGENT: Alert key compromised, upgrade required
2017-09-25 20:37 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2017-09-25 20:37 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt?osvar=7&os=win&ver=0.93.3&id=48039da0
2017-09-25 20:37 (INFO) -- announcefetch.pyc:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2017-09-25 20:37 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2017-09-25 20:37 (ERROR) -- announcefetch.pyc:284 - Tried: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
2017-09-25 20:37 (WARNING) -- announcefetch.pyc:297 - Error fetching announce digest
2017-09-25 20:37 (INFO) -- ArmoryQt.py:3148 - Current block number: 486940
2017-09-25 20:38 (INFO) -- Networking.pyc:215 - Received new block.  000000000000000000bbc188fb247c7483680010ee8269b54bee82f90fc4b07a

After installing ubuntu 16.04.2 lts i installed armory package 0.96 but it doesn't work, i can't even see the icons looking for armory with nautilus and executing armoryQT under /usr/lib/armory it doesn't work too, the program simply won't start.
For now i'm still using 0.95.1 that works nicely, i really wonder what is wrong with the new version probably some issue with dependencies.
Is it possible to include with the 0.96 also all the dependencies required? would be very useful instead of leaving less expert users like me in the total darkness:)
Thanks

try again starting from november 2011 low at 2$, leaving out the first bubble of 2011 and compare results

We are at the beginning of the take off phase with institutional investors that are starting to notice bitcoin as a new asset where to invest.

Se qualcuno e' interessato, vendo www.bitchanger.com, un buon dominio se qualcuno vuole fare anche un exchange per bitcoin
L'offerta e' libera da fare sulla pagina del dominio.
Grazie

Beh si puo' quantificare anche numericamente, fino ad oggi, dal luglio 2010, il fattore di crescita giornaliero e' stato in media dello 0.12%.
Annuale e' circa del 57%, a due anni del 248%, le cifre non sono lineari perche il tasso di crescita e' composto.
Quindi se ora calcoli un prezzo medio di 130$, a due anni il prezzo medio sara' 320$,per raggiungere i 1000$ ci vorranno circa quattro anni e mezzo, ossia fine 2017, quando ci sara' gia' stato il passaggio da 25 btc a 12.5 btc per blocco.
E' attendibile, quattro anni per arrivare a 1000 dollari circa, il che significa che di picco puo' anche fare i 2000$.

Entrera' in vigore entro il 1 febbraio 2014.

Una nota riguardo all'inviare bonifici su bitstamp: ricordatevi che e' come mandare i soldi all'estero, se inviate piu' di diecimila euro annui dovete ricordavi l'anno successivo di riportare nel modello unico quadro RW la transazione. Se invece siete cittadini italiani con residenza fiscale in slovenia (dove risiede bistamp) non siete tenuti a riportare la transazione.

it is not working right now, and i've observed strange things in the last days, probably because bitcoinchart is changing something, we have to wait and then if slush can modify the plugin i'll appreciate:)

there is another issue, historical data is now downloaded with reversed order

mtgoxUSD 2013-04-11 13:39:45 1365680385 165.0 5.42
mtgoxUSD 2013-04-11 13:39:45 1365680385 164.86 1.25
mtgoxUSD 2013-04-11 13:39:44 1365680384 164.86 2.99
mtgoxUSD 2013-04-11 13:39:41 1365680381 164.9 0.6
mtgoxUSD 2013-04-11 13:39:34 1365680374 165.0 1.0
mtgoxUSD 2013-04-11 13:39:29 1365680369 165.0 3.57
mtgoxUSD 2013-04-11 13:39:29 1365680369 165.0 2.5

from latest to oldest, and of course the data is visualized in sierrachart in the reversed order, on the left the new data, on the right of the chart the old data, pretty odd:)

edit: real time data is visualized correctly but not the historical data

In questi giorni di festa, facendo zapping su sky ho visto che sulla cnbc ne hanno parlato, canale 528 mi pare.
Notevole per una moneta che 2 anni e mezzo fa quando la scoprii era semisconosciuta, forse ci siamo.
Inizio a crederci.

First of all leverage doesn't have any influence on risk, it will just reduce the margin required to open a position allowing you to open more trades to diversify or hedge your trading positions.
What is important it's the size of your trade, roughly to do 1 lot you need at least 1000 btc and for the min position size of 0.01 you need theoretically 10 btc but if you aren't good enough  is still too low as a starting deposit.
I don't think that for an amateur 25 btc are enough to cover the max initial equity drawdown that you'll probably have. Maybe 50 btcs are enough to operate with a position size of 0.01-0.02 Lot but as Kako said there are technical limitation to go under 100 btc.
If you think to be skilled enough, find 3 guys that are willing to give you 75 btcs and manage that sum for them.

Did twice today, from 1.2970 to 1.2935 and few mins ago from 1.2979 to 1.2958

here's the screenshot, the last two are gold/silver

2.9 pips on average EUR/USD and GBP/USD; they can vary a little around few tenths of  a pip

I've also activtrades as fiat forex broker, better spread on currencies but on silver/gold venetfx is better

venetfxsetup.exe it's virus free:
https://www.virustotal.com/file/90dd1c70f719c8882aa40c6e7e66e5909b16cfd07aab353c704d9d9412bb71cb/analysis/1349639967/
checked with virustotal, 43 antivirus.

yeah, i've understood why, because it's a 24/7 market so open and close are not the same because my sierrachart closes the daily bar when here is midnight (gmt time +2) and is different from bitcoinchart time zone.