Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS

[dreamwatcher]

Quick note:

After I updated the database for CAP on cap.cryptocoinexplorer.com, I updated the client with your updates.

I am not sure if this change was intentional or not, but the "flags" field when a block is POS now reads "proof-of-stake stake-modifier".

Most coins just read "proof-of-stake". I modified the database loader to understand the modified flag, though I do not like having customized code for a coin. One of the main points for developing CCE3 was to completely eliminate that need.

Just let me know if it is going to stay that way, or when you change it back so I can adjust the code accordingly.

[1714129664]

1714129664

[1714129664]

1714129664

[1714129664]

1714129664

[tricass]

i also downloaded the 1.5.2 and it is not syncing not a single connection and i added the nodes to the conf file

Yeah no issues syncing on my wallet

having the same issue, adding
addnode=cap.nodes.btcrypt.net:7685 to my conf now, and get this synced up!

UPdate - this works perfectly, syncing up now!

This did not work for me. I needed more nodes so added these and am now syncing....

listen=1
addnode=50.137.233.14         
addnode=69.10.44.115           
addnode=192.64.86.238
addnode=cap.nodes.btcrypt.net:7685
addnode=72.78.100.7
addnode=216.155.142.154
addnode=50.117.78.242
addnode=46.105.118.226
addnode=67.210.249.29
addnode=23.251.65.46
addnode=37.187.73.182
addnode=84.200.17.107
addnode=nodes.btcrypt.net

[presstab]

i also downloaded the 1.5.2 and it is not syncing not a single connection and i added the nodes to the conf file

Yeah no issues syncing on my wallet

having the same issue, adding
addnode=cap.nodes.btcrypt.net:7685 to my conf now, and get this synced up!

UPdate - this works perfectly, syncing up now!

Mind posting your conf file content? i have added the above, but still nada.

thanks.

I haven't confirmed this in the source code, but someone else further back in the thread posted saying that their client only began to sink when the .conf was named BottleCaps.conf not bottlecaps.conf - I am not sure if this has any truth to it, but that is what I am using too and only have a single addnode and it syncs right away.

Edit - found this in the source code, not sure whether this means that it must have the right capitilization or not, but it is there
init.cpp line 222

Code:

"  -conf=<file>           " + _("Specify configuration file (default: BottleCaps.conf)") + "\n" +

[NuShrike]

Some of my nodes not recently posted (from Bottlecaps.conf on Win7):
addnode=202.60.68.65
addnode=173.192.30.91
addnode=37.187.28.68
addnode=142.4.219.23
addnode=54.186.69.238
addnode=[2001:0:9d38:6abd:289b:1e6d:b95e:87e2]
addnode=72.52.231.153
addnode=[2001:0:5ef5:79fb:30bf:21b5:a9e8:a252]
addnode=[2001:0:9d38:6ab8:3860:27e1:9fc7:22fd]
addnode=68.96.116.162
addnode=50.149.31.242
addnode=84.200.17.249
addnode=118.127.61.68
addnode=23.252.65.46
addnode=212.83.191.197
addnode=173.192.180.226
addnode=144.76.33.10
addnode=70.98.114.237
addnode=2.101.76.175
addnode=24.255.59.102

Less likely to still exist going down the list.

[dreamwatcher]

addnode=84.200.17.249

Used to be the CCE3 test server. The CAP daemon for CCE is now on  84.200.17.107. Feel free to use it (22 connections right now).

I have given Tranz a domain to use as a seed node that points to this address if he wants to use it

[ElTomeko27]

Guys I v got a warning in my wallet "WARNING: Checkopint it too old. Redownload Blockchain. If warning persist contact the Development Team" What is wrong??

[presstab]

Guys I v got a warning in my wallet "WARNING: Checkopint it too old. Redownload Blockchain. If warning persist contact the Development Team" What is wrong??

This happened to me too. Try restarting the client and waiting for a few minutes and see if it goes away. That is what worked for me.

[ElTomeko27]

Guys I v got a warning in my wallet "WARNING: Checkopint it too old. Redownload Blockchain. If warning persist contact the Development Team" What is wrong??

This happened to me too. Try restarting the client and waiting for a few minutes and see if it goes away. That is what worked for me.

True, now its seems to be ok. ETA new wallet ver.??

[presstab]

Guys I v got a warning in my wallet "WARNING: Checkopint it too old. Redownload Blockchain. If warning persist contact the Development Team" What is wrong??

This happened to me too. Try restarting the client and waiting for a few minutes and see if it goes away. That is what worked for me.

True, now its seems to be ok. ETA new wallet ver.??

I think Tranz said something like 30 days from now.  Then it will be 30 days from the release until hard fork occurs.

[sheffters]

Cap.nodes.btcrypt.net is down at the moment.

Kernel patch and other updates have somehow borked the scrypt and x11 wallets so none of them start. Bitcoin / primecoin wallets still running, so #headscratch

I need to rebuild it. Will do over the weekend.

S.

[Tranz]

Quick note:

After I updated the database for CAP on cap.cryptocoinexplorer.com, I updated the client with your updates.

I am not sure if this change was intentional or not, but the "flags" field when a block is POS now reads "proof-of-stake stake-modifier".

Most coins just read "proof-of-stake". I modified the database loader to understand the modified flag, though I do not like having customized code for a coin. One of the main points for developing CCE3 was to completely eliminate that need.

Just let me know if it is going to stay that way, or when you change it back so I can adjust the code accordingly.

No this shouldn't be this way. When I issue getblock on a PoS block I get flags of just proof-of-stake. Which RPC command is giving you that?

[dreamwatcher]

Quick note:

After I updated the database for CAP on cap.cryptocoinexplorer.com, I updated the client with your updates.

I am not sure if this change was intentional or not, but the "flags" field when a block is POS now reads "proof-of-stake stake-modifier".

Most coins just read "proof-of-stake". I modified the database loader to understand the modified flag, though I do not like having customized code for a coin. One of the main points for developing CCE3 was to completely eliminate that need.

Just let me know if it is going to stay that way, or when you change it back so I can adjust the code accordingly.

No this shouldn't be this way. When I issue getblock on a PoS block I get flags of just proof-of-stake. Which RPC command is giving you that?

<Edited due to new information>

Nevermind, I think figured it out and it was on my end and a change i need to make to all the explorers.
For example:

Code:

/bottlecapsd getblock 0c7ca959f024fd3978baac766f3e926296ba34bda1355cb402378c1cc7c23ae4
{
    "hash" : "0c7ca959f024fd3978baac766f3e926296ba34bda1355cb402378c1cc7c23ae4",
    "confirmations" : 585,
    "size" : 455,
    "height" : 452151,
    "version" : 4,
    "merkleroot" : "1f2f9f4f861d19be465b6fdf66b93f62b9b6281bfa669531a9d55797ffaf215c",
    "mint" : 0.03334700,
    "time" : 1400241722,
    "nonce" : 0,
    "bits" : "1e00ffff",
    "difficulty" : 0.00390625,
    "previousblockhash" : "209aaa5a4590a2ff500a9ddd8aed2828443c7b6ae61d254d47127c3f0c3d2135",
    "nextblockhash" : "000000001ae348915add9d6e7d573d29aee634b9968bd623177cb542c8210694",
    "flags" : "proof-of-stake stake-modifier",
    "proofhash" : "0000023cabb7b7d4415132b8ac57444941c6d46ca396faed5907d6d2324ebd3d",
    "entropybit" : 0,
    "modifier" : "ead1ba8ee00e2648",
    "modifierchecksum" : "64b1e979",
    "tx" : [
        "b5f3336d507f4e325083e0f3ad9102df626ab6a11879cc2df27874468ef1f7ae",
        "8376612bc7d03dfd735c7fb6728ee6d5aecd939c55c0ba516812dffc9dda758f"
    ],
    "signature" : "3045022001d5c9ac9b2eafe69c49431557d26ef29ff25a59310b301b0bae095fdfb086c8022100a239bfe23dda210aa3fc48a983ec7510ed68275206aead86d33960bfe384f910"
}

The block before it reports a different modifier and the blocks after report the same modifier.  The "stake modifier" is an extra flag indicating that the stake modifier has been switched.

Anyway, a simple change in the check condition from == "proof-of-stake" to != "proof-of-work" solves the issue and this has helped me find a bug that I need to patch on all explorers.  

[Tranz]

Ahh. glad to hear you found the bug.

I have added faststart tonight. Still testing full sync, speed test.
https://github.com/Tranz5/bottlecaps/commit/ed8833b8c5df86490fadf77760b11afa9a263547

[Tranz]

Ahh. glad to hear you found the bug.

I have added faststart tonight. Still testing full sync, speed test.
https://github.com/Tranz5/bottlecaps/commit/ed8833b8c5df86490fadf77760b11afa9a263547

5hrs sync, 10 sec load. Good by me!

[kingscrown]

any working pool on last version ?

[Tranz]

any working pool on last version ?

Might try this one?
http://cap.cryptotroll.com/index.php

[Tranz]

Coin Control with weight added.
https://github.com/Tranz5/bottlecaps/commit/a9f1653073ab35592fd09145b8d64e22e08eedea

Thanks to presstab for getting this one going.

[presstab]

I have added faststart tonight. Still testing full sync, speed test.
https://github.com/Tranz5/bottlecaps/commit/ed8833b8c5df86490fadf77760b11afa9a263547

Wow I thought this would be much more complicated. This is the most important updates in my opinion.

[Tranz]

Coin Control with weight added.
https://github.com/Tranz5/bottlecaps/commit/a9f1653073ab35592fd09145b8d64e22e08eedea

Thanks to presstab for getting this one going.

It's great to see these updates rolling in.  Great job, guys!  Does anyone have an opinion about dropping the instances of camel case from BottleCaps?  I know it is minor, but it tends to confuse people when they create a .conf file and it must be named BottleCaps.conf as opposed to Bottlecaps.conf or bottlecaps.conf. 

And a question for Tranz: When you compile the QT for Windows, do you go the route of including all the separate .dll files in a zip or do you go with something like Gitian?  I have my preference, but I am just curious.

Once I am done, it will be 1 static exe, no dlls.

[tokyoghetto]

i personally don't use cryptocointalk,  I don't know about other members. This new development might lose momentum if the discussion is moved IMO.