Our wallet is updated, but we won't be re-enabling it till a blockexplorer is up.  

thanks
richie@bittrex

http://explorer.triangles.technology


Coin Amount fixed. Some basic css.

And yes, I was lazy, i did not make my own css, I ripped it from some other coins block explorer. There will be time to change that - but that's not today.

Time to bring everyone to the right chain:

If  "getblockhash 12460" in the debug console doesnt give you this output you're not on the right chain: 4df338563eb017db366be9568e9595f8e2b18580fe0d361db4022ad8c6add694.

So, how to get there with a really clean wallet and a really clean blockchain file in a really easy way?

1. In your currently running wallet go to debug console and do a "dumpprivkey <TRIaddress>" for every address you have in the "Receive"-Tab (you can spare those which have no coins and which you dont want to keep.). Note those private keys in some txt file. [to see change addresses in your old wallet, use listaddressgroupings in console - pseudo]
2. Close wallet. Rename the %appdata%\roaming\triangles folder and keep it as a backup.
3. Create a new, empty "triangles" folder in %appdata%\roaming. Drop only this bootstrap there, nothing else: https://mega.co.nz/#!RZVDhDia!XHDCWzUpMEzZTkU30ll5zGGIT_peBdj9TvFs3DgmTgs (after you extracted it from the zip archive)
4. Start the wallet (takes a while - it imports the blockchain from bootstrap). Use "-connect=ubxidutptf2sslhq.onion:24112" at first run (Its the 24/7 node which will be the block explorer) and let it sync - you now have the cleanest of all possible wallets and databases.
5. Leave your new, clean wallet connected to that node and do the importprivkey thing with each of your keys you kept in that txt file. "importprivkey <privkey>" in debug console.
6. Let the wallet run that way  (connected to ubxidutptf2sslhq.onion:24112) until most of your acquired coinage is used (simply wait a few mins). After you mined a few blocks close your wallet and start it again (without "-connect=....")

Please do every step as written. Especially the restarting without "-connect" at the end

Now check again:

getblockhash 12460

4df338563eb017db366be9568e9595f8e2b18580fe0d361db4022ad8c6add694


Problems? Tell me.
(brb - 1 to 2 hours)

if you have more than one staking wallet: do one first - wait a few mins - do the 2nd. this way you decrease the risk of creating a "private fork".

Time to bring everyone to the right chain:

If  "getblockhash 12460" in the debug console doesnt give you this output you're not on the right chain: 4df338563eb017db366be9568e9595f8e2b18580fe0d361db4022ad8c6add694.

So, how to get there with a really clean wallet and a really clean blockchain file in a really easy way?

1. In your currently running wallet go to debug console and do a "dumpprivkey <TRIaddress>" for every address you have in the "Receive"-Tab (you can spare those which have no coins and which you dont want to keep.). Note those private keys in some txt file.
2. Close wallet. Rename the %appdata%\roaming\triangles folder and keep it as a backup.
3. Create a new, empty "triangles" folder in %appdata%\roaming. Drop only this bootstrap there, nothing else: https://mega.co.nz/#!RZVDhDia!XHDCWzUpMEzZTkU30ll5zGGIT_peBdj9TvFs3DgmTgs (after you extracted it from the zip archive)
4. Start the wallet (takes a while - it imports the blockchain from bootstrap). Use "-connect=ubxidutptf2sslhq.onion:24112" at first run (Its the 24/7 node which will be the block explorer) and let it sync - you now have the cleanest of all possible wallets and databases.
5. Leave your new, clean wallet connected to that node and do the importprivkey thing with each of your keys you kept in that txt file. "importprivkey <privkey>" in debug console.
6. Let the wallet run that way  (connected to ubxidutptf2sslhq.onion:24112) until most of your acquired coinage is used (simply wait a few mins). After you mined a few blocks close your wallet and start it again (without "-connect=....")

Please do every step as written. Especially the restarting without "-connect" at the end

Now check again:

getblockhash 12460

4df338563eb017db366be9568e9595f8e2b18580fe0d361db4022ad8c6add694


Problems? Tell me.
(brb - 1 to 2 hours)

if you have more than one staking wallet: do one first - wait a few mins - do the 2nd. this way you decrease the risk of creating a "private fork".

Yes, did everything you said. synced to block 12190 immediately. restarted wallet and now its to block 12193

10:22:05

getblockhash 12193


10:22:05

6e34c6ccdf84638057025485cd184e6f0731edc5c0eced086e64e8e07df2c2d9

0 active connections for the wallet?

We might actually be okay now.  Chain movement is much better.

Anyone who wants to test TRI with us but has no TRI, sync your chain to the current block, and I'll send you 5 TRI.  PM me your TRI address.

Everyone with TRI, update to latest client.  I think we finally got it.

Wallets:

First make a backup of your wallet. Everyone should do that from time to time. Copy the "%appdata%\roaming\triangles" folder (Windows) to a safe place. Done.

WINDOWS wallet, v 3.4.3.1 "Cheops":

https://mega.co.nz/#!dUkW1TBY!tt7a9rVi4qhdkVi-LiT2MXdBTnV_XtLGmq3KGLlptZA


Included is a folder with a bootstrap.dat file with 10881 blocks (if you wallet isn't synced to 10881 blocks before you update OR IF YOU PREVIOUSLY USED YESTERDAYS RELEASE - see the included readme!). Also a folder with a peers.dat file (if you have trouble finding peers - see the readme!). This bootstrap.dat file is also useful if u just downloaded the wallet: create a folder "triangles" in %appdata%\roaming and place the bootstrap.dat into that folder - then start the wallet.

If u have coins in your wallet, please start your wallet  with the "-connect=lkta5xj5nlnxxmrt.onion:24112" switch via commandline the first time after you updated your wallet. Its a non staking node and syncing to that node first prevents initial forking. Wouldn't  be much of an issue if it happens though. This also helps if u have trouble getting a connection despite using the peers.dat (see above).

once synced, close your wallet and start it again without "-connect" parameter. otherwise youre wallet wont connect to other nodes.

Also I think after 24 or maybe even 48h it's time to calculate the average blocktime and decide if to change some parameters. Like introducing a NODE_MIN_STAKING_INTERVAL or something. No more "block spamming", probably no more or almost no 0.00 reward blocks.