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

are you to submit a pull request to the main git repo? or should we switch to yours?
I'm almost new to this coin so I don't know who "has the authority".

Here is my fixes:
https://github.com/bitbandi/Trinity/commit/a354c4d33c16e53c9950a9955d457398c5aa76c2

This fixes the GetNextWorkRequired function after 955000 block.
And between 915235 and 955000 this function completely wrong, check sould disable between this blocks.

I added a checkpoint at 1039000 block, based on this pool hash:
http://gcpool.eu/trinity/public/index.php?page=statistics&action=round&search=1039000

And now blockchain is good, if cryptopia can sync, there is no reason to delist.

Elbandi

And working nodes

addnode=64.57.133.229
addnode=72.228.50.246
addnode=185.39.3.28
addnode=78.69.188.169
addnode=192.241.181.81
addnode=87.207.169.147
addnode=180.214.232.93
addnode=74.196.45.14
addnode=137.135.60.66
addnode=94.230.86.122
addnode=5.196.10.58
addnode=64.57.133.229
addnode=72.228.50.246
addnode=185.39.3.28
addnode=78.69.188.169

Oh, wait! I looked into my source, there is a fix for coding bug in GetNextWorkRequired.

i will put that to the github at weekend.

Elbandi

Reply from CT


    Sender: sa_ddam21310/31/2015 12:23:09 AM


                            Hi

    Thanks for the nodes but unfortunately they do not fix the problem we have with the TTY wallet

    Every time we try to resync the chain it stops at block 11 and wont go any further, then eventually all the connections disappear and wont reconnect until we delete the blockchain again

    ./TTY getinfo
    {
        "version" : 1000001,
        "protocolversion" : 70001,
        "walletversion" : 60000,
        "balance" : 0.00000000,
        "blocks" : 11,
        "timeoffset" : 0,
        "connections" : 2,
        "proxy" : "",
        "pow_algo_id" : 1,
        "pow_algo" : "scrypt",
        "difficulty" : 0.00024414,
        "difficulty_sha256d" : 0.00024414,
        "difficulty_scrypt" : 0.00024414,
        "difficulty_groestl" : 0.00024414,
        "testnet" : false,
        "keypoololdest" : 1446250643,
        "keypoolsize" : 101,
        "paytxfee" : 0.00000000,
        "errors" : ""
    }

    The debug,log is just fill of orphan blocks, so it seems this latest version has some issues that need to be fixed by the dev.

    connected 89.70.100.251
    send version message: version 70001, blocks=11, us=0.0.0.0:0, them=89.70.100.251:62621, peer=89.70.100.251:62621
    receive version message: version 70001, blocks=1037917, us=162.255.117.105:63472, them=89.70.100.251:62621, peer=89.70.100.251:62621
    received block 00000000000578a33f8cb9a2743ab8a1b5af71f5cb07c34cef062c8d294729f8
    ProcessBlock: ORPHAN BLOCK, prev=00000000000271c78d1390d9aa4ea1dabe7aeccd12d6461a1a0cb33909b2d8ad
    received block 000000000003a1cc01048c2814e76d5b32ba3e00ce8db825b45f67b28bae57f6
    ProcessBlock: ORPHAN BLOCK, prev=00000000000578a33f8cb9a2743ab8a1b5af71f5cb07c34cef062c8d294729f8
    received block 0000000000019c39efebc0a3ca9e0dc83c73324394d209528e056f0cc5e15585
    ProcessBlock: ORPHAN BLOCK, prev=000000000003a1cc01048c2814e76d5b32ba3e00ce8db825b45f67b28bae57f6
    stored orphan tx 35939d63eff854d8765362652073d3214a97ae779c008833d973521a09e39f62 (mapsz 1)
    received block 0000000000023e6429bf08f110d23302f329dd9d3e6d8607a6378d864c0d83fd
    ProcessBlock: ORPHAN BLOCK, prev=0000000000019c39efebc0a3ca9e0dc83c73324394d209528e056f0cc5e15585
    received block fb194fc3ea09fdac31339267d7aeea93e36a1892dba168392cbb177640821d46
    ProcessBlock: ORPHAN BLOCK, prev=0000000000023e6429bf08f110d23302f329dd9d3e6d8607a6378d864c0d83fd
    stored orphan tx 67b1dd477b63718815c0431cb63bd3755033a4a3ad6f09e60ebf660ce6d11ca1 (mapsz 2)
    received block 000008331254354ce28b4d6fab6b711b871bb671f1f382b210cdc65e6fdaeaf5
      nActualTimespan = 7  before bounds
    GetNextWorkRequired RETARGET
    nTargetTimespan = 600    nActualTimespan = 570
    Before: 1e0fffff  00000fffff000000000000000000000000000000000000000000000000000000
    After:  1e0f3332  00000f3332400000000000000000000000000000000000000000000000000000
    ERROR: AcceptBlock() : incorrect proof of work
    ERROR: ProcessBlock() : AcceptBlock FAILED
    Misbehaving: 89.70.100.251:62621 (0 -> 100) DISCONNECTING
    disconnecting node 89.70.100.251
    trying connection 89.70.100.251 lastseen=0.0hrs
    connected 89.70.100.251
    send version message: version 70001, blocks=11, us=0.0.0.0:0, them=89.70.100.251:62621, peer=89.70.100.251:62621
    receive version message: version 70001, blocks=1037922, us=162.255.117.105:63713, them=89.70.100.251:62621, peer=89.70.100.251:62621
    received block c3c09dd02335fd906ba65cbe647d795b9339e4c0fc96c890cf16947948c90a2b
    ProcessBlock: ORPHAN BLOCK, prev=fb194fc3ea09fdac31339267d7aeea93e36a1892dba168392cbb177640821d46


    We are going to attempt to install a windows wallet offsite and import all the users private keys so users can submit a support ticket to withdraw their funds.


    Thanks
                       


--------------------


I will send them the Info about the Bootstrap File

here is a bootstrap file:
https://www.dropbox.com/s/eahlh1w7h6jhk36/bootstrap.dat?dl=0

Can't believe an exchange owner is unable to do a couple addnodes....

how about another exchange ?

News from Cryptopia :


#4185 - TTY Wallet Status
Category:    General
Status:    Closed
Opened:    10/29/2015 5:51:50 PM
Last Update:    10/30/2015 5:08:08 AM
Ticket description:

Hello ,

you mailed me before 2 Weeks :


                            Hi,

    The trinity wallet did for when they released this version and only gave us 12hours notice so by the time I woke up the fork had already started and everything was a mess.


    Our pool mined 900 blocks on the old fork which people traded/sold and now the coins don't exist when we upgraded to the new version.

    Then as you know that version was a total fail, and we have reverted back, but we are still down 900 blocks.

    Its going to take some time to audit the 5000 affected accounts after that the decision will be made if Trinity will remain on the site or be removed as this has cost us quite a lot of money. We found it extremely rude they expected us to upgrade 4 wallets in less than 12 hours usually coins give us at least a months notice.


    Thanks
    Cryptopia Support
                        


----------

I wanna ask for Status now , whats the Problems to fix ?




Answer =



    Sender: sa_ddam21310/30/2015 5:08:01 AM


                            Hi,

    We cannot get the wallet to sync, it has been stuck on block 11 for weeks.

    We have tried everything but still no luck.

    Once we find a way to get it synced we will give the users 4 weeks to withdraw their coins before it is delisted.



    Thanks
                        




and my Answer now =

#4189 - TTY Wallet Issue Nodes
Category:    General
Status:    New
Opened:    10/30/2015 6:15:27 AM
Last Update:    10/30/2015 6:15:27 AM
Ticket description:

Hi !

try this for your Trinity Wallet Problem

Nodes
198.50.217.13:62621    70001    TTY v.9:1.0.0.1    10/17/2015 00:11:07    19.192 MB
78.69.188.169:62621    70001    TTYDEV:1.0.0.1    10/29/2015 15:40:48    3.792 MB
89.70.100.251:62621    70001    TTYDEV:1.0.0.1    10/29/2015 20:22:16    0.628 MB

here  i also started with a clean install.
and the info what says here.
and syncing perfect.
i am even solo mining now.
and pool mining and it works smoothly
nice coin  see what i will gets

https://bitcointalksearch.org/topic/m.12577250

I started with a clean install, downloaded blockchain, added latest addnodes and it synced fine. Try resetting your blockchain and peers.

proof ?

i read this:

I mined some of this in the beginning. Updated wallet in August. Fired it up yesterday while thinking about mining and wouldnt sync. Added all addnodes in this thread, updated exe, and block and peer. Stuck at 2 weeks at block 954140. Ideas?

DEV says its not broken and the full fix is coming in about a month

so keep mining

What is happening with this coin, dev any updates?

yes, sha thats me. 

13 days, broken, no dev fixes, and no info... Waste of time? Again?

hah, cryptsy... unattainable
maybe another one little-known exchange, but silence of dev does not give any chance