Hello,

KK ? are you ready ?

 

Best regards

Cest Ballot

Would be perfect! To bad I'm horrible at marketing :/

Looks like the pool is down again.

Edit: It's back.

http://pool.cestballot.fr/

News :

pool is up after little update.

we increase min diff at 3.77

we have 2500+ connections for 750reques/s

we will work on min diff autobalance and GPU pool.

during GPU pool beta test and after we will increase min diff at 3.9 or more to secure all pool process

With Trash, make cash
Stop loss cash, Recycle your Trash

Best regards

Cest Ballot

the biggest features are still being built out

Voting for CSD/////
 Your vote will be worth more if you login (Register)  and YOU get 500 sat for vote !!!!
Register user 5 votes, 24 h
For registrer you win 10 000 sat !!!! (at current rate CP btc )
https://cryptoine.com/user/register?ref=ZNeEasctGV

Then you also get extra 2 Crypto Points
register and vote  

From our IRC: Updates on Core Development

@Razerglass
not a bad idea laughingbear, Videlicet is pos triggered by block? or time?

@Videlicet
I use time lock block activations, so it will be an exact time, which we can count down until the second as we see block version 4 activate, new changes activate in core, and PoS blocks start being accepted.
Since our clocks are unified within a few seconds, why not take full advantage of it
I'll include updates to coinshield.io for the update too
To show the countdown to updates under Unified Time in the Network Tab.
And the current block version, etc.

+laughingbear
nice

@Videlicet
So we can all monitor future updates, will also have under connections a field that says "Connections still not updated"
So we can see how much of the network has updated.
I want to build a clean protocol for core updates that make it smoothest possible for all users, part of this will be an automatic update feature
But I only want to do this once node trust is done, so that trusted nodes can seed their binary to other nodes that need to update.
For linux users, might make a seperate bin that automatically pulls github source and compiles on new updates.
But this will be when I release source, which I really don't want to do until we are pushing Core 2.0.0 so it can be fully LLL integrated, as this will change a lot of the directory structure, code structure, dependencies, etc.
Our first library to rid of is Berklee DB to be replace by LLD, then eventually to c++ 11 and rid ourselves of boost.
So our only dependency will be OpenSSL.
Will make compiling a lot nicer
Which means the whole serializations system in Coin Shield core will be replaced by the LLS

@cestballot
LLS?

@Videlicet
Which means before we will need to change txid hash to be generated from LLS serialization rather than boost
Lower Level Serialization
I built it from scratch

Thank You,
Viz.

This is more regarding future updates post 1.0.3 

Thank You,
Viz.

Maybe Our Coin Shield?

Funny you say this, cause I own ourcoinshield.org 

Was my first choice in domain before we went to coinshield.io
Viz.