[ANN]❁ KORE Tor Masternodes, Browser, VoIP, Aether OS, KOREPhone, KOREbay Funded

[p4nt3on]

Hi,

I'm following this forum for several months and with the help of bitcointalk I set up a lot different masternodes. Now that I wanted to setup a KORE mn I encountered a problem that eventually forced me to create an account and post my question. :-)

Can KORE mns be run as a hot wallet setup? I want to leave the collateral in the wallet on the VPS and I tried almost all flags within the configs but:
a) it seems as if the KORE mn does not parse the masternode.conf correctly as 'masternode list-conf' results in an empty array {}
b) debug.log says: CActiveMasternode::ManageStatus() - not capable: Could not connect to <myonionaddress>.onion:10743

See my kore.config below.

I would really appreciate any advice.

Best
p4nt3on

Code:

################################
# basic settings
################################
txindex=1
logtimestamps=1
server=1
listen=1
daemon=1
gen=0
maxconnections=256
staking=0
#externalip=...
#port=10743
#bind=...:10743

################################
# masternode specific settings
################################
masternode=1
masternodeprivkey=...
masternodeaddr=...:10743

#############################
# optional indices
#############################
addressindex=1
timestampindex=1
spentindex=1

#############################
# JSONRPC
#############################
rpcuser=...
rpcpassword=...
rpcallowip=127.0.0.1
rpcport=9932

#############################
# Direct Peer Nodes
#############################
addnode=fzmjhi7xbapufts6.onion
addnode=p6sfbaw762mcqyxg.onion
addnode=b5gacg24h6licg5m.onion
addnode=skrivht2uj3yjluv.onion
addnode=yylyof6avhsmb327.onion
addnode=mpkl5osmeqbc3ekk.onion
addnode=a3pnebzu45dlled2.onion
addnode=6ric6c7mi7ahz2vp.onion
addnode=zidlcde3vmowux3u.onion
addnode=uei3hz5jstv7tfo6.onion
addnode=2id37bekzaqqjcos.onion
addnode=n2yrtxzafo57hzie.onion
addnode=iurptsejm4sjrbpi.onion
addnode=vyohgk7zesm3zl2w.onion
addnode=qaj5jpgvcrrlnwlh.onion
addnode=gvb63xigsmkowrbh.onion
addnode=5dbshryxx7lo2cl5.onion
addnode=7hemavllpt4ratxe.onion
addnode=kjcvxfytfbzvqely.onion
addnode=db24lr474vczwz5a.onion

[1713974429]

1713974429

[1713974429]

1713974429

[1713974429]

1713974429

[Chiraag001]

I found a post today: "https://bitcointalk.org/index.php?topic=2096416.0


IMO this is a 30x potential and maybe even a x50-60?

Can anyone else see this?

Its listed on Bittrex only"

Is it just shilling or serious?

I wrote this and I was serious. Look at all the privacy coins marketcap. Look at Bitbay marketcap.

[MikeMike]

I found a post today: "https://bitcointalk.org/index.php?topic=2096416.0


IMO this is a 30x potential and maybe even a x50-60?

Can anyone else see this?

Its listed on Bittrex only"

Is it just shilling or serious?

I wrote this and I was serious. Look at all the privacy coins marketcap. Look at Bitbay marketcap.

Once KORE wallet bugs are all worked out and the Surf's Up! browser is released we will
open be marketing KORE in earnest.
Might take 2 to 3 updates to get to that point.

[CryptoNick]

Hi,

I'm following this forum for several months and with the help of bitcointalk I set up a lot different masternodes. Now that I wanted to setup a KORE mn I encountered a problem that eventually forced me to create an account and post my question. :-)

Can KORE mns be run as a hot wallet setup? I want to leave the collateral in the wallet on the VPS and I tried almost all flags within the configs but:
a) it seems as if the KORE mn does not parse the masternode.conf correctly as 'masternode list-conf' results in an empty array {}
b) debug.log says: CActiveMasternode::ManageStatus() - not capable: Could not connect to <myonionaddress>.onion:10743

See my kore.config below.

I would really appreciate any advice.

Best
p4nt3on

Code:

################################
# basic settings
################################
txindex=1
logtimestamps=1
server=1
listen=1
daemon=1
gen=0
maxconnections=256
staking=0
#externalip=...
#port=10743
#bind=...:10743

################################
# masternode specific settings
################################
masternode=1
masternodeprivkey=...
masternodeaddr=...:10743

#############################
# optional indices
#############################
addressindex=1
timestampindex=1
spentindex=1

#############################
# JSONRPC
#############################
rpcuser=...
rpcpassword=...
rpcallowip=127.0.0.1
rpcport=9932

#############################
# Direct Peer Nodes
#############################
addnode=fzmjhi7xbapufts6.onion
addnode=p6sfbaw762mcqyxg.onion
addnode=b5gacg24h6licg5m.onion
addnode=skrivht2uj3yjluv.onion
addnode=yylyof6avhsmb327.onion
addnode=mpkl5osmeqbc3ekk.onion
addnode=a3pnebzu45dlled2.onion
addnode=6ric6c7mi7ahz2vp.onion
addnode=zidlcde3vmowux3u.onion
addnode=uei3hz5jstv7tfo6.onion
addnode=2id37bekzaqqjcos.onion
addnode=n2yrtxzafo57hzie.onion
addnode=iurptsejm4sjrbpi.onion
addnode=vyohgk7zesm3zl2w.onion
addnode=qaj5jpgvcrrlnwlh.onion
addnode=gvb63xigsmkowrbh.onion
addnode=5dbshryxx7lo2cl5.onion
addnode=7hemavllpt4ratxe.onion
addnode=kjcvxfytfbzvqely.onion
addnode=db24lr474vczwz5a.onion

Have you edited the Masternode.conf file? What you posted is your Kore.conf file. There is a guide on Kore.Life that shows how to set up the VPS and Local Wallet. So I would assume you take the Local wallet settings and use them in your Remote VPS Masternode.conf file there but don't use a local onion. If the RAW TX Data is not being broadcast on the network you will get that error. So you would need to use the same onion address as the Masternode instead of a Local Onion address and send the coin from the MN and to the MN and then copy the RAW TX data from the VPS screen.

That entire step has to be done or you will get that - not capable: error

[p4nt3on]

Hi,

I'm following this forum for several months and with the help of bitcointalk I set up a lot different masternodes. Now that I wanted to setup a KORE mn I encountered a problem that eventually forced me to create an account and post my question. :-)

Can KORE mns be run as a hot wallet setup? I want to leave the collateral in the wallet on the VPS and I tried almost all flags within the configs but:
a) it seems as if the KORE mn does not parse the masternode.conf correctly as 'masternode list-conf' results in an empty array {}
b) debug.log says: CActiveMasternode::ManageStatus() - not capable: Could not connect to <myonionaddress>.onion:10743

See my kore.config below.

I would really appreciate any advice.

Best
p4nt3on

Code:

################################
# basic settings
################################
txindex=1
logtimestamps=1
server=1
listen=1
daemon=1
gen=0
maxconnections=256
staking=0
#externalip=...
#port=10743
#bind=...:10743

################################
# masternode specific settings
################################
masternode=1
masternodeprivkey=...
masternodeaddr=...:10743

#############################
# optional indices
#############################
addressindex=1
timestampindex=1
spentindex=1

#############################
# JSONRPC
#############################
rpcuser=...
rpcpassword=...
rpcallowip=127.0.0.1
rpcport=9932

#############################
# Direct Peer Nodes
#############################
addnode=fzmjhi7xbapufts6.onion
addnode=p6sfbaw762mcqyxg.onion
addnode=b5gacg24h6licg5m.onion
addnode=skrivht2uj3yjluv.onion
addnode=yylyof6avhsmb327.onion
addnode=mpkl5osmeqbc3ekk.onion
addnode=a3pnebzu45dlled2.onion
addnode=6ric6c7mi7ahz2vp.onion
addnode=zidlcde3vmowux3u.onion
addnode=uei3hz5jstv7tfo6.onion
addnode=2id37bekzaqqjcos.onion
addnode=n2yrtxzafo57hzie.onion
addnode=iurptsejm4sjrbpi.onion
addnode=vyohgk7zesm3zl2w.onion
addnode=qaj5jpgvcrrlnwlh.onion
addnode=gvb63xigsmkowrbh.onion
addnode=5dbshryxx7lo2cl5.onion
addnode=7hemavllpt4ratxe.onion
addnode=kjcvxfytfbzvqely.onion
addnode=db24lr474vczwz5a.onion

Have you edited the Masternode.conf file? What you posted is your Kore.conf file. There is a guide on Kore.Life that shows how to set up the VPS and Local Wallet. So I would assume you take the Local wallet settings and use them in your Remote VPS Masternode.conf file there but don't use a local onion. If the RAW TX Data is not being broadcast on the network you will get that error. So you would need to use the same onion address as the Masternode instead of a Local Onion address and send the coin from the MN and to the MN and then copy the RAW TX data from the VPS screen.

That entire step has to be done or you will get that - not capable: error

Hi CryptoNick,

thank you for your fast response. Of course I updated the masternode.conf file. I also followed the guide on kore.life but it doesn't cover hot wallet setups - it's more a guide for a cold wallet setup...

I used the same onion address (from ~/.kore/onion/hostname) in the following config directives:
- masternode.conf: (mn0 <my_masternode>.onion:10743 <masternodeprivkey> <txid> <txvout>)
- kore.conf - masternodeaddr=<my_masternode>.onion:10743
- kore.conf - bind=<my_masternode>.onion:10743
- kore.conf - externalip=<my_masternode>.onion

But it shows up the same error over and over again. I actually sent the collateral transaction from one MN wallet address to another and used the txid/txvout in the masternode.conf file, so I'm not sure what could be wrong. 

[Chiraag001]

I found a post today: "https://bitcointalk.org/index.php?topic=2096416.0


IMO this is a 30x potential and maybe even a x50-60?

Can anyone else see this?

Its listed on Bittrex only"

Is it just shilling or serious?

I wrote this and I was serious. Look at all the privacy coins marketcap. Look at Bitbay marketcap.

Once KORE wallet bugs are all worked out and the Surf's Up! browser is released we will
open be marketing KORE in earnest.
Might take 2 to 3 updates to get to that point.

Sounds good brother! The current roadmap looks really good - there is a lot to come - do you have a rough idea of how long those features will take to develop.

In any case in The meantime ill keep toppping up  lol  

[TheMatrix101]

Hi,

I'm following this forum for several months and with the help of bitcointalk I set up a lot different masternodes. Now that I wanted to setup a KORE mn I encountered a problem that eventually forced me to create an account and post my question. :-)

Can KORE mns be run as a hot wallet setup? I want to leave the collateral in the wallet on the VPS and I tried almost all flags within the configs but:
a) it seems as if the KORE mn does not parse the masternode.conf correctly as 'masternode list-conf' results in an empty array {}
b) debug.log says: CActiveMasternode::ManageStatus() - not capable: Could not connect to <myonionaddress>.onion:10743

See my kore.config below.

I would really appreciate any advice.

Best
p4nt3on

Code:

################################
# basic settings
################################
txindex=1
logtimestamps=1
server=1
listen=1
daemon=1
gen=0
maxconnections=256
staking=0
#externalip=...
#port=10743
#bind=...:10743

################################
# masternode specific settings
################################
masternode=1
masternodeprivkey=...
masternodeaddr=...:10743

#############################
# optional indices
#############################
addressindex=1
timestampindex=1
spentindex=1

#############################
# JSONRPC
#############################
rpcuser=...
rpcpassword=...
rpcallowip=127.0.0.1
rpcport=9932

#############################
# Direct Peer Nodes
#############################
addnode=fzmjhi7xbapufts6.onion
addnode=p6sfbaw762mcqyxg.onion
addnode=b5gacg24h6licg5m.onion
addnode=skrivht2uj3yjluv.onion
addnode=yylyof6avhsmb327.onion
addnode=mpkl5osmeqbc3ekk.onion
addnode=a3pnebzu45dlled2.onion
addnode=6ric6c7mi7ahz2vp.onion
addnode=zidlcde3vmowux3u.onion
addnode=uei3hz5jstv7tfo6.onion
addnode=2id37bekzaqqjcos.onion
addnode=n2yrtxzafo57hzie.onion
addnode=iurptsejm4sjrbpi.onion
addnode=vyohgk7zesm3zl2w.onion
addnode=qaj5jpgvcrrlnwlh.onion
addnode=gvb63xigsmkowrbh.onion
addnode=5dbshryxx7lo2cl5.onion
addnode=7hemavllpt4ratxe.onion
addnode=kjcvxfytfbzvqely.onion
addnode=db24lr474vczwz5a.onion

Have you edited the Masternode.conf file? What you posted is your Kore.conf file. There is a guide on Kore.Life that shows how to set up the VPS and Local Wallet. So I would assume you take the Local wallet settings and use them in your Remote VPS Masternode.conf file there but don't use a local onion. If the RAW TX Data is not being broadcast on the network you will get that error. So you would need to use the same onion address as the Masternode instead of a Local Onion address and send the coin from the MN and to the MN and then copy the RAW TX data from the VPS screen.

That entire step has to be done or you will get that - not capable: error

Hi CryptoNick,

thank you for your fast response. Of course I updated the masternode.conf file. I also followed the guide on kore.life but it doesn't cover hot wallet setups - it's more a guide for a cold wallet setup...

I used the same onion address (from ~/.kore/onion/hostname) in the following config directives:
- masternode.conf: (mn0 <my_masternode>.onion:10743 <masternodeprivkey> <txid> <txvout>)
- kore.conf - masternodeaddr=<my_masternode>.onion:10743
- kore.conf - bind=<my_masternode>.onion:10743
- kore.conf - externalip=<my_masternode>.onion

But it shows up the same error over and over again. I actually sent the collateral transaction from one MN wallet address to another and used the txid/txvout in the masternode.conf file, so I'm not sure what could be wrong. 

KORE MNs are meant to be hot/cold that is why the walkthrough is for that. I believe there is a way to do a hot setup a little wonky like but I don't know it/wouldn't advise you do it that way

an alternative?
Maybe do the hot/cold then ftp your local wallet.dat to your server so you dont have to worry about it?

Hope I helped
Matrix

[Mxrider420z]

Hello guys how you doing?,

If you use Teamviewer please update it to the latest version as there is a vulnerability that can give unathorized remote access

https://blog.malwarebytes.com/cybercrime/2017/12/use-teamviewer-fix-this-dangerous-permissions-bug-with-an-update/

If you can live without teamviewer thats the best option as they are NSA/CIA partner all indicates.

Wanna take the time to wish a merry christmas and happy new year to all.

The team is hard working and will continue working through the holidays.

Cheers,

Mx

[2bfree]

can someone give me a short pitch why this is better then any other coin out there and what does Kore mean???

[MikeMike]

can someone give me a short pitch why this is better then any other coin out there and what does Kore mean???

Read the complete OP page.
Then read it again.
https://bitcointalk.org/index.php?topic=2096416.msg20949347#msg20949347

MikeMike

[CryptoNick]

Hi,

I'm following this forum for several months and with the help of bitcointalk I set up a lot different masternodes. Now that I wanted to setup a KORE mn I encountered a problem that eventually forced me to create an account and post my question. :-)

Can KORE mns be run as a hot wallet setup? I want to leave the collateral in the wallet on the VPS and I tried almost all flags within the configs but:
a) it seems as if the KORE mn does not parse the masternode.conf correctly as 'masternode list-conf' results in an empty array {}
b) debug.log says: CActiveMasternode::ManageStatus() - not capable: Could not connect to <myonionaddress>.onion:10743

See my kore.config below.

I would really appreciate any advice.

Best
p4nt3on

Code:

################################
# basic settings
################################
txindex=1
logtimestamps=1
server=1
listen=1
daemon=1
gen=0
maxconnections=256
staking=0
#externalip=...
#port=10743
#bind=...:10743

################################
# masternode specific settings
################################
masternode=1
masternodeprivkey=...
masternodeaddr=...:10743

#############################
# optional indices
#############################
addressindex=1
timestampindex=1
spentindex=1

#############################
# JSONRPC
#############################
rpcuser=...
rpcpassword=...
rpcallowip=127.0.0.1
rpcport=9932

#############################
# Direct Peer Nodes
#############################
addnode=fzmjhi7xbapufts6.onion
addnode=p6sfbaw762mcqyxg.onion
addnode=b5gacg24h6licg5m.onion
addnode=skrivht2uj3yjluv.onion
addnode=yylyof6avhsmb327.onion
addnode=mpkl5osmeqbc3ekk.onion
addnode=a3pnebzu45dlled2.onion
addnode=6ric6c7mi7ahz2vp.onion
addnode=zidlcde3vmowux3u.onion
addnode=uei3hz5jstv7tfo6.onion
addnode=2id37bekzaqqjcos.onion
addnode=n2yrtxzafo57hzie.onion
addnode=iurptsejm4sjrbpi.onion
addnode=vyohgk7zesm3zl2w.onion
addnode=qaj5jpgvcrrlnwlh.onion
addnode=gvb63xigsmkowrbh.onion
addnode=5dbshryxx7lo2cl5.onion
addnode=7hemavllpt4ratxe.onion
addnode=kjcvxfytfbzvqely.onion
addnode=db24lr474vczwz5a.onion

Have you edited the Masternode.conf file? What you posted is your Kore.conf file. There is a guide on Kore.Life that shows how to set up the VPS and Local Wallet. So I would assume you take the Local wallet settings and use them in your Remote VPS Masternode.conf file there but don't use a local onion. If the RAW TX Data is not being broadcast on the network you will get that error. So you would need to use the same onion address as the Masternode instead of a Local Onion address and send the coin from the MN and to the MN and then copy the RAW TX data from the VPS screen.

That entire step has to be done or you will get that - not capable: error

Hi CryptoNick,

thank you for your fast response. Of course I updated the masternode.conf file. I also followed the guide on kore.life but it doesn't cover hot wallet setups - it's more a guide for a cold wallet setup...

I used the same onion address (from ~/.kore/onion/hostname) in the following config directives:
- masternode.conf: (mn0 <my_masternode>.onion:10743 <masternodeprivkey> <txid> <txvout>)
- kore.conf - masternodeaddr=<my_masternode>.onion:10743
- kore.conf - bind=<my_masternode>.onion:10743
- kore.conf - externalip=<my_masternode>.onion

But it shows up the same error over and over again. I actually sent the collateral transaction from one MN wallet address to another and used the txid/txvout in the masternode.conf file, so I'm not sure what could be wrong.  

Try this:
masternode start -all <passphrase>

I think you just need to initialize the masternode since there is no GUI it was a step that is missing from the local wallet. Loading the Config doesn't start the Masternode.

Then to clear your passphrase from the history use this:
cat /dev/null > ~/.bash_history && history -c && exit
or just edit the .bash_history file to get rid of your passphrase entries.

[p4nt3on]

Hi,

I'm following this forum for several months and with the help of bitcointalk I set up a lot different masternodes. Now that I wanted to setup a KORE mn I encountered a problem that eventually forced me to create an account and post my question. :-)

Can KORE mns be run as a hot wallet setup? I want to leave the collateral in the wallet on the VPS and I tried almost all flags within the configs but:
a) it seems as if the KORE mn does not parse the masternode.conf correctly as 'masternode list-conf' results in an empty array {}
b) debug.log says: CActiveMasternode::ManageStatus() - not capable: Could not connect to <myonionaddress>.onion:10743

See my kore.config below.

I would really appreciate any advice.

Best
p4nt3on

Code:

################################
# basic settings
################################
txindex=1
logtimestamps=1
server=1
listen=1
daemon=1
gen=0
maxconnections=256
staking=0
#externalip=...
#port=10743
#bind=...:10743

################################
# masternode specific settings
################################
masternode=1
masternodeprivkey=...
masternodeaddr=...:10743

#############################
# optional indices
#############################
addressindex=1
timestampindex=1
spentindex=1

#############################
# JSONRPC
#############################
rpcuser=...
rpcpassword=...
rpcallowip=127.0.0.1
rpcport=9932

#############################
# Direct Peer Nodes
#############################
addnode=fzmjhi7xbapufts6.onion
addnode=p6sfbaw762mcqyxg.onion
addnode=b5gacg24h6licg5m.onion
addnode=skrivht2uj3yjluv.onion
addnode=yylyof6avhsmb327.onion
addnode=mpkl5osmeqbc3ekk.onion
addnode=a3pnebzu45dlled2.onion
addnode=6ric6c7mi7ahz2vp.onion
addnode=zidlcde3vmowux3u.onion
addnode=uei3hz5jstv7tfo6.onion
addnode=2id37bekzaqqjcos.onion
addnode=n2yrtxzafo57hzie.onion
addnode=iurptsejm4sjrbpi.onion
addnode=vyohgk7zesm3zl2w.onion
addnode=qaj5jpgvcrrlnwlh.onion
addnode=gvb63xigsmkowrbh.onion
addnode=5dbshryxx7lo2cl5.onion
addnode=7hemavllpt4ratxe.onion
addnode=kjcvxfytfbzvqely.onion
addnode=db24lr474vczwz5a.onion

Have you edited the Masternode.conf file? What you posted is your Kore.conf file. There is a guide on Kore.Life that shows how to set up the VPS and Local Wallet. So I would assume you take the Local wallet settings and use them in your Remote VPS Masternode.conf file there but don't use a local onion. If the RAW TX Data is not being broadcast on the network you will get that error. So you would need to use the same onion address as the Masternode instead of a Local Onion address and send the coin from the MN and to the MN and then copy the RAW TX data from the VPS screen.

That entire step has to be done or you will get that - not capable: error

Hi CryptoNick,

thank you for your fast response. Of course I updated the masternode.conf file. I also followed the guide on kore.life but it doesn't cover hot wallet setups - it's more a guide for a cold wallet setup...

I used the same onion address (from ~/.kore/onion/hostname) in the following config directives:
- masternode.conf: (mn0 <my_masternode>.onion:10743 <masternodeprivkey> <txid> <txvout>)
- kore.conf - masternodeaddr=<my_masternode>.onion:10743
- kore.conf - bind=<my_masternode>.onion:10743
- kore.conf - externalip=<my_masternode>.onion

But it shows up the same error over and over again. I actually sent the collateral transaction from one MN wallet address to another and used the txid/txvout in the masternode.conf file, so I'm not sure what could be wrong.  

Try this:
masternode start -all <passphrase>

I think you just need to initialize the masternode since there is no GUI it was a step that is missing from the local wallet. Loading the Config doesn't start the Masternode.

Then to clear your passphrase from the history use this:
cat /dev/null > ~/.bash_history && history -c && exit
or just edit the .bash_history file to get rid of your passphrase entries.

I tried it this way, but it didn't work - same error message. Actually the command "masternode start-alias mn0" would do the same as the one you mentioned.
"masternode list-conf" should return the config of the MN if parsed correctly from masternode.conf, but it results in an empty array, so from my perspective the parsing step fails.

[CryptoNick]

Hi,

I'm following this forum for several months and with the help of bitcointalk I set up a lot different masternodes. Now that I wanted to setup a KORE mn I encountered a problem that eventually forced me to create an account and post my question. :-)

Can KORE mns be run as a hot wallet setup? I want to leave the collateral in the wallet on the VPS and I tried almost all flags within the configs but:
a) it seems as if the KORE mn does not parse the masternode.conf correctly as 'masternode list-conf' results in an empty array {}
b) debug.log says: CActiveMasternode::ManageStatus() - not capable: Could not connect to <myonionaddress>.onion:10743

See my kore.config below.

I would really appreciate any advice.

Best
p4nt3on

Code:

################################
# basic settings
################################
txindex=1
logtimestamps=1
server=1
listen=1
daemon=1
gen=0
maxconnections=256
staking=0
#externalip=...
#port=10743
#bind=...:10743

################################
# masternode specific settings
################################
masternode=1
masternodeprivkey=...
masternodeaddr=...:10743

#############################
# optional indices
#############################
addressindex=1
timestampindex=1
spentindex=1

#############################
# JSONRPC
#############################
rpcuser=...
rpcpassword=...
rpcallowip=127.0.0.1
rpcport=9932

#############################
# Direct Peer Nodes
#############################
addnode=fzmjhi7xbapufts6.onion
addnode=p6sfbaw762mcqyxg.onion
addnode=b5gacg24h6licg5m.onion
addnode=skrivht2uj3yjluv.onion
addnode=yylyof6avhsmb327.onion
addnode=mpkl5osmeqbc3ekk.onion
addnode=a3pnebzu45dlled2.onion
addnode=6ric6c7mi7ahz2vp.onion
addnode=zidlcde3vmowux3u.onion
addnode=uei3hz5jstv7tfo6.onion
addnode=2id37bekzaqqjcos.onion
addnode=n2yrtxzafo57hzie.onion
addnode=iurptsejm4sjrbpi.onion
addnode=vyohgk7zesm3zl2w.onion
addnode=qaj5jpgvcrrlnwlh.onion
addnode=gvb63xigsmkowrbh.onion
addnode=5dbshryxx7lo2cl5.onion
addnode=7hemavllpt4ratxe.onion
addnode=kjcvxfytfbzvqely.onion
addnode=db24lr474vczwz5a.onion

Have you edited the Masternode.conf file? What you posted is your Kore.conf file. There is a guide on Kore.Life that shows how to set up the VPS and Local Wallet. So I would assume you take the Local wallet settings and use them in your Remote VPS Masternode.conf file there but don't use a local onion. If the RAW TX Data is not being broadcast on the network you will get that error. So you would need to use the same onion address as the Masternode instead of a Local Onion address and send the coin from the MN and to the MN and then copy the RAW TX data from the VPS screen.

That entire step has to be done or you will get that - not capable: error

Hi CryptoNick,

thank you for your fast response. Of course I updated the masternode.conf file. I also followed the guide on kore.life but it doesn't cover hot wallet setups - it's more a guide for a cold wallet setup...

I used the same onion address (from ~/.kore/onion/hostname) in the following config directives:
- masternode.conf: (mn0 <my_masternode>.onion:10743 <masternodeprivkey> <txid> <txvout>)
- kore.conf - masternodeaddr=<my_masternode>.onion:10743
- kore.conf - bind=<my_masternode>.onion:10743
- kore.conf - externalip=<my_masternode>.onion

But it shows up the same error over and over again. I actually sent the collateral transaction from one MN wallet address to another and used the txid/txvout in the masternode.conf file, so I'm not sure what could be wrong.  

Try this:
masternode start -all <passphrase>

I think you just need to initialize the masternode since there is no GUI it was a step that is missing from the local wallet. Loading the Config doesn't start the Masternode.

Then to clear your passphrase from the history use this:
cat /dev/null > ~/.bash_history && history -c && exit
or just edit the .bash_history file to get rid of your passphrase entries.

I tried it this way, but it didn't work - same error message. Actually the command "masternode start-alias mn0" would do the same as the one you mentioned.
"masternode list-conf" should return the config of the MN if parsed correctly from masternode.conf, but it results in an empty array, so from my perspective the parsing step fails.

Probably because the masternode command is not available in the daemon only the CLI. They work separately.

[darkthan]

i hope that kore team has enjoyed christmas and prepared news for 2018 !!!

[MikeMike]

i hope that kore team has enjoyed christmas and prepared news for 2018 !!!

Judging by the way 2017 closed out,.. 208 is going to be one heck of a year for KORE!
 

[jbjb1234]

What’s the word... ah yes, hodl. Fingers crossed for a good dev update in the new year.

[Mxrider420z]

i hope that kore team has enjoyed christmas and prepared news for 2018 !!!

Judging by the way 2017 closed out,.. 208 is going to be one heck of a year for KORE!
 

2018 should be a life changing year.

Hey guys how you doing?

Ohh yeah 2018 will be a great year for Kore and good cryptos

Go Kore, Go BTC

[reffi]

wow internet coins finally starting to rise!! NEOS and SHIFT going crazy!  Hope KORE can join the momentum soon with good news! Now is the time!!!!!!!!!!

[MikeMike]

wow internet coins finally starting to rise!! NEOS and SHIFT going crazy!  Hope KORE can join the momentum soon with good news! Now is the time!!!!!!!!!!

KORE has its own pattern of price movements.
To try to compare it to others or expect it to behave like others is futile.

[MikeMike]

For those helping to test the Windows  32 and 64 bit wallets
a new version is on the GIT.

MikeMike