yep.

sounds all right. you dont neccessarily mint a block at  once when are staking. staking may take a while - this increases with rising diff. what does it say about your weight when u hover the red triangle?

edit: wait a few mins - coins have to reach min stake age. blocks will be mined!

ps: also yes, 500! 3/4 thank you!

edit: blocks mined. confirmed.

edit 2: network weight 7. its adjusting. TRI became self aware.

that.

those blocks should stop to occur once more nodes are connected/diff rises.

i see them! thanks! now with 3/4 confirmations

see above.

edit: diff was 6e-8, now it is 4e-7.

btw guys, i guess u could safely resend the TRI now.

Low diff. It will adjust.

The number of blocks has no influence on the interest rate. you get 33% per anno based on coinage when the block gets minted - thats it.

edit: Some other of my coins reached stake min age and minted a block. looking really good.

edit: I just mined a 0.00 reward block. Even that can happen with low diff. But as i said - diff is rising/adapting.

Btw - you asked regarding network weight yesterday:

Its 0 if only few clients are staking (intended behaviour)  - it should rise if more wallets are online/staking.

edit: PoS diff is rising - it lost one zero since blockchain restart. So these extremely fast block intervals should level. Good!

Yes, there is one step: Bittrex isnt synced yet. Once they are, all these transaction are sent. Either that, or they cancel them in bittrex and you can resend.

Most important:
Not a single coin is lost.


Edit: I think some coins of mine reached minimum stake age and just mined a block. That was the 10977-blocks deadlock. We are obviously past that.

Haha.


@ the guy who resyncs the blockchain from scratch: isn't that annoying? use the bootstrap.dat!

edit: Added it. Also added it to my signature.

Update again: Since strange crashes on win8 (only for some users) happened, clean rebuild. Didnt work though - u either have to use a original 10881 blocks wallet (which has never been used with another version) or you have to do the import and export privkey thing. see a few posts above.


Starting @ block 10881 once again (with an updated client - so you have to work with the bootstrap file here if you used yesterdays release!):


THIS APPEARS TO BE WORKING.UPDATE NOW!

This is an instant hard fork - there is no update height involved (because we would never reach it)!


New GitHub repository:

https://github.com/TrianglesCommunityProject/triangles

bootstrap.dat and peers.dat only (see below): https://mega.co.nz/#!5BsnRCRR!RkUsysowjxWmUmT8HjF-JgoRR-SIrOdBfMHpQVwe9qE

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).



MAC wallet, wallet, v 3.4.3.1 "Cheops":

WE NEED SOMEONE WITH A MAC WHO VOLUNTEERS TO COMPILE IT!


TRI's main specifications:

X13 PoS over TOR

Coins in Circulation: ~49.5k
Annual interest: 33%
Coin Cap: 120k

Coin maturity: 7 blocks
Minimum stake age: 1 hour
Maximum stake age: 12 hours

Confirmations: 4



Tell me if problems arise - especially if your wallet crashes.

PS:

TRI  Address THrVU7gEKMQmtzoNMAGcGKitQ8MKGaHS13

1 hour alone is not enough. For network security reasons you cant create a PoS block with coins you created with the same stake modifier - (stake modifier interval - see latest Github commit).

in other words: at least a block with a different stake modifier between when you mined a PoS block + modifier interval  and when your coins mature (1 h later if they got 7 confirmations). those conditions are rather easy to meet though (they ARE already met for this cycle).

same applies to transfered coins.

that modifier interval was 1 hour before latest commit - so thats why we got stuck @ 10977 - now its 5 minutes.


I doubt i made anything clear now.

Basically: 2-3 wallets (croTek, whalebone, pseudonymdude...) and things work. For real this time.

Join the fun!

That worked @ StephenJH? 

However, you have to resend the transaction you sent after block 108881.

ok, then thats the cause. let me try to reproduce it...

yep. thats the reason.



Hint: If you used your wallet.dat with any previous released Cheops-Version its likely  "corrupted". It crashes when it tries to stake then. If that happens:

Workaround:

1. start the wallet with "-stake=0"
2. dump privkey in console: "dumpprivkey <TRIaddress>". do this for every Adress you have in the "Receive" Tab. Copy those Keys into a txt file or similar.
3. close the wallet.
4. rename the "triangles"-folder in %appdata%\roaming and keep it as a backup
5. create a new folder "triangles" in %appdata%\roaming
6. put the bootstrap dat there
7. start your wallet. after -2 mins a synced, clean wallet should come up
8. import your priv keys from step 2 via debug console: "importprivkey <privkey>"

Done, you now have a working wallet.

Edit: The two commands for debug console:


dumpprivkey <trianglesaddress> - Reveals the private key corresponding to <trianglesaddress>
importprivkey <trianglesprivkey> [label] - Adds a private key (as returned by dumpprivkey) to your wallet.

probably because the wallet was used with other version after 108881, right? (so it contains data which doesnt fit to change parameters) see above.

privkey should work around that issue.

is that a wallet update of the block 10881-time? or did u use that wallet.dat with later releases? the latter, right?

ok, do the privkey thing please, i dont know why, but that wallet is somehow corrupted (for the client)  thats something that should _always_ work.

that should work 100% as long as you have a clean running wallet. keep a backup as usual and try it.

try the "-repairwallet" switch first!

edit 2: "-stake=0" should disable staking. or "-reservebalance=100000".

edit 3: if u have a backup of your "triangles" folder from the 10881-blocks time: simply use it.

We can't simply use the 10977 blocks chain due to the changes i made to the code. I forgot that for a minute, sorry. It wont get completely loaded with the current client, so lets try 108881 again.

We still have 2 other options though:

- I could create a bootstrap with 10916 blocks out of the 10977 blocks - we could work with that
- i could add a hard checkpoint in the sources so we could still use 10977. i will do that if we have no success with this try. when we have those 3-4 staking clients online again, things should just work out the same way they did with 10977 blocks chain. *fingers crossed*

Update again: Since strange crashes on win8 (only for some users) happened, clean rebuild.


Starting @ block 10881 once again (with an updated client - so you have to work with the bootstrap file here if you used yesterdays release!):


This update is mandatory! You have to update now!

This is an instant hard fork - there is no update height involved (because we would never reach it)!


New GitHub repository:

https://github.com/TrianglesCommunityProject/triangles

bootstrap.dat and peers.dat only (see below): https://mega.co.nz/#!5BsnRCRR!RkUsysowjxWmUmT8HjF-JgoRR-SIrOdBfMHpQVwe9qE

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).



MAC wallet, wallet, v 3.4.3.1 "Cheops":

WE NEED SOMEONE WITH A MAC WHO VOLUNTEERS TO COMPILE IT!


TRI's main specifications:

X13 PoS over TOR

Coins in Circulation: ~49.5k
Annual interest: 33%
Coin Cap: 120k

Coin maturity: 7 blocks
Minimum stake age: 1 hour
Maximum stake age: 12 hours

Confirmations: 4



Tell me if problems arise - especially if your wallet crashes.

ok...i will check that tomorrow - whatever that is.

One thing you could try: does it run in win 7 compatibilty mode?


Or you could simply import your private key(s) into the blank, working wallet:

- start original wallet without connections (so it doesnt crash - remove peers.dat)
- dump all private keys via console: dumpprivkey <TRIaddress> (repeat for all adresses u have in "receive" tab), copy the keys somewhere
- start up blank, new, synced wallet. import the keys via debug console: importprivkey <privkey>

You would lose your unconfirmed transactions  though. Those become visible again as soon as someone else who has them in his mempool confirms them (=mines a block. should happen within the next blocks - if  not: resend them).

Worth a try, you cant lose anything if you keep a backup of your original folder.


Ok, out for a few hours now. Sleep! Finally...


Re:


Upcoming shortly:

- clean rebuild of the wallet (strange win8 starting issues for some ppl)
- starting off @ at yesterdays height until we got stuck again: block 10977 (maybe - it shouldn't but maybe - that also resolves the strange win8 issues). also the blockchain was quite lively then, it should move immediately!

 I have a good feeling about this one.

but a clean wallet can connect and is synced?