Quote from: dmz241 on August 17, 2018, 06:50:00 AM

Quote from: TheMatrix101 on August 16, 2018, 05:03:36 PM

Quote from: dmz241 on August 16, 2018, 03:08:03 AM

I was on Kore Core version v0.12.5.0-aefd2fa-dirty (64-bit) I am guessing thats not working so it was blocked. How are you able to block wallets doesnt that go against decentralization if you can just block people? Also do I just need to download the new wallet and run that or do I need to remove all the synced data and run from scratch?

Are you insinuating that BITCOIN AND ALL OTHER COINS are centralized? If so, then yes, we are centralized.

]

Make sure you know your stuff before you falsely accuse a team of centralization. Im also curious how you think forks work. YOUR wallet wasnt blocked. your PROTOCOL was blocked along with everyone else running that protocol and below, mainly because they were causing massive network issues. Now your wallet CAN be blocked (or rather temporarily banned) by other wallets because of sending bad blocks and bad updates but that has nothing to do with team singling out a single wallet and saying it can't connect to the network. there are requirements that need to be met before you can access the network. first and foremost is tor. If you aren't on tor then you can't connect to the network, is that centralization? Our wallet, exactly like bitcoin, is open-source. If you dont like banning old peers for network stability (remember even bitcoin does this!) then it is easily within your power to fork the kore repository and make your own version of KORE that allows for all old peers to connect, however you will not be allowed to connect to the kore network without the adequate requirements being met, just like Bitcoin.

as for your other questions its easy to block old peers, in fact here is the commit i did that did it.

https://github.com/Kore-Core/KORE/commit/5cc4fa3e9b430fbc6115f661d325a74f26429378#diff-c61070c281aed6ded69036c08bd08add
and here is the commit of bitcoin doing a similar thing.
https://github.com/bitcoin/bitcoin/commit/1ce418929a17c063a0a2e3b176b82d280ef053a6#diff-c61070c281aed6ded69036c08bd08add

You should be able to download the new wallet and run and sync with the chain but seeing as its been a while since i implemented the higher min protocol version, and thus you probably went off on a fork with the old pre-implementation chain, then you might have to attempt to reindex.

Matrix

Matrix, I am not accusing anyone of anything. I am trying to understand how it is possible even if it is possible in bitcoin. Its for self learning. I have always been a supporter here and there are no hard feelings here. Thanks for the detailed information as I truly dont understand the technical side of wallets and this is an eye opener also. Again I ask these questions to learn not to play a blame game. I guess I put the question wrong maybe thats what offended you.

I appologize then, how i read it sounded like it was.
How it works is relatively simple. when a wallet connects to another wallet it sends it's information
essentially:
"hi im koreisawesome.onion, here is my current block and this is the protocol im running, can i connect?"
the reply returns the same info but from the other wallet
"hi koreisawesome.onion, sure you can connect, here is my protocol and information"

now if its an old protocol it would essentially be like:
"hi im koreisawesome.onion, here is my current block and this is the protocol im running, can i connect?"
"no"

you can run the command kore-cli getpeerinfo to get the info the wallets are sending eachother

Code:

{
"id": 1843,
"addr": "hggmh3vhkjebz4j5.onion",
"services": "0000000000000005",
"relaytxes": true,
"lastsend": 1534615596,
"lastrecv": 1534615597,
"bytessent": 239236,
"bytesrecv": 254434,
"conntime": 1534609655,
"timeoffset": -8,
"pingtime": 0.990347,
"minping": 0.720863,
"version": 70101,
"subver": "/Kore:0.12.6.2/",
"inbound": false,
"startingheight": 269444,
"banscore": 0,
"synced_headers": 269502,
"synced_blocks": 269502,
"inflight": [
],
"whitelisted": false,
"bytessent_per_msg": {
"addr": 55,
"dseep": 139160,
"getaddr": 24,
"getdata": 3477,
"getheaders": 1021,
"headers": 4218,
"inv": 83811,
"mnb": 416,
"mnp": 2907,
"mnw": 322,
"ping": 1764,
"pong": 1568,
"sendheaders": 24,
"ssc": 320,
"verack": 24,
"version": 125
},
"bytesrecv_per_msg": {
"*other*": 146420,
"addr": 4970,
"block": 8703,
"getdata": 1220,
"getheaders": 1021,
"headers": 5472,
"inv": 82803,
"ping": 1764,
"pong": 1568,
"sendheaders": 24,
"ssc": 320,
"verack": 24,
"version": 125
}
},

you can see in the example above
"version": 70101
this is the protocol version that the wallet is looking at, it relates to the network requests that that wallet can send and receive.
all we do then is tell the wallet "hey if the 'version' is below this number, dont allow it to connect"

hope that helped

Matrix