Pages:
Author

Topic: [ANN] CoinonatX-PoW/PoS-Masternodes-75% APR (CXT Sister) -NEW THREAD - page 47. (Read 63684 times)

sr. member
Activity: 292
Merit: 251
Hi dev. coinonatxd don't work in debian8.
Code:
./coinonatxd any_command any_options
don't answer
Code:
cat coinonatx.conf
rpcallowip=127.0.0.1
rpcuser=my_login
rpcpassword=my_pass
staking=0
server=1
daemon=1
listen=1
Code:
cat debug.log
.....
SetBestChain: new best=036ebf8e44f3d4ad08288c1af139a5f311d8ed7799c114ae3d02d2a0385edfce  height=57090  trust=25178000413117657170  blocktrust=1933528342854728  date=09/15/17 01:37:20
ProcessBlock: ACCEPTED
Successfully synced, asking for Masternode list and payment list
Code:
ps aux | grep coinonatx
coinona+ 17151  0.2  0.4 982212 75688 ?        Ssl  07:02   0:32 ./coinonatxd
root     27800  0.0  0.0  99512  6340 ?        Ss   09:58   0:00 sshd: coinonatx [priv]
coinona+ 27807  0.0  0.0  99512  4844 ?        S    09:58   0:00 sshd: coinonatx@pts/2
coinona+ 28102  0.0  0.0  12728  2200 pts/2    S+   10:03   0:00 grep coinonatx
Don't ignore this.


Sorry, just noticed debug log shows the wallet running so I'm assuming it compiled fine. Is ./coinonatxd -? working? Anyway, your conf is missing a port. A non-masternode wallet config should look something like this:

Code:
rpcallowip=127.0.0.1
rpcuser=
rpcpassword=
rpcport=44578
daemon=1
server=1
listenonion=0
addnode=lindaminingpool.ddns.net
addnode=193.70.109.114

A masternode wallet conf should look like this:
Code:
rpcallowip=127.0.0.1
rpcuser=
rpcpassword=
staking=0
server=1
listen=1
port=
masternode=1
masternodeaddr=:
masternodeprivkey=
addnode=2001:19f0:7402:533:5400:ff:fe7e:bbd
addnode=45.76.179.109

Thanks. Testing this.
sr. member
Activity: 292
Merit: 251
Hi dev. coinonatxd don't work in debian8.
Code:
./coinonatxd any_command any_options
don't answer
Code:
cat coinonatx.conf
rpcallowip=127.0.0.1
rpcuser=my_login
rpcpassword=my_pass
staking=0
server=1
daemon=1
listen=1
Code:
cat debug.log
.....
SetBestChain: new best=036ebf8e44f3d4ad08288c1af139a5f311d8ed7799c114ae3d02d2a0385edfce  height=57090  trust=25178000413117657170  blocktrust=1933528342854728  date=09/15/17 01:37:20
ProcessBlock: ACCEPTED
Successfully synced, asking for Masternode list and payment list
Code:
ps aux | grep coinonatx
coinona+ 17151  0.2  0.4 982212 75688 ?        Ssl  07:02   0:32 ./coinonatxd
root     27800  0.0  0.0  99512  6340 ?        Ss   09:58   0:00 sshd: coinonatx [priv]
coinona+ 27807  0.0  0.0  99512  4844 ?        S    09:58   0:00 sshd: coinonatx@pts/2
coinona+ 28102  0.0  0.0  12728  2200 pts/2    S+   10:03   0:00 grep coinonatx
Don't ignore this.


The pre-compiled wallet for download here is only for ubuntu. If you're using debian you'll have to compile it yourself. Did you compile it yourself without errors?

Yes, i make this wallet without errors. os debian8. I can make only coinonatxd, qt-wallet don't compile in my os. This have many errors.
member
Activity: 68
Merit: 10
Hi dev. coinonatxd don't work in debian8.
Code:
./coinonatxd any_command any_options
don't answer
Code:
cat coinonatx.conf
rpcallowip=127.0.0.1
rpcuser=my_login
rpcpassword=my_pass
staking=0
server=1
daemon=1
listen=1
Code:
cat debug.log
.....
SetBestChain: new best=036ebf8e44f3d4ad08288c1af139a5f311d8ed7799c114ae3d02d2a0385edfce  height=57090  trust=25178000413117657170  blocktrust=1933528342854728  date=09/15/17 01:37:20
ProcessBlock: ACCEPTED
Successfully synced, asking for Masternode list and payment list
Code:
ps aux | grep coinonatx
coinona+ 17151  0.2  0.4 982212 75688 ?        Ssl  07:02   0:32 ./coinonatxd
root     27800  0.0  0.0  99512  6340 ?        Ss   09:58   0:00 sshd: coinonatx [priv]
coinona+ 27807  0.0  0.0  99512  4844 ?        S    09:58   0:00 sshd: coinonatx@pts/2
coinona+ 28102  0.0  0.0  12728  2200 pts/2    S+   10:03   0:00 grep coinonatx
Don't ignore this.


Sorry, just noticed debug log shows the wallet running so I'm assuming it compiled fine. Is ./coinonatxd -? working? Anyway, your conf is missing a port. A non-masternode wallet config should look something like this:

Code:
rpcallowip=127.0.0.1
rpcuser=
rpcpassword=
rpcport=44578
daemon=1
server=1
listenonion=0
addnode=lindaminingpool.ddns.net
addnode=193.70.109.114

A masternode wallet conf should look like this:
Code:
rpcallowip=127.0.0.1
rpcuser=
rpcpassword=
staking=0
server=1
listen=1
port=
masternode=1
masternodeaddr=:
masternodeprivkey=
addnode=2001:19f0:7402:533:5400:ff:fe7e:bbd
addnode=45.76.179.109
member
Activity: 68
Merit: 10
Hi dev. coinonatxd don't work in debian8.
Code:
./coinonatxd any_command any_options
don't answer
Code:
cat coinonatx.conf
rpcallowip=127.0.0.1
rpcuser=my_login
rpcpassword=my_pass
staking=0
server=1
daemon=1
listen=1
Code:
cat debug.log
.....
SetBestChain: new best=036ebf8e44f3d4ad08288c1af139a5f311d8ed7799c114ae3d02d2a0385edfce  height=57090  trust=25178000413117657170  blocktrust=1933528342854728  date=09/15/17 01:37:20
ProcessBlock: ACCEPTED
Successfully synced, asking for Masternode list and payment list
Code:
ps aux | grep coinonatx
coinona+ 17151  0.2  0.4 982212 75688 ?        Ssl  07:02   0:32 ./coinonatxd
root     27800  0.0  0.0  99512  6340 ?        Ss   09:58   0:00 sshd: coinonatx [priv]
coinona+ 27807  0.0  0.0  99512  4844 ?        S    09:58   0:00 sshd: coinonatx@pts/2
coinona+ 28102  0.0  0.0  12728  2200 pts/2    S+   10:03   0:00 grep coinonatx
Don't ignore this.


The pre-compiled wallet for download here is only for ubuntu. If you're using debian you'll have to compile it yourself. Did you compile it yourself without errors?

Why do some of the masternodes that are listed on the coinonatx masternode network keep showing 00ms:00s ? This is my problem at the moment. Got some coins coming through, but there's something not right?

Reading your posts it seems you may have some confusion regarding staking vs masternode. Both will earn you coins but they are mutually exclusive, meaning a staking wallet cannot be a masternode and a masternode cannot stake. If you didn't setup the coinonatx.conf file correctly to run the masternode you're wallet is probably staking even if you've created and started a masternode in the wallet GUI. It simply gets ignored. If you see the little up arrow icon between the lock and the connection bars then you are not running a masternode, you are staking. If you're masternode is running properly then you shouldn't have an up arrow icon at all. Like so:

member
Activity: 91
Merit: 10
Say the original dev does decide to just bail on this coin...i mean, what if community just picks it up and revives it? Its got a fairly low supply, MNs, decent exchanges. I've come across other coins with less potential.
member
Activity: 112
Merit: 10
Why do some of the masternodes that are listed on the coinonatx masternode network keep showing 00ms:00s ? This is my problem at the moment. Got some coins coming through, but there's something not right?

You can ignore those 00

-support team
sr. member
Activity: 292
Merit: 251
Hi dev. coinonatxd don't work in debian8.
Code:
./coinonatxd any_command any_options
don't answer
Code:
cat coinonatx.conf
rpcallowip=127.0.0.1
rpcuser=my_login
rpcpassword=my_pass
staking=0
server=1
daemon=1
listen=1
Code:
cat debug.log
.....
SetBestChain: new best=036ebf8e44f3d4ad08288c1af139a5f311d8ed7799c114ae3d02d2a0385edfce  height=57090  trust=25178000413117657170  blocktrust=1933528342854728  date=09/15/17 01:37:20
ProcessBlock: ACCEPTED
Successfully synced, asking for Masternode list and payment list
Code:
ps aux | grep coinonatx
coinona+ 17151  0.2  0.4 982212 75688 ?        Ssl  07:02   0:32 ./coinonatxd
root     27800  0.0  0.0  99512  6340 ?        Ss   09:58   0:00 sshd: coinonatx [priv]
coinona+ 27807  0.0  0.0  99512  4844 ?        S    09:58   0:00 sshd: coinonatx@pts/2
coinona+ 28102  0.0  0.0  12728  2200 pts/2    S+   10:03   0:00 grep coinonatx
Don't ignore this.
member
Activity: 112
Merit: 10
Not sure my MN started correctly. When I do a list-conf I get emptyness and the winners command returns block numbers but no node IP's and my node doesnt show up in the master nodes list
I am also getting a lot of socket recv error 104.

Here is the config file, Redacted of course

rpcallowip=127.0.0.1
rpcuser=a...d
rpcpassword=AlDv......dQZNh
staking=0
server=1
listen=1
addnode=lindaminingpool.ddns.net
addnode=193.70.109.114
port=41100
masternode=1
masternodeaddr=45.xx.xx.xx:41100
masternodeprivkey=64..............................................................................

Anyone have any thoughts.



The conf file is perfect. You can try to restart wallet, unlock it, then start masternodes. You can then lock it if you want.

-support team
full member
Activity: 333
Merit: 100
Not sure my MN started correctly. When I do a list-conf I get emptyness and the winners command returns block numbers but no node IP's and my node doesnt show up in the master nodes list
I am also getting a lot of socket recv error 104.

Here is the config file, Redacted of course

rpcallowip=127.0.0.1
rpcuser=a...d
rpcpassword=AlDv......dQZNh
staking=0
server=1
listen=1
addnode=lindaminingpool.ddns.net
addnode=193.70.109.114
port=41100
masternode=1
masternodeaddr=45.xx.xx.xx:41100
masternodeprivkey=64..............................................................................

Anyone have any thoughts.
member
Activity: 68
Merit: 10
Thanks kydub, that one did have a broken config but the other non-working masternode was correct.

I've turned off staking using

Code:
staking=0
reservebalance=5000

and the masternode now shows
Code:
./coinonatxd getstakinginfo
{
    "enabled" : false,
    "staking" : false,
    "errors" : "",
    "currentblocksize" : 0,
    "currentblocktx" : 0,
    "pooledtx" : 0,
    "difficulty" : 292822.64254297,
    "search-interval" : 0,
    "weight" : 250329408570,
    "netstakeweight" : 223617043699649,
    "expectedtime" : 0
}

But I'm still seeing repeated

Code:
CActiveMasternode::ManageStatus() - Checking inbound connection to 'x.x.x.x:44678'
CActiveMasternode::GetMasterNodeVin - Could not locate specified vin from possible list
CActiveMasternode::ManageStatus() - Could not find suitable coins!
CActiveMasternode::Dseep() - Error: masternode is not in a running status
CActiveMasternode::ManageStatus() - Error on Ping: masternode is not in a running statusconnected to self at x.x.x.x:51448, disconnecting
CDarkSendPool::UpdateState() == 3 | 3
connect() to 80.92.226.17:44678 failed after select(): Network is unreachable

in both nodes so was wondering if there was a problem in the XCXT network.

Thanks


I don't think you need to include reservebalance in the conf. Did you use listaddressgroupings to check the address balances to ensure 5000 xcxt are in the mn address? I received a reward 1 minute ago so I doubt it's the network. Is it possible your wallet is locked? How are you starting your masternode? So it unlocks it should be
Code:
masternode start

I did manage to find a similar issue and solution for dash. Here it is adapted to coinonatxd

Quote
Problem:
You have masternode in list but coinonatxd masternode debug gives you Could not find suitable coins!. Few hours later you node drops out of list.

Explanation:
This means that your node was not activated actually. On a successfully activated remote masternode coinonatxd masternode debug should return Masternode successfully started. One reason why your masternode wasn't activated could be that new activation message can't reach your masternode from your local wallet because somewhere on its route there are only v11 masternodes and they just ignore new messages.

Fix:
To fix this you need to connect to your node directly and there are few ways to do this:

Simple one, temporary: open console in local wallet and type
Code:
addnode : onetry
- this will force your client to open direct connection to your MN.

if #1 didn't work for some reason or you want to force your wallet to connect to your MNs every time you run it use the connect arugment when starting the wallet like so:
Code:
./coinonatxd -connect=:
or add
Code:
connect=:
in coinonatx.conf. You can add it multiple times if you have many masternodes. Note: this way your client will connect only to specified IPs.
member
Activity: 68
Merit: 10
Hi Kydub, I'm a little confused as why you've put my handle in your comments? I'm not part of the support team, I'm just here to get help on setting up my MN. There are times that I have seen someone post something and I've tried to comment to help. Sometimes I post something and then find that I need to format, spell check or alter something. If I've posted something it's to help and I think those that look at my comments will see this.

There's a huge amount of strange stuff in the crypto world; I'm being kind here. There's a lot of selectivity when it comes to answering people across the board, let alone how they answer also. I'm not sure if the people that created the prior coin are scammers or not. I've already bought a good amount of Coinonatx prior to having a better look at the history behind this coin. What to do, when I've already lost a lot of money in the whole crypto market. Huge amount of time spent and my health has suffered from this, but I think I've worked out a plan, as of last night, to turn things around. Inclusive of this plan, I'm hoping that this coin and its developers will turn this coin into a success also.

I would say that if you look at a hit song that makes millions, the reason it does this is that it adds value. Millions of people at there hum drum jobs doing work that they don't like. When they hear a song on the radio that makes them happy, they are favorable to buying this song, supporting this, even going to the concerts, buying t-shirts etc i.e. You create something that adds value to this world and you are blessed by it. This is what I would say to the people behind the creation of this coin. Look to bless people with your work, make people happy and you will be rewarded many times over; you'll also be able to live with yourself, sleep better and have good dharma in this life and thereafter. I watched a guy on youtube go through the process of creating as many coins as he liked i.e. just a number imputed to the software field, he then went through showing how to post this on an exchange i.e. poof coins out of thin air. Not sure if I'm totally right on this. I'm just saying here that if there are people from the old coin that feel unhappy, I would bend over backwards to giving them the swap on the new coin and make them happy; this will also foster support for the new coin and make more money in the long run. You'll also feel better about yourself and create good dharma for your spirit. It's not about who has the most toys at the end, it's about eternal values and success in creating a spirit of gold.

At this stage, I can't afford a MN with any other coin and I'm hoping on this coin. I know in the first week that I staked a coinonatx Mn I got 100 coins; not sure if I'd get that with any other coin. The recent thing is to try and run more MN's. I just hope that the crypto market and this coin continues for me to see at least me getting the money back that I've lost and hopefully to see profits at some stage. So far the support team on bitcointalk fairly decent in helping me. I've still got more questions.

@ted_nugent I only mentioned you because at least twice I've received an email notification with a post from you and when I followed the link to reply the post was no longer on this board. I just assumed you changed your mind and deleted them. It was meant only to illustrate that even deleted posts end up in my inbox. I meant no offense.

I'm in the same boat as you. The choice was to either abandon ship and cut my losses or continue on with hope that I'd at least recoup my investment, even if this turned out to be a scam. I, and many others, share your sentiment regarding the swap. Why the devs don't make an effort to properly accommodate the very people that believed in them and are making them money is beyond me. The lack of transparency, responsiveness, and respect on devs part is beyond me. The devs apparent inability to follow through with their many promises and lack of concern is beyond me. I can only assume that when the shit hits the fan all will become clear in retrospect. So here we sit in the precarious position of desiring devs success while also being overwhelmingly frustrated with the path they've led us on. So devs, please get your shit together, treat your investors with some respect, and make this coin successful for the sake of all of us.
newbie
Activity: 33
Merit: 0
Thanks kydub, that one did have a broken config but the other non-working masternode was correct.

I've turned off staking using

Code:
staking=0
reservebalance=5000

and the masternode now shows
Code:
./coinonatxd getstakinginfo
{
    "enabled" : false,
    "staking" : false,
    "errors" : "",
    "currentblocksize" : 0,
    "currentblocktx" : 0,
    "pooledtx" : 0,
    "difficulty" : 292822.64254297,
    "search-interval" : 0,
    "weight" : 250329408570,
    "netstakeweight" : 223617043699649,
    "expectedtime" : 0
}

But I'm still seeing repeated

Code:
CActiveMasternode::ManageStatus() - Checking inbound connection to 'x.x.x.x:44678'
CActiveMasternode::GetMasterNodeVin - Could not locate specified vin from possible list
CActiveMasternode::ManageStatus() - Could not find suitable coins!
CActiveMasternode::Dseep() - Error: masternode is not in a running status
CActiveMasternode::ManageStatus() - Error on Ping: masternode is not in a running statusconnected to self at x.x.x.x:51448, disconnecting
CDarkSendPool::UpdateState() == 3 | 3
connect() to 80.92.226.17:44678 failed after select(): Network is unreachable

in both nodes so was wondering if there was a problem in the XCXT network.

Thanks
member
Activity: 68
Merit: 10
Hi,

I'd already received 7 or 8 coins on each masternode which I believe were confirmed. It's been in this status for over 24 hours now.

Code:
$ ./CoinonatX/src/coinonatxd masternode list-conf
{
}

Code:
more .CoinonatX/masternode.conf
mn1 xxx.xxx.xxx.xxx:44678 526c1a###########################fb3f238 526c1###############################b3f238 1

Tried removing peers.dat and adding known good nodes to the .conf

Getting lots of connection refused and recv error 104:

Code:
socket recv error 104
connect() to 36.55.235.149:44678 failed after select(): Connection refused
CActiveMasternode::ManageStatus() - Checking inbound connection to '104.238.182.27:44678'
CActiveMasternode::GetMasterNodeVin - Could not locate specified vin from possible list
CActiveMasternode::ManageStatus() - Could not find suitable coins!
CActiveMasternode::Dseep() - Error: masternode is not in a running status
CActiveMasternode::ManageStatus() - Error on Ping: masternode is not in a running statussocket recv error 104
connect() to 188.102.211.160:44678 failed after select(): No route to host
CDarkSendPool::UpdateState() == 3 | 3
socket recv error 104
connect() to 177.85.75.12:44678 failed after select(): Connection refused
socket recv error 104
SetBestChain: new best=02e5149c46b6033bf8f056685a09bd835f1a636465c1d13bad496dcf220cec39  height=56344  trust=24528830554925494281  blocktrust=1742341774611765  date=09/14/17 11:19:12
ProcessBlock: ACCEPTED

Thanks


I haven't run an XCXT node using masternode.conf but I would expect different values for the masternode private key and collateral output transaction id. What you posted shows the same value twice. And neither seem to be the length I would expect for a private key or transaction id. So I'm not sure what they are. Also, try
Code:
listaddressgroupings
to check the mn address still has at least 5000 XCXT. Someone else recently had a problem with coins dropping out because staking was still enabled. You can check with
Code:
getstakinginfo
newbie
Activity: 33
Merit: 0
Hi,

I'd already received 7 or 8 coins on each masternode which I believe were confirmed. It's been in this status for over 24 hours now.

Code:
$ ./CoinonatX/src/coinonatxd masternode list-conf
{
}

Code:
more .CoinonatX/masternode.conf
mn1 xxx.xxx.xxx.xxx:44678 526c1a###########################fb3f238 526c1###############################b3f238 1

Tried removing peers.dat and adding known good nodes to the .conf

Getting lots of connection refused and recv error 104:

Code:
socket recv error 104
connect() to 36.55.235.149:44678 failed after select(): Connection refused
CActiveMasternode::ManageStatus() - Checking inbound connection to '104.238.182.27:44678'
CActiveMasternode::GetMasterNodeVin - Could not locate specified vin from possible list
CActiveMasternode::ManageStatus() - Could not find suitable coins!
CActiveMasternode::Dseep() - Error: masternode is not in a running status
CActiveMasternode::ManageStatus() - Error on Ping: masternode is not in a running statussocket recv error 104
connect() to 188.102.211.160:44678 failed after select(): No route to host
CDarkSendPool::UpdateState() == 3 | 3
socket recv error 104
connect() to 177.85.75.12:44678 failed after select(): Connection refused
socket recv error 104
SetBestChain: new best=02e5149c46b6033bf8f056685a09bd835f1a636465c1d13bad496dcf220cec39  height=56344  trust=24528830554925494281  blocktrust=1742341774611765  date=09/14/17 11:19:12
ProcessBlock: ACCEPTED

Thanks
member
Activity: 112
Merit: 10
I had 2 masternodes running and receiving payments for a couple of days. Yesterday they both stopped working with
Code:
CActiveMasternode::ManageStatus() - Checking inbound connection to 'xxx.xxx.xxx.xxx:44678'
CActiveMasternode::GetMasterNodeVin - Could not locate specified vin from possible list
CActiveMasternode::ManageStatus() - Could not find suitable coins!
CActiveMasternode::Dseep() - Error: masternode is not in a running status

and I can't get them to restart the master nodes

list-conf shows nothing

Any hints appreciated, thanks !

You need to wait for it to get 15 confirmations after you send 5000 for MN
You can try in 1 hour to start MN

-support team

newbie
Activity: 33
Merit: 0
I had 2 masternodes running and receiving payments for a couple of days. Yesterday they both stopped working with
Code:
CActiveMasternode::ManageStatus() - Checking inbound connection to 'xxx.xxx.xxx.xxx:44678'
CActiveMasternode::GetMasterNodeVin - Could not locate specified vin from possible list
CActiveMasternode::ManageStatus() - Could not find suitable coins!
CActiveMasternode::Dseep() - Error: masternode is not in a running status

and I can't get them to restart the master nodes

list-conf shows nothing

Any hints appreciated, thanks !
member
Activity: 112
Merit: 10
I'm still confused about the locking your wallet thing. Is this the same as encrypting the wallet? as on my Coinonatx mac software, all I have is 'Encrypt Wallet' from 'Setting' in the menu bar. The little padlock icon on the Coinonatx wallet software seemingly does not allow me to click on this to change it from a locked to unlocked state. I believe that you can do this with the PIVX padlock icon, but my memory might be wrong on this. Is there a hot key factor to get the padlock to change state from locked to unclocked?

Also, I'd like to know when to encrypt/lock? the wallet in
1) the process of A) setting up for a masternode or B) setting up for staking and
2) When to lock/encrypt? or unlock/unencrypt the wallet while A) 'running' the masternode or B) staking.

Please explain. Thanks

You cannot see the lock / unlock option unless you encrypt wallet

It is not necessary to encrypt or lock the wallet at all, but if you want to be secure on a VPS then you can do this.
Staking needs the wallet to be unlocked but only for staking. There is such option which you can tick mark, while unlocking.
You can unlock or lock the wallet while being Masternode. When you want to start a masternode, the wallet should be unlocked. You can lock it later on.

-support team
newbie
Activity: 21
Merit: 0
I'm still confused about the locking your wallet thing. Is this the same as encrypting the wallet? as on my Coinonatx mac software, all I have is 'Encrypt Wallet' from 'Setting' in the menu bar. The little padlock icon on the Coinonatx wallet software seemingly does not allow me to click on this to change it from a locked to unlocked state. I believe that you can do this with the PIVX padlock icon, but my memory might be wrong on this. Is there a hot key factor to get the padlock to change state from locked to unclocked?

Also, I'd like to know when to encrypt/lock? the wallet in
1) the process of A) setting up for a masternode or B) setting up for staking and
2) When to lock/encrypt? or unlock/unencrypt the wallet while A) 'running' the masternode or B) staking.

Please explain. Thanks
member
Activity: 68
Merit: 10
darksend.cpp:978:29: error: cannot convert ‘bool’ to ‘bool*’ in initialization      bool* pfMissingInputs = false;

This happened in several locations I made the following changes to the code to make the compiler happy and accomplish the same thing.


        bool pfMissingInputs;
        if(!AcceptableInputs(mempool, tx, false, &pfMissingInputs)){

Since the variable is used only locally withing the scope of the current function, it should be ok to allocate the variable on the stack and then pass its address into the
AcceptableInputs function. Within the function the value is set to false in the event that its not already done.

Thank you. That is correct. It's a bug carried over from the original code by the The Darkcoin developers. For some reason older compilers allowed it, but newer compilers don't. FYI if anyone is wondering darksend.cpp:978 is a reference to line 978 in src/darksend.cpp
Pages:
Jump to: