Topic: [ANN] DigitalNote |XDN| - ICCO Announce - NEWS - page 139. (Read 450263 times)

We are glad with all your support, but we never receive anything from you, as i know. No mail or any other forum post from here or digitalnotetalk.org. Correct me if i am wrong.
All support is a user-to-user support. At least now. We (developers) are working on xdn development, new features and implementation of community ideas.
Also soon community will receive wiki-alike notes about XDN and working with new API.
I will make few announcements soon (next 7-10 days), so you can think about it as a good news

 

Hi,

I'm new here and I would love if anyone from XDN can tell me some news. I work for a big german Investmentgroup, we talked about XDN.
But the big Problem we had is that it seems that the support of XDN is not really working good.
I as a member with technician background couldn't convince them, that XDN has still a big potential, because they need a up-to-date state.

Maybe you can write some good news to make me convince them!

Thank you!

https://www.poloniex.com/exchange#btc_xdn

Where do you follow that? I'm kinda new...

Installed v.1.0.6 for Windows 7 64 bit and, having finally remembered to add the exe process to the excluded programs in my anti-virus , the wallet immediately started syncing, then when I exited the wallet a 'Saving Data' message appeared and as it did so 3 of the files in the roaming folder all updated simultaneously - so far so good - but ~ 2 hours later the 'Saving Data' process was still continuing but without showing any further updates to the files in the roaming folder, at least as far as I could see. I therefore closed the 'Saving Data' message and in the Windows Task Manager ended the digitalnotewallet.exe process. I restarted the wallet, allowed it to sync for a few minutes, and then exited the wallet, with the same result as before - i.e. the 'Saving Data' process updated the files and then continued but without any further updates to the files in the roaming folder being made. 

Volume and price is finally catching up for xdn i like it

The link is OK.
Thanks :-).

Please, try ctrl+f5 on the official digitalnote.org website and try again.

Hello guys,

My GUI wallet sync stuck at block 225034.

Any ideas?

Just checked : now the link on digitalnotetalk work, thank you.

(the link on the homepage of digitalnote.org still don't work)

Check it again, please, there was a problem with a link:) No "!" in link. Solved.

This is the link for the Linux GUI version 1.0.6 that don't work (It work's but there is no file to download) :-(.

Excellent price up

Just installed 1.0.6 version of the wallet for Windows 7 64 bit. Works fine 

I can't download the 1.0.6 version of the wallet for Linux (Ubuntu).
The Linux download link on "digitalnote.org" is for uploading files in MEGA, not downloading the wallet (links for Windows are OK).

Hello community,

is very quiet in here. I am trying the banking system and i am going to wait a couple of months to see the results.

Thank you dNote for your work and dedication.

1.0.6-beta

Process:         digitalnotewallet [51591]
Path:            /Applications/digitalnotewallet.app/Contents/MacOS/digitalnotewallet
Identifier:      
Version:         .. ($..)
Code Type:       X86-64 (Native)
Parent Process:  launchd [226]
Responsible:     digitalnotewallet [51591]
User ID:         501

Date/Time:       2016-02-28 14:59:35.350 +0000
OS Version:      Mac OS X 10.9.5 (13F34)
Report Version:  11
Anonymous UUID:  ----------------------


Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
terminating with uncaught exception of type std::__1::system_error: Object was not initialized
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib           0x00007fff90868866 __pthread_kill + 10
1   libsystem_pthread.dylib          0x00007fff95b5a35c pthread_kill + 92
2   libsystem_c.dylib                0x00007fff90243b1a abort + 125
3   libc++abi.dylib                  0x00007fff91894f31 abort_message + 257
4   libc++abi.dylib                  0x00007fff918ba93a default_terminate_handler() + 240
5   libobjc.A.dylib                  0x00007fff8f455322 _objc_terminate() + 124
6   libc++abi.dylib                  0x00007fff918b81d1 std::__terminate(void (*)()) + 8
7   libc++abi.dylib                  0x00007fff918b7c5b __cxa_throw + 124
8                                    0x00000001035c9c57 CryptoNote::TransactionPrefixImpl::~TransactionPrefixImpl() + 19879
9                                    0x000000010349e490 WalletGui::InprocessNode::init(std::__1::function const&) + 1584
10                                   0x00000001034eec61 QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) + 3841
11                                   0x00000001034ee891 QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) + 2865
12                                   0x00000001034ebf98 std::__1::__tree, std::__1::allocator >, std::__1::less, std::__1::allocator > >, std::__1::allocator, std::__1::allocator > > >::destroy(std::__1::__tree_node, std::__1::allocator >, void*>*) + 1736
13  libdyld.dylib                    0x00007fff9754e5fd start + 1

--- I hope that helps to find the error

I have no problem of whatsoever kind with the previous 1.0.5-beta ,  I'll keep running that wallet for the meanwhile …

i always have to "force quit" the gui-wallet.

1.0.6-beta / OSX 10.10.5


edit: not always. the last time it used the wallet it was possible with cmd-q.

Thank you for all bug reports, please, keep testing, sync may have issues because we are updating some of seed nodes.

We will investigate all bugs and will upload fixed versions.

1.0.6-beta does not work on OSX 10.9.5 , it is not
getting past the first screen , not indicating any loading ,
one can only quit which prompts a crash of the app at that

The previous version 1.0.5-beta does work ,
never crashes , is fast and fully functional …
I am going to use this one until it's fixed …