Blocks are just rolling in |
|
|
|
|
so many forks my qt couldnt figure out which one it wanted to follow. the joys of such low stake time
|
|
|
|
but the trouble at the start of the new wallet without chain stays
Use the updated links |
|
|
|
Wallet build on Linux (Mint) fails with the following error: /usr/bin/ld: unrecognized option '--large-address-aware'
/usr/bin/ld: use the --help option for usage information
collect2: error: ld returned 1 exit status
make: *** [NoirShares-Qt] Error 1
Was building this way (from the latest git): qmake-qt4 NoirShares-qt.pro
make Please advise. Delete this: !win32:!macx { QMAKE_LFLAGS *= -static QMAKE_LFLAGS *= -Wl,--large-address-aware } from NoirShares-qt.pro Updated Git with .pro file for linux qt. make sure you update your library locations or it may not build properly. |
|
|
|
Hi everybody.
I am new here. I like the proyect and I want to be part of it.
Yesterday I downloaded and installed the wallet but it does not work and I can not fix it.
When I open the wallet remains "Out of sync" and on the bottom right there are 2 computers with the red cross ("0 active connections").
I created the configuration file (NoirShares.conf) with this content:
upnp=1
DNSSEED=1
daemon=1
server=0
listen=1
testnet=0
maxconnections=100
4way=1
gen=0
genproclimit=2
rpcuser=
rpcpassword=
rpcconnect=127.0.0.1
rpcallowip=
port=8500
rpcport=8501
addnode=107.170.254.5
addnode= 41.78.77.178
addnode=192.241.213.244
addnode=172.245.183.30
addnode=162.243.131.88
addnode=54.213.71.178
addnode=192.241.213.224
addnode=54.80.61.11
addnode=198.199.96.129
addnode=54.197.175.238
addnode=["8.38.76.74:44523","37.187.129.122:8500","5.9.145.52:55704","5.9.158.79:8500","67.255.7.120:37366","79.98.25.220:47659","192.3.92.18:42572","193.219.47.35:43053","95.87.247.228:51427","72.182.4.161:8500","76.16.120.82:14571","129.24.128.122:56252","62.210.177.239:47720","178.162.192.197:57676","173.44.130.3:49777","123.30.243.63:8500","68.54.118.59:45224","70.30.179.48:19146","68.228.174.238:51539","108.174.146.78:33604","128.199.195.155:60369","109.165.172.31:14871","192.99.144.139:39837","86.144.99.19:8500","75.143.69.254:55901","74.67.28.40:50060","221.0.90.210:58240","80.130.210.223:39355","67.82.102.95:8500","60.182.36.3:45947","24.63.84.124:55432","93.35.237.86:63894","82.138.34.183:61709","123.12.118.211:8500","202.158.5.2:8500","176.227.196.146:54068","222.242.169.196:45040","140.249.12.192:5472","83.254.222.157:60441","218.87.165.133:60479"]
... but that did not fixed the problem.
The log file (Help / Debug window / Debug log file) says that there are "time out" problems:
NoirShares version v0.1.3.0-g99999-Barwizi (February 20, 2014)
Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
Startup time: 05/18/14 23:32:22
Default data directory C:\Users\ariel\AppData\Roaming\NoirShares
Used data directory C:\Users\ariel\Desktop\NoirShares QT\Data
dbenv.open LogDir=C:\Users\ariel\Desktop\NoirShares QT\Data\database ErrorFile=C:\Users\ariel\Desktop\NoirShares QT\Data\db.log
Bound to 0.0.0.0:8500
Loading block index...
LoadBlockIndex(): hashBestChain=0184ba6f36581ce17b44 height=0 trust=1 date=05/31/74 00:48:10
LoadBlockIndex(): synchronized checkpoint 0184ba6f36581ce17b443111bdae8f367616a293be73a2bf344d78cdc95c08a4
Verifying last 0 blocks at level 1
block index 3ms
Loading wallet...
nFileVersion = 1090100
wallet 443ms
Loading addresses...
Loaded 1 addresses from peers.dat 0ms
RandAddSeed() 176296 bytes
mapBlockIndex.size() = 1
nBestHeight = 0
setKeyPool.size() = 100
mapWallet.size() = 0
mapAddressBook.size() = 1
Done loading
refreshWallet
send version message: version 60006, blocks=0, us=0.0.0.0:0, them=0.0.0.0:0, peer=127.0.0.1:0
DNS seeding disabled
ThreadMapPort started
ThreadIRCSeed started
ThreadSocketHandler started
ThreadOpenAddedConnections started
trying connection 107.170.254.5:8500 lastseen=361237.8hrs
ipcThread started
ThreadOpenConnections started
ThreadMessageHandler started
ThreadStakeMinter started
Flushed 1 addresses to peers.dat 3ms
CPUMiner started for proof-of-stake
trying connection 217.157.9.88:8500 lastseen=227.0hrs
IRC :giraffe.heliacal.net NOTICE AUTH :*** Looking up your hostname...
IRC :giraffe.heliacal.net NOTICE AUTH :*** Couldn't look up your hostname
IRC SENDING: NICK x720952700
IRC SENDING: USER x720952700 8 * : x720952700
IRC :giraffe.heliacal.net 001 x720952700 :Welcome to the LFNet Internet Relay Chat Network x720952700
IRC :giraffe.heliacal.net 002 x720952700 :Your host is giraffe.heliacal.net[92.243.23.21/6667], running version hybrid-7.2.3
IRC :giraffe.heliacal.net 003 x720952700 :This server was created Dec 10 2013 at 18:22:54
IRC :giraffe.heliacal.net 004 x720952700 giraffe.heliacal.net hybrid-7.2.3 CDGabcdfgiklnorsuwxyz biklmnopstveI bkloveI
IRC SENDING: USERHOST x720952700
GetMyExternalIP() received [190.247.209.164] 190.247.209.164:0
GetMyExternalIP() returned 190.247.209.164
AddLocal(190.247.209.164:8500,5)
connection timeout
trying connection 41.78.77.178:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.0hrs
connection timeout
trying connection 192.241.213.244:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.0hrs
connection timeout
trying connection 172.245.183.30:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.0hrs
connection timeout
trying connection 162.243.131.88:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.0hrs
No valid UPnP IGDs found
connection timeout
trying connection 54.213.71.178:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.0hrs
connection timeout
trying connection 192.241.213.224:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.0hrs
connection timeout
trying connection 54.80.61.11:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.0hrs
connection timeout
trying connection 198.199.96.129:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.0hrs
connection timeout
trying connection 54.197.175.238:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.0hrs
connection timeout
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.0hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.0hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
Flushed 1 addresses to peers.dat 5ms
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
trying connection 107.170.254.5:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 41.78.77.178:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 192.241.213.244:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 172.245.183.30:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
connection timeout
trying connection 162.243.131.88:8500 lastseen=361237.8hrs
connection timeout
trying connection 217.157.9.88:8500 lastseen=227.1hrs
Flushed 1 addresses to peers.dat 4ms
connection timeout
...
...
...
...
I tried shutting down the antivirus and firewall, but nothing...
Any idea of what may be happening ?
Thanks.
use the build linked in the OP. your using an old version. delete everything but wallet.dat |
|
|
|
Wallet build on Linux (Mint) fails with the following error: /usr/bin/ld: unrecognized option '--large-address-aware'
/usr/bin/ld: use the --help option for usage information
collect2: error: ld returned 1 exit status
make: *** [NoirShares-Qt] Error 1
Was building this way (from the latest git): qmake-qt4 NoirShares-qt.pro
make Please advise. couple things. you will need to adjust the .pro for linux as it is currently setup for windows. you will need to adjust for your libraries to point at the correct locations. also your going to need to comment out a couple things as well that are specific to windows builds. |
|
|
|
Quick question on the stake. The OP says 3% stake but does anyone know what time period this is for? Daily? Weekly? Monthly? Annually?
Is there any way to determine how many POS shares have been minted to date vs. generated via proof of work?
3% stake with possibility of stake every 7-14 coindays |
|
|
|
UPDATE
Pre-ANN
As you may have noticed EBT has been under attack for the last few weeks. These attacks have been traced back to hashing spikes that are greatly disproportionate relative to the difficulty. In order to address these attacks the EBT Team has decided to end POW at the next halving. At block 400000 there will be 0 block rewards for POW blocks, effectively negating attacks. This will reduce the coin supply to an estimated: 157,648,686 total EBT down from the original 250,000,000 EBT originally slated for minting. Along with this change, the new QT will feature several improvements.
1. Coin Control
2. Cosmetic changes
3. Unlock button for POS minting located on the overview page
The EBT Team thanks all of you for your ongoing support. We look forward to the positive effect we believe these changes will have. As always we love to hear your feedback and appreciate your input. Keep your eyes on this thread as more big things are just around the corner. All we can say is that we have a new partner working on an exciting project.
I think that is a good decision Up and running with correct daemon 3.0.0.1 |
|
|
|
@sellbuy, If you're still digging EBT, it looks like it's arga's pool, you , and me  yup back up and running again :p Argakiig, I love your dark UI. Real easy on the eyes, and different. that was the point. I tend to work on pools late at night, so the dark is better for the eyes not as harsh but thank you |
|
|
|
@sellbuy, If you're still digging EBT, it looks like it's arga's pool, you , and me yup back up and running again :p |
|
|
|
I have some compiling issues latest git version $ make -f makefile.unix
g++ -c -O2 -msse2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -I/home/matthias/usr/mining/nrs/NRS/src -I/home/matthias/usr/mining/nrs/NRS/src/obj -DUSE_UPNP=0 -DUSE_IPV6=1 -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/alert.d -o obj/alert.o alert.cpp
alert.cpp:242:1: fatal error: opening dependency file obj/alert.d: No such file or directory
}
^
compilation terminated.
make: *** [obj/alert.o] Error 1
I have to do: then I get NoirSharesd compiled. But qt version I get not compilied: $ qmake NoirShares-qt.pro
$ make -j4
...
/usr/bin/ld: unrecognized option '--large-address-aware'
/usr/bin/ld: use the --help option for usage information
collect2: error: ld returned 1 exit status
make: *** [NoirShares-Qt] Error 1
$ ld -version
GNU ld (GNU Binutils for Debian) 2.24.51.20140425
any suggestions? I get through that by deleting line 163, 164 in NoirShares-qt.pro, but I got a lot of other problems after that. Don't have time to fix it yet. So the new source in completely broken in Linux. The dev could provide the fix for us, please? Thanks. No one even cares about Linux users without a wallet ?? Even the dev? Anyone has any idea how to compile the wallet in Linux? Thanks. Most of the time if your using linux you know how to compile and fix errors, that being said comment out lines 156-159 of the .pro file and you should be fine. there may be other things you need to do, and dependencies you need to check, that being said you can also qmake with the appropriate switches to disable things like qrcode and such if you dont have them. |
|
|
|
What's with the huge and I do mean HUGE amount of orphans?
Please give details. ebt.argakiig.us Thank you for the details. We have contacted this pool operator. This seems to be a problem with this particular pool. Please recognize that Proof of Work (PoW) mining efficiency will go down as more blocks are found by Proof Of Stake (PoS). So don't be surprised to have more difficulty finding blocks by PoW, even when the nominal difficulty is low. For example, the nominal PoW difficulty right now is 0.293. However, the difficulty realized by PoW miners is approximately 0.9, due to competition from PoS, which is responsible for 21 of the last 30 blocks (at 274729). No preference is given to PoS minting relative to PoW mining, but over time, the amount of eligible stake will go up, resulting in a greatly increased competition from PoS minters. It is getting near the point in EBT's life cycle that creating new coins is probably easiest done by buying EBT from an exchange and letting it stake to mint transactions. That minting becomes more efficient relative to mining over time is a designed property of PoW/PoS coins like EBT. That makes sense. Thank you. Carful examination of the pool reveals that it is functioning as expected. Pos blocks will quite often orphan pow blocks due to increasing PoS mining capacity on the network. Thank you for your continued support of my pool |
|
|
|
why do u have to dump the private keys and all that stuff, because all i did was install the new QT wallet open it and it synced?
Updated Qt with PoS Fix 32 and 64bit exe and zips https://github.com/NoirX/NoirShares-Qtsource https://github.com/NoirX/NRSNoirshares Upgrade Process Step 0 Dump Private Keys Step 1 See if blockchain redownload is needed. Help > Debug Window > Console. In the console type "getblock ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeeee" If return is Block not found (code -5) there is no need to re-download the chain proceed to step 5 1a otherwise backup privatekeys type "dumpprivkey <NRS Address>" and copy down the output some place safe as this is how you will get your coins back. 1b repeat 1a for each receiving address Step 2 Shut down NoirShares, verify not still running in background Step 3 If Block found open application data folder for NoirShares Windows default is %appdata%/NoirShares Linux default is ~/.NoirShares Mac OSx default is /Users/<your-user-name>/Library/NoirShares Step 4 Delete everything except wallet.dat(unless you dumpedprivkeys in step 1) and (optional)NoirShares.conf Step 5 Install new QT, unzip new QT, or build new Qt. Allow to sync to block height found at http://nrs.argakiig.usStep 6 If keys were dumped in step 1 Help > Debug Window > Console type "importprivkey <privkey from 1a>", Repeat for each private key. (Note: Qt can appear to hang during import step this is normal as block-chain is being checked for address to update balance with) Do i really need to dump private keys and all this jazz? I just backed up the wallet file and deleted everything else. New client is installed and re-downloading the blockchain... looks good so far. If you delete everything but the wallet.dat you shouldnt have any issues. this was more of a CYA then anything else. Plus if you dumpprivkeys you have a backup of your wallet and could essentially make a paper wallet if you wanted. Just a thought |
|
|
|
|
I will be here in a minute I just am working in between everything else
Give me a min and I can get it out
|
|
|
|
|
yes you won, now release builds. I can do 32 and 64 bit win qts as long as I have a source :p
|
|
|
|
thanks... I'm still learning all about how the actual protocol works and such... appreciate the explanation too! i thought privkeys were in the dat... just your coins?
the wallet.dat is a collection of your private keys and transactions associated with them. if you want to move your address to a new wallet.dat you would need your privatekeys. |
|
|
|
|
Show Posts
