[ANN] Triangles [TRI] Now Stable & Working Anonymous Cloak over TOR - ON BITTREX

[popolite11]

Guys, i've been trying to get synced all the way.  This usually happens after block 13000

ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake fff23827e8b0625b9feae1b2ddadc06d5efc4f8d904dfb5327164791aeecb0ff, hashProof=dbc40f0051f4f4a786b76e1de750dcd426e1b66571d5ffe9ef34541687583d85
WARNING: ProcessBlock(): check proof-of-stake failed for block 7c77066ed3d686ae6ed3fe42d41ca00029c125449c0ab3f9f178d48bb6a686ff
received block fc984ec25ff21f218996
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 3e840aa35046817ca3d2b37c192abd25c2276c6a1d2773faa11ae7d0817f7de2, hashProof=8ba89d084bd539ede2d1ebab7f3a4f549af2644271b40f2ada355f7f97679a61
WARNING: ProcessBlock(): check proof-of-stake failed for block fc984ec25ff21f218996b160e05305881e57c5fd0321698a97ba61cd4e4cd31b


Any suggestions?  tried the bootstrap.. tried the connect... never had this many problems trying to sync

Thanks
richie@bittrex

try to re download the blockchain again.

[wurstgelee]

Guys, i've been trying to get synced all the way.  This usually happens after block 13000

ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake fff23827e8b0625b9feae1b2ddadc06d5efc4f8d904dfb5327164791aeecb0ff, hashProof=dbc40f0051f4f4a786b76e1de750dcd426e1b66571d5ffe9ef34541687583d85
WARNING: ProcessBlock(): check proof-of-stake failed for block 7c77066ed3d686ae6ed3fe42d41ca00029c125449c0ab3f9f178d48bb6a686ff
received block fc984ec25ff21f218996
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 3e840aa35046817ca3d2b37c192abd25c2276c6a1d2773faa11ae7d0817f7de2, hashProof=8ba89d084bd539ede2d1ebab7f3a4f549af2644271b40f2ada355f7f97679a61
WARNING: ProcessBlock(): check proof-of-stake failed for block fc984ec25ff21f218996b160e05305881e57c5fd0321698a97ba61cd4e4cd31b


Any suggestions?  tried the bootstrap.. tried the connect... never had this many problems trying to sync

Thanks
richie@bittrex

try to re download the blockchain again.

Nope. Read a few posts above.

[StephenJH]

I tried to run a fresh wallet just to check.
Using bootstrap in the instructions I get stuck at 13000. Also using the latest bootstrap on the website I get stuck.

I do have a wallet synced and minting though.

[pseudonymdude]

Ok, small update - I have to catch a plane!

There obviously is a problem with clients trying to fully sync from bootstrap.dat.

"-checkblocks=0" doesnt throw an error though - so you face no problems if u only check your own blockchain copy.

I narrowed it down to some changes 3angle made in the sources earlier. I will continue to further investigate this issue and fix it. Since I´m on holidays from now on, this might take a few days. In the worst case, this will happen next Tuesday - when I return.


This means:

- Do nothing if you have a running, synced wallet -  just let the minting roll.
- If you face any problems, make sure you`re synced to ubxidutptf2sslhq.onion:24112 (block explorer node)
- If you can't sync - don't put too much effort in this. It will be fixed, no coins will be lost.
- Do not panic.

PS: This issue was discovered when bittrex tried to sync their wallet. I verified it and can reproduce it.
PPS: I will most likely check in later that day.

If you're going to be making changes to the source and if it's a simple change, do you think the network could handle 10+ or 20+ confirms on generated blocks?

[wurstgelee]

Checkin in. Not in a useful condition. But checking in.

And yes. 53 was way to much, 7 is too low. 17 might be a good value - a  way higher value would increase the risk of a deadlock too much i guess.Also im thinking about changing blocktime. Its currently 1 minute. Do we need that? 4 confirmations only. So with 3 minutes, a transaction will confirm within 12 mins (avg.).  Also higher rewards per PoS block (avg) and less 0.00 blocks come with this.

Still fast enough? Or not? I  need opinions!

If you (you=all of you) have any idea or wish regarding core parameters - bring it now.

Lets discuss this.

Cheers!

[wurstgelee]

I tried to run a fresh wallet just to check.
Using bootstrap in the instructions I get stuck at 13000. Also using the latest bootstrap on the website I get stuck.

I do have a wallet synced and minting though.


Yep. That resembles my observations.

[StephenJH]

Cheers bud! Having fun? 

[pseudonymdude]

Checkin in. Not in a useful condition. But checking in.

And yes. 53 was way to much, 7 is too low. 17 might be a good value - a  way higher value would increase the risk of a deadlock too much i guess.Also im thinking about changing blocktime. Its currently 1 minute. Do we need that? 4 confirmations only. So with 3 minutes, a transaction will confirm within 12 mins (avg.).  Also higher rewards per PoS block (avg) and less 0.00 blocks come with this.

Still fast enough? Or not? I  need opinions!

If you (you=all of you) have any idea or wish regarding core parameters - bring it now.

Lets discuss this.

Cheers!

17 sounds okay.  I'm not sure how many wallets we have staking currently, but even with three wallets and reasonable network difficulty, you could probably raise it significantly over 17 with no problems.  I'm not 100% sure what controls how much TRI I stake per block, but as long as I keep staking 1 - 2 TRI (out of my 390+ TRI) per block, I think you could probably raise it back up to 50 with no problems.  If you think the network would be fine with that, maybe that would be best.

As a compromise, how about 2 minute blocks?

[wurstgelee]

Cheers bud! Having fun?  

Hell yes!

Edit: Oh, I'm a full member now. Trustworthy at last. :p
Edit 2: I personally verified that the wallet and minting are working in Spain. Prove of Country - every coin needs it.

[StephenJH]

"Hell Yes!"

  Just lounging on the beach with an umbrella in your drink?

Block times from 2-5min seem reasonable. And as many confirmations as you think we can handle without hitting that stalemate again.

[NightmareLev8]

Enjoy your stay in Spain

I also think that 2-3 Minutes for block times is enough.
With the number of confirmations I don't know, maybe around 20 confirmations. But as StephenJH said, we should ensure that we never reach the point again where we have no staking coins.  

[wurstgelee]

ARRRRRR! To all of that!

(pirate mode*)


*when typing requires one eye only while insanely yelling "ARRRRR".

Edit: Oh, top of a new page. Ok. Important info here, as usual: TRI is the shit right before it starts being the shit. Told you so.

[wurstgelee]

"Hell Yes!"

  Just lounging on the beach with an umbrella in your drink?

Block times from 2-5min seem reasonable. And as many confirmations as you think we can handle without hitting that stalemate again.

Close. No umbrellas in gin tonic.

Fun fact: 0.7l Tanqeray: EUR 13.50 regular price, not even a special offer.

The queen and I can recommend Gin. All of you shpuld drink more Gin. Oh and rum. Drink more rum and gin. Its good for you. Well, maybe not exactly good. But good.

:p

[StephenJH]

  hahaha

I need to brush up http://www.wikihow.com/Talk-Like-a-Pirate

TRI is the shit right before it starts being the shit. Told you so.

I noticed there hasn't been much selling.

[StephenJH]

Is someone drafting a new ann? Obviously it shouldn't be published before bittrex wallet is back online but that's just a few days away.

[whalebone]

Is someone drafting a new ann? Obviously it shouldn't be published before bittrex wallet is back online but that's just a few days away.

I offered to do this earlier and am still willing and able.

I would keep it simple at the start like the playgrounds and down low word press while focusing on the correct syncing instructions.

[pseudonymdude]

Is someone drafting a new ann? Obviously it shouldn't be published before bittrex wallet is back online but that's just a few days away.

I offered to do this earlier and am still willing and able.

I would keep it simple at the start like the playgrounds and down low word press while focusing on the correct syncing instructions.

If anyone is currently drafting an ANN, let us know, but the team here is pretty small.  If you're willing to do it, you're definitely nominated to draft it.  I would say not to post it until we've tested it for several days, bittrex is online, and there are no problems.

Also, perhaps we should create a single username as the new dev (or just OP) that several of us have access to in case some people leave in the future?  That username would post and be able to edit the ANN obviously.

Thoughts?

[NightmareLev8]

If anyone is currently drafting an ANN, let us know, but the team here is pretty small.  If you're willing to do it, you're definitely nominated to draft it.  I would say not to post it until we've tested it for several days, bittrex is online, and there are no problems.

Also, perhaps we should create a single username as the new dev (or just OP) that several of us have access to in case some people leave in the future?  That username would post and be able to edit the ANN obviously.

Thoughts?

Currently I'm developing a small faucet (with a gambling factor) for TRI. So I'm occupied with this.
But I agree that we have to first solve the other problems (especially the syncing one) before posting a new ANN.

[StephenJH]

Also, perhaps we should create a single username as the new dev (or just OP) that several of us have access to in case some people leave in the future?

Hmmmm. I think an argument can be made for creating a username... but also a strong argument could be made for wurst or another longstanding member. If it were up to me I'd have wurst make the post, without a doubt.

[wurstgelee]

Checking in.

A new dev account is a good option i think. We simply need to be absolutely transparent, like stating who is operating this account and why ("its teamwork") with each of the accounts listed verifying that by posting an answer in the ANN.
No credibility issues then. And workload sharing would be easier. Or am I missing something?