ANN ~BINARY~[BIC] Scrypt | 15 sec blocks | 84M coins | Binarycoin *REVIVED*

[MbccompanyX]

Hello all!

Please, We hope you all can find it to forgive my unexplained leave of abcense.
As an explanation: the holidays were killer and I personally had just moved into a new place
so I was also in process of packing several uhauls worth of stuff, taking mining equipment down, prepping the new place and setting everything back up which easily consumed the past couple months of mine and the rest of the team also had engagements so it wound up being an extended break.

News update:
Actually development is back in full swing. There are many things in the works and we will are excited to start rolling some out immediately.
Featuring the website (FINALLY) along with a standalone Binarycoin website (because no project is complete without having its own website regardless of team involvement).
Seriously exciting stuff and a PATCH to the previously gummed up wallet is coming out within 24 hours of this post.

There will be chat support coming out along with the site launch (chat portion may come later still having some minor issues with it so if complaints roll in it will be taken down til it's perfect) and get this "Phone support" Still figuring out the hours on that one though.

Finally I'd like to extend a big thank you to anyone still running or holding this coin.
You guys are who we're doing this for (Even if it's an almost dead project atm).

- The Coderz

So it's been like 13 days. Any updates for the wallet and the site?

Maybe one single thing that is visible on the profile of the "dev" could tell you something

Last Active:   January 17, 2016, 06:02:40

He didn't got online from when he made that post, and this time i don't think there can be something like a holiday to create a motive during which he wasn't on and even so, 13 days in my opinion are enough to do even a little bit of the things he wrote that was going to do and even try some tests on them

[coiner561]

Hello all!

Please, We hope you all can find it to forgive my unexplained leave of abcense.
As an explanation: the holidays were killer and I personally had just moved into a new place
so I was also in process of packing several uhauls worth of stuff, taking mining equipment down, prepping the new place and setting everything back up which easily consumed the past couple months of mine and the rest of the team also had engagements so it wound up being an extended break.

News update:
Actually development is back in full swing. There are many things in the works and we will are excited to start rolling some out immediately.
Featuring the website (FINALLY) along with a standalone Binarycoin website (because no project is complete without having its own website regardless of team involvement).
Seriously exciting stuff and a PATCH to the previously gummed up wallet is coming out within 24 hours of this post.

There will be chat support coming out along with the site launch (chat portion may come later still having some minor issues with it so if complaints roll in it will be taken down til it's perfect) and get this "Phone support" Still figuring out the hours on that one though.

Finally I'd like to extend a big thank you to anyone still running or holding this coin.
You guys are who we're doing this for (Even if it's an almost dead project atm).

- The Coderz

So it's been like 13 days. Any updates for the wallet and the site?

Maybe one single thing that is visible on the profile of the "dev" could tell you something

Last Active:   January 17, 2016, 06:02:40

He didn't got online from when he made that post, and this time i don't think there can be something like a holiday to create a motive during which he wasn't on and even so, 13 days in my opinion are enough to do even a little bit of the things he wrote that was going to do and even try some tests on them

Yeah I agree with you. I posted to see if he gets a notification or something of his thread and come back online.
My wallet says it needs another 9512 blocks to fully sync with total of 2000301 but from what I can see from securepayments pool they are currenctly mining block: 1990829: 2016-01-30 09:14:58 GMT-5 are we on a different chain or something?

[tuaris]

My wallet says it needs another 9512 blocks to fully sync with total of 2000301 but from what I can see from securepayments pool they are currenctly mining block: 1990829: 2016-01-30 09:14:58 GMT-5 are we on a different chain or something?

It does indeed seem that the chain forked sometime back in November 2015 and no one noticed until now.  It also appears to have been maliciously done..

The chain forked at block #1979437.

Block #1979436 is identical on both chains, but #1979437 differs.  Here is block #1979436 from the two chains.  Note how the "nextblockhash" differs.

CHAIN B:

Code:

{
"hash" : "6e5ba68a92afb441b5ab58bdd64ad2f18c4d076e909803f333a631480e716606",
"confirmations" : 30429,
"size" : 244605,
"height" : 1979436,
"version" : 1,
"merkleroot" : "4e1584b9fc5e95c86951f2ad3801cf5bdd2b7a964e281e069ab4ee22a3050856",
"tx" : [
"fec94908aa7404d373d7c7ea7c628299906a9f498851f35745e0be2b0ec7419c",
"da9f579c09b3b572394f0df14b807772cfe6509984ac1850baa3a25c175ecb61",
"bef8251199c0e7cfa30627ceadcfcceee5fa5f44e61085fd0e0e499533ff08d5",
"8a86559415ecc080b74dc22058d6c0e59bdbf5bc7316705cb1de43a197f5f8f7",
"400aa1f23a111f11142c2167e9e843ec4b65ec63c25d8a6b46ea92f831c96275"
],
"time" : 1447410081,
"nonce" : 904462464,
"bits" : "1d06cbd3",
"difficulty" : 0.14713906,
"previousblockhash" : "90a17a9d505f7d8354f3e2000c7fae78ffc0367c0a885392c751e8942774f7cb",
"nextblockhash" : "bba184b397aab4d81f68cc7314b519da4d2c4f205db630d25830d0e416744cb0"
}

CHAIN A:

Code:

(
    [hash] => 6e5ba68a92afb441b5ab58bdd64ad2f18c4d076e909803f333a631480e716606
    [confirmations] => 12123
    [size] => 244605
    [height] => 1979436
    [version] => 1
    [merkleroot] => 4e1584b9fc5e95c86951f2ad3801cf5bdd2b7a964e281e069ab4ee22a3050856
    [tx] => Array
        (
            [0] => fec94908aa7404d373d7c7ea7c628299906a9f498851f35745e0be2b0ec7419c
            [1] => da9f579c09b3b572394f0df14b807772cfe6509984ac1850baa3a25c175ecb61
            [2] => bef8251199c0e7cfa30627ceadcfcceee5fa5f44e61085fd0e0e499533ff08d5
            [3] => 8a86559415ecc080b74dc22058d6c0e59bdbf5bc7316705cb1de43a197f5f8f7
            [4] => 400aa1f23a111f11142c2167e9e843ec4b65ec63c25d8a6b46ea92f831c96275
        )

    [time] => 1447410081
    [nonce] => 904462464
    [bits] => 1d06cbd3
    [difficulty] => 0.14713906
    [previousblockhash] => 90a17a9d505f7d8354f3e2000c7fae78ffc0367c0a885392c751e8942774f7cb
    [nextblockhash] => 0c5a03f8762bfec4b2fe4a46113130309616067725ff0458786464a622e09149
)

Here is block #1979437 from both chains.  Notice the timestamp on the block between the two chains:

CHAIN B:

Code:

{
"hash" : "bba184b397aab4d81f68cc7314b519da4d2c4f205db630d25830d0e416744cb0",
"confirmations" : 30427,
"size" : 232640,
"height" : 1979437,
"version" : 1,
"merkleroot" : "f49fa553e9b8b7e600d8fe86f78b55c3da7c8d81e19dbcd2483b1a184fd6ea1d",
"tx" : [
"eefb0b38cbe8bb4a42b731c3b13d4e1e57e2d14f12ca16ff821aa98bf3d0a8b7",
"0f1b977c235652f140fbd0a3d9c123f48735bcbc80e71118046fec96877fa58c",
"515989b43028811de34255144f564075b4ec891314ace763b11968e6c60d58f3",
"95536663a5ecd453964b9cc74a54c62751aa20ed0adf47ade64aaeb8f9d8870d"
],
"time" : 1447412555,
"nonce" : 741146912,
"bits" : "1d06cbd3",
"difficulty" : 0.14713906,
"previousblockhash" : "6e5ba68a92afb441b5ab58bdd64ad2f18c4d076e909803f333a631480e716606",
"nextblockhash" : "b57f37919c354ca527d8378c7e9c40967e1c23c7e3d5d5beddb64fabd29b882e"
}

CHAIN A:

Code:

(
    [hash] => 0c5a03f8762bfec4b2fe4a46113130309616067725ff0458786464a622e09149
    [confirmations] => 12122
    [size] => 397
    [height] => 1979437
    [version] => 1
    [merkleroot] => a8f66a0ff68c22805bdfcaf688c4eb7a888c4ee47ada903abbb13790eca7a0ac
    [tx] => Array
        (
            [0] => 438a13845dcf0beb518fe2ad8c4763c5a896f08cb6734bd8fa9bcc75aa6ac4da
            [1] => ebe552f8ce102d6a13cfc1db5026caffbb1172734eab89fc0c93869fa991b5e3
        )

    [time] => 1447412922
    [nonce] => 173130296
    [bits] => 1d06cbd3
    [difficulty] => 0.14713906
    [previousblockhash] => 6e5ba68a92afb441b5ab58bdd64ad2f18c4d076e909803f333a631480e716606
    [nextblockhash] => 6fa04463cc631f8a877c240dda1a2a4261d5075cf1915342c6b89bafd221e8e0
)

The timestamp on block #1979437 from CHAIN B is Fri,13 Nov 2015 11:02:35 GMT while on CHAIN A it is Fri, 13 Nov 2015 11:08:42 GMT.   Block #1979437 was stale on CHAIN A, this is normal and eventually CHAIN A will catch up when the block propagates and the 'correct' chain is activated.

However 20 minutes later block #1979438 is extracted on CHAIN B, but on CHAIN A #1979438 is extracted only 13 seconds later.  Odd huh..?
Block #1979437 from CHAIN B hasn't propagated after 20 minutes.

CHAIN B:

Code:

{
"hash" : "b57f37919c354ca527d8378c7e9c40967e1c23c7e3d5d5beddb64fabd29b882e",
"confirmations" : 30427,
"size" : 100176,
"height" : 1979438,
"version" : 1,
"merkleroot" : "bd4211e39aeefcf69b0fd8119843eddf2560472b1f055316b51eba949f622902",
"tx" : [
"3d69e4b425643421d5c34bcd32ad9496a2a685e5eca939ecb5c826019731acd7",
"1e243337decf49069d60724b162ec518f835f6c3cafcd80bf73f9ad25878a9ce"
],
"time" : 1447413746,
"nonce" : 1177223456,
"bits" : "1d06cbd3",
"difficulty" : 0.14713906,
"previousblockhash" : "bba184b397aab4d81f68cc7314b519da4d2c4f205db630d25830d0e416744cb0",
"nextblockhash" : "71ea0b19c4ab3ac3dea5c304ed642cbf742fb98538d682eea9fba6cc8785bda4"
}

CHAIN A:

Code:

(
    [hash] => 6fa04463cc631f8a877c240dda1a2a4261d5075cf1915342c6b89bafd221e8e0
    [confirmations] => 12121
    [size] => 205
    [height] => 1979438
    [version] => 1
    [merkleroot] => 30013b3b187aeaebf1d9b6350a06899d381d3fece04e794d0854574759c311b5
    [tx] => Array
        (
            [0] => 30013b3b187aeaebf1d9b6350a06899d381d3fece04e794d0854574759c311b5
        )

    [time] => 1447412935
    [nonce] => 4236804432
    [bits] => 1d06cbd3
    [difficulty] => 0.14713906
    [previousblockhash] => 0c5a03f8762bfec4b2fe4a46113130309616067725ff0458786464a622e09149
    [nextblockhash] => b1bd687737f78895d8824fab7b9ecf32596cea8bf0591680abfda78af1d4db20
)

Things get even more strange at block #1979439.  On CHAIN B this block is extracted almost 3 hours later at Fri, 13 Nov 2015 14:16:59 GMT! While CHAIN A is moving along at a normal pace having this same block extracted only 4 seconds later at Fri, 13 Nov 2015 11:08:59 GMT.

CHAIN B:

Code:

{
"hash" : "71ea0b19c4ab3ac3dea5c304ed642cbf742fb98538d682eea9fba6cc8785bda4",
"confirmations" : 30426,
"size" : 227507,
"height" : 1979439,
"version" : 1,
"merkleroot" : "be2f674ef4dfc6c7ebdb6d808de8855a70afae70dcc7321c7278bb9660a1fc98",
"tx" : [
"06debe8b1bff5b0d8bde9bc695889296b3cc0f57254481234ddde434fae3c837",
"ebe552f8ce102d6a13cfc1db5026caffbb1172734eab89fc0c93869fa991b5e3",
"64d995ae3e01429500da3bb47d1b57019c0295f88088d4897218710b45f34b46",
"f5cbec4c229da5747065ca7d74589b3dc5e6f5a761b913674fdfcd9db0f02de5",
"43c0bcd859b635f217d13199e8b1384596f9f001e0175bb1407c135874d65ca4"
],
"time" : 1447424219,
"nonce" : 2376207104,
"bits" : "1d06cbd3",
"difficulty" : 0.14713906,
"previousblockhash" : "b57f37919c354ca527d8378c7e9c40967e1c23c7e3d5d5beddb64fabd29b882e",
"nextblockhash" : "db968b37f69149a1babb466d7447c09bc40412c1bca85a7c066767c36287d60e"
}

CHAIN A:

Code:

(
    [hash] => b1bd687737f78895d8824fab7b9ecf32596cea8bf0591680abfda78af1d4db20
    [confirmations] => 12120
    [size] => 205
    [height] => 1979439
    [version] => 1
    [merkleroot] => f99df620a0f9cae45d4fbf4b05c8d8f5307fc9758d3ac9db1a97145a8fdc04af
    [tx] => Array
        (
            [0] => f99df620a0f9cae45d4fbf4b05c8d8f5307fc9758d3ac9db1a97145a8fdc04af
        )

    [time] => 1447412939
    [nonce] => 3048277727
    [bits] => 1d06cbd3
    [difficulty] => 0.14713906
    [previousblockhash] => 6fa04463cc631f8a877c240dda1a2a4261d5075cf1915342c6b89bafd221e8e0
    [nextblockhash] => 2ba9f2bcb9ae882ffaa43494ae91134c616887ddca600378e9a25eea778a2996
)

The network continues to fork.  Block #1979440 is extract from CHAIN B about 10 minutes after it's #1979439 (Fri, 13 Nov 2015 14:28:35 GMT).  On CHAIN A block #1979440 is extracted 15 seconds after it's #1979439 (Fri, 13 Nov 2015 11:09:14 GM).

CHAIN B:

Code:

{
"hash" : "db968b37f69149a1babb466d7447c09bc40412c1bca85a7c066767c36287d60e",
"confirmations" : 30425,
"size" : 234279,
"height" : 1979440,
"version" : 1,
"merkleroot" : "9831c1a008132a1cb725c259e64be62f832df5d22f24ca1f9025a407be973c03",
"tx" : [
"f20bc19d4370cf420a2ed664dbe947dd4e782ca3473e8832b467c8edad27f154",
"cf9869ff18cb042471a91fa69a8dfd2b6d0a7d9b7441caa6425fbdb008462c6b",
"6ca11e8ea9e1b04baddac8c89811573617b19dfffbbae1267b03b4983fa7b37c",
"a912edd8171dbe977dda13f054ee821c1a441f93969bec673a2f3269c482e49d",
"7ade390eea83dd8136e8dbf14076aca3394824246f4963fe4ceaec4738a5df74"
],
"time" : 1447424915,
"nonce" : 2204533214,
"bits" : "1d06cbd3",
"difficulty" : 0.14713906,
"previousblockhash" : "71ea0b19c4ab3ac3dea5c304ed642cbf742fb98538d682eea9fba6cc8785bda4",
"nextblockhash" : "73cb52a7071f4f0052900cb952c46d782eb6fb7aba2e546ae7a9e3988a9c9b37"
}

CHAIN A:

Code:

(
    [hash] => 2ba9f2bcb9ae882ffaa43494ae91134c616887ddca600378e9a25eea778a2996
    [confirmations] => 12119
    [size] => 205
    [height] => 1979440
    [version] => 1
    [merkleroot] => ed541177082e314cb52074ed623e25cdae032202827a9703ae4237ad375fd25e
    [tx] => Array
        (
            [0] => ed541177082e314cb52074ed623e25cdae032202827a9703ae4237ad375fd25e
        )

    [time] => 1447412954
    [nonce] => 516278877
    [bits] => 1d06cbd3
    [difficulty] => 0.14713906
    [previousblockhash] => b1bd687737f78895d8824fab7b9ecf32596cea8bf0591680abfda78af1d4db20
    [nextblockhash] => d67d2ac16e75e25e81e185b2380403fa36841485e37e338111c576006583067a
)

Blocks continue to be extracted on CHAIN B:

Code:

"hash" : "73cb52a7071f4f0052900cb952c46d782eb6fb7aba2e546ae7a9e3988a9c9b37",
"confirmations" : 30424,
"size" : 7027,
"height" : 1979441,
"version" : 1,
"merkleroot" : "ecbef08c29cdbfd4a5f6cea9357e7dfcd7079e9da127a6b1f2f4afe9740503fe",
"tx" : [
"d6e4b9f2163b7544b31d42956012034968752e3439fdbd1685673bba3bfdb428",
"c5ff7bda62b7e778f27548d686efc1249d5d93f45d40d3bdcc7742cbe9d7f9c5",
"e9c3946e5239e7ac115338da4c92c9aa26690bba798c9d113c030391880e1625",
"37571976c7209a0480e74b066d191baac658543b7cb90b4b027172f438658f7a"
],
"time" : 1447424925,
"nonce" : 3585901383,
"bits" : "1d06cbd3",
"difficulty" : 0.14713906,
"previousblockhash" : "db968b37f69149a1babb466d7447c09bc40412c1bca85a7c066767c36287d60e",
"nextblockhash" : "a06b26e9a730ba0d78a7f6f769bec5d2a89167de6c2c2c7b73744f39b575fc9d"
}

Blocks also continue to be extracted on CHAIN A:

Code:

(
    [hash] => d67d2ac16e75e25e81e185b2380403fa36841485e37e338111c576006583067a
    [confirmations] => 12120
    [size] => 205
    [height] => 1979441
    [version] => 1
    [merkleroot] => aba79f945e27931eee05b5ec892e0194de54340afc87d8a40cbee714dbb7cad8
    [tx] => Array
        (
            [0] => aba79f945e27931eee05b5ec892e0194de54340afc87d8a40cbee714dbb7cad8
        )

    [time] => 1447412997
    [nonce] => 2857746708
    [bits] => 1d06cbd3
    [difficulty] => 0.14713906
    [previousblockhash] => 2ba9f2bcb9ae882ffaa43494ae91134c616887ddca600378e9a25eea778a2996
    [nextblockhash] => 470ccb519cb54256c8ee09dce5753f87504b3b738b60807767d8f9f5630f166a
)

Blocks on CHAIN B are about 3 hours slower than those of CHAIN A.
Looking further, it's quite clear what is happening.  Look at the log from CHAIN B:

Code:

SetBestChain: new best=7174e3eb00ce9294a1dd  height=1979449  work=344439187775260  date=11/13/2015 15:26:08
ProcessBlock: ACCEPTED
received block f631a80d97e36e907520
SetBestChain: new best=f631a80d97e36e907520  height=1979450  work=344439819742338  date=11/13/2015 21:06:51

A gap of nearly 6 hours.  Look even further:

Code:

SetBestChain: new best=1a3b9b9707b11e29582f  height=1979466  work=344449931215586  date=11/14/2015 12:24:39
ProcessBlock: ACCEPTED
received block 9e8a3ee25eb17b10bf93
SetBestChain: new best=9e8a3ee25eb17b10bf93  height=1979467  work=344450563182664  date=11/15/2015 13:54:49
ProcessBlock: ACCEPTED

A 25+ hour gap.

Meanwhile, on CHAIN A, block #1979467 has already been extracted more than 2 days earlier at Fri, 13 Nov 2015 11:18:10 GMT:

Code:

(
    [hash] => 685cdccb27c54b02264f1090c37b94268480c92b82d3e6ab557f7bf8c56d51ad
    [confirmations] => 12094
    [size] => 205
    [height] => 1979467
    [version] => 1
    [merkleroot] => 39caa872e52c7916d3e67beffb6022a3dffac7278e61ee51c0a4f8400a9f72a3
    [tx] => Array
        (
            [0] => 39caa872e52c7916d3e67beffb6022a3dffac7278e61ee51c0a4f8400a9f72a3
        )

    [time] => 1447413490
    [nonce] => 3710800501
    [bits] => 1d06cbd3
    [difficulty] => 0.14713906
    [previousblockhash] => 114e7c4a85f6bc586b54d74c5995c6da2ef271ac464ac70c77388afa8267cd25
    [nextblockhash] => 0de8b8298d5af0b705880e8b15037d21f29e65f49b881be30fe0e424b56f12d9
)

CHAIN A stalls at block #1983892 which is extracted at Sat, 14 Nov 2015 09:20:19 GMT.

Code:

(
    [hash] => 1b376f511ce6ef8d1d3ccb984b4bbc7a8a12da0e3afd5c70252be12c2849f27b
    [confirmations] => 7670
    [size] => 205
    [height] => 1983892
    [version] => 1
    [merkleroot] => 77dda279a75a4c521de8d5d43aeb8aa2a69ad5dbf4b31115089f5fe71c471e81
    [tx] => Array
        (
            [0] => 77dda279a75a4c521de8d5d43aeb8aa2a69ad5dbf4b31115089f5fe71c471e81
        )

    [time] => 1447492819
    [nonce] => 2157275238
    [bits] => 1e06cbd0
    [difficulty] => 0.00057477
    [previousblockhash] => effda313591c20d2278096f7b1de7d1191356885ba5cdceaa09cb3bb5c8c189a
    [nextblockhash] => 0ccfb8f1c3040349da5287ddba6c200724018ca98240c3d16f0dd8a9e6932f00
)

While the attack continues with blocks being extracted at a high rate on CHAIN B.

Code:

ProcessBlock: ACCEPTED
received block 00282fe75a60b8968f0a
SetBestChain: new best=00282fe75a60b8968f0a  height=1979786  work=344652160680546  date=11/15/2015 18:38:58
ProcessBlock: ACCEPTED
received block 10dd49b954f485ddb53b
SetBestChain: new best=10dd49b954f485ddb53b  height=1979787  work=344652792647624  date=11/15/2015 18:39:02
ProcessBlock: ACCEPTED
received block b2595485b4955154a280
SetBestChain: new best=b2595485b4955154a280  height=1979788  work=344653424614702  date=11/15/2015 18:39:13
ProcessBlock: ACCEPTED
received block bce58af2cd001a15b7ba
SetBestChain: new best=bce58af2cd001a15b7ba  height=1979789  work=344654056581780  date=11/15/2015 18:39:27
ProcessBlock: ACCEPTED
received block f2bde72133f36b6efe37
SetBestChain: new best=f2bde72133f36b6efe37  height=1979790  work=344654688548858  date=11/15/2015 18:39:57
ProcessBlock: ACCEPTED
received block 39ea927ca41d1b3151bb
SetBestChain: new best=39ea927ca41d1b3151bb  height=1979791  work=344655320515936  date=11/15/2015 18:41:07
...

4,426 blocks are mined in a period of 13 hours and by block #1983893 CHAIN B (Mon, 16 Nov 2015 03:27:16 GMT) is now ahead of CHAIN A (Thu, 26 Nov 2015 04:05:03 GMT):

CHAIN B:

Code:

{
"hash" : "a8d852c427110b57b16e1bbeebdaea0bc1ac94c63f6ca39697392bea94c3f3d7",
"confirmations" : 25972,
"size" : 317,
"height" : 1983893,
"version" : 1,
"merkleroot" : "ae78c0e941fc74016f3fa9b6ed9a8a2d194b45f9c1368f1a34584e194b12d992",
"tx" : [
"ae78c0e941fc74016f3fa9b6ed9a8a2d194b45f9c1368f1a34584e194b12d992"
],
"time" : 1447644436,
"nonce" : 1542849024,
"bits" : "1e06cbd0",
"difficulty" : 0.00057477,
"previousblockhash" : "39888a17161be5242f22d17fdc4cf2bbe555db654bf951161bc06356293d3168",
"nextblockhash" : "ea0f9dfa35e6daeeeae72e7d1e6924cccf8c49db5e19cc8e583691b3deb9ee20"
}

CHAIN A:

Code:

Array
(
    [hash] => 0ccfb8f1c3040349da5287ddba6c200724018ca98240c3d16f0dd8a9e6932f00
    [confirmations] => 7669
    [size] => 3165
    [height] => 1983893
    [version] => 1
    [merkleroot] => 158ebfa755bd4e2d17c9a502a6204c4d5ff11f4bfacba13af97353bbbabf5290
    [tx] => Array
        (
            [0] => b8857d17ec1a3e4b213909d5a63b6daef74fdbd8c6325aa89e435831512ede5a
            [1] => e3330a2c5c9a39f08d5f6e1f4aa39f97c48c85a31b7c86d3e18e52c07fda620b
            [2] => 658829014933092f697ca58cc13e83f29f030c88f56790bb5dbcfd48b3e29216
            [3] => 4ef1e8da53968ffa04f44ef1b4f07cacfcb12edd6c52fe0d8cbccd6bcb9e5fa0
            [4] => 98420e95b67399d303d5d2c8c706d72b01bfc7db6b66013df03524496cd9dd74
            [5] => 57314196a1f32eba9631f2b27cc6894e027bd2803b725c74f0abd6c0e5397df0
            [6] => fd5b47c25e370fbf999fa4dc382c37f1cf9571ad1a1864e6dec23e8c54fcfd7f
            [7] => 95434f95d28bdae57149ec52dd449ca7488bbb4c46b4da87616f5477f009acb1
            [8] => 16522c8731ff6a2995e89b5719e0b5e4f062c30f85f24578501db5b587e3e5ce
            [9] => a1215262e55f06358dcad78ed7c162bf575db7a3bf04270abc6ea81150164162
            [10] => 29c0904dffda2040e6c183d8987611d1588ae26b5938334d0f871dc92468f21b
            [11] => 03d595c1c2377f1b5787e2749d9d071b5966fa58ed7f68e8b73b93442cb81215
            [12] => 1dabc452eac51f63b30e874f90995958f333b977966b0a8ce4ff9466c4c9b239
            [13] => 43bbb679302e3768bd166c14c0218e010d14f1f3bf887dfb4949a73c002d0416
            [14] => 6c16e09af4845390d2f963db6aecac2d1fc22ca1ae874b73e33511ae9f7a9e40
        )

    [time] => 1448510703
    [nonce] => 1848770560
    [bits] => 1e06cbd0
    [difficulty] => 0.00057477
    [previousblockhash] => 1b376f511ce6ef8d1d3ccb984b4bbc7a8a12da0e3afd5c70252be12c2849f27b
    [nextblockhash] => 9902f32ceb4b11a5abd913c9c7dd2cd5034b557bcac991558d4b36461bf43e88
)

There is a huge fork and it will take a very long time to re-organize it's self.

[coiner561]

Is there a chance of this happening due to the 15 only sec block time and the lack of more miners?

[CryptoCoderz]

Is there a chance of this happening due to the 15 only sec block time and the lack of more miners?

This is most likely due to the fact that I had been gone for a minute. Sorry about that.
Anyway besides the site finally being finished and getting linked to Binary-Coin.com I believe we might be able to shed some light on the chain split.

Seems like a pool or other network split us apart and yes it was due to mining issues with the 15 second block times (which is something that is a bit unnavoidable with its rate of speed but something that we are looking into a way to manage all of the micro forks that will innevitably occur).

During the split however ANYONE USING OUR WALLETS IS ON THE CORRECT CHAIN.

The reason I say this is because our wallets are HARD CODED to our nodes and our nodes are on the original chain with checkpoints.
(Will provide details upon request)


Another reason why I say this is a while back there was an attacker who actually contacted me asking why his blocks weren't being accepted. Looking into the issue we quickly found that the payout amount had been heavily changed (to pay an ridiculous amount more than original block payout) and the nodes were rejecting their transanctions then kicked them off the network entirely.... fail....

We have been launching more and more nodes over the past few days as you all should notice connections increase to your wallets followed by a client update coming TONIGHT

PLEASE keep us posted about any questions or concerns and I just wanted to say thank you to all of you still running Binarycoin and believing in it. We all see a bright future for it.

Also, a HUGE THANK YOU to the research into the side chain and such an informational post with great attention to detail.
Honestly we haven't even had time to fully digest everything but after verifying a few things on our end I can say that again anyone running our client is on the right chain.

As for the chain stalling out a little while ago I'd like to apologize as during the facility migration our mining equipment was not setup for quite some time but now have dedicated mining equipment back on the chain. (not much just a couple lighter miners to keep it rolling for now and to allow other's to have the chance to mine the chain and get some coins)

again we look forward to future developments with Binarycoin and will have an update for you all tonight.

[animalroam]

Just a heads up that a block explorer is operating here: http://cryptobe.com/chain/Binary.

[CryptoCoderz]

Just a heads up that a block explorer is operating here: http://cryptobe.com/chain/Binary.

THanks much animalroam!


BTW:



No more Delays, We launch today FYI to all (Bugs are worked out)!!! New ANN will be posted lasted by END OF DAY.
New nodes have been launched and hardcoded into the new wallet.
New features include:
Auto-updating wallet (you'll never be running on an outdated client anymore)
A large support effort has been put towards this coin and will now feature chat support from the official site and even phone/email support.
Many further upgrades and improvements are scheduled but we feel this is a good stepping stone is to officially launch as a team and push this project forward.
Mobile Wallet is coming + web wallet soon!

BIGGEST NOTE: This wallet upgrade will NOT mess you or your coins up. This is a seamless upgrade that is aimed at adding more checkpoints to the coin, adding stability and increasing security while at the same enhancing usability.

[animalroam]

Just a heads up that a block explorer is operating here: http://cryptobe.com/chain/Binary.

THanks much animalroam!


BTW:



No more Delays, We launch today FYI to all (Bugs are worked out)!!! New ANN will be posted lasted by END OF DAY.
New nodes have been launched and hardcoded into the new wallet.
New features include:
Auto-updating wallet (you'll never be running on an outdated client anymore)
A large support effort has been put towards this coin and will now feature chat support from the official site and even phone/email support.
Many further upgrades and improvements are scheduled but we feel this is a good stepping stone is to officially launch as a team and push this project forward.
Mobile Wallet is coming + web wallet soon!

BIGGEST NOTE: This wallet upgrade will NOT mess you or your coins up. This is a seamless upgrade that is aimed at adding more checkpoints to the coin, adding stability and increasing security while at the same enhancing usability.

Hi CryptoCoderz,

Did you get a notice about the late payment in PM?

Thanks.

[CryptoCoderz]

Hi CryptoCoderz,

Did you get a notice about the late payment in PM?

Thanks.

We are EXTREMELY sorry about this! Will not happen again, I have PM'd you back.

[CryptoCoderz]

BinaryCoin's WebPage


Linux:
COMING SOON

Windows:
DOWNLOAD WINDOWS CLIENT w/ Auto-Updater (v0.6.4.1)
Compiled by "CryptoCoderz"

OSX:
DOWNLOAD MAC OSX 10.8+ CLIENT  (v0.6.4)
Compiled by "ctgiant"


Excuse us guys we have been very busy and it's still not a good excuse. To be honest not everything is even finished to where we wanted however it is all functional and working well so we have released what we have so far and will updating the site along with all of our support features very quickly.

Thank you all for bearing with us through this and I do apologize about the wait, hopefully everyone can look past this and see the development in mind.

Looking forward to hearing from everyone in Binarycoin.
If you guys want there is also a Bianrycoin chat room on the website!
We ourselves though will be more active after the weekend (after most of the updates roll through)

[CryptoCoderz]

Hello binarycoin Community!


Some good news: We've been added to another great exchange!



Thank you COINGATHER!!!

Feel free to have a look and get involved here as well! Currently this makes 3 total places to by/sell/trade your binary!
Real world usability in mind this is a great stepping stone and once some volume starts moving around should solidify this coin nicely in the crypto world.

Please let me/us know if you any questions! We are here to help!

[DigitalCurrencyConsultant]

plus 1 now makes 3 

[lorenz2356]

can you give a copy of installer. it always says it has an error. 

[CryptoCoderz]

can you give a copy of installer. it always says it has an error.  

Sure we can provide you with a standalone client link if you'd like or simply uninstall and re-install the client and run it (it initially runs an update to verify the procedure is working)

Just as an explaination:  cLient_Runner_B.exe runs the getVer.exe which is in the installed APPDATA directory under CryptoCoderz/BIC-Client, getVer reaches out to cryptocoderz.com (coded with IP instead of domain name) and gravs a version txt which it reads from to determine whether or not to download a new client.

Please provide any errors you are experiencing to us we will remedy them! We want a flawless working system.

[coiner561]

https://gyazo.com/dd4a51d512f5d006b07c46cdb392c426
Got this after downloading and trying to install the wallet

[lorenz2356]

can you give a copy of installer. it always says it has an error.  

Sure we can provide you with a standalone client link if you'd like or simply uninstall and re-install the client and run it (it initially runs an update to verify the procedure is working)

Just as an explaination:  cLient_Runner_B.exe runs the getVer.exe which is in the installed APPDATA directory under CryptoCoderz/BIC-Client, getVer reaches out to cryptocoderz.com (coded with IP instead of domain name) and gravs a version txt which it reads from to determine whether or not to download a new client.

Please provide any errors you are experiencing to us we will remedy them! We want a flawless working system.

"it says integrity check failed. common causes are incomplete download and damage media"

re redoanload it 4x but it doesn't work. can you give me a link? 

[coiner561]

can you give a copy of installer. it always says it has an error.  

Sure we can provide you with a standalone client link if you'd like or simply uninstall and re-install the client and run it (it initially runs an update to verify the procedure is working)

Just as an explaination:  cLient_Runner_B.exe runs the getVer.exe which is in the installed APPDATA directory under CryptoCoderz/BIC-Client, getVer reaches out to cryptocoderz.com (coded with IP instead of domain name) and gravs a version txt which it reads from to determine whether or not to download a new client.

Please provide any errors you are experiencing to us we will remedy them! We want a flawless working system.

"it says integrity check failed. common causes are incomplete download and damage media"

re redoanload it 4x but it doesn't work. can you give me a link? 

same here

https://gyazo.com/dd4a51d512f5d006b07c46cdb392c426
Got this after downloading and trying to install the wallet

[CryptoCoderz]

"it says integrity check failed. common causes are incomplete download and damage media"

re redoanload it 4x but it doesn't work. can you give me a link? 

Well that's unnerving. Here is a direct link to the client, simply rename the .txt to .exe and run the client
STANDALONE CLIENT

https://gyazo.com/dd4a51d512f5d006b07c46cdb392c426
Got this after downloading and trying to install the wallet

 THANK YOU FOR THE PIC!!! Re-compiling the installer, excuse the mistake I must have cut it off prematurely some how!
In the meantime please feel free to use the standalone client, just remember to grab the repaired auto-updating client later if you'd like to not have to worry about phased out clients later in developement.

 simply rename the .txt to .exe and run the client
STANDALONE CLIENT

[coiner561]

"it says integrity check failed. common causes are incomplete download and damage media"

re redoanload it 4x but it doesn't work. can you give me a link? 

Well that's unnerving. Here is a direct link to the client, simply rename the .txt to .exe and run the client
STANDALONE CLIENT

https://gyazo.com/dd4a51d512f5d006b07c46cdb392c426
Got this after downloading and trying to install the wallet

 THANK YOU FOR THE PIC!!! Re-compiling the installer, excuse the mistake I must have cut it off prematurely some how!
In the meantime please feel free to use the standalone client, just remember to grab the repaired auto-updating client later if you'd like to not have to worry about phased out clients later in developement.

 simply rename the .txt to .exe and run the client
STANDALONE CLIENT

No problem. Is there an IRC channel for BIC?

[CryptoCoderz]

No problem. Is there an IRC channel for BIC?

There was at one point but if it still exists or its condition is completely unkown by us at this time.
On the cryptocoderz.com site though there is a chat built into the site and a binarycoin room for community members to lounge in.
I know it's not the same as an IRC with a tipping bot but one step at a time.

Well my FTP client cut the upload off early... Didnt for all the other coins we support with auto-installers, just of course this one lol. (fixing this now, will have it re-uploaded latest within 6 hours)