Dear Diamond programmers and owners.

Is it normal, that synchronised wallet 2.1.0.3 on Mac OS, "closes unexpectedly" (or, simply speaking, crushes) since today?

I installed it a week ago, synced the whole blockchain (for some reason, it did not work with downloaded blockchain files), and today it crushes constantly, not even opening the actual wallet window.

I know Mac version has always been a kind of a "poor unwanted relative", but could you do something with it, please?

Hello.

I almost had similar issue - transferred more than 800 DMD to another address, not realising I was in the wrong fork.

DMD team was quite professional and always found time to respond to my mails. I highly appreciate that.

Mac OS wallet 2.1.0.1 indeed, crashes whenever one does anything else but look . However, it connects to correct nodes and synchronises well.

Even after full re-sync, my last transaction was shown as unconfirmed, but withdrawn from my account.

Open the console and execute "repairwallet". The very next block (few minutes time) will fix everything and the amount will be correct.

Many thanks for prompt reaction.

Version 2.2 seems to work. When the OS X binary is available, I'll pick it up.

Once again - thanks and good luck.

A Mac Mini with OS X Yosemite 10.10.3 with all latest updates and patches.

Just installed Electrum. Never used it before. No wallets on this mac. Created a wallet, everything is fine.

Transferred 0.5 BTC to the new wallet. Received nicely, waiting for confirmation.

Closed Electrum.

After 5 minutes tried to open Electrum again. Got a message box: "Electrum error" with 2 buttons: "Open Console" and "Terminate". No error number, no error description.

Below is a copy of latest Electrum messages from Console.

Is it normal for a freshly released version? Will I ever see my half-bitcoin again?

Please, help.


12/06/15 18:49:14,504 Electrum[435]: Traceback (most recent call last):
12/06/15 18:49:14,504 Electrum[435]:   File "/Applications/Electrum.app/Contents/Resources/__boot__.py", line 125, in <module>
12/06/15 18:49:14,504 Electrum[435]:     _run()
12/06/15 18:49:14,504 Electrum[435]:   File "/Applications/Electrum.app/Contents/Resources/__boot__.py", line 62, in _run
12/06/15 18:49:14,504 Electrum[435]:     exec(compile(source, path, 'exec'), globals(), globals())
12/06/15 18:49:14,504 Electrum[435]:   File "/Applications/Electrum.app/Contents/Resources/electrum.py", line 410, in <module>
12/06/15 18:49:14,504 Electrum[435]:     args.func(config)
12/06/15 18:49:14,505 Electrum[435]:   File "/Applications/Electrum.app/Contents/Resources/electrum.py", line 129, in run_gui
12/06/15 18:49:14,505 Electrum[435]:     gui.main(url)
12/06/15 18:49:14,505 Electrum[435]:   File "/Applications/Electrum.app/Contents/Resources/lib/python2.7/gui/qt/__init__.py", line 219, in main
12/06/15 18:49:14,505 Electrum[435]:     w.load_wallet(wallet)
12/06/15 18:49:14,505 Electrum[435]:   File "/Applications/Electrum.app/Contents/Resources/lib/python2.7/gui/qt/main_window.py", line 236, in load_wallet
12/06/15 18:49:14,505 Electrum[435]:     self.update_receive_tab()
12/06/15 18:49:14,505 Electrum[435]:   File "/Applications/Electrum.app/Contents/Resources/lib/python2.7/gui/qt/main_window.py", line 810, in update_receive_tab
12/06/15 18:49:14,505 Electrum[435]:     for req in self.wallet.get_sorted_requests(self.config):
12/06/15 18:49:14,506 Electrum[435]:   File "/Applications/Electrum.app/Contents/Resources/lib/python2.7/lib/wallet.py", line 1318, in get_sorted_requests
12/06/15 18:49:14,506 Electrum[435]:     return sorted(map(lambda x: self.get_payment_request(x, config), self.receive_requests.keys()), key=itemgetter('timestamp'))
12/06/15 18:49:14,506 Electrum[435]:   File "/Applications/Electrum.app/Contents/Resources/lib/python2.7/lib/wallet.py", line 1318, in <lambda>
12/06/15 18:49:14,506 Electrum[435]:     return sorted(map(lambda x: self.get_payment_request(x, config), self.receive_requests.keys()), key=itemgetter('timestamp'))
12/06/15 18:49:14,506 Electrum[435]:   File "/Applications/Electrum.app/Contents/Resources/lib/python2.7/lib/wallet.py", line 1245, in get_payment_request
12/06/15 18:49:14,506 Electrum[435]:     path = os.path.join(rdir, key + '.bip70')
12/06/15 18:49:14,506 Electrum[435]:   File "posixpath.pyc", line 77, in join
12/06/15 18:49:14,506 Electrum[435]: AttributeError: 'NoneType' object has no attribute 'endswith'
12/06/15 18:49:14,523 Electrum[435]: Electrum Error
12/06/15 18:49:14,523 Electrum[435]: 2015-06-12 18:49:14.522 Electrum[435:69930] Electrum Error
12/06/15 18:49:16,158 Console[441]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable

Dear colleagues and Miner.eu

When I switch the A2 new mini on, and open your scripta interface, both blades are mining normally. However, in about 30 seconds, their hash rate begins to decrease and reaches 0 (zero) in 20-25 seconds. And stays there indefinitely. Restarting the miner does not help, neither does rebooting Raspberry. Only if I physically turn the power supply off and on again, the blades start working, but everything happens again like I described in the beginning.

Please, help.

-------------------------------------------

21/09/2014

I sent almost exactly the same text directly to Miner.eu yesterday. Received an answer today:
-----------
Hi,

You could search youtube to find some instruction of setting up the miner.

https://github.com/MinerEU/scripta_a2
It is our image download link for the miner, please check this out as well.

good luck!
--------------

I wonder, do they read their customers' mails at all?

I sent another mail - quote below:

--------------

Dear Support.

1. There are no videos depicting the setup of A2 New Mini Terminator with Raspberry PI built-in. None. Not on YouTube, not anywhere.
2. As I have already mentioned, I installed your Scripta miner and interface using CURL from Raspberry. Successfully.

Let me, please, specify the problem again.

1. A2 New Mini Terminator is powered correctly.
2. Immediately after power-on, when Raspberry loads, your Scripta interface shows that both blades are working normally.
3. In 30-35 seconds, hashing rate on both blades starts to decrease.
4. In another 30-40 seconds, both blades come to zero.
5. Miner restart or Raspberry reboot does not help.

Could you, please, help. I can execute and send you results of any log outputs, grep - whatever you need.

Regards

--------------

Sorry for being boring - when is VIA launched for mining? There is not a single countdown timer anywhere, pools don't have this info either.

A stupid question from a Noob: Is it somehow possible to get rid of the chat window in the wallet?

I am not much of a chatter, also combined with excessively "colourful" TalkCoin logo, when I open the wallet, I have a distinct impression of having arrived to some comic strip adolescents'  chat.

Otherwise, the coin is fine. I love NIST5. Very stable and performant algo for 290X, compared to X11 and X13.