Topic: [ANN][AID] AidBit | Digital-currency redefined | POW/POS | Groestl | Charity - page 28. (Read 101116 times)

Quote from: HR on July 28, 2014, 12:09:14 PM

Actually, we've changed the protocol version and are ignoring the older versions. Unfortunately we're experiencing new forks and we're still investigating what is going on. Master Checkpoint Node is trying hard to keep everything together for now.
You can connect directly to one of our pool nodes.

Code:

#aidbit.conf
connect=maya.aidbit.net
connect=felix.aidbit.net
connect=kei.aidbit.net

This way you'll limit connection to other nodes.

I know it's frustrating, but it's no better on this side.

Regards,

AidBit

I was looking at the Litecoin Wiki looking for something else and came across the -checkpoints switch for the conf file which limits connectivity to only accepting the block chain matching built-in checkpoints.

Master Checkpointing is already operational and should work much better then just built-in checkpoints... Thanks.

I suspected as much . . . I'm still very low on the learning curve . . . trying to learn and be as helpful as possible in exchange . . .

Question: Master Checkpointing is done from the Master Checkpoint Node? Working to keep everything in line?

Question: -checkpoints is done from each individual wallet (that is so configured)? Working only to ensure that that particular wallet is indeed on the correct blockchain?

Yes, correct!

So each miner could "double up" their protection by including the -checkpoints switch in their own conf file?

Also, another question, did you make some changes that went into effect after block 14898?

AidBit

full member

Activity: 154

Merit: 100

Quote from: AidBit on July 28, 2014, 11:29:32 AM

Quote from: AidBit on July 28, 2014, 11:29:32 AM

Actually, we've changed the protocol version and are ignoring the older versions. Unfortunately we're experiencing new forks and we're still investigating what is going on. Master Checkpoint Node is trying hard to keep everything together for now.
You can connect directly to one of our pool nodes.

Code:

#aidbit.conf
connect=maya.aidbit.net
connect=felix.aidbit.net
connect=kei.aidbit.net

This way you'll limit connection to other nodes.

I know it's frustrating, but it's no better on this side.

Regards,

AidBit

I was looking at the Litecoin Wiki looking for something else and came across the -checkpoints switch for the conf file which limits connectivity to only accepting the block chain matching built-in checkpoints.

Master Checkpointing is already operational and should work much better then just built-in checkpoints... Thanks.

I suspected as much . . . I'm still very low on the learning curve . . . trying to learn and be as helpful as possible in exchange . . .

Question: Master Checkpointing is done from the Master Checkpoint Node? Working to keep everything in line?

Question: -checkpoints is done from each individual wallet (that is so configured)? Working only to ensure that that particular wallet is indeed on the correct blockchain?

Yes, correct!

HR

legendary

Activity: 1176

Merit: 1011

Transparency & Integrity

Actually, we've changed the protocol version and are ignoring the older versions. Unfortunately we're experiencing new forks and we're still investigating what is going on. Master Checkpoint Node is trying hard to keep everything together for now.
You can connect directly to one of our pool nodes.

Code:

#aidbit.conf
connect=maya.aidbit.net
connect=felix.aidbit.net
connect=kei.aidbit.net

This way you'll limit connection to other nodes.

I know it's frustrating, but it's no better on this side.

Regards,

AidBit

I was looking at the Litecoin Wiki looking for something else and came across the -checkpoints switch for the conf file which limits connectivity to only accepting the block chain matching built-in checkpoints.

Master Checkpointing is already operational and should work much better then just built-in checkpoints... Thanks.

I suspected as much . . . I'm still very low on the learning curve . . . trying to learn and be as helpful as possible in exchange . . .

Question: Master Checkpointing is done from the Master Checkpoint Node? Working to keep everything in line?

Question: -checkpoints is done from each individual wallet (that is so configured)? Working only to ensure that that particular wallet is indeed on the correct blockchain?

idad01

full member

Activity: 148

Merit: 100

Quote from: srcxxx on July 28, 2014, 07:58:27 AM

18:19:00

getblockhash 15213

18:19:00

00000000162ea1f7d2e56600657f052174711511257cd0af27ef04fd48a1c392

Correct?

YES

Dear developers,

Please provide a list of nodes on the correct fork for us to use (via "addnode" or perhaps even "connect" in .conf). Or upload a "correct" blockchain data files.
Today my pool encountered "invalid checkpoint error" again. After deleting data and re-downloading it became normal.
But on my windows machine I deleted, re-downloaded and am getting the "invalid checkpoint error" again!
I assume these problems happen because some nodes are on incorrect fork and it is a matter of luck to which node my wallet connects.
But can't you perhaps increase the protocol version or something similar?

These problems are quite similar to Diamondcoin issues when they were switching to POS+POW.
I remember that they issued a patch to ignore nodes on "old blockchain".

I'm quite worried that even though I'm on correct fork, perhaps in 1 hour I'll hit the "invalid checkpoint".

Thank you

Actually, we've changed the protocol version and are ignoring the older versions. Unfortunately we're experiencing new forks and we're still investigating what is going on. Master Checkpoint Node is trying hard to keep everything together for now.
You can connect directly to one of our pool nodes.

Code:

#aidbit.conf
connect=maya.aidbit.net
connect=felix.aidbit.net
connect=kei.aidbit.net

This way you'll limit connection to other nodes.

I know it's frustrating, but it's no better on this side.

Regards,

AidBit

nice

AidBit

full member

Activity: 154

Merit: 100

Actually, we've changed the protocol version and are ignoring the older versions. Unfortunately we're experiencing new forks and we're still investigating what is going on. Master Checkpoint Node is trying hard to keep everything together for now.
You can connect directly to one of our pool nodes.

Code:

#aidbit.conf
connect=maya.aidbit.net
connect=felix.aidbit.net
connect=kei.aidbit.net

This way you'll limit connection to other nodes.

I know it's frustrating, but it's no better on this side.

Regards,

AidBit

I was looking at the Litecoin Wiki looking for something else and came across the -checkpoints switch for the conf file which limits connectivity to only accepting the block chain matching built-in checkpoints.

Master Checkpointing is already operational and should work much better then just built-in checkpoints... Thanks.

HR

legendary

Activity: 1176

Merit: 1011

Transparency & Integrity

Quote from: Sigi on July 28, 2014, 10:53:06 AM

Actually, we've changed the protocol version and are ignoring the older versions. Unfortunately we're experiencing new forks and we're still investigating what is going on. Master Checkpoint Node is trying hard to keep everything together for now.
You can connect directly to one of our pool nodes.

Code:

#aidbit.conf
connect=maya.aidbit.net
connect=felix.aidbit.net
connect=kei.aidbit.net

This way you'll limit connection to other nodes.

I know it's frustrating, but it's no better on this side.

Regards,

AidBit

I was looking at the Litecoin Wiki looking for something else and came across the -checkpoints switch for the conf file which limits connectivity to only accepting the block chain matching built-in checkpoints.

Sigi

newbie

Activity: 16

Merit: 0

Maybe you should change the logo and rename the coin to ForkBit od AidFork or something. Grin

http://i.imgur.com/SInnG6D.jpg

No intention of insulting the hard working dev, I just couldn't help myself playing with the logo

Sigi

newbie

Activity: 16

Merit: 0

Maybe you should change the logo and rename the coin to ForkBit od AidFork or something. Grin

http://i.imgur.com/SInnG6D.jpg

Litejavichu

hero member

Activity: 693

Merit: 500

Quote from: srcxxx on July 28, 2014, 07:58:27 AM

Quote from: srcxxx on July 28, 2014, 07:58:27 AM

18:19:00

getblockhash 15213

18:19:00

00000000162ea1f7d2e56600657f052174711511257cd0af27ef04fd48a1c392

Correct?

YES

Dear developers,

Please provide a list of nodes on the correct fork for us to use (via "addnode" or perhaps even "connect" in .conf). Or upload a "correct" blockchain data files.
Today my pool encountered "invalid checkpoint error" again. After deleting data and re-downloading it became normal.
But on my windows machine I deleted, re-downloaded and am getting the "invalid checkpoint error" again!
I assume these problems happen because some nodes are on incorrect fork and it is a matter of luck to which node my wallet connects.
But can't you perhaps increase the protocol version or something similar?

These problems are quite similar to Diamondcoin issues when they were switching to POS+POW.
I remember that they issued a patch to ignore nodes on "old blockchain".

I'm quite worried that even though I'm on correct fork, perhaps in 1 hour I'll hit the "invalid checkpoint".

Thank you

Actually, we've changed the protocol version and are ignoring the older versions. Unfortunately we're experiencing new forks and we're still investigating what is going on. Master Checkpoint Node is trying hard to keep everything together for now.
You can connect directly to one of our pool nodes.

Code:

#aidbit.conf
connect=maya.aidbit.net
connect=felix.aidbit.net
connect=kei.aidbit.net

This way you'll limit connection to other nodes.

I know it's frustrating, but it's no better on this side.

Regards,

AidBit

Well, I apologize for my previous sarcasm in previous post Embarrassed

.... I have to admit that the DEV is very committed, although errors he is without sleep several days to resolve. Atheistcoin you the same thing happened and dev decides to ignore who does not update.

AidBit

full member

Activity: 154

Merit: 100

18:19:00

getblockhash 15213

18:19:00

00000000162ea1f7d2e56600657f052174711511257cd0af27ef04fd48a1c392

Correct?

YES

Dear developers,

Please provide a list of nodes on the correct fork for us to use (via "addnode" or perhaps even "connect" in .conf). Or upload a "correct" blockchain data files.
Today my pool encountered "invalid checkpoint error" again. After deleting data and re-downloading it became normal.
But on my windows machine I deleted, re-downloaded and am getting the "invalid checkpoint error" again!
I assume these problems happen because some nodes are on incorrect fork and it is a matter of luck to which node my wallet connects.
But can't you perhaps increase the protocol version or something similar?

These problems are quite similar to Diamondcoin issues when they were switching to POS+POW.
I remember that they issued a patch to ignore nodes on "old blockchain".

I'm quite worried that even though I'm on correct fork, perhaps in 1 hour I'll hit the "invalid checkpoint".

Thank you

Actually, we've changed the protocol version and are ignoring the older versions. Unfortunately we're experiencing new forks and we're still investigating what is going on. Master Checkpoint Node is trying hard to keep everything together for now.
You can connect directly to one of our pool nodes.

Code:

#aidbit.conf
connect=maya.aidbit.net
connect=felix.aidbit.net
connect=kei.aidbit.net

This way you'll limit connection to other nodes.

I know it's frustrating, but it's no better on this side.

Regards,

AidBit

HR

legendary

Activity: 1176

Merit: 1011

Transparency & Integrity

Norton is identifying the AidBit sgminer.exe as Trojan.ADH.2

http://www.symantec.com/security_response/writeup.jsp?docid=2011-030906-0727-99&vid=42292&product=Norton%20360%20Premier%20Edition&version=20.5.0.28&plang=sym:ES&layouttype=Retail&buildname=Retail&heartbeatID=D75B5ED8-FB61-4FC5-BA12-03A0ED9609B1&env=prod&vendorid=&plid=69&plgid=4&skup=21223125&skum=21236901&skuf=21222959&endpointid=%7BD75B5ED8-FB61-4FC5-BA12-03A0ED9609B1%7D&partnerid=&lic_type=2&lic_attr=21124114&psn=7C8HGG8T2TCD&osvers=5.1&oslocale=iso:ESP&oslang=iso:SPA&os=windows

I know the false positive is posted on the website, but if a traditional signature is what's needed to avoid that, why not include it? Norton automatically quarantines it and you need to disactivate the AV in order to work with it. This might be scaring off potential newcomers.

minerd.exe is also identified as a bitcoinminer as though it were a botnet install (which it's not, but that 'red flag' is another something that can scare people off).

http://www.symantec.com/security_response/writeup.jsp?docid=2011-091213-5424-99&vid=4294907612&product=Norton%20360%20Premier%20Edition&version=20.5.0.28&plang=sym:ES&layouttype=Retail&buildname=Retail&heartbeatID=D75B5ED8-FB61-4FC5-BA12-03A0ED9609B1&env=prod&vendorid=&plid=69&plgid=4&skup=21223125&skum=21236901&skuf=21222959&endpointid=%7BD75B5ED8-FB61-4FC5-BA12-03A0ED9609B1%7D&partnerid=&lic_type=2&lic_attr=21124114&psn=7C8HGG8T2TCD&osvers=5.1&oslocale=iso:ESP&oslang=iso:SPA&os=windows

The wallet download itself is identified as WS.Reputation.1 - which just basically means that it has a low reputation score - and is also automatically quarantined.

http://www.symantec.com/security_response/writeup.jsp?docid=2010-051308-1854-99&vid=4294919973&product=Norton%20360%20Premier%20Edition&version=20.5.0.28&plang=sym:ES&layouttype=Retail&buildname=Retail&heartbeatID=D75B5ED8-FB61-4FC5-BA12-03A0ED9609B1&env=prod&vendorid=&plid=69&plgid=4&skup=21223125&skum=21236901&skuf=21222959&endpointid=%7BD75B5ED8-FB61-4FC5-BA12-03A0ED9609B1%7D&partnerid=&lic_type=2&lic_attr=21124114&psn=7C8HGG8T2TCD&osvers=5.1&oslocale=iso:ESP&oslang=iso:SPA&os=windows

I've submitted the files to Symantec. Maybe they'll clear things up after analyzing them.

srcxxx

sr. member

Activity: 266

Merit: 250