[ANN] Denarius [D] - First "Tribus" PoW/PoS Hybrid Masternodes, Ring Sigs

[berron]

Any update on MN issue fix?
when we can expect update?

If anyone can post status here, it would be really good.

v2.5.21 will be released soon, which will require MN transactions to mature for 500 blocks. the fix will activate on block 1.25M in order to give nodes time to update. the commit is here https://github.com/denariuscrypto/denarius/commit/4e066cbcd2c23da37fb353f2d7ab85acb831bfcc

this is basically a simple workaround which just increases the MN maturation time so that the particular issue is effectively useless until 500+ MNs exist on the network, it isn't the large update i've been working on (which will be in the v2.6 branch).

In v2.6, we are redesigning how the MN selection system works completely; payments are made based on the average DNR earnings of all registered MNs and no MN is allowed to be paid more than any other. The wallet will show you the exact earnings of each of your masternodes, and possibly also the exact earnings of every masternode on the network, so that you can see this info clearly.

i apologize for my absence, unfortunately I can't rely on the crypto development to pay my bills and I had to take a new job which has required me to spend a lot of time away from home recently and I felt like there was 'not long left' until I finished up the v2.6 branch, however I've been getting a lot of messages lately to ask me to just do something, so v2.5.21 will be it

to those who mined with hashbag.cc - I will try to get it back up and running now!

Yup, the commits are up now in the v2.6 branch on the main Github. v2.6 will be a mandatory update that users will need to update to before block 1.25 million. The final versioning will be v2.6

https://github.com/carsenk/denarius/tree/v2.6

The release will be coming soon for those to update to with mining pools, masternodes, nodes, explorers, and regular wallets.

https://twitter.com/carsenjk/status/1038955904056549377

alright so yeah in v2.7 we will be redesigning the MN selection system. v2.6 will be this fix and a few other additions.

Hi devs.

We are in block 1.22M, but I have seen github master branch continues in the old v2.5.2.0. Can we update our MN's with enkayz fork or carsenk v2.6 branch or we should wait the fork to be included in the main branch??

Thanks and salute

[1714803979]

1714803979

[1714803979]

1714803979

[1714803979]

1714803979

[1714803979]

1714803979

[1714803979]

1714803979

[1714803979]

1714803979

[HE[A]RTLESS]

why im use chaindata at first post

it say error loading block index?

[manosv]

I created a poll about what is best for Denarius at this point in time
the poll is here: https://www.strawpoll.me/16477866
Denarius counts on you to decide what you want for the project to go forward.

[kingcarsen]

Any update on MN issue fix?
when we can expect update?

If anyone can post status here, it would be really good.

v2.5.21 will be released soon, which will require MN transactions to mature for 500 blocks. the fix will activate on block 1.25M in order to give nodes time to update. the commit is here https://github.com/denariuscrypto/denarius/commit/4e066cbcd2c23da37fb353f2d7ab85acb831bfcc

this is basically a simple workaround which just increases the MN maturation time so that the particular issue is effectively useless until 500+ MNs exist on the network, it isn't the large update i've been working on (which will be in the v2.6 branch).

In v2.6, we are redesigning how the MN selection system works completely; payments are made based on the average DNR earnings of all registered MNs and no MN is allowed to be paid more than any other. The wallet will show you the exact earnings of each of your masternodes, and possibly also the exact earnings of every masternode on the network, so that you can see this info clearly.

i apologize for my absence, unfortunately I can't rely on the crypto development to pay my bills and I had to take a new job which has required me to spend a lot of time away from home recently and I felt like there was 'not long left' until I finished up the v2.6 branch, however I've been getting a lot of messages lately to ask me to just do something, so v2.5.21 will be it

to those who mined with hashbag.cc - I will try to get it back up and running now!

Yup, the commits are up now in the v2.6 branch on the main Github. v2.6 will be a mandatory update that users will need to update to before block 1.25 million. The final versioning will be v2.6

https://github.com/carsenk/denarius/tree/v2.6

The release will be coming soon for those to update to with mining pools, masternodes, nodes, explorers, and regular wallets.

https://twitter.com/carsenjk/status/1038955904056549377

alright so yeah in v2.7 we will be redesigning the MN selection system. v2.6 will be this fix and a few other additions.

Hi devs.

We are in block 1.22M, but I have seen github master branch continues in the old v2.5.2.0. Can we update our MN's with enkayz fork or carsenk v2.6 branch or we should wait the fork to be included in the main branch??

Thanks and salute

We will be releasing v3 instead of v2.6, it will include the fix and several new features. The block that is currently set will be block 1.35 million instead now. There will be plenty of time to update once we release it, which should be later today or tomorrow.

[vella85]

Thanks for the update Carsen! I haven't posted in a while in here but I'm still holding my DNR and still building towards my first masternode. It was nice to check the DNR market and see DNR have some nice volume and price increase. I was glad that I bought more a few weeks ago when the price was low but didn't have a lot of spare BTC to buy what I wanted to buy but it's put me a step closer to owning a node.

[chrysophylax]

Any update on MN issue fix?
when we can expect update?

If anyone can post status here, it would be really good.

v2.5.21 will be released soon, which will require MN transactions to mature for 500 blocks. the fix will activate on block 1.25M in order to give nodes time to update. the commit is here https://github.com/denariuscrypto/denarius/commit/4e066cbcd2c23da37fb353f2d7ab85acb831bfcc

this is basically a simple workaround which just increases the MN maturation time so that the particular issue is effectively useless until 500+ MNs exist on the network, it isn't the large update i've been working on (which will be in the v2.6 branch).

In v2.6, we are redesigning how the MN selection system works completely; payments are made based on the average DNR earnings of all registered MNs and no MN is allowed to be paid more than any other. The wallet will show you the exact earnings of each of your masternodes, and possibly also the exact earnings of every masternode on the network, so that you can see this info clearly.

i apologize for my absence, unfortunately I can't rely on the crypto development to pay my bills and I had to take a new job which has required me to spend a lot of time away from home recently and I felt like there was 'not long left' until I finished up the v2.6 branch, however I've been getting a lot of messages lately to ask me to just do something, so v2.5.21 will be it

to those who mined with hashbag.cc - I will try to get it back up and running now!

Yup, the commits are up now in the v2.6 branch on the main Github. v2.6 will be a mandatory update that users will need to update to before block 1.25 million. The final versioning will be v2.6

https://github.com/carsenk/denarius/tree/v2.6

The release will be coming soon for those to update to with mining pools, masternodes, nodes, explorers, and regular wallets.

https://twitter.com/carsenjk/status/1038955904056549377

alright so yeah in v2.7 we will be redesigning the MN selection system. v2.6 will be this fix and a few other additions.

Hi devs.

We are in block 1.22M, but I have seen github master branch continues in the old v2.5.2.0. Can we update our MN's with enkayz fork or carsenk v2.6 branch or we should wait the fork to be included in the main branch??

Thanks and salute

We will be releasing v3 instead of v2.6, it will include the fix and several new features. The block that is currently set will be block 1.35 million instead now. There will be plenty of time to update once we release it, which should be later today or tomorrow.

Thanks for the update mate ...

#crysx

[AngryWhiteWolf]

Wallet v3 will contain something related to FGPA mining? It would be awesome for GPU miners to come back and have a chance to mine DNR again.
With GPU we'll surely come back to the price from Feb-March.

[kingcarsen]

DENARIUS V3 IS HERE!

This is a MANDATORY UPDATE and EVERYONE must UPDATE BEFORE BLOCK 1.35 MILLION!

Denarius v3.0.0 - MANDATORY UPDATE
- Lowered Proof of Data fee to 0.001 DNR per PoD submission, also added the ability to add a 24 character narration with your PoD submission.
- Added the RPC command masternode list full to display an array of all masternodes on the network and information about them
- Added the RPC command getblockheader "hash"
- Added the RPC command senddnrtoanon, sendanontoanon, sendanontodnr, estimateanonfee, txnreport, anoninfo, and anonoutputs
- Any references to Darksend are now referred to as Fortuna, Darksend no longer functions as usual, Ring Sigs have taken its place as our go to privacy feature
- Added Native Tor Optional Support (Start Denarius with the nativetor=1 flag to run with Native Tor with OBFS), Denarius now requires the libevent dependency to be built. (For those running a Ubuntu daemon, simply run ``` sudo apt-get install libevent-dev ``` to be able to compile Denarius)
- Added Ring Signatures, supporting anon txs after block 1.35 million and with protocol 30000, minimum Ring Signature Size supported will be 5, Recommended 16
- Fixed the known Hybrid Masternode exploit, the exploit fix patch goes live on block 1.35 million, ensure all your nodes are updated to v3.0.0 before block 1.35m!
- Denarius's Protocol is now 30000, after block 1.35 million, older protocol clients will no longer connect to the network
- Updated Splash Screen
- Lots of miscellaneous updates and improvements to Denarius

Get it here: https://github.com/carsenk/denarius/releases
You can git pull in your current cloned repo of Denarius to pull the newly updated "master" branch to recompile and update!

EVERYONE MUST UPDATE ASAP BEFORE BLOCK 1.35 MILLION, ALL NODES AND WALLETS MUST UPDATE, THIS INCLUDES ALL MINING POOLS, MASTERNODES, NODES, EXPLORERS, SPV SERVERS, and NORMAL WALLETS.

[AngryWhiteWolf]

I can confirm that is working perfectly on Ubuntu 16.04, thank you for solving so quickly the problem with masternodes and for the other features implemented.

[cryptonewzealand]

This is how I updated the MN wallet on VPS / vultr end:

Logged in to vps

Code:

denariusd stop
sudo apt-get install libevent-dev 
cd /denarius
git pull
cd src
make -f makefile.unix
sudo mv ~/denarius/src/denariusd /usr/local/bin/denariusd
denariusd --daemon

Then to check correct version running:

Code:

denariusd getinfo

Should say "version" : "v3.0.0.0"

[berron]

When compiling qt for ubuntu 16.04 I am having an error in the object 'build/backtrace.o'

To compile I'm simply doing

qmake denarius-qt.pro
make

Any ideas about the possible mistake?'

Thanks and salute

[kingcarsen]

When compiling qt for ubuntu 16.04 I am having an error in the object 'build/backtrace.o'

To compile I'm simply doing

qmake denarius-qt.pro
make

Any ideas about the possible mistake?'

Thanks and salute

You need libevent-dev installed now due to Tor integration:

Code:

sudo apt-get install libevent-dev

[ibinsad]

Fpgas owners pump it, mine it.. Then dump.
Good luck DNR.

[kingcarsen]

Denarius is the most impressive coin today when it has raised nearly 80%.
I guess more things behind the scene because it 's strange if the price rocketed only due to mandatory wallet upgrade.

It is a mandatory wallet upgrade, and also includes some really heavily wanted features like Tor and Ring Sigs....as usual Trezor and Ledger support are being worked on.

[sylph93]

When compiling qt for ubuntu 16.04 I am having an error in the object 'build/backtrace.o'

To compile I'm simply doing

qmake denarius-qt.pro
make

Any ideas about the possible mistake?'

Thanks and salute

You need libevent-dev installed now due to Tor integration:

Code:

sudo apt-get install libevent-dev

I did install libevent-dev, but I have 'build/hs_cache.o' error while compiling qt wallet.

What else should I do?

src/tor/address.h: In function ‘tor_addr_to_mapped_ipv4h’:
src/tor/torcompat.h:548:37: error: ‘const struct in6_addr’ has no member named ‘s6_addr32’
 #define S6_ADDR32(x) ((uint32_t*)(x).s6_addr32)
                                     ^
src/tor/address.h:126:35: note: in expansion of macro ‘S6_ADDR32’
 #define tor_addr_to_in6_addr32(x) S6_ADDR32(*tor_addr_to_in6_assert(x))
                                   ^
src/tor/address.h:153:14: note: in expansion of macro ‘tor_addr_to_in6_addr32’
     addr32 = tor_addr_to_in6_addr32(a);

[Shikahgo]

DENARIUS V3 IS HERE!

This is a MANDATORY UPDATE and EVERYONE must UPDATE BEFORE BLOCK 1.35 MILLION!

Denarius v3.0.0 - MANDATORY UPDATE
- Lowered Proof of Data fee to 0.001 DNR per PoD submission, also added the ability to add a 24 character narration with your PoD submission.
- Added the RPC command masternode list full to display an array of all masternodes on the network and information about them
- Added the RPC command getblockheader "hash"
- Added the RPC command senddnrtoanon, sendanontoanon, sendanontodnr, estimateanonfee, txnreport, anoninfo, and anonoutputs
- Any references to Darksend are now referred to as Fortuna, Darksend no longer functions as usual, Ring Sigs have taken its place as our go to privacy feature
- Added Native Tor Optional Support (Start Denarius with the nativetor=1 flag to run with Native Tor with OBFS), Denarius now requires the libevent dependency to be built. (For those running a Ubuntu daemon, simply run ``` sudo apt-get install libevent-dev ``` to be able to compile Denarius)
- Added Ring Signatures, supporting anon txs after block 1.35 million and with protocol 30000, minimum Ring Signature Size supported will be 5, Recommended 16
- Fixed the known Hybrid Masternode exploit, the exploit fix patch goes live on block 1.35 million, ensure all your nodes are updated to v3.0.0 before block 1.35m!
- Denarius's Protocol is now 30000, after block 1.35 million, older protocol clients will no longer connect to the network
- Updated Splash Screen
- Lots of miscellaneous updates and improvements to Denarius

Get it here: https://github.com/carsenk/denarius/releases
You can git pull in your current cloned repo of Denarius to pull the newly updated "master" branch to recompile and update!

EVERYONE MUST UPDATE ASAP BEFORE BLOCK 1.35 MILLION, ALL NODES AND WALLETS MUST UPDATE, THIS INCLUDES ALL MINING POOLS, MASTERNODES, NODES, EXPLORERS, SPV SERVERS, and NORMAL WALLETS.

So is this only stopping the script exploit? Some clarity on the subject would be appreciated, as we all know there are a few exploits that have taken place over the past few months. As well Enkayz mentioned this solution only scales for up to 500 MN's, is this still the case?

[berron]

When compiling qt for ubuntu 16.04 I am having an error in the object 'build/backtrace.o'

To compile I'm simply doing

qmake denarius-qt.pro
make

Any ideas about the possible mistake?'

Thanks and salute

You need libevent-dev installed now due to Tor integration:

Code:

sudo apt-get install libevent-dev

Installed and tried to compile with both command line and QT creator. I always found this error:

11:55:55: Running steps for project denarius-qt...
11:55:55: Configuration unchanged, skipping qmake step.
11:55:55: Starting: "/usr/bin/make"
cd /home/hache/denarius/src/leveldb && CC=gcc CXX=g++ /usr/bin/make OPT="-pipe -fpermissive -fstack-protector-all --param ssp-buffer-size=1 -O2" libleveldb.a libmemenv.a
make[1]: Entering directory '/home/hache/denarius/src/leveldb'
make[1]: 'libleveldb.a' is up to date.
make[1]: 'libmemenv.a' is up to date.
make[1]: Leaving directory '/home/hache/denarius/src/leveldb'
cd /home/hache/denarius; /bin/sh share/genbuild.sh /home/hache/denarius/build/build.h
gcc -c -pipe -std=c99 -O2 -D_REENTRANT -Wall -W -fPIC -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DQT_DISABLE_DEPRECATED_BEFORE=0 -DUSE_UPNP=1 -DSTATICLIB -DUSE_DBUS -DUSE_IPV6=1 -DUSE_LEVELDB -DHAVE_BUILD_INFO -DLINUX -DLINUX -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -Isrc -Isrc/json -Isrc/qt -Isrc/tor -Isrc/qt/plugins/mrichtexteditor -Isrc/leveldb/include -Isrc/leveldb/helpers -isystem /usr/include/i386-linux-gnu/qt5 -isystem /usr/include/i386-linux-gnu/qt5/QtPrintSupport -isystem /usr/include/i386-linux-gnu/qt5/QtWidgets -isystem /usr/include/i386-linux-gnu/qt5/QtGui -isystem /usr/include/i386-linux-gnu/qt5/QtNetwork -isystem /usr/include/i386-linux-gnu/qt5/QtDBus -isystem /usr/include/i386-linux-gnu/qt5/QtCore -Ibuild -Ibuild -I/usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -o build/backtrace.o src/tor/backtrace.c
Assembler messages:
Fatal error: can't create build/backtrace.o: Permission denied
In file included from src/tor/orconfig.h:13:0,
                 from src/tor/backtrace.c:16:
src/tor/backtrace.c: In function 'clean_backtrace':
Makefile:6195: recipe for target 'build/backtrace.o' failed
src/tor/orconfig_linux.h:578:44: error: 'REG_RIP' undeclared (first use in this function)
 #define PC_FROM_UCONTEXT uc_mcontext.gregs[REG_RIP]
                                            ^
src/tor/backtrace.c:88:27: note: in expansion of macro 'PC_FROM_UCONTEXT'
   stack[n] = (void*) ctx->PC_FROM_UCONTEXT;
                           ^
src/tor/orconfig_linux.h:578:44: note: each undeclared identifier is reported only once for each function it appears in
 #define PC_FROM_UCONTEXT uc_mcontext.gregs[REG_RIP]
                                            ^
src/tor/backtrace.c:88:27: note: in expansion of macro 'PC_FROM_UCONTEXT'
   stack[n] = (void*) ctx->PC_FROM_UCONTEXT;
                           ^
make: *** [build/backtrace.o] Error 2
11:55:56: The process "/usr/bin/make" exited with code 2.
Error while building/deploying project denarius-qt (kit: Qt 5.5.1 in PATH (System))
When executing step "Make"
11:55:56: Elapsed time: 00:01.

 

Thanks and salute

[outlawgr]

26 days till DNR party begins !

[kingcarsen]

When compiling qt for ubuntu 16.04 I am having an error in the object 'build/backtrace.o'

To compile I'm simply doing

qmake denarius-qt.pro
make

Any ideas about the possible mistake?'

Thanks and salute

You need libevent-dev installed now due to Tor integration:

Code:

sudo apt-get install libevent-dev

Installed and tried to compile with both command line and QT creator. I always found this error:

11:55:55: Running steps for project denarius-qt...
11:55:55: Configuration unchanged, skipping qmake step.
11:55:55: Starting: "/usr/bin/make"
cd /home/hache/denarius/src/leveldb && CC=gcc CXX=g++ /usr/bin/make OPT="-pipe -fpermissive -fstack-protector-all --param ssp-buffer-size=1 -O2" libleveldb.a libmemenv.a
make[1]: Entering directory '/home/hache/denarius/src/leveldb'
make[1]: 'libleveldb.a' is up to date.
make[1]: 'libmemenv.a' is up to date.
make[1]: Leaving directory '/home/hache/denarius/src/leveldb'
cd /home/hache/denarius; /bin/sh share/genbuild.sh /home/hache/denarius/build/build.h
gcc -c -pipe -std=c99 -O2 -D_REENTRANT -Wall -W -fPIC -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DQT_DISABLE_DEPRECATED_BEFORE=0 -DUSE_UPNP=1 -DSTATICLIB -DUSE_DBUS -DUSE_IPV6=1 -DUSE_LEVELDB -DHAVE_BUILD_INFO -DLINUX -DLINUX -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -Isrc -Isrc/json -Isrc/qt -Isrc/tor -Isrc/qt/plugins/mrichtexteditor -Isrc/leveldb/include -Isrc/leveldb/helpers -isystem /usr/include/i386-linux-gnu/qt5 -isystem /usr/include/i386-linux-gnu/qt5/QtPrintSupport -isystem /usr/include/i386-linux-gnu/qt5/QtWidgets -isystem /usr/include/i386-linux-gnu/qt5/QtGui -isystem /usr/include/i386-linux-gnu/qt5/QtNetwork -isystem /usr/include/i386-linux-gnu/qt5/QtDBus -isystem /usr/include/i386-linux-gnu/qt5/QtCore -Ibuild -Ibuild -I/usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -o build/backtrace.o src/tor/backtrace.c
Assembler messages:
Fatal error: can't create build/backtrace.o: Permission denied
In file included from src/tor/orconfig.h:13:0,
                 from src/tor/backtrace.c:16:
src/tor/backtrace.c: In function 'clean_backtrace':
Makefile:6195: recipe for target 'build/backtrace.o' failed
src/tor/orconfig_linux.h:578:44: error: 'REG_RIP' undeclared (first use in this function)
 #define PC_FROM_UCONTEXT uc_mcontext.gregs[REG_RIP]
                                            ^
src/tor/backtrace.c:88:27: note: in expansion of macro 'PC_FROM_UCONTEXT'
   stack[n] = (void*) ctx->PC_FROM_UCONTEXT;
                           ^
src/tor/orconfig_linux.h:578:44: note: each undeclared identifier is reported only once for each function it appears in
 #define PC_FROM_UCONTEXT uc_mcontext.gregs[REG_RIP]
                                            ^
src/tor/backtrace.c:88:27: note: in expansion of macro 'PC_FROM_UCONTEXT'
   stack[n] = (void*) ctx->PC_FROM_UCONTEXT;
                           ^
make: *** [build/backtrace.o] Error 2
11:55:56: The process "/usr/bin/make" exited with code 2.
Error while building/deploying project denarius-qt (kit: Qt 5.5.1 in PATH (System))
When executing step "Make"
11:55:56: Elapsed time: 00:01.

 

Thanks and salute

Try changing in the denarius-qt.pro file the line that has QMAKE_CFLAGS from -std=c99 to -std=gnu99

[vella85]

Is DNR close to getting added to Ledger Nano S? I just saw their recent additions and I don't know most of them lol so how are these cryptocurrencies getting listed even though they haven't be around a long time like DNR and even ADA? I see a lot of people complaining about not adding ADA which is understandable as it is a top 10 coin. Has there been any word on DNR being added anytime soon?