CRAVE: Revival

[itneg]

Why there are 2 CRAVE coins? You should change the name because can't be 2 different coins with one name...

[Slothman]

Why there are 2 CRAVE coins? You should change the name because can't be 2 different coins with one name...

Could you expand on that please?  CRAVE began back in 2015.

[NEVER.SELL.CRAVE....EVER]

Why there are 2 CRAVE coins? You should change the name because can't be 2 different coins with one name...

There's nowhere two Crave.The only one is this so tell us your source of such information   
Our Crave is more then 2 years old.

edit. I guess you've created a new account just for bringing some kind of FUD here expecting the price will go down and you can buy cheap Crave 

[CooleRRSA]

Hello everybody!
New release: v2.0.3.7

*New new commandline option for wallet database "-dbwalletcache"
Give you control of wallet database cache. By default cache database reduced to 1Mb.
*Blockchain database cache decreased to 10Mb by default
*New build option for more memory usage optimization
For masternode holders. I have added new buildoption "LOWMEM" (disabled by default). If enabled, usage of memory can be reduced by an additional 37Mb (from ~315Mb to ~277Mb with default database caches). But it brokes compatibility with blockchain database and you will need to resync database. The choice yours.

Recommended for masternode holders. Update your wallets.

[txcx]

Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

[CooleRRSA]

Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

If you use controller wallet for starting masternodes, it needs to be unlocked once for starting remote masternodes. After that remote masternodes will work autonomously and controller wallet do not needed anymore.
If your masternodes normaly starts but disappears after some time, check ip:port settings of your masternodes. They must be reachable from internet. Have correct ip and open port.

[txcx]

Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

If you use controller wallet for starting masternodes, it needs to be unlocked once for starting remote masternodes. After that remote masternodes will work autonomously and controller wallet do not needed anymore.
If your masternodes normaly starts but disappears after some time, check ip:port settings of your masternodes. They must be reachable from internet. Have correct ip and open port.

Good to know, checked again my firewall...
misstyped something with the rules, phew
now its gonna working fine
yay

[CooleRRSA]

Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

If you use controller wallet for starting masternodes, it needs to be unlocked once for starting remote masternodes. After that remote masternodes will work autonomously and controller wallet do not needed anymore.
If your masternodes normaly starts but disappears after some time, check ip:port settings of your masternodes. They must be reachable from internet. Have correct ip and open port.

Good to know, checked again my firewall...
misstyped something with the rules, phew
now its gonna working fine
yay

Good))) I think I need to add checking connection to masternodes while starting in controller wallet))

[txcx]

Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

If you use controller wallet for starting masternodes, it needs to be unlocked once for starting remote masternodes. After that remote masternodes will work autonomously and controller wallet do not needed anymore.
If your masternodes normaly starts but disappears after some time, check ip:port settings of your masternodes. They must be reachable from internet. Have correct ip and open port.

Good to know, checked again my firewall...
misstyped something with the rules, phew
now its gonna working fine
yay

Good))) I think I need to add checking connection to masternodes while starting in controller wallet))

And they are delisted again...
I don't know what to do else. There is something wrong.. But what or where...


These are my configs now:




Masternode #1 config (started with: ./craved1 -daemon -datadir=/home/mn/.crave)
Masternode #2 config (started with: ./craved2 -daemon -datadir=/home/mn/.crave2)
... and so on

~/.craveX/crave.conf

Code:

rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=30105
bind=127.0.0.2
bind=vps-ip
externalip=vps-ip
listen=1
server=1
daemon=1
staking=0
logtimestamps=1
port=9999
masternode=1
masternodeaddr=vps-ip:9999
masternodeprivkey=privkey
addnode=173.48.167.209:30104
addnode=107.170.147.51:9999
addnode=81.191.27.5:19914
addnode=195.154.163.121:30104

Other node configs are the same, but:

- rpcport gets a higher number (next is: 30106)
- bind gets a higher number (next is: 127.0.0.3)
- port gets a lower number (next is: 9998)


- masternode outputs are fine
- masternode keys are fine
- masternode conf looking well

ufw settings:

Code:

9990:9999/tcp              ALLOW       Anywhere
30100:30120/tcp            ALLOW       Anywhere
30100:30120/udp            ALLOW       Anywhere
9990:9999/udp              ALLOW       Anywhere
9990:9999/tcp (v6)         ALLOW       Anywhere (v6)
30100:30120/tcp (v6)       ALLOW       Anywhere (v6)
30100:30120/udp (v6)       ALLOW       Anywhere (v6)
9990:9999/udp (v6)         ALLOW       Anywhere (v6)

I run them on a 1 GB Ram Ubuntu 16.04 VPS with 4 GB Swap File,
Does it need more ram or should this be fine?

[CooleRRSA]

Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

If you use controller wallet for starting masternodes, it needs to be unlocked once for starting remote masternodes. After that remote masternodes will work autonomously and controller wallet do not needed anymore.
If your masternodes normaly starts but disappears after some time, check ip:port settings of your masternodes. They must be reachable from internet. Have correct ip and open port.

Good to know, checked again my firewall...
misstyped something with the rules, phew
now its gonna working fine
yay

Good))) I think I need to add checking connection to masternodes while starting in controller wallet))

And they are delisted again...
I don't know what to do else. There is something wrong.. But what or where...


These are my configs now:




Masternode #1 config (started with: ./craved1 -daemon -datadir=/home/mn/.crave)
Masternode #2 config (started with: ./craved2 -daemon -datadir=/home/mn/.crave2)
... and so on

~/.craveX/crave.conf

Code:

rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=30105
bind=127.0.0.2
bind=vps-ip
externalip=vps-ip
listen=1
server=1
daemon=1
staking=0
logtimestamps=1
port=9999
masternode=1
masternodeaddr=vps-ip:9999
masternodeprivkey=privkey
addnode=173.48.167.209:30104
addnode=107.170.147.51:9999
addnode=81.191.27.5:19914
addnode=195.154.163.121:30104

Other node configs are the same, but:

- rpcport gets a higher number (next is: 30106)
- bind gets a higher number (next is: 127.0.0.3)
- port gets a lower number (next is: 9998)


- masternode outputs are fine
- masternode keys are fine
- masternode conf looking well

ufw settings:

Code:

9990:9999/tcp              ALLOW       Anywhere
30100:30120/tcp            ALLOW       Anywhere
30100:30120/udp            ALLOW       Anywhere
9990:9999/udp              ALLOW       Anywhere
9990:9999/tcp (v6)         ALLOW       Anywhere (v6)
30100:30120/tcp (v6)       ALLOW       Anywhere (v6)
30100:30120/udp (v6)       ALLOW       Anywhere (v6)
9990:9999/udp (v6)         ALLOW       Anywhere (v6)

I run them on a 1 GB Ram Ubuntu 16.04 VPS with 4 GB Swap File,
Does it need more ram or should this be fine?

You use ipv4 or ipv6 address?

[txcx]

Unfortunately new problems came up.
Started all the nodes with the configuration from Slothman.

Nodes successfully started
Wallet says: "Masternode is Running" for all nodes.

But in the masternode list they are active: 00m:00s
After 30min to 1 hour alle nodes are not in the list anymore.

That's what happens now...

Don't know if this is affected by autolocking wallet?
If so, how to permantentely unlock wallet?

If you use controller wallet for starting masternodes, it needs to be unlocked once for starting remote masternodes. After that remote masternodes will work autonomously and controller wallet do not needed anymore.
If your masternodes normaly starts but disappears after some time, check ip:port settings of your masternodes. They must be reachable from internet. Have correct ip and open port.

Good to know, checked again my firewall...
misstyped something with the rules, phew
now its gonna working fine
yay

Good))) I think I need to add checking connection to masternodes while starting in controller wallet))

And they are delisted again...
I don't know what to do else. There is something wrong.. But what or where...


These are my configs now:




Masternode #1 config (started with: ./craved1 -daemon -datadir=/home/mn/.crave)
Masternode #2 config (started with: ./craved2 -daemon -datadir=/home/mn/.crave2)
... and so on

~/.craveX/crave.conf

Code:

rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=30105
bind=127.0.0.2
bind=vps-ip
externalip=vps-ip
listen=1
server=1
daemon=1
staking=0
logtimestamps=1
port=9999
masternode=1
masternodeaddr=vps-ip:9999
masternodeprivkey=privkey
addnode=173.48.167.209:30104
addnode=107.170.147.51:9999
addnode=81.191.27.5:19914
addnode=195.154.163.121:30104

Other node configs are the same, but:

- rpcport gets a higher number (next is: 30106)
- bind gets a higher number (next is: 127.0.0.3)
- port gets a lower number (next is: 9998)


- masternode outputs are fine
- masternode keys are fine
- masternode conf looking well

ufw settings:

Code:

9990:9999/tcp              ALLOW       Anywhere
30100:30120/tcp            ALLOW       Anywhere
30100:30120/udp            ALLOW       Anywhere
9990:9999/udp              ALLOW       Anywhere
9990:9999/tcp (v6)         ALLOW       Anywhere (v6)
30100:30120/tcp (v6)       ALLOW       Anywhere (v6)
30100:30120/udp (v6)       ALLOW       Anywhere (v6)
9990:9999/udp (v6)         ALLOW       Anywhere (v6)

I run them on a 1 GB Ram Ubuntu 16.04 VPS with 4 GB Swap File,
Does it need more ram or should this be fine?

You use ipv4 or ipv6 address?

i use ipv4, at the moment they are running since 2 hours...
i got also first rewards, crazy
but not sure when they are off again.

[Slothman]

I've had it where I had to start once it twice before staying up.  Probably just something weird with the ports, idk.

[txcx]

I've had it where I had to start once it twice before staying up.  Probably just something weird with the ports, idk.

Thanks, I'll have a look.

Last question about rewards.
Do you get them constantly?

My rewards right now:

0.66666 for node #2
0.66666 for node #1
0.66666 for node #1

Thats all for 3 hours, nothing about node #3 and #4 etc.
Seems something is buggy, or it take a while dont know.

[CooleRRSA]

I've had it where I had to start once it twice before staying up.  Probably just something weird with the ports, idk.

It's absolutly random, so it's normal))

Thanks, I'll have a look.

Last question about rewards.
Do you get them constantly?

My rewards right now:

0.66666 for node #2
0.66666 for node #1
0.66666 for node #1

Thats all for 3 hours, nothing about node #3 and #4 etc.
Seems something is buggy, or it take a while dont know.

It's absolutly random, so it's normal))

[Slothman]

I've had it where I had to start once it twice before staying up.  Probably just something weird with the ports, idk.

Thanks, I'll have a look.

Last question about rewards.
Do you get them constantly?

My rewards right now:

0.66666 for node #2
0.66666 for node #1
0.66666 for node #1

Thats all for 3 hours, nothing about node #3 and #4 etc.
Seems something is buggy, or it take a while dont know.

Well, say each node gets 4 crave per day.  That's 6 rewards per day, or one reward every ~4 hours per node.

I would wait a bit more to see what they do.  The rewards are random, so it might be more or less.

[DonQuijote]

I gave assistance to create masternodes, im old 
Good luck with the project

[txcx]

I've had it where I had to start once it twice before staying up.  Probably just something weird with the ports, idk.

Thanks, I'll have a look.

Last question about rewards.
Do you get them constantly?

My rewards right now:

0.66666 for node #2
0.66666 for node #1
0.66666 for node #1

Thats all for 3 hours, nothing about node #3 and #4 etc.
Seems something is buggy, or it take a while dont know.

Well, say each node gets 4 crave per day.  That's 6 rewards per day, or one reward every ~4 hours per node.

I would wait a bit more to see what they do.  The rewards are random, so it might be more or less.

Thanks a lot man, I'll see

[cpozzer]

Need some info here, got a masternode working, if lets say i have 510 coins in tht wallet and i want to send out 10 coins can i do tht? or will the masternode stop working?

[tkon3]

Need some info here, got a masternode working, if lets say i have 510 coins in tht wallet and i want to send out 10 coins can i do tht? or will the masternode stop working?

When you set up a masternode, you send 500 crave to a specific address, so you have 10 crave left on the first address that you can use freely.
You can also make transactions from the MN without touching the first 500 crave sent (need advanced coin control on your wallet)

[cpozzer]

Need some info here, got a masternode working, if lets say i have 510 coins in tht wallet and i want to send out 10 coins can i do tht? or will the masternode stop working?

When you set up a masternode, you send 500 crave to a specific address, so you have 10 crave left on the first address that you can use freely.

ok, so as long as my wallet doesnt go under 500 im fine right?