i love that gif.

But youre right, network is still stabilizing.

network weight 941. diff 1.5e-5 - we started with a fraction of that (6e-8).

currently: "Your weight is 10. Network weight is 941.. Expected time to earn reward is 1 hour"

Looking good.

looks good for now. but the the fixing thing has to happen anyways.

we will probably be able to do that without stopping and resyncing the whole thing with proper update height. if things dont get TOO messy over the next hours.

\o/

i  just made a bootstrap @ 11222 - so we can use that tomorrow in the worst case.

So much for today.
Network is alive, forks need to and will be adressed. Also 0 reward blocks and fast "Minting-Chains".

no:




getblockhash 11072

0ac5afcdbf8a47eb6ddd6d0d31e8f01a093f79dd4de6e8edc1250f35322926f8


getblockhash 11200

ece781fdff375c95a692d8551d809fe20dc15ac72478a161d1f2f4e5d8a591fd

thats my chain.

What a forky mess. I will definitely address that with a min minting interval tomorrow.


U should keep a wallet dat from block 10881 backed up. if u resync use that wallet.dat with the bootstrap.

if u dont have such wallet.dat: create and empty wallet with only bootstrap.dat in %appdata%\roaming\triangles, when its started import your wallets privkeys (read last pages). close wallet and safe your wallet.dat - its your clean 10881 blocks wallet from now on. then sync to the network.

if u used "-connect" switch, restart ur wallet without it once you are sync - otherwise your wallet wont connect to other nodes!

I would say we let the network run until tomorrow so everyone can play with it etc pp. Dont do any reasonable transaction or trades now!


I will fix that tomorrow and also select a suitable blockchain then - one which syncs from 10881 to the end without errors. Shouldnt really matter which one we/I select.
Expect the fix in approx. 24 hours, lets have fun with this playground until then.



edit: currently  both my wallets are synced to 11209. they did that on their own with bootstrap.dat.

let me check, maybe i forked. give me a few mins.

anyways....lets see how it evolves the next 12h.

please report how often u forked afterwards - maybe with some details like approx coins. if that isnt to personal.

remember:

Recovering from a fork:

Delete both blockchain files, drop bootstrap.dat into that folder, start wallet with "-connect lkta5xj5nlnxxmrt.onion".

As long as u have the same blockheight as that client youre fine (you can check via "getpeerinfo" - or if not there - search for the address in your debug.log or use the connect switch, see above).

We will decide tomorrow how and if this needs to be addressed.

Awesome. See above! Same thought. although a fixed minimum blocktime would be dangerous: different clients would try to mint a block the second those 2 mins are over - bi forking risk.  better do it with an interval per client, maybe even with some random part. 2.5 +/- 0.5 minutes or something.

It takes two to fork. I currently have 6 nodes "on my my side", so you better join me.

Delete blockchain files, put bootstrap into folder, start wallet with "-connect lkta5xj5nlnxxmrt.onion" - thats my sync node".

Reason for the fork happening: Large part of the weight distributed over few nodes. Will stabilize once more nodes come online.

For now, the right fork is where I am on (so you can easily sync to it with "-connect lkta5xj5nlnxxmrt.onion" and bootstrap in case u forked). If bittrex is online, bittrex is the right fork. Currently I'm thinking - if those forks continue to happen -  it might be wise to reduce the amount of blocks generated over time per wallet:

1st thought: 3mins min between blocks per wallet/node/address.

Effects/Facts:

- Easy fix
- Blockchain is working now, so we can do updates with proper forking at given block height without even interrupting the network - with enough time for everybody to update the client. As it is meant to be done.
- Forking risk would be greatly reduced
- The network would be a little slower (wouldnt matter with only 4 confirms needed - if u ask me).
- PoS rewards per block mintet gets bigger
- 0.00 reward blocks wouldl be greatly reduced up to almost no more 0.00 blocks.
- Chain-mining (where you mine a sequence of blocks) wont occur any more.

Any thoughts on this?

Btw... its relatively cold in northern/middle Europe currently. Noch beach.

I will be on a short island trip next weekend though.

(I have internet access - just in case)

Oh. Someone is on a fork with 11089 blocks. Wrong way! You should resync from bootstrap.

No need to rush with anything! Lets get bittrex to sync and enable the wallet first (tomorrow? if things run smooth).

New ANN when Block Explorer is available maybe?

Anyways,I'm fine with whatever the "Test Team" suggests or wants to do.  I will deliver whats necessary from my side.

Yep. Github is up-2-date.

PS: Someone could easily do the ANN thread if no "multiple Adminship" is possible - which is what i guess. It doesnt have to be me because I could simply PM the technical and download part to the Thread-Starter.

pps: damn, that blockchain runs smooth.

pps: those 0.0 coin blocks are btw normal and expected - influenced by the low maturity, the amount of network nodes and the interest rate and some other conditions i now cant recall. most important thing is: they keep the blockchain moving in adequate speed.

I dont know that either. But im glad if you guys manage that part. If they require something from me, let me know.

ps: Next stop: block explorer - I'm doing it. Might take 2-3 days - Weekend comes first.

It wouldnt hurt to notify bittrex about the progress and that we would like them to enable/update the wallet tomorrow if things still run smoothly.

edit: https://twitter.com/wurstgelee/status/505423199996485632

those 33% are fixed. the code is pretty clear about that:

with


So if u have 1 coin with an age of 365 days (1 year) on stake, you get a reward of .33 TRI.

That works.

its partly resolved - its no windows-issue, its a wallet.dat issue.
u will probably have to do the importprivkey-thing - unless u havent got a wallet.dat backup which wasnt even used once with any cheops release.

importprivkey works like a charm though.

protip: store your priv keys @ a safe place. thats all u need in case everything goes haywire.

for them to reenable the wallet again? i would have waited at least a few hours....but you seem to be optimistic.

about that new ann thread - is it possible to distribute admin rights here? so that more users could edit the OP?