Quote from: Troublesome96 on April 10, 2015, 04:57:52 PM

Quote from: Crestington on April 10, 2015, 11:51:39 AM

Quote from: ?!bennscammed!? on April 10, 2015, 11:12:38 AM

Quote from: Crestington on April 10, 2015, 10:29:05 AM

Quote from: MaryJ on April 10, 2015, 02:32:42 AM

oh and i asked bittrex to resync and when they did i sent them maryj to make up for the coins that people lost last week. then they had wallet issues again after it seemed to be fixed. im not the person to throw away money on an issue that seems to need a better solution thats in progress and will be here soon.

or do people think its a good idea for a company to fix say a broken work van constantly or buy a new one with less money than you would spend on repairs...

Hi,

Fire Rabbit asked me to give a hand with some Blockchain issues.

It's best not to get stressed out by issues and things going on around the Coin otherwise you tend to overlook things that turn out to be a very simple solution. Relax and smoke a joint, and lets get down to business.

What are the issues you are having? Please detail every incident relating to sync issues and events around that time.

I do development work on ColossusCoin2 and PayCon, I have also performed several successful hardforks and have been working with POS only Coins since before BlackCoin and NXT.

I can't guarantee you anything but I'm sure I can be of some help.

nice to see you here Wink

as far as i know coins can be sent but they dont arrive in the wallet they are sent to...
i dont know whom that was, but someone said sending between qt wallets worked for him, dont know if he had the same ip and thats why it worked.
also my wallet is staking and is showing a higher amount than the blockexplorer https://chainz.cryptoid.info/maryj/ does.
and therefor all exchanges disabled the wallets.
hope someone else can also give you some input.
also it would be good if you contact adam (DEV) and offer your help if you havent done this yet.

im happy to see you here offering your help.

It would be good to work though it here rather than through private messages as lots of feedback can help identify the issues. The Block explorer can show different balances than the wallet since it shows individual addresses, not wallet balances, a wallet consists of many addresses.

For a strong network you need a lot of people Staking on the network, that is having your Coins in your qt wallet, online.

A couple things I noticed

When changing the time drift, it should be changed through a hardfork based on nHeight but most people never go out of their way to update their wallet so a further step should be taken to bump the protocol and then a delayed reject on all peers on the lower protocol after the fork so you don't risk having both conflicting within the same protocol. 24 hours for the initial block drift is a HUGE amount of time and actually even being changed to 1 hour is also a very large amount of drift. The drift time should be as tight as possible, BlackCoins drift was down to just 5 minutes before they changed how their Stake functioned.

A couple other things needed for a strong network is a few good Static nodes for people to connect to and not just relying on a DNS seeder since it only adds addresses periodically.

Was the checkpoint master key new? or was it a descendant of the code it was cloned from?

What code was MaryJane cloned from? I have been through a lot of code and haven't seen the legacy retargeting anywhere else.

I do not know what it was cloned from but the wallet looks like the old silkcoin wallet so I am leaning that direction.

Firerabbit and I were able to exchange coins back and forth between each other a couple of days ago.

Originally the block explorer and bittrex's wallet were getting off so bittrex shut it down due to that. They re opened the market after resynching the chain and I believe the issue occurred again shortly there after.

Richie of bittrex stepped in and pointed out that chainz was showing multiple versions of the wallet running on the network, one of which was unaccounted for and/or not available on the git. He said they were shutting the market down until that was resolved and would keep it shut until the newest version was available on github.

The static nodes question has been brought up multiple times with no answer given. I believe most of the questions you ask are over the dev's head (no offense). This coin was contracted out to be developed. I believe earlz at one point had posted to github a wallet review that may help or not. I have not read it in sometime. And I do not believe it was ever brought up in this thread.

I am sure I am missing some or over generalized some issues, but this how I remember it at the moment.

I find that if you can find the source that it makes it easier to pinpoint where the issue might be and might have already had a fix done for it. My initial reactions are that it can be the targeting drift of 1 hours to 24 hours so possibly some big wallet was still on the old version, messing up the chain. Minimum age is 3 hours which is quite low so you would see a lot of compounding as well, chains out of sync can be Staking on their own chains. I have also seen some issues in other Coins where they were returning Coins to a specified address and bugging up the code and this legacy is quite strange to me.