Topic: Possible claims process for GLBSE assets. - page 2. (Read 2638 times)

That is a good point that I did not think of.  People would have to remove any withdraws from the csv file as well (if they made any withdraws) as they can't remove bitcoins that they aren't suppose to have.

Yeah - mentioned that in my last paragraph.  The real weakness is that it allows people to delete just their sell line - and leave in their buy.  With the buy being genuine (so unlikely to be contested) it would give huge credibility to someone who had bought/sold shares but was now claiming to only have ever bought them.  All it can really show is that at some point they probably owned some shares - not that they still retained them when GLBSE closed down.

My idea to prevent the addition of fraudulent buys and sell history in the file would be to compare the csv file with the GLBSE history and also against other claimants.  If there are was only one purchase at a given time yet two people are claiming that they bought the shares at that time point, then both of those claims would need to be considered suspect and evaluated further.

I recall someone mentioning they were still able to retrieve their account history .csv from GLBSE. Does someone remember the link to do so?

Bolded for convenience.

It seems like a decent starting point - but what's to stop someone either:

1.  Adding lines into the .csv file,
2.  Deleting sales from the .csv file - so the record of them buying shares is still there, but not the record of them subsequently selling them.

Haven't got a GLBSE .csv file on this computer, but last time I looked at one, I don't remember it being GPG signed or anything to allow guaranteeing its unmodified nature.  It would deter casual scammers - but actually could be used to give credibility to slightly more sophisticated ones.

One thing it DOES do (in its favour) is link shares claimed to specific transactions - so anyone inserting lines would run the risk of claiming a sale to someone else was to them and having it contradicted by the genuine buyer submitting a claim on the same transaction.

I believe I might have a possible solution for asset issuers for claim processing since it looks doubtful every passing day that Nefario is seriously going to send out the asset information.

I was looking through my GLBSE account history as downloaded from GLBSE in csv format and I noticed that there is the bitcoin address for withdraw and deposits.  This information is invaluable as it can be checked against the blockchain for confirmation.  Also the asset history has a list of all purchases and sales of assets and we have a history of all the orders.

This might be time consuming, especially for the large issuers, but it is a potential way that assets can be claimed.

Claimants can send their claims to the asset issuers with the account history that was downloaded from GLBSE and the total number of shares they remember owning before GLBSE shut down.  The claims team can then take that information and verify the claim by looking at the bitcoin addresses for withdraws and deposits and identifying that they actually occurred in the blockchain.  Then the claim team can check to see if the history adds up.  For example, if a claimant says they owned 1000 shares of some asset yet only deposited 2 bitcoins in their GLBSE account, then it would be possible to identify that this claim is false.

Also, once the bitcoin transfers and balance have been verified, those past bitcoin address can be confirmed to be controlled by the claimant.

Bitcoin address are listed in the Deposit and Withdraw of the csv file.  If you look at the address that is listed from the deposit it will list the GLBSE bitcoin address, but the bitcoin address listed in the withdraw will the the claimant's bitcoin address.

I think this might work, but I would like input from others on potential ways fraudulent claims could be submitted and whether it could bypass a check as I proposed above.