[ANN] DigitalNote |XDN| - ICCO Announce - NEWS

[papa_lazzarou]

You can use the latest version of DigitalNote with some minor fixes:

Graphical DigitalNote wallet for users:                                                     
https://mega.nz/#!Sx8xmYaQ!BnCHYMb-DLz0eGqrbmlQwiqMwDq3gxyfzcTiskUbCm8 DigitalNote wallet Linux

Console DigitalNote wallet for services:
https://mega.nz/#!y1FEnDKZ!gg_JuARdXHbcyjK98BTKqmj6giDZml-BSNoS2RiY2x0 Simplewallet Linux

Thanks. But I want to compile it.

[dNote]

Please, provide more info about your error, copy-paste all your logs about that.

Hi,

Linux Mint 17.1 Rebecca
Boost 1.55
gcc version 4.9.2 posix
GNU Make 3.81
Latest code from github HEAD -> https://github.com/xdn-project/digitalnote

pastebin

Thanks.

According to your log, it looks like you have a problem with building only connectivity_tool (not a critical issues to run digitalnote). And you may not have any problems with building digitalnoted and simplewallet. Check it, please.

Maybe for some reason, you had some older source code, so after you made "git pull" and made a building of the digitalnote in the same folder. In that case you should regenerate makefile with CMake and try to build it again.

[dNote]

Thank you, NewsBTC folks, @Cryptallica,  for DigitalNote article  http://us.newsbtc.com/digitalnote-xdn-truly-anonymous-decentralized-and-private-banking/

[MoneroMooo]

According to your log, it looks like you have a problem with building only connectivity_tool (not a critical issues to run digitalnote). And you may not have any problems with building digitalnoted and simplewallet. Check it, please.

Maybe for some reason, you had some older source code, so after you made "git pull" and made a building of the digitalnote in the same folder. In that case you should regenerate makefile with CMake and try to build it again.

I've already seen people report link failures on connectivity_tool for Monero. It was always on Ubuntu though, I think, I'd never seen this reported on Mint. So I don't think it's old code, but something to do with the build system both got from cryptonote. I wonder if it's a linking order issue. I'm not sure how to tell cmake to output the gcc (or ld) command line it's running, but I'd be curious to see it, in case it's not placing the epee stuff after the last object/lib that uses epee.

[papa_lazzarou]

According to your log, it looks like you have a problem with building only connectivity_tool (not a critical issues to run digitalnote). And you may not have any problems with building digitalnoted and simplewallet. Check it, please.

Maybe for some reason, you had some older source code, so after you made "git pull" and made a building of the digitalnote in the same folder. In that case you should regenerate makefile with CMake and try to build it again.

I've already seen people report link failures on connectivity_tool for Monero. It was always on Ubuntu though, I think, I'd never seen this reported on Mint. So I don't think it's old code, but something to do with the build system both got from cryptonote. I wonder if it's a linking order issue. I'm not sure how to tell cmake to output the gcc (or ld) command line it's running, but I'd be curious to see it, in case it's not placing the epee stuff after the last object/lib that uses epee.

Hi moo. Now that you mention it this does look like the same problem I had compiling monero for windows. And its not just linking connectivity tool. If I try to make with -k flag it will subsequently fail in linking digitalnoted, simpleminer, core_proxy and all the testing units.

cmake -E cmake_link_script CMakeFiles/connectivity_tool.dir/link.txt --verbose=1

Code:

/usr/bin/c++    -std=c++11 -D_GNU_SOURCE  -Wall -Wextra -Wpointer-arith -Wundef -Wvla -Wwrite-strings -Werror -Wno-error=extra -Wno-error=deprecated-declarations -Wno-error=sign-compare -Wno-error=strict-aliasing -Wno-error=type-limits -Wno-unused-parameter -Wno-error=unused-variable -Wno-error=undef -Wno-error=uninitialized -Wno-error=unused-result -Wlogical-op -Wno-error=maybe-uninitialized -Wno-error=clobbered -Wno-error=unused-but-set-variable -Wno-reorder -Wno-missing-field-initializers -march=native -maes -pthread -O3 -DNDEBUG -Ofast -DNDEBUG -Wno-unused-variable -flto    CMakeFiles/connectivity_tool.dir/connectivity_tool/conn_tool.cpp.o  -o connectivity_tool -rdynamic ../contrib/libepee.a librpc.a libcryptonote_core.a libcrypto.a libcommon.a libserialization.a -lboost_system -lboost_filesystem -lboost_thread -lboost_date_time -lboost_chrono -lboost_regex -lboost_serialization -lboost_program_options -Wl,-Bstatic -lboost_coroutine -Wl,-Bdynamic -lboost_context -lpthread -lrt 
/tmp/ccCMVJJn.ltrans0.ltrans.o: In function `void epee::serialization::json::run_handler<epee::serialization::portable_storage>(epee::serialization::portable_storage::hsection, __gnu_cxx::__normal_iterator<char const*, std::string>&, __gnu_cxx::__normal_iterator<char const*, std::string>, epee::serialization::portable_storage&)':
ccCMVJJn.ltrans0.o:(.text+0x40e): undefined reference to `epee::log_space::log_singletone::get_prefix_entry()'
ccCMVJJn.ltrans0.o:(.text+0x4ee): undefined reference to `epee::log_space::log_singletone::do_log_message(std::string const&, int, int, bool, char const*)'
ccCMVJJn.ltrans0.o:(.text+0x517): undefined reference to `epee::log_space::log_singletone::get_set_err_count(bool, unsigned long)'
ccCMVJJn.ltrans0.o:(.text+0x525): undefined reference to `epee::log_space::log_singletone::get_set_err_count(bool, unsigned long)'
ccCMVJJn.ltrans0.o:(.text+0x70e): undefined reference to `epee::log_space::log_singletone::get_prefix_entry()'
ccCMVJJn.ltrans0.o:(.text+0x7ee): undefined reference to `epee::log_space::log_singletone::do_log_message(std::string const&, int, int, bool, char const*)'

(snip)

Thanks mate!

[arnuschky]

According to your log, it looks like you have a problem with building only connectivity_tool (not a critical issues to run digitalnote). And you may not have any problems with building digitalnoted and simplewallet. Check it, please.

Maybe for some reason, you had some older source code, so after you made "git pull" and made a building of the digitalnote in the same folder. In that case you should regenerate makefile with CMake and try to build it again.

I've already seen people report link failures on connectivity_tool for Monero. It was always on Ubuntu though, I think, I'd never seen this reported on Mint. So I don't think it's old code, but something to do with the build system both got from cryptonote. I wonder if it's a linking order issue. I'm not sure how to tell cmake to output the gcc (or ld) command line it's running, but I'd be curious to see it, in case it's not placing the epee stuff after the last object/lib that uses epee.

No problem on 14.04 for me.

[MoneroMooo]

I'd say try running the line manually, to make sure you get the same error, and then try running the same, with an extra ../contrib/libepee.a inserted just after libserialization.a and see if that helps.

[dNote]

By the way we are working on ALIAS, but not OpenAlias, but our own Digital Aliasing system, made for web. Not only DNS, but DNS + JSON API.
For all cryptos, but made for DigitalNote. Very flexible and easy for both users and developers. With the Aliasing we will introduce a ready to use platform based on it for free aliasing, as well as your own platform building instructions. Stay tuned.

The age of DigitalNote services is coming.

[arnuschky]

By the way we are working on ALIAS, but not OpenAlias, but our own Digital Aliasing system, made for web. Not only DNS, but DNS + JSON API.
For all cryptos, but made for DigitalNote. Very flexible and easy for both users and developers. With the Aliasing we will introduce a ready to use platform based on it for free aliasing, as well as your own platform building instructions. Stay tuned.

Couldn't you just slap a JSON-API on top of OpenAlias? I mean, why create yet another standard if the existing one is battle-tested and works fine?

[dNote]

By the way we are working on ALIAS, but not OpenAlias, but our own Digital Aliasing system, made for web. Not only DNS, but DNS + JSON API.
For all cryptos, but made for DigitalNote. Very flexible and easy for both users and developers. With the Aliasing we will introduce a ready to use platform based on it for free aliasing, as well as your own platform building instructions. Stay tuned.

Couldn't you just slap a JSON-API on top of OpenAlias? I mean, why create yet another standard if the existing one is battle-tested and works fine?

we always create our own standards, we don`t want to fork/copy any of features of any of coins, like you can see how far is DigitalNote from any other CryptoNote:

"d" in address (with extra letter), supply structure -> no dust generation outputs, messages, blockchain banking, etc, etc, etc, we keep work to provide #1 proof-of-work cryptocurrency with true value because of its features.

OpenAlias was good, but we are going to make some better stuff. And DigitalNote aliases will include all OpenAlias features, but updated, with JSON-API and with different easy to use structures.
 


 

[redpepper]

You guys rock!  It sounds like the aliases will be super easy to use, just like the rest of what DigitalNote does.

[dNote]

You guys rock!  It sounds like the aliases will be super easy to use, just like the rest of what DigitalNote does.

Yes, we are working to make it easy for web developers and services integration. DNS+JSON-API will be very useful for any cryptocurrency alias, including Bitcoin.

[duplan]

I happened to stumble upon a unique vision — based upon pristine reasoning — which could very likely give XDN an abnormally huge push //
I will give it more thought , and however , my intuition tells me to wait for all favourable circumstances to fall into place : <flow

[esoum.1003]

Hello dNote,

Look what fluffy_troll a trollero dev is talking about you.

I think is disgusting trolleros devs makes such comments about another dev.

Please comment the post.

I am littering it with comments as we speak.

Please compare development of monero with the development of the fathers of the code that your coin uses, ups, sorry, this project was stolen from T_F_T.

Yes, thats when you scammers started. You Trolleros Devs couldn't even create a genesis block, so you stole the project from T_F_T.

We forked the repo, and retained the social contract implicit in Monero's launch by not relaunching it, thus ensuring that even thankful_for_today was rewarded for his work (ie. as an early miner). If we had relaunched it then it would have been difficult to do so fairly, someone on either side would feel mistreated.

Look what another dev think of your work, 6 months ago, and Monero did not change a thing since then.

Looking at it objectively is always better than quoting the opinion of "another dev", especially when that dev is likely involved in the Bytecoin scam.

As for me - monero is a biggest bubble, because there is only speculation about it

Of course there's speculation. But there is also actual use.

blockchain is unusable with its size

How do you suppose you'll have a usable cryptocurrency that is actually used, and yet not have an ever-growing blockchain? What a silly comment, it really shows the desperation of this trolling.

IMO almost everything about monero seems terrible - unusable blockchain size (On average PC, it just can`t be a network node)

Runs just fine on a Raspberry Pi 1 with 256mb RAM, so I guess he must be talking about running it on a 486 DX2 66.

block intervals

Chosen by...thankful_for_today! And here I thought you were hailing him as an incredible human being?

tx generation size

Is duck dark digital dontcareNote really trying to claim that their transactions are significantly smaller?

fee size

0.001 XMR per kilobyte (most transactions are 1kb-2kb), so that's about $0.0000056 per transaction. Gosh. So expensive.

no GUI after almost 1 year since start

Wrong. There are several GUIs: https://getmonero.org/getting-started/choose

totally wrong way of development

As opposed to dNote, which has the "totally right" way of development, no? If that's the case, then why have they attracted NO other contributors?

https://github.com/xdn-project/digitalnote/graphs/contributors vs. https://github.com/monero-project/bitmonero/graphs/contributors

looks like just no understanding of CN technology.

Looks like I've got to rehash some of our research bulletins. Let's do this one:

MRL-0003: Monero is Not That Mysterious

[MoneroMooo]

0.001 XMR per kilobyte (most transactions are 1kb-2kb), so that's about $0.0000056 per transaction. Gosh. So expensive.

Offtopic, but for the record: 0.01 monero per kB. Typo, I guess.
(It used to be less, but had to be bumped because blockchain spammers too advantage)

[dNote]

Hello dNote,

Look what fluffy_troll a trollero dev is talking about you.

I think is disgusting trolleros devs makes such comments about another dev.

Can you please give me a link to that and i will answer directly. Thank you.

[duplan]

We all know how negatively to violently biased some Monero pushers and
trolls are acting out against XDN as seen on a trollbox and in online threads .

Let's always overlook the pointlessness of losing time and energy on quarrels
that will only delay our concentration and elaborations of details which truly
benefit our community and this crypto currency project as a whole . Anyone
who compares , by feature or comparative trial , will find enough incentive to
go either one way or another with support or investment . Intellectual cockfights
might be funny to follow for a while , no doubt about that , gossip is entertainment .

Personally , I believe in the growing opportunities or features XDN offers and delivers —
among other projects — XDN is one of my favourite projects supported ; posh love privacy . 

[dNote]

Hello dNote,

Look what fluffy_troll a trollero dev is talking about you.

I think is disgusting trolleros devs makes such comments about another dev.

As for me - monero is a biggest bubble, because there is only speculation about it

Of course there's speculation. But there is also actual use.

<-Actual use? Look at XMR blocks and transactions count, i can see lots of "empty" blocks here http://chainradar.com/xmr/blocks

blockchain is unusable with its size

How do you suppose you'll have a usable cryptocurrency that is actually used, and yet not have an ever-growing blockchain? What a silly comment, it really shows the desperation of this trolling.

<-Sorry, i may said it in the way you didn`t get me. I mean № of blocks (more than 500 000 after just one year), big size of blockchain, lots of "dust" there, with "bad" outputs.

IMO almost everything about monero seems terrible - unusable blockchain size (On average PC, it just can`t be a network node)

Runs just fine on a Raspberry Pi 1 with 256mb RAM, so I guess he must be talking about running it on a 486 DX2 66.

<- Read previous statement.

block intervals

Chosen by...thankful_for_today! And here I thought you were hailing him as an incredible human being?

<- So you can change everything if you want and can.

tx generation size

Is duck dark digital dontcareNote really trying to claim that their transactions are significantly smaller?

<- Yes, for sure, XDN DigitalNote (duck, Dark) transactions are significantly smaller, not only transactions, but all "mixing process" is much more efficient, avoiding dust. Let me show you:

DigitalNote "generation" transaction has no dust and very small and good for mixing and SMALLEST CryptoNote transaction, because of outputs structure (only 2 outputs with static block reward and no dust, because of halvings. 150 block reward= 100and 50). DigitalNote "generation" transaction size = 130 bytes (i take min. nowdays value!), and average XDN "empty" block = 174 bytes.
http://chainradar.com/xdn/block/59e82fb50a8690ce37c3ee3887671894fe96c5b53dfdc1fbbd2b8e32c8d9416c
http://chainradar.com/xdn/blocks

Monero XMR average generation transaction consist of min. 4 outputs with dust now and lots of XMR blockchain transaction outputs consists lots of "dust", bad for mixing, bad for blockchain size.
Average XMR "generation" transaction size = 209 bytes (i take min. nowdays value!) and average "empty" block = 253 bytes.
http://chainradar.com/xmr/block/3ce1606a4741d65f8c6cf9fa879b74c7af0c955912adf2457ca55b121a8b4f1c

So lets compare. Lower values are better.

                                                DigitalNote XDN            vs           Monero XMR transaction and block size.
Generation tranaction size                   130                     vs                                    209            <- XDN wins >60% over XMR here
"Empty" block size                               174                     vs                                    253         

fee size

0.001 XMR per kilobyte (most transactions are 1kb-2kb), so that's about $0.0000056 per transaction. Gosh. So expensive.

<- ok

no GUI after almost 1 year since start

Wrong. There are several GUIs: https://getmonero.org/getting-started/choose

<- Show me native cross platform (Linux, OsX, Windows) GUI that i can build myself? I can`t find any open-source Monero GUI with described specifications, and only with this specifications there is a need in this GUI.

totally wrong way of development

As opposed to dNote, which has the "totally right" way of development, no? If that's the case, then why have they attracted NO other contributors?

https://github.com/xdn-project/digitalnote/graphs/contributors vs. https://github.com/monero-project/bitmonero/graphs/contributors
<- First, thank you, xdn-project repo is new, second and main one -  you, guys, have much a bigger mouths and time to spend on shouting.

looks like just no understanding of CN technology.

Looks like I've got to rehash some of our research bulletins. Let's do this one:

MRL-0003: Monero is Not That Mysterious
<- Looks like too many words and much less features and important improvements.

[duplan]

dnote , you can find all quotes in their respective thread pages if you click on the name date lines provided above each quote ;
anyway , the list-rehash of your quotes likely comes from this thread , a long pointless one : its mostly under post #56 below the black pics
https://bitcointalk.org/index.php?topic=1139306.msg12018686#msg12018686

I would not mind , let's move on for the better

[smooth]

DigitalNote "generation" transaction has no dust and very small and good for mixing and SMALLEST CryptoNote transaction, because of outputs structure (only 2 outputs with static block reward and no dust, because of halvings. 150 block reward= 100and 50). DigitalNote "generation" transaction size = 130 bytes (i take min. nowdays value!), and average XDN "empty" block = 174 bytes.

I'm curious why you didn't just make it 100 or 200 which would have been even smaller (one output), about half the size instead of 150 (two outputs).

BTW, I don't see the point of rehashing a bunch of bickering from February, clearly everyone has moved on and continued development since then. If trolls are digging that stuff up to create conflict, it would probably be better to just ignore them.