Topic: [ANN] Trinity - TTY (SHA256d, Scrypt, Myr-groest) Trinamic Block Value System - page 19. (Read 46348 times)

old wallet version , newest doesnt work for me

scrypt pool now at diff 0.7
works

and both pools on the right chain . chain accept transactions from different wallets


Newest Wallet crashed MYSQL Database Trinity because Connection dropped often from Chain . This damaged the Trinity SQL Share and Blocks Table .
I reorganize Tables but after all i has to install a clean Trinity SQL.

You have to re-Sign in .

Sorry for that

new or old 

testing SHA and Scrypt Pool with OLD !!!! Wallet ( newest Wallet does not work and drops connection )


http://gcpool.eu/p3347/public/       Scrpyt Pool

http://gcpool.eu/trinity/public/        SHA256 Pool

My pool seems ok:

"version" : 1000001,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 957141,
    "timeoffset" : 0,
    "connections" : 4,
    "proxy" : "",
    "pow_algo_id" : 0,
    "pow_algo" : "sha256d",
    "difficulty" : 32895.24413502,
    "difficulty_sha256d" : 32895.24413502,
    "difficulty_scrypt" : 3.21673157,
    "difficulty_groestl" : 0.00351271,
    "testnet" : false,
    "keypoololdest" : 1443122980,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""

What wallet do you use?

Sorry Dude but your newest Update kills Connections

2015-10-02 21:05:36 [Pool]      [trinity] (Thread 3) getblocktemplate call failed for daemon instance 0 with error {"code":-9,"message":"Trinity is not connected!"}
2015-10-02 21:05:36 [Pool]      [trinity] (Thread 1) getblocktemplate call failed for daemon instance 0 with error {"code":-9,"message":"Trinity is not connected!"}


only 1 Node and it drops the line


Thats the Fault and its crashed the whole SQL Table on Trinity Pool

i will shutdown Pool ....

i will retest with old Wallet . and if its stable then i reopend


New Wallet:

trinity/src# ./trinityd getinfo
{
    "version" : 1000001,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 87927.93094019,
    "blocks" : 956452,
    "timeoffset" : 0,
    "connections" : 0,
    "proxy" : "",
    "pow_algo_id" : 0,
    "pow_algo" : "sha256d",
    "difficulty" : 14173.70448718,
    "difficulty_sha256d" : 14173.70448718,
    "difficulty_scrypt" : 3.21673157,
    "difficulty_groestl" : 0.13754882,
    "testnet" : false,
    "keypoololdest" : 1437427739,
    "keypoolsize" : 102,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

old wallet :

rinity/src# ./trinitydold getinfo
{
    "version" : 1000001,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 88375.93094019,
    "blocks" : 956460,
    "timeoffset" : 0,
    "connections" : 2,
    "proxy" : "",
    "pow_algo_id" : 0,
    "pow_algo" : "sha256d",
    "difficulty" : 14173.70448718,
    "difficulty_sha256d" : 14173.70448718,
    "difficulty_scrypt" : 3.21673157,
    "difficulty_groestl" : 0.09309888,
    "testnet" : false,
    "keypoololdest" : 1437427739,
    "keypoolsize" : 102,
    "paytxfee" : 0.00000000,
    "errors" : ""


connects and get nodes



Not a good Work on your Wallet

Regards Glen

little update


Pool SQL for Trinity crashed ...

will debug and copy all to new database.

Regards Glen

We should be fine as long as the wallets keep getting updated. As long as your pool wallet is updated to newest source, we should continue mining as the other pool is not online now either so we should be able to easily fix the chain now with mining. Thanks, 5mil

Me Wallet is Update and Block @ 956444

Node : 77.239.57.149

 

Same issue for me. Stuck at 915235.

Hi !

just saw that Pool got Probs with new Wallet .


But i am busy at Work and can check it only later tonight


So pls STOP MINING  !!!
( i just shutdown Stratum )

Regards Glen

He's working on a fix for that, patience friend

Synchrone wallet can not be normal. if there is a problem with your nodes?

Try putting these blocks in your data folder and you should sync up to where I am at.
https://drive.google.com/file/d/0B2QdkQ_BNnlQX0hpazNTekJQQ1U/view?usp=sharing

It seems there may still be a problem with just syncing past 915235. This will go on the list for the next update that I do.

if I sync from 0 I get stuck at block 915235 

I will mine some coins. waiting for rig rental to complete

Was just looking at your coin . How long has it been here for ? I may be interested in mining a few .

The problem is that Cryptopia has not changed their wallets yet. cryptopia is maintaining the longest chain right now and its not the same client.
so everyone connected to them with their old clients is keeping that network longer. when they add the new code, the longer network will match out clients and we will sync to it. I encourage everyone to run the new client software. Thanks, 5mil

Edit: The nice part is the fix seems to be functional. I am syncing the blockchain from 0 on the new client network from 2 other nodes with no issues. So as soon as the pools have updated to the new code, we should be in good shape. Thanks everyone!

Good job dev 

I'm stuck at block 917354...