Topic: TycheCash - Cash on the Tyche Network - page 3. (Read 29157 times)

100k Blocks !!

New wallet release and MacOS GUI updated dmg requiring No Pre-requisite

• Windows 64 Bit CLI and GUI
• MacOS CLI
• MacOS GUI
• Ubuntu 14.04 CLI
• Ubuntu 16.04 CLI
• Web Wallet

All the binaries are available on https://tyche.cash and GitHUB Release

Jithin has done it. After a longer period of extensive tests the Tychecash web wallet is on mainnet now. Anyone can create web wallet now. please visit 

https://wallet.tychecash.net

1. Open the page
2. Accept the conditions
3. Register for web walet.
4. Verify your email address and
5. Enjoy we wallet.


Credit goes to Jithin.

I think with this there will be no problems. here they try to perform constant updates of the system, which affects the improvement of its functionality. so it's important, and it's about high potential.

ANN: GitHub source and binaries updated . This is an Important Update which fixes some of the bugs left in the last update .
Download latest binary from  Release 1.3.1 from Github .

Exchanges are requested to update their daemon and re-sync.

Those who do not want complete re-sync can run simplewallet in light mode :



Important : Further improvements to code coming shorty, be prepared to update again.

GitHub Source: https://github.com/blockchain-next/TycheCash

Thanks for acknowledging our efforts , it really encourage us.

It's worth praising the team that it is actively working on updating the functionality of its project

Thank you for spending your time to compose a thread which contains links to three important channels of TycheCash project.
I would prefer to use Discord and Telegram channels.

It looks like the blockchain can only move with Mega hash power. Something to look into since even with some decent hash power on the pools it takes hours to find a block. The new difficulty change does not fix all problems maybe ? Miner count seem to dwindle and we need them back soon.

Any thing news, particularly promising ones, recent days, tychecoin?
Daily liquidity in Altex exchange is very low today.

The Discord channel looks helpful with actively dev and mods.
Additionally, normal users tend to try helping others as fast as possible if they can.
What a solid community in TycheCash Discord channel!

Discord : https://discord.gg/hEjaXmR

Telegram : https://t.me/tychecash

WhatsApp : https://chat.whatsapp.com/CLds1rQEjZNJQJPqpxTplg

Where are links to join TycheCash project's Discord and Telegram channels?
Please give me links to join because I really to get more info on TycheCash project.

On our discord and telegram channel u will get a quiker response . See the link in ANN post.

I should have said, it was showing the current, correct block height on my second resync attempt... but it was 300 blocks behind or so at the 76000 level.  I am re-down loading the latest Wallet and will try to sync from 0 again and will try your suggestions.  Thanks for the quick response.  BTW - Is this the best place to ask for help on such matters or is there another channel / discord chat you prefer I use?  If so, please just let me know.

Thanks again for your quick response.

GKM

1. Have the latest binary from the GitHUB
2. If you are already on latest binary , re-sync from 0
3. If you have re-synced from 0 , then u must have come to correct height . To check that simple open simple wallet and on wallet prompt use command bc_height and if that shows correct height , ignore those outputs , those are not error messages to take action on user's behalf , it shows whats being processed by the daemon . U can surpass those messages by setting log level to 1 while starting daemon

I've resynced my wallet... but it is now getting stuck at 76000 with the following kind of errors seen in the wallet log:

2018-Jun-25 04:33:02.806495 INFO [Blockchain] ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 76078
2018-Jun-25 04:33:02.806495 INFO [Blockchain] id:    <198b68b375cf4693ef04240a74be424d5412e1b74e476d110aa486509e6753c0>
2018-Jun-25 04:33:02.806495 INFO [Blockchain] PoW:    <0afffa742beb5f7cf75bc2180e63d4263884fa9dc118213838f904d309000000>
2018-Jun-25 04:33:02.806495 INFO [Blockchain] difficulty:    51867271
2018-Jun-25 04:33:02.814508 INFO [outputs_visitor] One of outputs for one of inputs have wrong tx.unlockTime = 76044
2018-Jun-25 04:33:02.814508 INFO [Blockchain] Failed to handle_output for output no = 0, with absolute offset 50346
2018-Jun-25 04:33:02.814508 INFO [Blockchain] Failed to get output keys for tx with amount = 300.00000000 and count indexes 1
2018-Jun-25 04:33:02.814508 INFO [Blockchain] Failed to check ring signature for tx <9a987b828881070cba56841cddfb2f4730f920b4c6d0eacd9a2e0ada1415e9ec>
2018-Jun-25 04:33:02.814508 ERROR [core] Transaction verification impossible: <9a987b828881070cba56841cddfb2f4730f920b4c6d0eacd9a2e0ada1415e9ec>
2018-Jun-25 04:33:02.817490 INFO [outputs_visitor] One of outputs for one of inputs have wrong tx.unlockTime = 76037
2018-Jun-25 04:33:02.817490 INFO [Blockchain] Failed to handle_output for output no = 0, with absolute offset 35099
2018-Jun-25 04:33:02.817490 INFO [Blockchain] Failed to get output keys for tx with amount = 8000.00000000 and count indexes 1
2018-Jun-25 04:33:02.817490 INFO [Blockchain] Failed to check ring signature for tx <0aefa1810e4a34e0a9d80e647fb7da3c3f618b3ea98e0a2c6082363aab1d29ec>



I can send full log if you like?
Any advice is greatly appreciated.

Thx.

There's no Double spend possible , yes because of timestamp attack blocks were stuck and since it was getting difficult block by block getting to 76000 we decided to hardfork at 75900 itself because of timestamp attack and chain forks there were several double spend attempt , and to prevent that daemon was taking a lot and lot of time verifying that and thus getting the next block . So it was necessary . Binaries and source already updated . Kindly download from GitHub. for now DO NOT download from tyche.cash .

Thank you for the very important upgrade!
I wish all things will be fine with both TycheCash network and exchanges' wallets.

ANN: GitHub source and binaries updated . Download latest binary from Release . Those who have synced beyond 75900 need to re-sync .
Exchanges are requested to update their daemon and re-sync.