Bitcoin Forum
November 13, 2018, 11:49:33 PM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
   Home   Help Search Login Register More  
Pages: « 1 ... 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 [380] 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 »
  Print  
Author Topic: [ANN][KARM] Karma / ₭ / X11  (Read 572415 times)
warfwarf
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
June 07, 2015, 06:20:20 PM
 #7581

This is another one among the series I am planning to do:

http://i.imgur.com/Q9lzLrx.png
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1542152973
Hero Member
*
Offline Offline

Posts: 1542152973

View Profile Personal Message (Offline)

Ignore
1542152973
Reply with quote  #2

1542152973
Report to moderator
1542152973
Hero Member
*
Offline Offline

Posts: 1542152973

View Profile Personal Message (Offline)

Ignore
1542152973
Reply with quote  #2

1542152973
Report to moderator
Alphi
Hero Member
*****
Offline Offline

Activity: 798
Merit: 1000


View Profile
June 07, 2015, 07:16:17 PM
 #7582

I uploaded my peers.dat file if anyone is having issues connecting to the network.
peers.dat keeps track of a list of all connections you have made with other karma wallet users.
It does not contain any personal information and so can be deleted or overwritten without affecting your coin holdings.

in order to keep this file updated and running smoothly, you should run our wallet and allow it to fully sync at least once a month.

https://www.dropbox.com/s/dkkxrslilob9pwa/peers.dat?dl=0

please make sure you backup your wallet.dat file ALWAYS before copying any files into your karma data folder.

KARMA: KSc9oGgGga1TS4PqZNFxNS9LSDjdSgpC1B      VERT: VgKaooA5ZuLLUXTUANJigH9wCPuzBUBv9H
DOGE:   DRN7pXid34o6wQgUuK8BoSjWJ5g8jiEs4e
thevictimofuktyranny
Legendary
*
Offline Offline

Activity: 1078
Merit: 1001


View Profile
June 07, 2015, 07:27:30 PM
 #7583

I uploaded my peers.dat file if anyone is having issues connecting to the network.
peers.dat keeps track of a list of all connections you have made with other karma wallet users.
It does not contain any personal information and so can be deleted or overwritten without affecting your coin holdings.

in order to keep this file updated and running smoothly, you should run our wallet and allow it to fully sync at least once a month.

https://www.dropbox.com/s/dkkxrslilob9pwa/peers.dat?dl=0

please make sure you backup your wallet.dat file ALWAYS before copying any files into your karma data folder.


Yep, that peers.dat file has sorted out the problem Smiley
Alphi
Hero Member
*****
Offline Offline

Activity: 798
Merit: 1000


View Profile
June 07, 2015, 07:55:00 PM
 #7584

Yep, that peers.dat file has sorted out the problem Smiley

no problemo.. it usually does.. I like to keep my list of peers updated.

KARMA: KSc9oGgGga1TS4PqZNFxNS9LSDjdSgpC1B      VERT: VgKaooA5ZuLLUXTUANJigH9wCPuzBUBv9H
DOGE:   DRN7pXid34o6wQgUuK8BoSjWJ5g8jiEs4e
batesresearch
Legendary
*
Offline Offline

Activity: 1736
Merit: 1056


View Profile WWW
June 07, 2015, 08:03:57 PM
 #7585

This is another one among the series I am planning to do:



Another great video!

Fallen down the crypto rabbithole!
bondi
Sr. Member
****
Offline Offline

Activity: 344
Merit: 250


View Profile
June 07, 2015, 08:12:35 PM
 #7586

Just sharing a video about Karma....



Great video.
Thanks for uploading.
bondi
Sr. Member
****
Offline Offline

Activity: 344
Merit: 250


View Profile
June 07, 2015, 08:13:07 PM
 #7587

This is another one among the series I am planning to do:



Good one.
Keep them coming Smiley
easteagle13
Hero Member
*****
Offline Offline

Activity: 658
Merit: 500


View Profile
June 08, 2015, 07:39:35 AM
 #7588

This is another one among the series I am planning to do:



Good job warf!

TIP ME ₭ARMA:  KJeEKJv1LXHM8cYeRgQG3q87BFA4W3sTGg  FOR KARMA TRANSLATION BUDGET SEND TO: KHvkhA7RTFnG8N5RWPB48gs2y8K1od6xF4
OFF. ₭ARMA FB PAGE: https://www.facebook.com/karmacoin.me. http://lill.com
socoban
Sr. Member
****
Offline Offline

Activity: 316
Merit: 250


View Profile
June 08, 2015, 07:57:04 AM
 #7589

Just sharing a video about Karma....



What software did you use for that video creation? Expecially what software did you use to syntetize the voice? I am seeking for free voice syntetizer(Google translate has a voice syntetizer, but it is not officially available ).  Thanks
Angora
Full Member
***
Offline Offline

Activity: 241
Merit: 100


View Profile
June 08, 2015, 09:35:04 PM
 #7590

Need some help getting my windows wallet to sync.  Been running it non-stop for a week and can not get past block 636559.

client version : v0.8.6.5-beta
Open SSL version: OpenSSL 1.0.1h 5 Jun 2014
current block: 636559
total blocks: 748068

debug log:

2015-06-08 21:24:59 received block ec7f0fe68216f49888e9155394c7cd9ae5068eb0e9666ba938b96f42a3006dd4
2015-06-08 21:24:59 Difficulty Retarget - Kimoto Gravity Well
2015-06-08 21:24:59 PastRateAdjustmentRatio = 1.07017
2015-06-08 21:24:59 Before: 1c28b268  0000000028b26800000000000000000000000000000000000000000000000000
2015-06-08 21:24:59 After:  1c28ce95  0000000028ce954cbc955540b48f17ed8499c95fdd14d47be3d6a3d6baee0ab9
2015-06-08 21:25:00 InvalidChainFound: invalid block=ec7f0fe68216f49888e9155394c7cd9ae5068eb0e9666ba938b96f42a3006dd4  height=701317  log2_work=55.148925  date=2015-06-08 21:25:37
2015-06-08 21:25:00 InvalidChainFound:  current best=0744049604bea9d5953e94cbf044fecc291c8137e6f4a6576a33130fc7d4f9fc  height=636559  log2_work=55.121487  date=2015-04-23 23:33:00
2015-06-08 21:25:00 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-06-08 21:25:00 ProcessBlock: ACCEPTED

PEERS INFO:

{
"addr" : "110.23.43.140:9432",
"services" : "00000003",
"lastsend" : 1433799032,
"lastrecv" : 1433799088,
"bytessent" : 443271,
"bytesrecv" : 7082683,
"blocksrequested" : 0,
"conntime" : 1433795525,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701280,
"banscore" : 0
},
{
"addr" : "92.222.38.197:9432",
"services" : "00000003",
"lastsend" : 1433799137,
"lastrecv" : 1433799086,
"bytessent" : 442389,
"bytesrecv" : 7079719,
"blocksrequested" : 0,
"conntime" : 1433795545,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701281,
"banscore" : 0
},
{
"addr" : "188.165.2.147:9432",
"services" : "00000003",
"lastsend" : 1433799063,
"lastrecv" : 1433799089,
"bytessent" : 578598,
"bytesrecv" : 9421922,
"blocksrequested" : 0,
"conntime" : 1433795545,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701281,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "24.15.13.38:9432",
"services" : "00000003",
"lastsend" : 1433799086,
"lastrecv" : 1433799086,
"bytessent" : 304592,
"bytesrecv" : 4753137,
"blocksrequested" : 0,
"conntime" : 1433795575,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701282,
"banscore" : 0
},
{
"addr" : "212.25.36.96:9432",
"services" : "00000003",
"lastsend" : 1433798984,
"lastrecv" : 1433799097,
"bytessent" : 162224,
"bytesrecv" : 2412196,
"blocksrequested" : 0,
"conntime" : 1433795581,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701282,
"banscore" : 0
},
{
"addr" : "125.237.57.107:9432",
"services" : "00000003",
"lastsend" : 1433799033,
"lastrecv" : 1433799087,
"bytessent" : 28990,
"bytesrecv" : 77519,
"blocksrequested" : 0,
"conntime" : 1433796310,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701290,
"banscore" : 0
},
{
"addr" : "188.165.82.228:9432",
"services" : "00000003",
"lastsend" : 1433799134,
"lastrecv" : 1433799088,
"bytessent" : 24839,
"bytesrecv" : 78260,
"blocksrequested" : 0,
"conntime" : 1433796679,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701293,
"banscore" : 0
},
{
"addr" : "192.95.29.153:9432",
"services" : "00000003",
"lastsend" : 1433799056,
"lastrecv" : 1433799133,
"bytessent" : 7325,
"bytesrecv" : 84532,
"blocksrequested" : 0,
"conntime" : 1433796688,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701293,
"banscore" : 0
}
]
CryptoJohn
Legendary
*
Offline Offline

Activity: 1358
Merit: 1000


Well, That's Crypto :-\


View Profile
June 09, 2015, 08:41:21 PM
 #7591

Wow, I have not checked karma in months. Good to see activity still exists.

Alphi
Hero Member
*****
Offline Offline

Activity: 798
Merit: 1000


View Profile
June 10, 2015, 12:23:50 AM
 #7592

Need some help getting my windows wallet to sync.  Been running it non-stop for a week and can not get past block 636559.

backup your wallet.dat
delete your blocks, database and chainstate directories from the wallet directory (default is C:\Users\[YOUR_USER_ID]\AppData\Roaming\Karma)
update your peers.dat file (as per details above)
launch the app and sync again from the beginning (the block-chain is only a few hundred MB)

KARMA: KSc9oGgGga1TS4PqZNFxNS9LSDjdSgpC1B      VERT: VgKaooA5ZuLLUXTUANJigH9wCPuzBUBv9H
DOGE:   DRN7pXid34o6wQgUuK8BoSjWJ5g8jiEs4e
soopy452000
Legendary
*
Offline Offline

Activity: 1176
Merit: 1000

Founder Core Developer - NavCoin Ⓝ | Sherloc


View Profile WWW
June 10, 2015, 03:39:51 AM
 #7593

Hello All,

I have investigated the matter further and identified the cause of this issue and came to the conclusion that the Blockchain magic of KarmaCoin Here:

At Line :

https://github.com/karmateam/karma/blob/master-0.8/src/main.cpp#L3298


Code:
// The message start string is designed to be unlikely to occur in normal data.
// The characters are rarely used upper ASCII, not valid as UTF-8, and produce
// a large 4-byte int at any alignment.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Karma: increase each by adding 2 to bitcoin's value.

These Magic Bytes should be unique but unfortunately in this case these characters contradict with many other coins thus you guys are experiencing the sync issue.

To correct this problem would require a hardfork and the community will need to agree on that.

Warm Regards,
~SoopY~


Working/Online Times
04:00:00 GMT - 12:00:00 GMT / 00:00:00 EDT - 08:00:00 EDT

Coin Developments & Contributions 1. SherlockCoin (SHC) (https://bitcointalk.org/index.php?topic=454981) 2. [RESURRECTION] Bringing Life to Growthcoin (GRW) , Community Backed Development! (https://bitcointalk.org/index.php?topic=469464) 3. [ANN][66][New Maintainer] ★Coin 66★ (https://bitcointalk.org/index.php?topic=493987) 4. [RE-ANN] Galaxycoin Revival!-FORK AT BLOCK 255145, KGW, RANDOM BLOCK REWARDS (https://bitcointalk.org/index.php?topic=495693) 5. [RESURRECTION] Taking Astrocoin to the Moon,KGW Implemented + HARD FORK AT 17520 https://bitcointalk.org/index.php?topic=516549 6. [RESURRECTION] Bringing Electric back to the grid, Community Backed Development! https://bitcointalk.org/index.php?topic=514790
chrysophylax
Legendary
*
Offline Offline

Activity: 1316
Merit: 1074


--- ChainWorks Industries ---


View Profile WWW
June 10, 2015, 03:53:46 AM
 #7594

Hello All,

I have investigated the matter further and identified the cause of this issue and came to the conclusion that the Blockchain magic of KarmaCoin Here:

At Line :

https://github.com/karmateam/karma/blob/master-0.8/src/main.cpp#L3298


Code:
// The message start string is designed to be unlikely to occur in normal data.
// The characters are rarely used upper ASCII, not valid as UTF-8, and produce
// a large 4-byte int at any alignment.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Karma: increase each by adding 2 to bitcoin's value.

These Magic Bytes should be unique but unfortunately in this case these characters contradict with many other coins thus you guys are experiencing the sync issue.

To correct this problem would require a hardfork and the community will need to agree on that.

Warm Regards,
~SoopY~


hardfork and move on ...

get it back on track ...

#crysx

GRN - Gfz2cXMkhMZYWSFvLEMnM8bXk7X5Mtq2J2 . Exchange - https://www.cryptopia.co.nz/Exchange/?market=GRN_BTC . CWI-Thread - https://bitcointalk.org/index.php?topic=1563601 . EMail - crysx@gnxs.com . CWI-Pyroxene (theMine) - http://pyroxene.chainworksindustries.com/ .
soopy452000
Legendary
*
Offline Offline

Activity: 1176
Merit: 1000

Founder Core Developer - NavCoin Ⓝ | Sherloc


View Profile WWW
June 10, 2015, 09:24:14 AM
 #7595

Hello All,

I have investigated the matter further and identified the cause of this issue and came to the conclusion that the Blockchain magic of KarmaCoin Here:

At Line :

https://github.com/karmateam/karma/blob/master-0.8/src/main.cpp#L3298


Code:
// The message start string is designed to be unlikely to occur in normal data.
// The characters are rarely used upper ASCII, not valid as UTF-8, and produce
// a large 4-byte int at any alignment.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Karma: increase each by adding 2 to bitcoin's value.

These Magic Bytes should be unique but unfortunately in this case these characters contradict with many other coins thus you guys are experiencing the sync issue.

To correct this problem would require a hardfork and the community will need to agree on that.

Warm Regards,
~SoopY~


hardfork and move on ...

get it back on track ...

#crysx

yup , everyone will need to agree on this.

Working/Online Times
04:00:00 GMT - 12:00:00 GMT / 00:00:00 EDT - 08:00:00 EDT

Coin Developments & Contributions 1. SherlockCoin (SHC) (https://bitcointalk.org/index.php?topic=454981) 2. [RESURRECTION] Bringing Life to Growthcoin (GRW) , Community Backed Development! (https://bitcointalk.org/index.php?topic=469464) 3. [ANN][66][New Maintainer] ★Coin 66★ (https://bitcointalk.org/index.php?topic=493987) 4. [RE-ANN] Galaxycoin Revival!-FORK AT BLOCK 255145, KGW, RANDOM BLOCK REWARDS (https://bitcointalk.org/index.php?topic=495693) 5. [RESURRECTION] Taking Astrocoin to the Moon,KGW Implemented + HARD FORK AT 17520 https://bitcointalk.org/index.php?topic=516549 6. [RESURRECTION] Bringing Electric back to the grid, Community Backed Development! https://bitcointalk.org/index.php?topic=514790
gjhiggins
Legendary
*
Offline Offline

Activity: 1526
Merit: 1050



View Profile WWW
June 10, 2015, 10:23:23 AM
 #7596

these characters contradict with many other coins

Indeed so:

https://github.com/search?p=9&q=unsigned+char+pchMessageStart%5B4%5D+%3D+%7B+0x70%2C+0x35%2C+0x22%2C+0x05+%7D%3B&type=Code&utf8=%E2%9C%93

Cheers

Graham
BanzaiBTC
Legendary
*
Online Online

Activity: 1190
Merit: 1002


Amsterdex & BlockPioneers Developer


View Profile WWW
June 10, 2015, 10:27:43 AM
 #7597

Sighs... One of the basic things you need to change when forking a coin... How is it possible nobody noticed this sooner?  Huh

Hardfork it is then..

edit:

How about we add a few more hardcoded seeds?




And are we certain these are Karma only? Or do other coins have these as well.. Google didnt help me much on this one



All located here: https://github.com/karmateam/karma/blob/master-0.8/src/net.cpp
chrysophylax
Legendary
*
Offline Offline

Activity: 1316
Merit: 1074


--- ChainWorks Industries ---


View Profile WWW
June 10, 2015, 10:33:35 AM
 #7598

Hello All,

I have investigated the matter further and identified the cause of this issue and came to the conclusion that the Blockchain magic of KarmaCoin Here:

At Line :

https://github.com/karmateam/karma/blob/master-0.8/src/main.cpp#L3298


Code:
// The message start string is designed to be unlikely to occur in normal data.
// The characters are rarely used upper ASCII, not valid as UTF-8, and produce
// a large 4-byte int at any alignment.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Karma: increase each by adding 2 to bitcoin's value.

These Magic Bytes should be unique but unfortunately in this case these characters contradict with many other coins thus you guys are experiencing the sync issue.

To correct this problem would require a hardfork and the community will need to agree on that.

Warm Regards,
~SoopY~


hardfork and move on ...

get it back on track ...

#crysx

yup , everyone will need to agree on this.

as a community - i agree ...

as a fork for the coin - not really ...

the coin for the moment is going nowhere ( as far as development is concerned - not by means of trading which is doing ok ) ...

so for those who have mined and bought and baghold - this is a dead end unless something is done ...

everyone needs to voice their opinions - and i have mine ...

im for the hardfork ... so count my vote as 1 Smiley ...

#crysx

GRN - Gfz2cXMkhMZYWSFvLEMnM8bXk7X5Mtq2J2 . Exchange - https://www.cryptopia.co.nz/Exchange/?market=GRN_BTC . CWI-Thread - https://bitcointalk.org/index.php?topic=1563601 . EMail - crysx@gnxs.com . CWI-Pyroxene (theMine) - http://pyroxene.chainworksindustries.com/ .
Alphi
Hero Member
*****
Offline Offline

Activity: 798
Merit: 1000


View Profile
June 10, 2015, 05:04:19 PM
 #7599

Hello All,

I have investigated the matter further and identified the cause of this issue and came to the conclusion that the Blockchain magic of KarmaCoin Here:

At Line :

https://github.com/karmateam/karma/blob/master-0.8/src/main.cpp#L3298


Code:
// The message start string is designed to be unlikely to occur in normal data.
// The characters are rarely used upper ASCII, not valid as UTF-8, and produce
// a large 4-byte int at any alignment.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Karma: increase each by adding 2 to bitcoin's value.

These Magic Bytes should be unique but unfortunately in this case these characters contradict with many other coins thus you guys are experiencing the sync issue.

To correct this problem would require a hardfork and the community will need to agree on that.

Warm Regards,
~SoopY~


hardfork and move on ...

get it back on track ...

#crysx

yup , everyone will need to agree on this.

I am not convinced that a hard fork is necessary.. as stated in the post above, those magic bytes appear in many many other coins so if it was that serious a problem then ALL of those other coins will also be experiencing it.

From what I understand of the problem some people are experiencing a situation where there wallet is attempting to connect to nodes from other coins..  the majority (people who keep their wallets peers.dat file updated) do not appear to have this problem

As a software developer with more than 12 years solid commercial experience I can tell you that making fundamental changes to a piece of software forcing EVERYONE to either update or be locked out of the network (i.e. a Hardfork) is the absolute last resort option. Just imagine if windows and android operating systems forced users to update their entire operating system to the latest version and shut off connection the internet to anyone who did not update, every time they found a security flaw.. that is essentially what a hard fork is.

What I would like to know is that since the default port number for each coin is different such that very few coins actually share the same port number, then how and why is it possible for peers to be showing up from other coin networks?

Surely we should be looking at how this is possible and how we can prevent it from happening.
for example.. is there some code we could add to the peer handling mechanism which would only accept peers that connect via the valid port numbers and reject all others?.

You should not be able to "Addnode" peers with invalid port numbers for example.

And also regarding the suggestion from others about hard forking to hard code seed nodes.. not a very good idea.. since seed nodes come and go over time you will inevitably end up with hard coded seed node links that are broken. Of course nothing is stopping people from compiling their own wallets with additional seed nodes (this does not require a had fork).. and of course nothing is stopping people from simply using a peers.dat file which has update peer information already contained within.

the last time this coin hard forked we became bombarded with complaints from people who had not updated their wallets and were either looking for missing coins or had been mining on the wrong fork for many weeks and lost their newly mined coins as a result.

therefore I will not support any hard fork unless I can be convinced that there is a fatal flaw in the software which cannot be fixed by any other method than a hard fork and I am also convinced that the relevant testing is done on the test-net before switching over to the main network.

let me just remind you all that those magic bytes have been with the coin since day one.. and the coin network has been running successful since day one.


KARMA: KSc9oGgGga1TS4PqZNFxNS9LSDjdSgpC1B      VERT: VgKaooA5ZuLLUXTUANJigH9wCPuzBUBv9H
DOGE:   DRN7pXid34o6wQgUuK8BoSjWJ5g8jiEs4e
soopy452000
Legendary
*
Offline Offline

Activity: 1176
Merit: 1000

Founder Core Developer - NavCoin Ⓝ | Sherloc


View Profile WWW
June 10, 2015, 05:16:49 PM
 #7600

Hello All,

I have investigated the matter further and identified the cause of this issue and came to the conclusion that the Blockchain magic of KarmaCoin Here:

At Line :

https://github.com/karmateam/karma/blob/master-0.8/src/main.cpp#L3298


Code:
// The message start string is designed to be unlikely to occur in normal data.
// The characters are rarely used upper ASCII, not valid as UTF-8, and produce
// a large 4-byte int at any alignment.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Karma: increase each by adding 2 to bitcoin's value.

These Magic Bytes should be unique but unfortunately in this case these characters contradict with many other coins thus you guys are experiencing the sync issue.

To correct this problem would require a hardfork and the community will need to agree on that.

Warm Regards,
~SoopY~


hardfork and move on ...

get it back on track ...

#crysx

yup , everyone will need to agree on this.

I am not convinced that a hard fork is necessary.. as stated in the post above, those magic bytes appear in many many other coins so if it was that serious a problem then ALL of those other coins will also be experiencing it.

From what I understand of the problem some people are experiencing a situation where there wallet is attempting to connect to nodes from other coins..  the majority (people who keep their wallets peers.dat file updated) do not appear to have this problem

as a software developer with more than 12 years solid commercial experience I can tell you that making fundamental changes to a piece of software forcing EVERYONE to either update or be locked out of the network (i.e. a Hardfork) is the absolute last resort option.

what I would like to know is that since the default port number for each coin is different such that very few coins actually share the same port number, then how and why is it possible for peers to be showing up from other coin networks?

surely we should be looking at how this is possible and how we can prevent it from happening.
for example.. is there some code we could add to the peer handling mechanism which would only accept peers that connect via the valid port numbers and reject all others?.

You should not be able to "Addnode" peers with invalid port numbers for example.

And also regarding the suggestion from others about hard forking to hard code seed nodes.. not a very good idea.. since seed nodes come and go over time you will inevitably end up with hard coded seed node links that are broken. Of course nothing is stopping people from compiling their own wallets with additional seed nodes (this does not require a had fork).. and of course nothing is stopping people from simply using a peers.dat file which has update peer information already contained within.

the last time this coin hard forked we became bombarded with complaints from people who had not updated their wallets and were either looking for missing coins or had been mining on the wrong fork for many weeks and lost their newly mined coins as a result.

therefore I will not support any hard fork unless I can be convinced that there is a serious flaw in the software which cannot be fixed by any other method than a hard fork and I am also convinced that the relevant testing is done on the test-net before switching over to the main network.

let me just remind you all that those magic bytes have been with the coin since day one.. and the coin network has been running successful since day one.



Thank you for your thoughts mate , but it is with my experience being on the Crypto scene that I'm telling or more suggesting and pointing where the issue is, I've seen this issue commonly on many coins and that too most due to the above said issue. Anyhow I m not here to make or force the community or anyone here to hardfork and as such , I was asked to look into the code provide a fix , I found the error , has notified the community and it is upto the community to do whats best for the coin and themselves. And about the magic bytes being there since the first day and that it wasn't a problem back then is not the case mate , the issue comes when the blockchain matures, not in the beginning.

I didn't mean to disrespect anyone's opinion or ideas guys , I just shared my views on the matter as I was asked to , it is upto the community on doing whatever is needed.

Thank you so very much Alphi for your kind inputs regards to the same and opening up a conversation related to the matter and opening door for further discussions within the community.

Warm Regards,
~SoopY~

Working/Online Times
04:00:00 GMT - 12:00:00 GMT / 00:00:00 EDT - 08:00:00 EDT

Coin Developments & Contributions 1. SherlockCoin (SHC) (https://bitcointalk.org/index.php?topic=454981) 2. [RESURRECTION] Bringing Life to Growthcoin (GRW) , Community Backed Development! (https://bitcointalk.org/index.php?topic=469464) 3. [ANN][66][New Maintainer] ★Coin 66★ (https://bitcointalk.org/index.php?topic=493987) 4. [RE-ANN] Galaxycoin Revival!-FORK AT BLOCK 255145, KGW, RANDOM BLOCK REWARDS (https://bitcointalk.org/index.php?topic=495693) 5. [RESURRECTION] Taking Astrocoin to the Moon,KGW Implemented + HARD FORK AT 17520 https://bitcointalk.org/index.php?topic=516549 6. [RESURRECTION] Bringing Electric back to the grid, Community Backed Development! https://bitcointalk.org/index.php?topic=514790
Pages: « 1 ... 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 [380] 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!