Pages:
Author

Topic: [ANN] Denarius [D] - First "Tribus" PoW/PoS Hybrid Masternodes, Ring Sigs - page 56. (Read 504255 times)

member
Activity: 135
Merit: 10
when I run masternode list-conf in the wallet I get no output even though my masternode.conf file has the correct data and is in the correct folder, how do I trouble shoot this?

Wallet is synced and I have restarted it a few times, it's unlocked...

You want to run the command "masternode outputs" to get your masternode outputs, the list-conf command just displays what is in your .conf file, so it may be empty then. You run masternode outputs after you send the TX including the 5,000 DNR. The masternode needs a valid vin (TX) to operate.

I have already done masternode outputs and created the masternode.conf file.

My problem is even through the conf file has the data in it, when i run list-conf its empty in the console...

It just returns



{
}
sr. member
Activity: 1148
Merit: 417
when I run masternode list-conf in the wallet I get no output even though my masternode.conf file has the correct data and is in the correct folder, how do I trouble shoot this?

Wallet is synced and I have restarted it a few times, it's unlocked...

You want to run the command "masternode outputs" to get your masternode outputs, the list-conf command just displays what is in your .conf file, so it may be empty then. You run masternode outputs after you send the TX including the 5,000 DNR. The masternode needs a valid vin (TX) to operate.
member
Activity: 135
Merit: 10
when I run masternode list-conf in the wallet I get no output even though my masternode.conf file has the correct data and is in the correct folder, how do I trouble shoot this?

Wallet is synced and I have restarted it a few times, it's unlocked...
sr. member
Activity: 1148
Merit: 417
NOTICE to hashbag.cc users:

During the weekend of 2nd-4th March, hashbag.cc forked to the incorrect DNR chain. After restoring the correct chain, many miners were overpaid significantly based on work they'd done during the fork.

Unfortunately, this caused consistent errors in payments as the balances being paid were not available in the wallet, which flowed on to all payments since. After reconciling accounts, users were in significant negative balances (i.e. overpaid) which would have required several hours/days of mining to restore to zero and start earning payments again.

As a result, all user history has been purged. All accounts should have been paid at fairly for what they mined whilst on the correct chain. Please forgive the disruption. We will be continuing our 0% fee mining whilst we ensure the payments are correctly processing over the next couple of weeks.

If you require any support, please join our Discord at https://discord.gg/AvQ7Ryc.

sounds like the pool found a way to steal coins....best not to use hashbag.cc

how do I set up the options for zpool? anyone know?

I will stand up for hashbag.cc anyday of the week, everything enkayz is saying is 100% true and valid, he has been here since the beginning supporting DNR with commits to our github and with yiimp as well. He does always try to do things the right way, without reconciling balances to zero, tons of miners would be in a negative, meaning you would not get payments as fast and would basically be paying off coins for no reason. enkayz is more than likely doing this at his own loss even, when a pool goes off chain and people keep mining it, nothing you can really do for that lost time there.

well isnt a split chain the result of a 51% attack?

No.

Also official release of the BarterDEX with DNR support is out: https://github.com/KomodoPlatform/BarterDEX/releases/tag/0.8.10-r1-rc
member
Activity: 294
Merit: 12
NOTICE to hashbag.cc users:

During the weekend of 2nd-4th March, hashbag.cc forked to the incorrect DNR chain. After restoring the correct chain, many miners were overpaid significantly based on work they'd done during the fork.

Unfortunately, this caused consistent errors in payments as the balances being paid were not available in the wallet, which flowed on to all payments since. After reconciling accounts, users were in significant negative balances (i.e. overpaid) which would have required several hours/days of mining to restore to zero and start earning payments again.

As a result, all user history has been purged. All accounts should have been paid at fairly for what they mined whilst on the correct chain. Please forgive the disruption. We will be continuing our 0% fee mining whilst we ensure the payments are correctly processing over the next couple of weeks.

If you require any support, please join our Discord at https://discord.gg/AvQ7Ryc.

sounds like the pool found a way to steal coins....best not to use hashbag.cc

how do I set up the options for zpool? anyone know?

I will stand up for hashbag.cc anyday of the week, everything enkayz is saying is 100% true and valid, he has been here since the beginning supporting DNR with commits to our github and with yiimp as well. He does always try to do things the right way, without reconciling balances to zero, tons of miners would be in a negative, meaning you would not get payments as fast and would basically be paying off coins for no reason. enkayz is more than likely doing this at his own loss even, when a pool goes off chain and people keep mining it, nothing you can really do for that lost time there.

well isnt a split chain the result of a 51% attack?
full member
Activity: 539
Merit: 105
IDENA.IO - Proof-Of-Person Blockchain
Hey guys, when i go compile the masternode daemon i'm running into a problem...

make -f makefile.unix  

 

I get this:

 

/bin/sh ../share/genbuild.sh obj/build.h

g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wno-format -Wno-unused-parameter -Wno-literal-suffix -g -DBOOST_SPIRIT_THREADSAFE -I/home/dnrmn1/denarius/src -I/home/dnrmn1/denarius/src/obj -I/home/dnrmn1/denarius/src/json -DIS_ARCH_64 -DUSE_UPNP=1 -I/home/dnrmn1/denarius/src/leveldb/include -DUSE_LEVELDB -I/home/dnrmn1/denarius/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/db.d -o obj/db.o db.cpp

In file included from db.cpp:6:0:

db.h:14:20: fatal error: db_cxx.h: No such file or directory

compilation terminated.

makefile.unix:203: recipe for target 'obj/db.o' failed

make: *** [obj/db.o] Error 1

Any thoughts?

Seems your missing some of the deps.

Run this again:
Code:
sudo apt-get install git build-essential libboost-all-dev libqrencode-dev libminiupnpc-dev libssl-dev libdb++-dev

No ur panties are missing from butt. U hacked the pentagon server and uncovered the shoking truth about jerusalem mission. U thought I did not know what u were up to? I wonder why u dont remember how I promised to beat u up if u ever come back to this thread.




Huh

Looked like you mistaken l337 developer with someone else. Carsenk might have even uncovered the truth about alien on Mars.

Instead of talking panties and Pentagon due to post rage🙏 .. same as road rage😉.. any real reasons to substantiate  anger
full member
Activity: 282
Merit: 100
Hey guys, when i go compile the masternode daemon i'm running into a problem...

make -f makefile.unix   

 

I get this:

 

/bin/sh ../share/genbuild.sh obj/build.h

g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wno-format -Wno-unused-parameter -Wno-literal-suffix -g -DBOOST_SPIRIT_THREADSAFE -I/home/dnrmn1/denarius/src -I/home/dnrmn1/denarius/src/obj -I/home/dnrmn1/denarius/src/json -DIS_ARCH_64 -DUSE_UPNP=1 -I/home/dnrmn1/denarius/src/leveldb/include -DUSE_LEVELDB -I/home/dnrmn1/denarius/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/db.d -o obj/db.o db.cpp

In file included from db.cpp:6:0:

db.h:14:20: fatal error: db_cxx.h: No such file or directory

compilation terminated.

makefile.unix:203: recipe for target 'obj/db.o' failed

make: *** [obj/db.o] Error 1

Any thoughts?

Seems your missing some of the deps.

Run this again:
Code:
sudo apt-get install git build-essential libboost-all-dev libqrencode-dev libminiupnpc-dev libssl-dev libdb++-dev

No ur panties are missing from butt. U hacked the pentagon server and uncovered the shoking truth about jerusalem mission. U thought I did not know what u were up to? I wonder why u dont remember how I promised to beat u up if u ever come back to this thread.




Huh

Looked like you mistaken l337 developer with someone else. Carsenk might have even uncovered the truth about alien on Mars.
hero member
Activity: 2147
Merit: 518
Hey guys, when i go compile the masternode daemon i'm running into a problem...

make -f makefile.unix   

 

I get this:

 

/bin/sh ../share/genbuild.sh obj/build.h

g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wno-format -Wno-unused-parameter -Wno-literal-suffix -g -DBOOST_SPIRIT_THREADSAFE -I/home/dnrmn1/denarius/src -I/home/dnrmn1/denarius/src/obj -I/home/dnrmn1/denarius/src/json -DIS_ARCH_64 -DUSE_UPNP=1 -I/home/dnrmn1/denarius/src/leveldb/include -DUSE_LEVELDB -I/home/dnrmn1/denarius/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/db.d -o obj/db.o db.cpp

In file included from db.cpp:6:0:

db.h:14:20: fatal error: db_cxx.h: No such file or directory

compilation terminated.

makefile.unix:203: recipe for target 'obj/db.o' failed

make: *** [obj/db.o] Error 1

Any thoughts?

Seems your missing some of the deps.

Run this again:
Code:
sudo apt-get install git build-essential libboost-all-dev libqrencode-dev libminiupnpc-dev libssl-dev libdb++-dev

No ur panties are missing from butt. U hacked the pentagon server and uncovered the shoking truth about jerusalem mission. U thought I did not know what u were up to? I wonder why u dont remember how I promised to beat u up if u ever come back to this thread.


member
Activity: 75
Merit: 10
I am new to crypto currencys and I started with Denarius. I am positive that it will grow and have trust in it. Thanks to all who contribute to it's development.  Cheesy
sr. member
Activity: 1148
Merit: 417
Hey guys, when i go compile the masternode daemon i'm running into a problem...

make -f makefile.unix   

 

I get this:

 

/bin/sh ../share/genbuild.sh obj/build.h

g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wno-format -Wno-unused-parameter -Wno-literal-suffix -g -DBOOST_SPIRIT_THREADSAFE -I/home/dnrmn1/denarius/src -I/home/dnrmn1/denarius/src/obj -I/home/dnrmn1/denarius/src/json -DIS_ARCH_64 -DUSE_UPNP=1 -I/home/dnrmn1/denarius/src/leveldb/include -DUSE_LEVELDB -I/home/dnrmn1/denarius/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/db.d -o obj/db.o db.cpp

In file included from db.cpp:6:0:

db.h:14:20: fatal error: db_cxx.h: No such file or directory

compilation terminated.

makefile.unix:203: recipe for target 'obj/db.o' failed

make: *** [obj/db.o] Error 1

Any thoughts?

Seems your missing some of the deps.

Run this again:
Code:
sudo apt-get install git build-essential libboost-all-dev libqrencode-dev libminiupnpc-dev libssl-dev libdb++-dev
member
Activity: 135
Merit: 10
Hey guys, when i go compile the masternode daemon i'm running into a problem...

make -f makefile.unix   

 

I get this:

 

/bin/sh ../share/genbuild.sh obj/build.h

g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wno-format -Wno-unused-parameter -Wno-literal-suffix -g -DBOOST_SPIRIT_THREADSAFE -I/home/dnrmn1/denarius/src -I/home/dnrmn1/denarius/src/obj -I/home/dnrmn1/denarius/src/json -DIS_ARCH_64 -DUSE_UPNP=1 -I/home/dnrmn1/denarius/src/leveldb/include -DUSE_LEVELDB -I/home/dnrmn1/denarius/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/db.d -o obj/db.o db.cpp

In file included from db.cpp:6:0:

db.h:14:20: fatal error: db_cxx.h: No such file or directory

compilation terminated.

makefile.unix:203: recipe for target 'obj/db.o' failed

make: *** [obj/db.o] Error 1

Any thoughts?
sr. member
Activity: 1148
Merit: 417
@everyone Just a little update  Cool Cool Cool Cool Cool Cool Cool Cool
https://denarius.host/ and https://denariustalk.org/ are both now on Cloudflare, so they should run and load much faster, no matter your location. Added DNR to Ledger (put up PR), added DNR to the Agama wallet (PR is up, waiting on confirm etc.), added DNR to the BarterDEX as both native and electrum modes for atomic swaps (unofficial binaries are available), Updated DNR to v2.0.2.0 (Win 64bit Binary Available, macOS now available (includes atomic swap support, hybrid masternodes, and PoS fix, and Cryptopia trading api), added DNR to BIP39 github (PR is up and unofficial fork) for seed phrase support for DNR wallets.

Get Denarius v2.0.2.0 here: https://github.com/carsenk/denarius/releases/tag/v2.0.2.0
Get Unofficial BarterDEX with DNR Support here: https://github.com/carsenk/BarterDEX/releases/tag/0.8.9-rc
Ledger PR Link: https://github.com/LedgerHQ/ledger-wallet-chrome/pull/91
Denarius BIP39 Tool: https://github.com/carsenk/bip39


https://denariustalk.org/index.php?/topic/159-denarius-v2020/
full member
Activity: 298
Merit: 100
hashbag.cc
NOTICE to hashbag.cc users:

During the weekend of 2nd-4th March, hashbag.cc forked to the incorrect DNR chain. After restoring the correct chain, many miners were overpaid significantly based on work they'd done during the fork.

Unfortunately, this caused consistent errors in payments as the balances being paid were not available in the wallet, which flowed on to all payments since. After reconciling accounts, users were in significant negative balances (i.e. overpaid) which would have required several hours/days of mining to restore to zero and start earning payments again.

As a result, all user history has been purged. All accounts should have been paid at fairly for what they mined whilst on the correct chain. Please forgive the disruption. We will be continuing our 0% fee mining whilst we ensure the payments are correctly processing over the next couple of weeks.

If you require any support, please join our Discord at https://discord.gg/AvQ7Ryc.

sounds like the pool found a way to steal coins....best not to use hashbag.cc

how do I set up the options for zpool? anyone know?

I will stand up for hashbag.cc anyday of the week, everything enkayz is saying is 100% true and valid, he has been here since the beginning supporting DNR with commits to our github and with yiimp as well. He does always try to do things the right way, without reconciling balances to zero, tons of miners would be in a negative, meaning you would not get payments as fast and would basically be paying off coins for no reason. enkayz is more than likely doing this at his own loss even, when a pool goes off chain and people keep mining it, nothing you can really do for that lost time there.

Thanks for the vote of confidence, Carsen.

I'm not here to rip anyone off, I'm still investigating what's gone on with the payments in the background with a view to at least pay out any transactions that were correct. At this stage it looks like the larger miners took the big chunks of overpayments, leaving a lot of smaller miners short of balances to pay with. Probably why I'm only fielding support requests for missing payments which are under 1 DNR.

In total people may have lost a couple of DNR each over the last 4 days of attempting to fix the imbalances (also note I have a full time job outside of crypto and basically the fork was noticed 2 hours before I had to leave home to work for two consecutive nights, I'm lucky I even had time to catch it).

As it stands now, everyone's getting paid properly again which is the most important part - I basically had enough of letting the non-payment issues occur because they were affecting far more miners than the over-payment (the larger miners are paid first, so the smallest of the miners are the ones who were missing out).

In future if the chain forks again, I'm simply going to shut the mining down until it can be properly fixed - it takes a bit of manual reconciliation efforts, so the more blocks end up erroneously mined, the worse the problem is.

And my Discord is now active, so if you ever have any problems, come hit me up and I will check it out. I've got a couple of helpers in there to raise me from the dead if there's a real problem going on too - that's just the kind of community we have here! Smiley
sr. member
Activity: 1148
Merit: 417
NOTICE to hashbag.cc users:

During the weekend of 2nd-4th March, hashbag.cc forked to the incorrect DNR chain. After restoring the correct chain, many miners were overpaid significantly based on work they'd done during the fork.

Unfortunately, this caused consistent errors in payments as the balances being paid were not available in the wallet, which flowed on to all payments since. After reconciling accounts, users were in significant negative balances (i.e. overpaid) which would have required several hours/days of mining to restore to zero and start earning payments again.

As a result, all user history has been purged. All accounts should have been paid at fairly for what they mined whilst on the correct chain. Please forgive the disruption. We will be continuing our 0% fee mining whilst we ensure the payments are correctly processing over the next couple of weeks.

If you require any support, please join our Discord at https://discord.gg/AvQ7Ryc.

sounds like the pool found a way to steal coins....best not to use hashbag.cc

how do I set up the options for zpool? anyone know?

I will stand up for hashbag.cc anyday of the week, everything enkayz is saying is 100% true and valid, he has been here since the beginning supporting DNR with commits to our github and with yiimp as well. He does always try to do things the right way, without reconciling balances to zero, tons of miners would be in a negative, meaning you would not get payments as fast and would basically be paying off coins for no reason. enkayz is more than likely doing this at his own loss even, when a pool goes off chain and people keep mining it, nothing you can really do for that lost time there.
member
Activity: 294
Merit: 12
NOTICE to hashbag.cc users:

During the weekend of 2nd-4th March, hashbag.cc forked to the incorrect DNR chain. After restoring the correct chain, many miners were overpaid significantly based on work they'd done during the fork.

Unfortunately, this caused consistent errors in payments as the balances being paid were not available in the wallet, which flowed on to all payments since. After reconciling accounts, users were in significant negative balances (i.e. overpaid) which would have required several hours/days of mining to restore to zero and start earning payments again.

As a result, all user history has been purged. All accounts should have been paid at fairly for what they mined whilst on the correct chain. Please forgive the disruption. We will be continuing our 0% fee mining whilst we ensure the payments are correctly processing over the next couple of weeks.

If you require any support, please join our Discord at https://discord.gg/AvQ7Ryc.

sounds like the pool found a way to steal coins....best not to use hashbag.cc

how do I set up the options for zpool? anyone know?
full member
Activity: 298
Merit: 100
hashbag.cc
NOTICE to hashbag.cc users:

During the weekend of 2nd-4th March, hashbag.cc forked to the incorrect DNR chain. After restoring the correct chain, many miners were overpaid significantly based on work they'd done during the fork.

Unfortunately, this caused consistent errors in payments as the balances being paid were not available in the wallet, which flowed on to all payments since. After reconciling accounts, users were in significant negative balances (i.e. overpaid) which would have required several hours/days of mining to restore to zero and start earning payments again.

As a result, all user history has been purged. All accounts should have been paid at fairly for what they mined whilst on the correct chain. Please forgive the disruption. We will be continuing our 0% fee mining whilst we ensure the payments are correctly processing over the next couple of weeks.

If you require any support, please join our Discord at https://discord.gg/AvQ7Ryc.

There are probably other miners that weren't paid at all - my case. But, with user history deleted, pretty hard to prove something. Good luck guys, I'll move to another pool.

Sorry to see you go, I am not happy about clearing the history either, trust me, it's why there's been so many issues for the last 4 days as I have struggled to balance it all out without wiping the history but the amount of people abusing me about the erratic payment schedules was getting a bit much. I do have everything backed up and plan to try and figure out any outstanding legitimate payment balances and process a payment once I get it figured out. If you let me know the address you were mining to, I can pull up the account and see what went wrong.
sr. member
Activity: 1148
Merit: 417
CMC Updated our Market Listings to include the BarterDEX (They do only show KMD pairings currently there) https://coinmarketcap.com/currencies/denarius-dnr/

For actual DEX Stats you can view https://dexstats.info or https://denarius.host
full member
Activity: 616
Merit: 100
NOTICE to hashbag.cc users:

During the weekend of 2nd-4th March, hashbag.cc forked to the incorrect DNR chain. After restoring the correct chain, many miners were overpaid significantly based on work they'd done during the fork.

Unfortunately, this caused consistent errors in payments as the balances being paid were not available in the wallet, which flowed on to all payments since. After reconciling accounts, users were in significant negative balances (i.e. overpaid) which would have required several hours/days of mining to restore to zero and start earning payments again.

As a result, all user history has been purged. All accounts should have been paid at fairly for what they mined whilst on the correct chain. Please forgive the disruption. We will be continuing our 0% fee mining whilst we ensure the payments are correctly processing over the next couple of weeks.

If you require any support, please join our Discord at https://discord.gg/AvQ7Ryc.

There are probably other miners that weren't paid at all - my case. But, with user history deleted, pretty hard to prove something. Good luck guys, I'll move to another pool.
full member
Activity: 298
Merit: 100
hashbag.cc
NOTICE to hashbag.cc users:

During the weekend of 2nd-4th March, hashbag.cc forked to the incorrect DNR chain. After restoring the correct chain, many miners were overpaid significantly based on work they'd done during the fork.

Unfortunately, this caused consistent errors in payments as the balances being paid were not available in the wallet, which flowed on to all payments since. After reconciling accounts, users were in significant negative balances (i.e. overpaid) which would have required several hours/days of mining to restore to zero and start earning payments again.

As a result, all user history has been purged. All accounts should have been paid at fairly for what they mined whilst on the correct chain. Please forgive the disruption. We will be continuing our 0% fee mining whilst we ensure the payments are correctly processing over the next couple of weeks.

If you require any support, please join our Discord at https://discord.gg/AvQ7Ryc.
sr. member
Activity: 1148
Merit: 417
Please add CryptoHub to exchange list

https://cryptohub.online/market/DNR/

Will do!

I got this message from VPS after start masternode with 'Status=9'

    "notCapableReason" : "Unknown. Check debug.log for more information.\n"

Is this OK?

Yes, status 9 is what you are mainly looking for, if you see your masternode listed for a few hours on https://denarius.host you will know it is online. Payments won't start till block 645k.

when will this coin be listed on a trusted exchange?

cryptopia is no longer a trusted exchange and any coin that has 90% of its volume only at cryptopia makes it look suspect

Cryptopia is still trusted, not sure where you are making this up from heh.

They have recently fixed deposits/withdrawals and they should be going through a lot faster now. They are still lagging behind on some support tickets, but they are filtering through them it seems, only a few users report not receiving a few withdrawals.

We also now have the BarterDEX, just updated the binaries to include electrum mode support for Denarius, so you no longer need a local chain installed to start atomic swapping! (We are already at 13 total atomic swaps that have been made now: https://denarius.host )

Utilizing the BarterDEX is probably our best new method of trading DNR. It requires no 3rd party and you are in control of your funds/trades. The fees are also very very minimal (Generally like 0.01% compared to Cryptopia's 0.2% per trade)

Latest Unofficial BarterDEX Binaries for all OS Platforms: https://github.com/carsenk/BarterDEX/releases/tag/0.8.9-rc
(Includes DNR support and DNR electrum mode support)

Do I need to download a program to use barterdex?

Yes, you download the BarterDEX itself (GUI version) https://github.com/carsenk/BarterDEX/releases/tag/0.8.9-rc all of the different binaries for different platforms are listed there, Linux, Windows, and macOS (Darwin).

KomodoPlatform/BarterDEX do also have a roadmap for improving the GUI/apps over time including an eventual mobile DEX.
Pages:
Jump to: