[ANN] VIVO - Masternodes, ASIC-Resistant, Secure, High MN Rewards, Decentralized - page 32.

tlaskows

full member

Activity: 564

Merit: 100

Join GANTECH’s team of game changers

Quote from: bathrobehero on August 22, 2017, 09:28:32 AM

Quote from: mainconcept on August 22, 2017, 09:25:31 AM

Quote from: Stopscampls on August 22, 2017, 09:12:09 AM

is there a way to mine solo? i ry it but miner shows JSON-RPC fail: method not found....what that meens? Huh

Because its a DASH clone you can unfortunately not solomine this coin.

No solomining and centralized funds (premine), feels like we're going backwards.

Mine Vivo. With my rig I can get < 200 coins a month (6 fast GPUs). And it looks like there are already 800,000 out there.

It's fair PoW disctribution. No ICO Wink

Steven3iii

full member

Activity: 238

Merit: 100

I like this coin and the community. Positive and helpful. Just right for what it is going to do. Grin

moinuddin14

full member

Activity: 126

Merit: 100

Quote from: Dead Things on November 29, 2017, 03:41:34 PM

Wondering if anybody knows the answer to this little conundrum of mine...

With Vivo, can I specify an address for MN rewards in the masternode.conf? Something like this...
mn1 127.0.0.2:19999 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg 2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c 0 VWNShrcr4LrQQurEapq7C3e5hhzhhdTJJp:100

I know this works on some other coins. Just not sure about Vivo. Thanks!

Yes you need to update the masternode.conf file both in the VPS and local wallet as well. At VPS you can keep the IP as 127.0.0.1 but in local you need to give the IP of the VPS and the port should be 12845. As mentioned below you need to update all the fields.

# Format: alias IP:port masternodeprivkey collateral_output_txid collateral_output_index

Dead Things

full member

Activity: 423

Merit: 100

Wondering if anybody knows the answer to this little conundrum of mine...

With Vivo, can I specify an address for MN rewards in the masternode.conf? Something like this...
mn1 127.0.0.2:19999 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg 2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c 0 VWNShrcr4LrQQurEapq7C3e5hhzhhdTJJp:100

I know this works on some other coins. Just not sure about Vivo. Thanks!

moinuddin14

full member

Activity: 126

Merit: 100

Dev, can you remove the annoying ads on the explorer page. Pretty hard to track the transactions with those ads showing at the end of the page.

cryptomaxsun

legendary

Activity: 2744

Merit: 1387

Ukrainians will resist

and the developer here does not want to answer why his coin does not work?

gscotch

member

Activity: 224

Merit: 10

Quote from: cryptomaxsun on November 29, 2017, 01:28:51 PM

Quote from: gscotch on November 29, 2017, 01:13:19 PM

Quote from: cryptomaxsun on November 29, 2017, 11:11:39 AM

and the remaining mistakes how to win?

Make sure you started daemon AFTER you copied/configured vivo.conf - try "vivo-cli getinfo" - should get you a similar error.
If that is the case:
- rename vivo.conf to smth else "mv ~/.vivocore/vivo.conf ~/.vivocore/vivo_.conf"
- stop daemon "vivo-cli stop"
- rename vivo.conf back to it's normal name "mv ~/.vivocore/vivo_.conf ~/.vivocore/vivo.conf"
- start daemon "vivod"

Wait for it to finish syncing and try to run sentinel again.

Did not help. What are the problems? Why do need sentinel? There are masternodes without sentinel and work fine.

from my experience vivo, innova, gobyte MN's after few days may stuck on random block. I understand that sentinel helps to sync MN with chain all the time.

please ask VIVO Devs on discord https://discord.gg/BXGzAx7

cryptomaxsun

legendary

Activity: 2744

Merit: 1387

Ukrainians will resist

Quote from: gscotch on November 29, 2017, 01:13:19 PM

Quote from: cryptomaxsun on November 29, 2017, 11:11:39 AM

and the remaining mistakes how to win?

Make sure you started daemon AFTER you copied/configured vivo.conf - try "vivo-cli getinfo" - should get you a similar error.
If that is the case:
- rename vivo.conf to smth else "mv ~/.vivocore/vivo.conf ~/.vivocore/vivo_.conf"
- stop daemon "vivo-cli stop"
- rename vivo.conf back to it's normal name "mv ~/.vivocore/vivo_.conf ~/.vivocore/vivo.conf"
- start daemon "vivod"

Wait for it to finish syncing and try to run sentinel again.

Did not help. What are the problems? Why do need sentinel? There are masternodes without sentinel and work fine.

gscotch

member

Activity: 224

Merit: 10

Quote from: cryptomaxsun on November 29, 2017, 11:11:39 AM

and the remaining mistakes how to win?

Make sure you started daemon AFTER you copied/configured vivo.conf - try "vivo-cli getinfo" - should get you a similar error.
If that is the case:
- rename vivo.conf to smth else "mv ~/.vivocore/vivo.conf ~/.vivocore/vivo_.conf"
- stop daemon "vivo-cli stop"
- rename vivo.conf back to it's normal name "mv ~/.vivocore/vivo_.conf ~/.vivocore/vivo.conf"
- start daemon "vivod"

Wait for it to finish syncing and try to run sentinel again.

cryptomaxsun

legendary

Activity: 2744

Merit: 1387

Ukrainians will resist

and the remaining mistakes how to win?

gscotch

member

Activity: 224

Merit: 10

Quote from: cryptomaxsun on November 29, 2017, 08:55:20 AM

Code:

vivo/sentinel# ./venv/bin/python bin/sentinel.py
-342: non-JSON HTTP response with '401 Unauthorized' from server
Cannot connect to dashd. Please ensure dashd is running and the JSONRPC port is open to Sentinel.

sentinel.conf

Code:

# specify path to dash.conf or leave blank
# default is the same as DashCore
dash_conf=/root/.vivocore/vivo.conf

# valid options are mainnet, testnet (default=mainnet)
network=mainnet
#network=testnet

# database connection details
db_name=database/sentinel.db
db_driver=sqlite

vivo.conf

Code:

rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=9998
listen=1
server=1
daemon=1
externalip=my ip-address
masternode=1
masternodeprivkey=***

which is correct rpcport?

how to fix the error?

rpcport=12845

lilaj4de

sr. member

Activity: 602

Merit: 250

I stayed in the doubt in relation to the masternodes, that is, my doubt is these masternodes will be of others Coin?

cryptomaxsun

legendary

Activity: 2744

Merit: 1387

Ukrainians will resist

Code:

vivo/sentinel# ./venv/bin/python bin/sentinel.py
-342: non-JSON HTTP response with '401 Unauthorized' from server
Cannot connect to dashd. Please ensure dashd is running and the JSONRPC port is open to Sentinel.

sentinel.conf

Code:

# specify path to dash.conf or leave blank
# default is the same as DashCore
dash_conf=/root/.vivocore/vivo.conf

# valid options are mainnet, testnet (default=mainnet)
network=mainnet
#network=testnet

# database connection details
db_name=database/sentinel.db
db_driver=sqlite

vivo.conf

Code:

rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=9998
listen=1
server=1
daemon=1
externalip=my ip-address
masternode=1
masternodeprivkey=***

which is correct rpcport?

how to fix the error?

degel_x

sr. member

Activity: 434

Merit: 250

Hi guys need some technical advice here, i have an innova masternode, can a vivo masternode coexist in the same server?, or is it recommended a vps per masternode, sorry to greddy to buy a 3 USD/month VPS (Just kidding, but i jst want to take care about just 1 server)

PhaseshiftUK

full member

Activity: 345

Merit: 100

Quote from: PhaseshiftUK on November 25, 2017, 04:44:28 PM

Quote from: Alex68 on November 17, 2017, 09:33:14 AM

In logfile "sentinel-cron.log" I often get error "Unable to submit: Object creation rate limit exceeded" - how to fix it?
normal command "venv/bin/python bin/sentinel.py" when issued manually returns no output

Updated: I just tried again manually and the same message came even from the manual command!
Later 20 times - all normal
it seems like this error happens after a certain wait time

I'm having this problem too. I'm running Ubuntu 16.04. My cron is set up correctly (see below), yet I keep getting "Watchdog expired" and in the sentinel log the same "Unable to submit: Object creation rate limit exceeded". Sentinel is doing my head in!

I'm still having Sentinel issues:

Code:

2017-11-29 04:05:45 No watchdogs exist... submitting new one.
Unable to submit: Object creation rate limit exceeded
2017-11-29 04:05:45 leaving watchdog_check

I believe that this is the cause of why mine keeps falling into "Watchdog_expired".

ddude

full member

Activity: 253

Merit: 101

Quote from: Steven3iii on November 29, 2017, 07:05:05 AM

Nice. Just bought a 1000 for masternode. What are the daily returns? Cool

can I use my own server?

yes you can use your own servers, the rewards are 5 vivo per day, as number of MN's have increased quite a bit.

shibob

full member

Activity: 672

Merit: 154

Blockchain Evangelist.

Quote from: Steven3iii on November 29, 2017, 07:05:05 AM

Nice. Just bought a 1000 for masternode. What are the daily returns? Cool

can I use my own server?

Welcome to the train! The chart looks good now. So way to go!

Steven3iii

full member

Activity: 238

Merit: 100

Nice. Just bought a 1000 for masternode. What are the daily returns? Cool

can I use my own server?

Achillis

newbie

Activity: 28

Merit: 0

Quote from: coinskeeper on November 28, 2017, 01:04:24 PM

Quote from: Zuggcrypto on November 28, 2017, 07:38:12 AM

Quote from: ?? on ??

Please spend your spare time and vote for VIVO to be listed on Mercatox:
https://mercatox.com/auth/register

Sign up first, then vote for free. Please remember one user are allowed to vote maximum 5 votes per month.

Statistics for VIVO today, for now we have totally 509 masternodes in network.
https://masternodes.pro/stats/vivo

3-rd exchange soulds good, it have bigger volumes than coinsmarkets... hopefully that will mean that bots on cryptopia wont be able to rule the prcie for long!

Can someone share voting link?

It will be good if Cryptopia follow Bittrex:
https://support.bittrex.com/hc/en-us/articles/115003004171-What-are-my-trade-limits-

Or be on it Wink

https://support.bittrex.com/hc/en-us/articles/202583854-Submitting-a-Coin-to-Bittrex

coinskeeper

member

Activity: 126

Merit: 10

Quote from: Zuggcrypto on November 28, 2017, 07:38:12 AM

Quote from: ?? on ??

Please spend your spare time and vote for VIVO to be listed on Mercatox:
https://mercatox.com/auth/register

Sign up first, then vote for free. Please remember one user are allowed to vote maximum 5 votes per month.

Statistics for VIVO today, for now we have totally 509 masternodes in network.
https://masternodes.pro/stats/vivo

3-rd exchange soulds good, it have bigger volumes than coinsmarkets... hopefully that will mean that bots on cryptopia wont be able to rule the prcie for long!

Can someone share voting link?

It will be good if Cryptopia follow Bittrex:
https://support.bittrex.com/hc/en-us/articles/115003004171-What-are-my-trade-limits-

Topic: [ANN] VIVO - Masternodes, ASIC-Resistant, Secure, High MN Rewards, Decentralized - page 32. (Read 201583 times)