only our wallet uses the long addresses which is exactly where the problem is

Dude, what is your problem.

I pached a wallet so it can send, and Im scamming.

I stop that and wait for an offical fix and im scamming


WTF do you want from me?


THERE IS A BUG IN YOUR CODE THAT PREVENTS TRANSACTIONS FROM BEING CREATED IF IT CONTAINS INPUTS FROM LONG ADDRESSES

YOU DEV KNOWS ABOUT THE ISSUE AND IS APPARENTLY WORKING ON A FIX, NOBODY ELSE HAS THE ISSUE BECAUSE NOBODY ELSE USES LONG ADDRESSES A FEATURE YOUR TEAM IMPLEMENTED


PLEASE EXPLAIN WHAT PART OF THIS YOU ARE FAILING TO GRASP

Are you OK,

Ok nevermind, we will wait on an official fix from your team.


Please let us know when you have a working wallet for us and wee will upgrade and open withdrawals



Thanks and goodluck

The fix I have implemented has NOT been tested so no, I cant run it in an automated fashion, cause unlike team FLY I would like to test my code before using it in a production environment.


XDEII can be withdrawn normally, but because this fix on FLY is experimental it will be a manual process, simple as that

Hell no, not after this bullshit, both you coins can get the fuck off my site

I have found the bug in YOUR code and am recompiling the wallet so we can clear our name from this shitstain


Log your tickets I will try get your coins out to you asap

Ok, so...


The release before last introduced new "exchange addresses" we had to completed rebuild the FLY wallet.

All coins from the old wallet were send to the new wallet using the new address type.

No there seems to be an issue with these address types as you cannot send transactions from the wallet anymore (reason for maintenance)

root@3a0e51278256:~# ./FLY sendtoaddress FQd7KNU1YPFCxLJtspQB52PE8Q3WVt7CCJ 1
error: {"code":-4,"message":"Error: Transaction creation failed  "}
root@3a0e51278256:~# ./FLY sendtoaddress FQd7KNU1YPFCxLJtspQB52PE8Q3WVt7CCJ 0.1
error: {"code":-4,"message":"Error: Transaction creation failed  "}
root@3a0e51278256:~# ./FLY sendtoaddress FQd7KNU1YPFCxLJtspQB52PE8Q3WVt7CCJ 0.01
error: {"code":-4,"message":"Error: Transaction creation failed  "}
root@3a0e51278256:~# ./FLY sendtoaddress FQd7KNU1YPFCxLJtspQB52PE8Q3WVt7CCJ 0.001
error: {"code":-4,"message":"Error: Transaction creation failed  "}
root@3a0e51278256:~# ./FLY sendtoaddress FQd7KNU1YPFCxLJtspQB52PE8Q3WVt7CCJ 0.0001
error: {"code":-4,"message":"Error: Transaction creation failed  "}
root@3a0e51278256:~# ./FLY sendtoaddress FQd7KNU1YPFCxLJtspQB52PE8Q3WVt7CCJ 0.00001
error: {"code":-4,"message":"Error: Transaction creation failed  "}
root@3a0e51278256:~# ./FLY getinfo
{
    "version" : "v2.1.0.0",
    "protocolversion" : 60091,
    "walletversion" : 60000,
    "balance" : 5194.32492063,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "combine threshold" : 1.00000000,
    "blocks" : 71901,
    "timeoffset" : -337,
    "moneysupply" : 207266.89799793,
    "connections" : 6,
    "proxy" : "",
    "difficulty" : {
        "proof-of-work" : 17.13538076,
        "proof-of-stake" : 0.99957293
    },
    "testnet" : false,
    "keypoololdest" : 1460945828,
    "keypoolsize" : 8606,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00000000,
    "staking status" : "Staking Not Active",
    "errors" : ""
}
root@3a0e51278256:~#


So now this release was given out to fix the issue, but obvious looking above it hasn't.

Now after reading this forum, looks like he is mentioning the long addresses being the issue, we were NEVER told these were being removed, just the fees.

infact the is 1000000% more information here then in the support tickets.

So the problem is, if I remove all the long addresses from the wallet to make the wallet work, the wallet will have ZERO coins because the way crypto currencies work is you send coins to an address and they are logged in the block chain against that address, so the wallet does not hold coins its just the sum off all inputs/outputs of the transactions in those addresses.

sooo....

we have no FLY, None, because we cannot send the coins from those long addresses anywhere, our only option is to go back to older backups of wallets and try recover as many private keys as we can in order to get some people some coins.

But any coins sent since the long addresses were implemented will be lost

Obviously this means we are no longer solvent in FLY which will cause all internal audit systems to fail, so the withdraw and trade services will not work due to the failing audit.


EDIT: I personally have 800ish FLY in my home wallet, so if you log a support ticket I can pay people out with that while we attempt to recover some FLY from old backups

Ok,

So apparently I have to remove all the new addresses added to the wallet, if you deposited any coins using the new addresses they will be gone.

This means Cryptopia will not have enough funds to cover user balances so be as fast as you can to withdraw as there will not be enough coins to go around.


This is out of our control as this is the second tome the FLY team has made us remove all addresses from the wallet and generate new ones.


DO NOT CONTINUIE DEPOSIT TO CRYPTOPIA ANYMORE, ALL ADDRESSES ARE GONE.

Please log a support ticket to withdraw your funds as we cannot automate this anymore

There are many reasons we use single addresses, the main one is the wallets themselves, once you get 10-20k addresses in one of these wallets the start do dramatically slow down, sometimes to the point where it can take minutes to scan a wallet for transactions.

We also have to maintain, encrypt the private keys for all addresses for disaster recovery situations

The other reason is Cryptopias audit system, I'm not sure how it works on other exchanges, But when developing the Cryptopia system I decided to use a blockchain approach, every single thing a user does on cryptopia that involves funds moving is logged in our internal blockchain, Trades, deposits withdraws everything, your balance is a sum of all incoming (Deposits, Buys, etc) minus all outgoings (Withdrawals, Sells etc).

In this situation your Cryptopia balance is never a random arbitrary number, its audited, you cant fake a balance, a trade has an owner, that owner had a deposit, that deposit has an address, that address has a tx, and that's our internal audit, so for performance reasons single addresses are also preferred here


But we do try to add all features users want, so I can definitely revisit this feature and see if I can make it workable.


I also have something cool coming up that I am hoping UNO would been keen to get a part of (will revel more once I have a demo up)


Keep it up UNO team

FCN now live on Cryptopia 

https://www.cryptopia.co.nz/Exchange?market=FCN_BTC


Welcome to the family

Ok, just log a support ticket if you want to withdraw your DMD from Cryptopia, coin is being removed from the site.

If anyone wants ownership of the UNO Cryptopia forum just let me know their Cryptopia username and I will assign it to them

cant get this to sync

2016-05-21 08:18:51 ERROR: CheckBlockHeader() : proof of work failed
2016-05-21 08:18:51 Misbehaving: 66.118.187.120:8764 (0 -> 50)
2016-05-21 08:18:51 ERROR: invalid header received
2016-05-21 08:18:51 ProcessMessage(headers, 16578003 bytes) FAILED peer=2
2016-05-21 08:18:51 ERROR: CheckBlockHeader() : proof of work failed
2016-05-21 08:18:51 Misbehaving: 192.254.71.126:8764 (0 -> 50)
2016-05-21 08:18:51 ERROR: invalid header received
2016-05-21 08:18:51 ProcessMessage(headers, 16578003 bytes) FAILED peer=3
2016-05-21 08:18:57 ERROR: CheckBlockHeader() : proof of work failed
2016-05-21 08:18:57 Misbehaving: 199.19.215.50:8764 (0 -> 50)
2016-05-21 08:18:57 ERROR: invalid header received
2016-05-21 08:18:57 ProcessMessage(headers, 16578003 bytes) FAILED peer=4


Any ideas?

I posted the error once not 10 fucking times.

Not sure how adding nodes to a wallet that has 20 connections its going to stop the wallet crashing.

I will install the old wallet again so people can withdraw, problem solved

Such a good idea infact that I have started coding this now.

Hopefully will be ready for tomorrows site update

We have been informed that our wallet is out of sync.

Our wallet matches this explorer https://chainz.cryptoid.info/pr/  are they out of sync too.

I cant for the life of me find out what the correct block height is, does anyone know, obviously not using the above explorer or Cryptopias Explorer or wallet)

Is there a fork? I have placed PR into maintenance while we try find the correct fork.


Thanks

Its already a base market (and one of my favorite coins of all time) 

Unfortunately we cannot allow access to an untrusted site/download on our wallet boxes, so we will just have to wait for a fix or just wait for the wallet to eventually sync.

Relying on 3rd party download to sync a wallet is pretty useless when you have a secure environment.


I wont "FUD" anymore on your thread and will leave you all too it, sorry I even posted the issue.

Well funny you mention that, I run a small exchange that has DMD listed, their new wallet does not sync correctly (keeps crashing), many people asking on the DMD thread why we are taking so long to sync, I post the errors from the DMD logs and guess what.

I am just fudding to drop the price, god I hate crypto.

Think its time to delist DMD

So now I'm fudding cause the new wallet wont sync.


... awesome logic DMD, just awesome


attack anyone that has an issue, that will fix it, right?