farsessanus   63eb4e2ebdbc2cdb6c96e4b8ace09cbb4587103b32b189b06996e2d5227c2290
isaacnem           63eb4e2ebdbc2cdb6c96e4b8ace09cbb4587103b32b189b06996e2d5227c2290

Another case of duplicate hash. and these two posts are next to each other https://bitcointalk.org/index.php?topic=440185.msg4865816#msg4865816

Then isaacnem sent a small amount https://blockchain.info/es/tx/e6e86c0f542339a5b9d70d5a1225df630263e5d9c4ee40a19f7ae0d466210a06 to prove the ownership of the sending account. so isaacnem : legitimate one and farsessanus fraudster. sorry  isaacnem for the inconvenience.

Interested!  0.035BTC: https://blockchain.info/es/tx/63eb4e2ebdbc2cdb6c96e4b8ace09cbb4587103b32b189b06996e2d5227c2290

Thanks!!

stakeholder List update to page 10 thread 2. The reason for this lateness is I found out couple of fraudsters and the main trick they used is to make reservations with other people transactions.

Since the fee changes every 10 pages, they can only use the transaction in that range because the first thing I checked is to see if there is indeed an transaction of the right amount. Now I also sorted the hash in alphabetical order and only accept unique transaction hash; if a hash was used the second time then that user is a fraudster. So it would take longer time now to update the list since the checking now requires more times and efforts.

I would also go back to earlier transactions to find every single fraudsters and throw them out of the list. The good thing is that all the records are public in the registration thread and all fraudsters will be found out easily using the method I lay out.

So go ahead and waste your times because I am going to find you and throw you out of the stakeholder list.