Topic: [ANN][COAL] BitCoal - MANDATORY UPDATE - CPU/GPU MINING - CRYPTONIGHT - page 17. (Read 58183 times)

forknoted on windows worked. discovered a corrupt wallet file. However when resynced only have 10,000 coal.  When problem manifest itself I had ~60,000. I reset and list transfers. noticed transfers with same transaction id. is this possible. Also address is not my trading account.
thx.

Sent Enre a message to get some info as i see he was active today in another forum. Maybe ill get a response or he will respond here.

Their response is that they won't update until the dev updates the "official" release. Could be a long wait.

Downloaded the 2.0.1 forknoted, re-synced with my original bat/conf and wallet and it is on the right block via Democats.
Now we just need Cryptopia to do the same

I may try that. The Daemon is on an ubuntu 14.04 server that is also a multi gpu miner. As long as I have a functioning wallet it does not matter what machine.
Thanks

I'm running the Windows cli, with no issues. It was shut down and I ran both components again just now and OK so far. Any chance you could install the Windows version on a different machine, and load your wallet into that?

It is the new simplewallet that came with linux files.
thx

Are you using the simplewallet associated with the 2.0.1 forknoted? I don't know if simplewallet changed; I downloaded that copy as well and ran it with the new forknoted.

Tried reset.
Wallet opens and displays address and command prompt, but will not sync.  Displays zero balance. had 60,000.
displays,

2017-May-06 06:24:28.327874 ERROR   [BlockchainSynchronizer] Failed to query blocks: NodeErrorCategory:5, Internal node error

Thx

What will it take to make forknoted 2.0.1 the official wallet release for this coin?

reset did not work.

try to 'reset' the wallet

Thanks, upgraded forknoted but now get block synchronization error from wallet. The wallet opens to prompt. but will not sync. Daemon works. my local pool miner works but cannot get wallet to sync.

See the previous post, slb recommended using forknote 2.0.1 and it worked well. Cryptopia has had it on maintenance for three days, maybe they need to read slb's post.

I am using forknote. Any insight as to problem? I see cryptopia has wallet down for maintenance.
THX

Consider democats/mypool as the real blockchain.  Use forknote 2.0.1. It has some additional tx validations and that may cause not validating blocks valid for older versions (it is causing fork if malicious transactions are included in blocks running older version)

I have been mining and trading Bitcoal for a while now. I shutdown for maintenance and restarted. cannot get wallet and daemon back online.

2017-May-04 05:45:29.239945 INFO    [192.121.166.182:7700 OUT] Sync data returned unknown top block: 161657 -> 162413 [756 blocks (0 days) behind]
2017-May-04 05:41:00.216430 ERROR   [192.121.166.182:7700 OUT] sent wrong block: failed to parse and validate block:
030099a291ef76d47d38e578b160a2e74fe7d69b0f2c6a0baf16cc9184414c7115110505aceb92c 80574cc019e4797ffec8e094b2a31412183401741441e8c6f48eb0d7eebdb079d2cc0000002075a 349168b5f525a725da579a104da946eedafd62e5180c264e9b2e015854e7654221bf47faa7cf387 60a112663c7584e417776efe95055cec0d8a9961b24ea3702d9a64f01ff9da64f0194afa4a0a6e5 0102ffeceb27dbf5d321bf4e1fb538d678d22c2ca2a5ea98b1918a741a4b7f0e2f4a4e011509dd8 6318813c24e7e03f0a31656e5423d788c27d07867f2e2e4b4a76252ad02080000000001c16e9803 21063b927a661aaafbea27778b802676bcbe7f7c8b5fa34f75b47717927199e2c27d0097d2a94af 866d195ade028e044957dce926cf57da9959aefab80c7282f9623b34519cc16cb6ee07aecdaecb5 d52ec6448a6ba27021dc4da84958ab4429a771df34f9ab37770d8dc1359787bf94b0933adb60b3f 385aebc20b650f585a91e4bf3f8dbec4127143ba49bbac2c840603d36c080db81a88996224f84c9 b43e9a6714727fd176aec068b652bd2b2b809262d52df351d1739e8e9d272bda53e6ff9fdbe97d1 d3e21ce2345bcdb740197fe68e2acd46883dda983fdfcaae4fe7e3f8a3101a9d80901ff9bd80909 ab94060256c538124661c3fdefdfd5e18ff0fea214c9d928d284f3d5093805844ee14cbac09fab0 3026050710e59a8b3d02d0a5d121f6b27a18dae796415dac14502c6f37c646844db80bbb02102df b96d204d85c1183e3a8a3361e594376f538057156dd17d2176205a6fa6ae5280c6868f01023ad8b 7802cd8a86e42dd1fdf17e09c8287ba336d4e01511e85de3a88031713e380bcc1960b029c75285a 65fa049e30ae6216afa42ec0274437d4c3585e18240dd0eeb28f18d680c8afa0250273c3d1c793f 7ca187b66885ffa450258f9b34a7657079262f1921ad88657222a80e0a596bb1102290824fb70ec c4a1d7176f7be86517306bca5fb3ac3ca480807e19b8d5c0e5a980e08d84ddcb0102ac25b34ee28 4a4c923c4be8b5e99157cd2fcbcd653532fa5f9ff91be07eebc7480c0caf384a30202f2c2cb928c b1ac4ec6d931a2a51149eb7e08ac7f40aa3c1d44f3b9546cfafc75210150bce0ec4ff0183b8d509 205a460e77bedb910c4828fc63e1bdf5eeed074a7bd014d09019fab479d3a7e22520a361ac35227 85bf9b5451fa9822760b25a51c4fdc
 dropping connection

The message is same with various peers.
Its a bit concerning consideringI have quit a bit of coal in wallet.
THX

Once the synchronization gets to that point (around 159,376) I start getting "sent wrong block: failed to parse and validate block:" followed by data, then "dropping connection"; this repeats endlessly (from different nodes).  The data is always the same.  Blocks are being received, very slowly (rate is about the same as new block creation, so always the same distance behind). Currently it is at 159,556.  I've deleted the database and started over a couple times; tried different spots on the hard disk; have not tried a different machine yet. Everything is smooth during synch until that spot.

Thanks.

What is the issue?