I saw from the 'Armory 0.95 is out' thread that allot of people were having problems so I've been sticking with 0.94.1. I'll try it though. Um, I couldn't find installation instructions sudo apt-get install armory_0.95.1_amd64.deb won't do it. here's the last section of the log file: Transaction:
TxHash: 45f5624a0b6474fba97177595007b28bca66d974219cae18bcda78a20b443f70 (BE)
Version: 1
nInputs: 1
nOutputs: 2
LockTime: 0
Inputs:
PyTxIn:
PrevTxHash: e1f8a259a2e20ff3da6a5f48d9fac644c3afce59fb424c5fcf377c1811ac4c07 (BE)
TxOutIndex: 1
Script: (47304402201460221ca3d090b1a57edfc6af0f285966f57108884abfa5f5c568)
Sender: 1B3NNgbFbbXEmXdRzMxNXac5nRJxvRGxeJ
Seq: 4294967295
Outputs:
TxOut:
Value: 10000000 (0.1)
Script: OP_HASH160 (3AZHVqAd4j6XiSQhb6A3UwdmkZc8kGxJaF) OP_EQUAL
TxOut:
Value: 3489990000 (34.8999)
Script: OP_DUP OP_HASH160 (16pJeN4n64X4nVnGK9APyv5nNcDdPXhtGC) OP_EQUALVERIFY OP_CHECKSIG
2016-11-04 17:48 (INFO) -- ArmoryQt.py:3708 - Sending Tx, 703f440ba278dabc18ae9c2174d966ca8bb20750597771a9fb74640b4a62f545
2016-11-04 17:48 (INFO) -- Networking.py:279 - sendTx called...
2016-11-04 17:48 (INFO) -- ArmoryQt.py:3710 - Transaction sent to Satoshi client...!
2016-11-04 17:48 (INFO) -- ArmoryQt.py:6584 - Bitcoins Sent!
Amount: 0.1001 BTC
From: Wallet "Restored - 2WuWWukLP" (2WuWWukLP)
To: 3AZHVqAd4j6XiSQhb6A3UwdmkZc8kGxJaF
2016-11-04 17:54 (INFO) -- TxFrames.py:720 - Change address behavior: NewAddr
2016-11-04 18:00 (INFO) -- ArmoryQt.py:6163 - New Block! : 437345
2016-11-04 18:00 (INFO) -- ArmoryQt.py:6171 - Current block number: 437345
2016-11-04 18:00 (INFO) -- ArmoryQt.py:6685 - BDM is safe for clean shutdown
2016-11-04 18:00 (INFO) -- SDM.py:683 - Called stopBitcoind
2016-11-04 18:00 (ERROR) -- SDM.py:894 - generic error
Traceback (most recent call last):
File "/usr/lib/armory/SDM.py", line 859, in __backgroundRequestTopBlock
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 97, in __call__
File "/usr/lib/python2.7/httplib.py", line 1051, in getresponse
response.begin()
File "/usr/lib/python2.7/httplib.py", line 415, in begin
version, status, reason = self._read_status()
File "/usr/lib/python2.7/httplib.py", line 379, in _read_status
raise BadStatusLine(line)
BadStatusLine: ''
2016-11-04 18:00 (ERROR) -- ArmoryUtils.py:3168 - Error in pybkgdthread: ''
Traceback (most recent call last):
File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3166, in run
File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 3103, in funcPartial
File "/usr/lib/armory/SDM.py", line 859, in __backgroundRequestTopBlock
File "/usr/lib/armory/bitcoinrpc_jsonrpc/authproxy.py", line 97, in __call__
File "/usr/lib/python2.7/httplib.py", line 1051, in getresponse
response.begin()
File "/usr/lib/python2.7/httplib.py", line 415, in begin
version, status, reason = self._read_status()
File "/usr/lib/python2.7/httplib.py", line 379, in _read_status
raise BadStatusLine(line)
BadStatusLine: ''
2016-11-04 18:00 (ERROR) -- Networking.py:350 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-11-04 18:00 (INFO) -- ArmoryQt.py:6727 - Attempting to close the main window! At least I have my formed wallets, which had taken weeks to achieve. I'll have to redo one of them as it kept telling me that I had the wrong password for it, but I'll be trying to import the wallets into Bitcoin-Qt as soon as it has caught up with the blockchain. In the mean time, I'm still quite disconcerted as to why armory got uninstalled. I uninstalled electrum while armory was running, but really wouldn't have expected it to somehow remove armory, yet let it keep running |
|
|
|
|
I've been trying to take my coins out of cold storage for the last few days. I found that it takes about 8 hours of scanning for each retrieved wallet, except when you shit it down then restart, in which case it takes about 8 hours of scanning, but without scanning all the wallets one by one, so much less slow. That's just a wee bug I guess.
Here's the really infuriating stuff: I had finally managed to have my wallets fully loaded and scanned, and showing their correct contents. All good. I then did a small test transaction, sending 0.1BTC to my Bitstamp account. Looking good, so I went to sent the maximum by pressing the 'MAX' button and I got a pop up saying something along the lines of, 'due to a thing about how bitcoin works, this transaction has not worked'. I can't get the correct accurate wording because after repeatedly trying again to just get this weird pop up every time, I decided to shut down armory and start it again, and I get, "armory: command not found". So I do a search and it's gone entirely from the computer! Only the .armory folder remains.
There were many other very annoying bug-like glitches I can't remember well enough, but it's been a real headache.
Why would armory self delete? Have I been hacked? I'm very careful with this Ubuntu 14.04LTS machine, always using VPN (Nord) and only ever connecting to Bitstamp, Poloniex, Blockchaininfo, bitcoinwisdom, nordvpn.com, ans the electrum and armory sites.
|
|
|
|
Open Terminal. type "armory" and press return. Report any (or absence of) results.
Thanks, I guess that was an obvious thing to try but I stupidly hadn't read the results carefully when doing it previously I got this: ~$ armory
Traceback (most recent call last):
File "/usr/lib/armory/ArmoryQt.py", line 36, in <module>
from twisted.internet.defer import Deferred
File "/usr/lib/python2.7/dist-packages/twisted/__init__.py", line 53, in <module>
_checkRequirements()
File "/usr/lib/python2.7/dist-packages/twisted/__init__.py", line 40, in _checkRequirements
raise ImportError(required + ".")
ImportError: Twisted requires zope.interface 3.6.0 or later. so after a quick google search, it was suggested that I "upgrade zope.interface to the latest version (with sudo pip install zope.interface --upgrade)", which I did, and now Armory is running again. I'm pretty sure this has something to do with the various python adjustments I had made in order to get Electrum working. Thanks for the troubleshooting pointers  |
|
|
|
|
yeah, when I click on the Armory icon nothing happens. Same for Armory, Armory(offline) and Armory(Test Network)
|
|
|
|
Try running without Auto-management of bitcoind. In Armory settings. Launch BitcoinQt before running Armory once you change the setting.
don't I have to start up Armory to change those settings? I looked in the ArmorySettings.txt but couldn't find anything that might change Auto-management settings. I also tried starting Armory with and without bitcoin-qt and bitcoind running. Maybe have to reinstall, but it's really making me paranoid |
|
|
|
|
I'm not sure how much the log file will help. It's not creating new entries when i try to run Armory. But in case it helps here are the most recent entries:
armorylog.txt:
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1080 - C++ block utilities loaded successfully
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:593 - Executing popen: free -m
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:593 - Executing popen: ['cat', '/proc/cpuinfo']
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1190 -
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1191 -
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1192 -
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1193 - ************************************************************
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1194 - Invoked: /usr/lib/armory/ArmoryQt.py
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1195 - ************************************************************
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1196 - Loading Armory Engine:
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1197 - Armory Version : 0.94.1
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1198 - Armory Build: : 811798a928
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1199 - PyBtcWallet Version : 1.35
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1200 - Detected Operating system: Linux
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1201 - OS Variant : Ubuntu-14.04-trusty
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1202 - User home-directory : /home/mapi
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1203 - Satoshi BTC directory : /home/mapi/.bitcoin/
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1204 - Armory home dir : /home/mapi/.armory/
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1205 - Detected System Specs :
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1206 - Total Available RAM : 3.79 GB
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1207 - CPU ID string : Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1208 - Number of CPU cores : 2 cores
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1209 - System is 64-bit : True
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1210 - Preferred Encoding : UTF-8
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1211 - Machine Arch : x86_64
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1212 - Available HDD (ARM) : 126 GB
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1213 - Available HDD (BTC) : 126 GB
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1214 -
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1215 - Network Name: Main Network
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1216 - Satoshi Port: 8333
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1217 - Do wlt check: True
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1218 - Named options/arguments to armoryengine.py:
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - nettimeout : 2
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - rescan : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - ignoreAllZC : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - rescanBalance : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - disableModules : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - port : None
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - interport : 8223
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - skipStatsReport : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - forceWalletCheck: False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - rebuild : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - datadir : DEFAULT
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - clearMempool : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - offline : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - coverageOutputDir: None
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - armoryDBDir : DEFAULT
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - satoshiPort : DEFAULT
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - useTorSettings : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - netlog : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - keypool : 100
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - coverageInclude : None
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - forceOnline : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - skipAnnounceCheck: False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - redownload : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - multisigFile : DEFAULT
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - disableTorrent : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - testAnnounceCode: False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - mtdebug : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - logDisable : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - settingsPath : /home/mapi/.armory/ArmorySettings.txt
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - verbosity : None
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - doDebug : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - enableDetSign : True
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - testnet : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - rpcport : DEFAULT
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - satoshiHome : DEFAULT
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - satoshiRpcport : DEFAULT
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - logFile : /home/mapi/.armory/ArmoryQt.py.log.txt
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - disableConfPermis: False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1220 - enableSupernode : False
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1221 - Other arguments:
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1224 - ************************************************************
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:1624 - C++ block utilities loaded successfully
2016-07-09 16:06 (INFO) -- BDM.py:420 - Using the asynchronous/multi-threaded BlockDataManager.
2016-07-09 16:06 (INFO) -- BDM.py:421 - Blockchain operations will happen in the background.
2016-07-09 16:06 (INFO) -- BDM.py:422 - Devs: check TheBDM.getState() before asking for data.
2016-07-09 16:06 (INFO) -- BDM.py:423 - Registering addresses during rescans will queue them for
2016-07-09 16:06 (INFO) -- BDM.py:424 - inclusion after the current scan is completed.
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:3535 - Using settings file: /home/mapi/.armory/ArmorySettings.txt
2016-07-09 16:06 (INFO) -- ArmoryQt.py:2709 - loadWalletsAndSettings
2016-07-09 16:06 (INFO) -- ArmoryQt.py:2763 - Loading wallets...
2016-07-09 16:06 (INFO) -- ArmoryQt.py:2822 - Number of wallets read in: 0
2016-07-09 16:06 (INFO) -- ArmoryQt.py:2268 - Setting up networking...
2016-07-09 16:06 (INFO) -- ArmoryQt.py:2297 - Internet status: 0
2016-07-09 16:06 (INFO) -- ArmoryQt.py:2412 - startBitcoindIfNecessary
2016-07-09 16:06 (INFO) -- ArmoryQt.py:2461 - setSatoshiPaths
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:593 - Executing popen: ['whereis', 'bitcoind']
2016-07-09 16:06 (INFO) -- SDM.py:453 - "whereis" returned: ['/usr/local/bin/bitcoind']
2016-07-09 16:06 (INFO) -- SDM.py:321 - Found bitcoind in the following places:
2016-07-09 16:06 (INFO) -- SDM.py:323 - /usr/local/bin/bitcoind
2016-07-09 16:06 (INFO) -- SDM.py:323 - /usr/local/bin/bitcoind
2016-07-09 16:06 (INFO) -- SDM.py:325 - Using: /usr/local/bin/bitcoind
2016-07-09 16:06 (INFO) -- SDM.py:496 - Reading bitcoin.conf file
2016-07-09 16:06 (INFO) -- SDM.py:536 - Setting permissions on bitcoin.conf
2016-07-09 16:06 (INFO) -- SDM.py:597 - Called startBitcoind
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:593 - Executing popen: ['/usr/local/bin/bitcoind', '-datadir=/home/mapi/.bitcoin/']
2016-07-09 16:06 (INFO) -- SDM.py:669 - PID of bitcoind: 28181
2016-07-09 16:06 (INFO) -- SDM.py:670 - PID of armory: 28166
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:593 - Executing popen: ['python', '/usr/lib/armory/guardian.py', '28166', '28181']
2016-07-09 16:06 (INFO) -- SDM.py:848 - Creating proxy in SDM: host=127.0.0.1, port=8332
2016-07-09 16:06 (INFO) -- ArmoryQt.py:1527 - setupUriRegistration
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:593 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:593 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2016-07-09 16:06 (INFO) -- ArmoryUtils.py:593 - Executing popen: find /home/mapi -type f -name "mimeTypes.rdf"
2016-07-09 16:06 (INFO) -- ArmoryQt.py:664 - Usermode: Advanced
2016-07-09 16:06 (INFO) -- ArmoryQt.py:1823 - Changing usermode:
2016-07-09 16:06 (INFO) -- ArmoryQt.py:1824 - From: Advanced
2016-07-09 16:06 (INFO) -- ArmoryQt.py:1832 - To: Advanced
2016-07-09 16:06 (INFO) -- ArmoryQt.py:5812 - Dashboard switched to auto-InitSync
2016-07-09 16:15 (INFO) -- ArmoryQt.py:2498 - loadBlockchainIfNecessary
2016-07-09 16:15 (INFO) -- ArmoryQt.py:2519 - Setting netmode: 1
2016-07-09 16:15 (INFO) -- ArmoryQt.py:5935 - Dashboard switched to "Scanning" mode
2016-07-09 16:15 (INFO) -- Networking.py:64 - Connection initiated. Start handshake
2016-07-09 16:15 (INFO) -- ArmoryQt.py:5935 - Dashboard switched to "Scanning" mode
2016-07-09 16:16 (ERROR) -- Networking.py:350 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-07-09 16:16 (INFO) -- ArmoryQt.py:5801 - Dashboard switched to auto-BadConnection
2016-07-09 16:16 (INFO) -- ArmoryQt.py:2519 - Setting netmode: 1
2016-07-09 16:16 (INFO) -- Networking.py:64 - Connection initiated. Start handshake
2016-07-09 16:16 (INFO) -- Networking.py:155 - Received version message from peer:
2016-07-09 16:16 (INFO) -- Networking.py:156 - Version: 70012
2016-07-09 16:16 (INFO) -- Networking.py:157 - SubVersion: /Satoshi:0.12.1/
2016-07-09 16:16 (INFO) -- Networking.py:158 - TimeStamp: 1468077286
2016-07-09 16:16 (INFO) -- Networking.py:159 - StartHeight: 419988
2016-07-09 16:16 (INFO) -- Networking.py:341 - Handshake finished, connection open!
armorycplog.txt:
|
|
|
|
|
I had managed to get Armory 0.94.1 fully installed and running fine on Ubuntu 14.04.4 LTS, and was about to open one of my old cold storage wallets, but now it won't start.
The only changes to my system have been basic Ubuntu updates and installing python pip and Electrum.
Has anyone had a similar problem? I would hate to have to uninstall and reinstall as it takes so long
|
|
|
|
Thanks. I'm sorry, but I'm still a bit confused about the procedure. I've downloaded the sha256sum file as you've instructed, but can't find your public key. Would that be something equivalent to Alan's key ID '98832223'? i.e. would I enter the following? $ gpg --recv-keys --keyserver keyserver.ubuntu.com **your key ID**
$ dpkg-sig --verify armory_0.94.1_amd64.deb |
|
|
|
|
What if you're not comfortable compiling from source yourself?
I downloaded the latest version as suggested by knightdk, and when I run the verify:
$ dpkg-sig --verify *.deb
it outputs the folowing:
Processing armory_0.94.0_amd64.deb...
I'm probably too much of a noob to figure out how all this isn't disconcerting
|
|
|
|
Has anyone else been getting, "This data is not currently available. Please try again later." when trying to do things in teh 'Trade' section?
Furthermore, a buy order I made did not get filled when the price went below it.
I saw that message once but I've only made a dozen trades or less since January. Are you trading in CAD? The order book is pretty thin for CAD orders; the 24-hour volume is usually less than 100 BTC. Somebody would have to be selling in order to fill your buy order... and it just isn't happening. trading XBT for ETH. The order book is pretty hefty, with huge volume over the last few days |
|
|
|
|
Has anyone else been getting, "This data is not currently available. Please try again later." when trying to do things in teh 'Trade' section?
Furthermore, a buy order I made did not get filled when the price went below it.
|
|
|
|
I have a large supply of CLAM on polo for trading and lending purposes - Can I vote for the removal of digging too?
Unfortunately not. Poloniex refuse to stake their coins. You could withdraw them and stake them yourself however. Is it a relatively simple procedure? or perhaps a step by step guide available? The whole petition thing is quite over my head I'm afraid but I would love to vote =) I've not had the time to figure it out for myself either. Has anyone made a straight forward step by step guide somewhere for those who might need it? No user guides!! The CLAMidea (careful how you say that) system is a poll test. If you ain't aristocratic able enough to figure it out, then you get to watch. There will be a full explanation and user guide available on the website once the client is squared-away. Cool. Thanks. Big up all you CLAMdevs for your good work |
|
|
|
|
I've had some issues with loading by card. The consequences have been a real headache, including a rejected payment for a food order.
e-coin has a link that I can use to recommend people to get e-coin cards, with a financial incentive. I would love to recommend people to them, but I don't want to look like an idiot for recommending a service that is still figuring out its bugs and such.
Here's hoping they pull their socks up soon
|
|
|
|
I have a large supply of CLAM on polo for trading and lending purposes - Can I vote for the removal of digging too?
Unfortunately not. Poloniex refuse to stake their coins. You could withdraw them and stake them yourself however. Is it a relatively simple procedure? or perhaps a step by step guide available? The whole petition thing is quite over my head I'm afraid but I would love to vote =) I've not had the time to figure it out for myself either. Has anyone made a straight forward step by step guide somewhere for those who might need it? |
|
|
|
|
The result of a vote doesn't necessarily bring about the result that's in the majority's best interest.
|
|
|
|
Then, there is this whale asshole who s decided to implement some kind of vicious plan targeting at either a) destroying CLAM and all other nice things I have already mentioned or b) dump the coin to its lows so he could pump it again and make more money. Either way, I m not happy, not cause of the price or my loss if I would decide to sell now but cause of the lack of sustainability and stability I d hoped I ve found in CLAM.
Yeah, the stability is not likely to be a thing for a while yet. As soon as the whale digger finishes, there's likely to be a buying frenzy, then a period of inevitable corrections and ups and downs. Should be fun! |
|
|
|
Any speculations on what's going on with the clam price?
Seems a bit weird that it's dropping so low considering how most coins are invested on the site. Maybe some people just trying to manipulate the market to get their hands on more coins?
other than the clam digger whale, I gather someone just won about 40k Clamon just-dice, so have no doubt been cashing out |
|
|
|
|
Show Posts
