|
idad01
|
|
July 28, 2014, 10:17:58 AM |
|
nice
|
|
|
|
idad01
|
|
July 28, 2014, 10:20:27 AM |
|
18:19:00  getblockhash 15213
18:19:00  00000000162ea1f7d2e56600657f052174711511257cd0af27ef04fd48a1c392
Correct?
|
|
|
|
boosh
|
|
July 28, 2014, 10:37:06 AM |
|
Is maya pool on correct fork ? Blockexplorer is on block 15188 and mywallet had syncing issues showing 15203 of 15226 downloaded and now its in sync at block 15208. Plus wallet has invalid checkpoint error.
|
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ PRIMEDICE The Premier Bitcoin Gambling Experience - Most Trusted & Popular Bitcoin Game @PrimeDice ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
|
|
|
AidBit (OP)
|
|
July 28, 2014, 10:51:07 AM |
|
18:19:00  getblockhash 15213
18:19:00  00000000162ea1f7d2e56600657f052174711511257cd0af27ef04fd48a1c392
Correct?
YES
|
|
|
|
operater1
Newbie
Offline
Activity: 11
Merit: 0
|
|
July 28, 2014, 10:52:16 AM |
|
wallet dont sync i download lastest from ofiicial site...what heppen ?they stuck on1156 block
|
|
|
|
srcxxx
|
|
July 28, 2014, 11: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
|
|
|
|
HR
Legendary
Offline
Activity: 1176
Merit: 1011
Transparency & Integrity
|
|
July 28, 2014, 12:06:11 PM |
|
|
|
|
|
AidBit (OP)
|
|
July 28, 2014, 01:02:35 PM |
|
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. #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
|
|
|
|
Litejavichu
|
|
July 28, 2014, 01:59:29 PM |
|
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. #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 .... 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.
|
|
|
|
Sigi
Newbie
Offline
Activity: 16
Merit: 0
|
|
July 28, 2014, 02:53:06 PM |
|
Maybe you should change the logo and rename the coin to ForkBit od AidFork or something. https://i.imgur.com/SInnG6D.jpg
|
|
|
|
Sigi
Newbie
Offline
Activity: 16
Merit: 0
|
|
July 28, 2014, 02:59:46 PM |
|
No intention of insulting the hard working dev, I just couldn't help myself playing with the logo
|
|
|
|
HR
Legendary
Offline
Activity: 1176
Merit: 1011
Transparency & Integrity
|
|
July 28, 2014, 03:12:54 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. #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.
|
|
|
|
AidBit (OP)
|
|
July 28, 2014, 03:29:32 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. #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.
|
|
|
|
idad01
|
|
July 28, 2014, 03:41:18 PM |
|
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. #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
|
|
|
|
HR
Legendary
Offline
Activity: 1176
Merit: 1011
Transparency & Integrity
|
|
July 28, 2014, 04: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. #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?
|
|
|
|
AidBit (OP)
|
|
July 28, 2014, 04:33:17 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. #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
Offline
Activity: 1176
Merit: 1011
Transparency & Integrity
|
|
July 28, 2014, 04:43:53 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. #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?
|
|
|
|
thenite0wl
|
|
July 28, 2014, 04:45:14 PM |
|
how does one use the checkpoint switch in the config, and should we. also is there a fix/wallet update coming today.
|
|
|
|
coke15
Member
Offline
Activity: 176
Merit: 10
|
|
July 28, 2014, 04:46:49 PM |
|
HI all is good for today,no sync error ,mining is "good". (still 670 and 511 no confirm) dev have you speak with coin swap? still no wallet on this exchange,i want back my aid good job
|
|
|
|
|