Will the new wallet offer in wallet solo/pool mining?
Could we make it to choose on first install startup where to put the blockchain as I can never find it. Especially with a problem like having to redownload the blockchain........
Topic: Nexus - Pure SHA3 + CPU/GPU + nPoS + 15 Active Innovations + More to Come - page 88. (Read 785531 times)
March 08, 2017, 06:42:34 PM
March 08, 2017, 04:15:44 PM
Just restart the wallet. 2.0.5 is only good for staking really.. Not for solo mining.
LLD is good for mining no wallet lag or wait for v3.0 wich will arrive any day now in Beta
LLD is good for mining no wallet lag or wait for v3.0 wich will arrive any day now in Beta
March 08, 2017, 01:11:58 PM
I redownloaded the blockchain from scratch several times to fix it, good luck.
Now I can't solo mine, keeps saying: failed to connect to llp serever.
Now I can't solo mine, keeps saying: failed to connect to llp serever.
If you get this message, it's probably because your wallet isn't unlocked for minting.
You need to upload nexus.conf file to your AppData/Roaming/Nexus folder.
Code:
llpallowip=127.0.0.1:9325
unified=1
mining=1
March 08, 2017, 09:00:49 AM
Anyone else having problems syncing the official wallet? 
I'm running 2.0.5 and everything has been fine for more than a month, however for the last three or more days it has been stuck unable to update.
I have two connections apparently, however I never download any blocks after 1231461.
Tried restarting a few times, no luck.
EDIT:
Running getpeerinfo in the client results in this:
I'm running 2.0.5 and everything has been fine for more than a month, however for the last three or more days it has been stuck unable to update.
I have two connections apparently, however I never download any blocks after 1231461.
Tried restarting a few times, no luck.
EDIT:
Running getpeerinfo in the client results in this:
Code:
[
{
"addr" : "96.43.131.82:9323",
"services" : "00000001",
"lastsend" : 1488968959,
"lastrecv" : 1488968960,
"conntime" : 1488968883,
"version" : 10100,
"subver" : "Nexus[v0.2.1.0 - LLD Beta]/ DB [0.1.1] PROTOCOL [v0.1.1]",
"inbound" : false,
"releasetime" : 0,
"height" : 1238346,
"banscore" : 0
},
{
"addr" : "136.243.14.170:9323",
"services" : "00000001",
"lastsend" : 1488969739,
"lastrecv" : 1488969739,
"conntime" : 1488969738,
"version" : 10100,
"subver" : "Nexus[v0.2.2.3 - LLD Stable]/ DB [0.1.1] PROTOCOL [v0.1.1]",
"inbound" : false,
"releasetime" : 0,
"height" : 1231461,
"banscore" : 0
}
]
I redownloaded the blockchain from scratch several times to fix it, good luck.
Now I can't solo mine, keeps saying: failed to connect to llp serever.
March 08, 2017, 03:31:57 AM
Anyone else having problems syncing the official wallet?
I'm running 2.0.5 and everything has been fine for more than a month, however for the last three or more days it has been stuck unable to update.
I have two connections apparently, however I never download any blocks after 1231461.
Tried restarting a few times, no luck.
EDIT:
Running getpeerinfo in the client results in this:
I'm running 2.0.5 and everything has been fine for more than a month, however for the last three or more days it has been stuck unable to update.
I have two connections apparently, however I never download any blocks after 1231461.
Tried restarting a few times, no luck.
EDIT:
Running getpeerinfo in the client results in this:
Code:
[
{
"addr" : "96.43.131.82:9323",
"services" : "00000001",
"lastsend" : 1488968959,
"lastrecv" : 1488968960,
"conntime" : 1488968883,
"version" : 10100,
"subver" : "Nexus[v0.2.1.0 - LLD Beta]/ DB [0.1.1] PROTOCOL [v0.1.1]",
"inbound" : false,
"releasetime" : 0,
"height" : 1238346,
"banscore" : 0
},
{
"addr" : "136.243.14.170:9323",
"services" : "00000001",
"lastsend" : 1488969739,
"lastrecv" : 1488969739,
"conntime" : 1488969738,
"version" : 10100,
"subver" : "Nexus[v0.2.2.3 - LLD Stable]/ DB [0.1.1] PROTOCOL [v0.1.1]",
"inbound" : false,
"releasetime" : 0,
"height" : 1231461,
"banscore" : 0
}
]
March 07, 2017, 11:38:20 PM
just in response to the error encountered with the compile ...
this is the end part of the compile and as such is not the full output - but you will get the idea ...
im trying to clone from the specific version ( which uses bdb ) but cannot seem to do so ...
any one have an actual parameter i can use to do so? ... would be a great help ...
tanx ...
#crysx
this is the end part of the compile and as such is not the full output - but you will get the idea ...
Code:
src/wallet/../LLD/key.h:135:3: warning: when initialized here [-Wreorder]
KeyDatabase(std::string strBaseLocationIn, std::string strDatabaseNameIn) : strDatabaseName(strDatabaseNameIn), strBaseLocation(strBaseLocationIn) { strLocation = strBaseLocation + strDatabaseName + ".keys"; }
^
In file included from src/wallet/../LLD/sector.h:5:0,
from src/wallet/../LLD/index.h:4,
from src/wallet/db.cpp:16:
src/wallet/../LLD/transaction.h: In member function ‘uint512 LLD::SectorTransaction::GetHash()’:
src/wallet/../LLD/transaction.h:99:9: warning: no return statement in function returning non-void [-Wreturn-type]
}
^
In file included from src/wallet/../LLD/index.h:4:0,
from src/wallet/db.cpp:16:
src/wallet/../LLD/sector.h: At global scope:
src/wallet/../LLD/sector.h:66:20: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
bool fReadOnly = false;
^
src/wallet/db.cpp: In member function ‘bool Wallet::CTimeDB::WriteTimeData(int)’:
src/wallet/db.cpp:351:2: warning: control reaches end of non-void function [-Wreturn-type]
}
^
src/wallet/db.cpp: In member function ‘bool Wallet::CTxDB::MigrateToLLD()’:
src/wallet/db.cpp:692:2: warning: control reaches end of non-void function [-Wreturn-type]
}
^
In file included from /home/common/cwi-build/deps/include/boost/asio/detail/impl/posix_event.ipp:24:0,
from /home/common/cwi-build/deps/include/boost/asio/detail/posix_event.hpp:95,
from /home/common/cwi-build/deps/include/boost/asio/detail/event.hpp:25,
from /home/common/cwi-build/deps/include/boost/asio/detail/task_io_service_thread_info.hpp:18,
from /home/common/cwi-build/deps/include/boost/asio/impl/handler_alloc_hook.ipp:26,
from /home/common/cwi-build/deps/include/boost/asio/handler_alloc_hook.hpp:80,
from /home/common/cwi-build/deps/include/boost/asio/detail/handler_alloc_helpers.hpp:21,
from /home/common/cwi-build/deps/include/boost/asio/detail/bind_handler.hpp:19,
from /home/common/cwi-build/deps/include/boost/asio/detail/wrapped_handler.hpp:18,
from /home/common/cwi-build/deps/include/boost/asio/io_service.hpp:24,
from /home/common/cwi-build/deps/include/boost/asio/basic_io_object.hpp:19,
from /home/common/cwi-build/deps/include/boost/asio/basic_socket.hpp:20,
from /home/common/cwi-build/deps/include/boost/asio/basic_datagram_socket.hpp:20,
from /home/common/cwi-build/deps/include/boost/asio.hpp:21,
from src/wallet/../core/../util/../util/util.h:30,
from src/wallet/../core/../util/bignum.h:16,
from src/wallet/../core/core.h:12,
from src/wallet/db.h:12,
from src/wallet/db.cpp:9:
/home/common/cwi-build/deps/include/boost/asio/error.hpp: At global scope:
/home/common/cwi-build/deps/include/boost/asio/error.hpp:252:45: warning: ‘boost::asio::error::system_category’ defined but not used [-Wunused-variable]
static const boost::system::error_category& system_category
^
/home/common/cwi-build/deps/include/boost/asio/error.hpp:254:45: warning: ‘boost::asio::error::netdb_category’ defined but not used [-Wunused-variable]
static const boost::system::error_category& netdb_category
^
/home/common/cwi-build/deps/include/boost/asio/error.hpp:256:45: warning: ‘boost::asio::error::addrinfo_category’ defined but not used [-Wunused-variable]
static const boost::system::error_category& addrinfo_category
^
/home/common/cwi-build/deps/include/boost/asio/error.hpp:258:45: warning: ‘boost::asio::error::misc_category’ defined but not used [-Wunused-variable]
static const boost::system::error_category& misc_category
^
In file included from /home/common/cwi-build/deps/include/boost/system/system_error.hpp:14:0,
from /home/common/cwi-build/deps/include/boost/thread/exceptions.hpp:22,
from /home/common/cwi-build/deps/include/boost/thread/pthread/thread_data.hpp:10,
from /home/common/cwi-build/deps/include/boost/thread/thread_only.hpp:17,
from /home/common/cwi-build/deps/include/boost/thread/thread.hpp:12,
from /home/common/cwi-build/deps/include/boost/thread.hpp:13,
from src/wallet/../core/../util/../util/util.h:26,
from src/wallet/../core/../util/bignum.h:16,
from src/wallet/../core/core.h:12,
from src/wallet/db.h:12,
from src/wallet/db.cpp:9:
/home/common/cwi-build/deps/include/boost/system/error_code.hpp:222:36: warning: ‘boost::system::posix_category’ defined but not used [-Wunused-variable]
static const error_category & posix_category = generic_category();
^
/home/common/cwi-build/deps/include/boost/system/error_code.hpp:223:36: warning: ‘boost::system::errno_ecat’ defined but not used [-Wunused-variable]
static const error_category & errno_ecat = generic_category();
^
/home/common/cwi-build/deps/include/boost/system/error_code.hpp:224:36: warning: ‘boost::system::native_ecat’ defined but not used [-Wunused-variable]
static const error_category & native_ecat = system_category();
^
make: *** [build/db.o] Error 1
DONE ...
im trying to clone from the specific version ( which uses bdb ) but cannot seem to do so ...
any one have an actual parameter i can use to do so? ... would be a great help ...
tanx ...
#crysx
March 07, 2017, 07:36:39 PM
I really like Monero in the sense that it is the closest we have today as digital cash, even more than Dash, but reading some info i'm starting to believe that proof of work is broken against big players (Pools), whoever they are if they have the money they can buy huge mining power and take more than 51% of any network. Proof of stake is fucked in the sense that whales are the ones that can make decisions and voting on the blockchain.
Good that Nexus is heavy on developing a Trust Network, because eventually the two POW mining channels are going to run out of reserves and only nPOS will support Nexus network, this new approach may finally put and end to this "take over" of crypto-currency just because i have the money or power to do so.
The tech on Monero is great but as it is only a POW coin it will be really sad to see that blockchain collapse because of this huge "Unknown" mining pool with such a mining power. I'll leave the article here for you guys to read and get to your own conclusions about POW Mining.
http://hubpages.com/technology/Monero-Attack-of-the-Dwarf
As a final question, in ten years time more or less when Nexus POW mining finish, will it be enough just with nPOS and Trust Network to protect Nexus from an external force with big power and resources?
Good that Nexus is heavy on developing a Trust Network, because eventually the two POW mining channels are going to run out of reserves and only nPOS will support Nexus network, this new approach may finally put and end to this "take over" of crypto-currency just because i have the money or power to do so.
The tech on Monero is great but as it is only a POW coin it will be really sad to see that blockchain collapse because of this huge "Unknown" mining pool with such a mining power. I'll leave the article here for you guys to read and get to your own conclusions about POW Mining.
http://hubpages.com/technology/Monero-Attack-of-the-Dwarf
As a final question, in ten years time more or less when Nexus POW mining finish, will it be enough just with nPOS and Trust Network to protect Nexus from an external force with big power and resources?
March 06, 2017, 07:49:57 PM
Post your compilation error please.
Viz.
Viz.
will do ...
at least the current error anyway ...
all the components ( boost - openssl - bdb ) are statically compiled first and then the daemon set to compile statically using the static components ... its the only way ( without dynamic compilation of EACH node we have - if we ever do a rollout ) to do this to simplify the rollout ...
i must be missing something here with the latest clone ( from git head / master ) ...
ill try the bdb clone / download and try a compile of that instead ... especially since the main purpose of this is to stake permanently ...
#crysx
March 06, 2017, 07:45:22 PM
Thanks,
I was staking with 2.2.2 for about 1 week and shut it down yesterday it
boots up and finds peer fast, but the blockchain is Frozen today. 5 Reboots
did not help.
I am much more comfortable using the pre-built Qt with 2.2.2 wallet.
I was staking with 2.2.2 for about 1 week and shut it down yesterday it
boots up and finds peer fast, but the blockchain is Frozen today. 5 Reboots
did not help.
I am much more comfortable using the pre-built Qt with 2.2.2 wallet.
Yea I'm myself stuck on block 1234065.
This is after a 48hr fresh download.
Please use version 2.0.5 for staking. Note you will need to download a new database bootstrap file also if you want to bootstrap.
https://github.com/Nexusoft/Nexus/releases/tag/0.2.0.5
http://nexusearth.com/bootstrap/Oracle-Database/recent.rar
o ok ...
thats something i didnt know ...
as most compiles of most coins use bdb - thats what i have been compiling with for clone of head on git ... silly me ...
ill try that instead ...
how can i clone ( or download through the script ) the direct 0.2.0.5 for compile? ... is there a direct link for git? ...
and just for clarity - does it NEED that bootstrap and only that bootstrap for it to work? ...
#crysx
March 06, 2017, 07:37:53 PM
So you giving finally giving this a shot crysx?
yup ...
i tried a long time ago ( when it was coinshield - i think ) but failed miserably ...
now cwi have a MUCH larger infrastructure and we can establish a bit of a testbed for coins - i would like to have a go at testing this coin ...
though there seems to be many issues - im working them out one by one ... most are centos 7 related - as its a rhel based system and ecc issues are abundant ( hence the script to compile a static binary for the node ) due to to redhats sheer legal redtape stubbornness - but most 'standard' coins compile nicely ... even the new bitcoin codebase ( dash - litecoin - and other coins included ) ...
i will post the error later today if i get the chance - but due to the various options ( and versions of components that are used ) - it will not be easy to determine what the error may be ...
btw - this will be done on the 'test' node only - so it will not be setup as seeds or nodes - unless the community / dev wants us ( cwi ) to help with the network sync / stability ... a deal can be cut then if that is the case ...
for now - its just me 'messing' with getting it compiled and testing staking ... too much work getting done elsewhere - and a LOT being done to get the new granite ( grn ) sorted for later this year including the cwi-website to tie all of this together ...
#crysx
March 06, 2017, 05:54:10 PM
Post your compilation error please.
Viz.
I'm not getting any error, the wallet just isn't updating after the block that I've mentioned. Viz.
March 06, 2017, 05:24:11 PM
Post your compilation error please.
Viz.
Viz.
March 06, 2017, 05:19:55 PM
Thanks,
I was staking with 2.2.2 for about 1 week and shut it down yesterday it
boots up and finds peer fast, but the blockchain is Frozen today. 5 Reboots
did not help.
I am much more comfortable using the pre-built Qt with 2.2.2 wallet.
I was staking with 2.2.2 for about 1 week and shut it down yesterday it
boots up and finds peer fast, but the blockchain is Frozen today. 5 Reboots
did not help.
I am much more comfortable using the pre-built Qt with 2.2.2 wallet.
Yea I'm myself stuck on block 1234065.
This is after a 48hr fresh download.
Please use version 2.0.5 for staking. Note you will need to download a new database bootstrap file also if you want to bootstrap.
https://github.com/Nexusoft/Nexus/releases/tag/0.2.0.5
http://nexusearth.com/bootstrap/Oracle-Database/recent.rar
March 06, 2017, 05:09:57 PM
hi all ...
can anyone help with the compilation of the wallet? ...
i just need a daemon not the qt wallet - as i want to install this on one of the nodes - under centos 7 x64 ...
the issue is the non-standard way of building the db via LLD ... i write / rewrite scripts to compile most of the coins we have on the nodes - but this one just seems completely impossible to build ... even when its in the last segment of compile - it dies with the db build error ...
there are NEVER instructions of how to build under rhel based systems - and im slowly changing that ... but this daemon has stumped me ...
can anyone give me pointers for the compile under centos 7 x64? ... im NOT a newbie - im just stumped and this is the only coin so far that refuses to compile ...
any help would be appreciated - as id like to test staking on daemon only on the vps ...
and before anyone says anything about ubuntu or debian based systems - the answer is no - we cant ... its a business / corporate decision ... it has to be rhel based centos 7 x64 specifically ... so its a good challenge for those that want one ... like me really - but im way over frustration with the compile ... its no longer a challenge for me - its a problem that needs to be fixed ...
so any help will be much appreciated ...
#crysx
can anyone help with the compilation of the wallet? ...
i just need a daemon not the qt wallet - as i want to install this on one of the nodes - under centos 7 x64 ...
the issue is the non-standard way of building the db via LLD ... i write / rewrite scripts to compile most of the coins we have on the nodes - but this one just seems completely impossible to build ... even when its in the last segment of compile - it dies with the db build error ...
there are NEVER instructions of how to build under rhel based systems - and im slowly changing that ... but this daemon has stumped me ...
can anyone give me pointers for the compile under centos 7 x64? ... im NOT a newbie - im just stumped and this is the only coin so far that refuses to compile ...
any help would be appreciated - as id like to test staking on daemon only on the vps ...
and before anyone says anything about ubuntu or debian based systems - the answer is no - we cant ... its a business / corporate decision ... it has to be rhel based centos 7 x64 specifically ... so its a good challenge for those that want one ... like me really - but im way over frustration with the compile ... its no longer a challenge for me - its a problem that needs to be fixed ...
so any help will be much appreciated ...
#crysx
Hi. Can you please post the error you are seeing when running the compile commands here?
p.s.
Note that 2.0.5 is the slightly older version that still uses Berkeley DB - if you are planning on staking it's recommend that you use that version. Are you able to compile that one?
March 06, 2017, 01:14:27 PM
Thanks,
I was staking with 2.2.2 for about 1 week and shut it down yesterday it
boots up and finds peer fast, but the blockchain is Frozen today. 5 Reboots
did not help.
I am much more comfortable using the pre-built Qt with 2.2.2 wallet.
I was staking with 2.2.2 for about 1 week and shut it down yesterday it
boots up and finds peer fast, but the blockchain is Frozen today. 5 Reboots
did not help.
I am much more comfortable using the pre-built Qt with 2.2.2 wallet.
Yea I'm myself stuck on block 1234065.
This is after a 48hr fresh download.
March 06, 2017, 11:35:39 AM
So you giving finally giving this a shot crysx?
March 06, 2017, 06:46:57 AM
hi all ...
can anyone help with the compilation of the wallet? ...
i just need a daemon not the qt wallet - as i want to install this on one of the nodes - under centos 7 x64 ...
the issue is the non-standard way of building the db via LLD ... i write / rewrite scripts to compile most of the coins we have on the nodes - but this one just seems completely impossible to build ... even when its in the last segment of compile - it dies with the db build error ...
there are NEVER instructions of how to build under rhel based systems - and im slowly changing that ... but this daemon has stumped me ...
can anyone give me pointers for the compile under centos 7 x64? ... im NOT a newbie - im just stumped and this is the only coin so far that refuses to compile ...
any help would be appreciated - as id like to test staking on daemon only on the vps ...
and before anyone says anything about ubuntu or debian based systems - the answer is no - we cant ... its a business / corporate decision ... it has to be rhel based centos 7 x64 specifically ... so its a good challenge for those that want one ... like me really - but im way over frustration with the compile ... its no longer a challenge for me - its a problem that needs to be fixed ...
so any help will be much appreciated ...
#crysx
can anyone help with the compilation of the wallet? ...
i just need a daemon not the qt wallet - as i want to install this on one of the nodes - under centos 7 x64 ...
the issue is the non-standard way of building the db via LLD ... i write / rewrite scripts to compile most of the coins we have on the nodes - but this one just seems completely impossible to build ... even when its in the last segment of compile - it dies with the db build error ...
there are NEVER instructions of how to build under rhel based systems - and im slowly changing that ... but this daemon has stumped me ...
can anyone give me pointers for the compile under centos 7 x64? ... im NOT a newbie - im just stumped and this is the only coin so far that refuses to compile ...
any help would be appreciated - as id like to test staking on daemon only on the vps ...
and before anyone says anything about ubuntu or debian based systems - the answer is no - we cant ... its a business / corporate decision ... it has to be rhel based centos 7 x64 specifically ... so its a good challenge for those that want one ... like me really - but im way over frustration with the compile ... its no longer a challenge for me - its a problem that needs to be fixed ...
so any help will be much appreciated ...
#crysx
March 05, 2017, 09:49:05 AM
Thanks,
I was staking with 2.2.2 for about 1 week and shut it down yesterday it
boots up and finds peer fast, but the blockchain is Frozen today. 5 Reboots
did not help.
I am much more comfortable using the pre-built Qt with 2.2.2 wallet.
I was staking with 2.2.2 for about 1 week and shut it down yesterday it
boots up and finds peer fast, but the blockchain is Frozen today. 5 Reboots
did not help.
I am much more comfortable using the pre-built Qt with 2.2.2 wallet.
March 04, 2017, 03:56:46 PM
Guys let me answer this one,
Depending on wich wallet you use.. The start up takes a long time.. The Orcle 2.0.5 takes verry long but is recommended wallet for staking.
The LLD 2.2.2 wallet is verry quick like 1 m startup.. But sometimes staking is glitched.
Now if u have this error ( not responding etc) maybe u should do a debug after starting the wallet then rescan the wallet.
Depending on wich wallet you use.. The start up takes a long time.. The Orcle 2.0.5 takes verry long but is recommended wallet for staking.
The LLD 2.2.2 wallet is verry quick like 1 m startup.. But sometimes staking is glitched.
Now if u have this error ( not responding etc) maybe u should do a debug after starting the wallet then rescan the wallet.
March 04, 2017, 03:21:29 PM
Hi everyone,
i have a Problem with the Nexus Wallet.
When i start the Windows Wallet (Nexus-QT.exe) its terminate with an error (nexus-qt.exe funtkioniert nicht mehr)
This problem I have since today
Has anybody the same problem?
My System:
Windows 10
16 GB Ram
Nexus Version: 0.2.0.5
Thx for help
Sorry for my bad English
i have a Problem with the Nexus Wallet.
When i start the Windows Wallet (Nexus-QT.exe) its terminate with an error (nexus-qt.exe funtkioniert nicht mehr)
This problem I have since today
Has anybody the same problem?
My System:
Windows 10
16 GB Ram
Nexus Version: 0.2.0.5
Thx for help
Sorry for my bad English
I have it also sometimes. I close and restart and dont do anything until the wallet is open. I think it is to heavy to start sometimes and take long time.
Jump to: