Now fixed.

BitcoinFX's announcement caught me unawares somewhat as I hadn't taken the opportunity to go through the code in detail to ensure as best I could that all the work-in-progress was properly tidied up. In the event, I overlooked a stray line of developer-convenience code that, under a set of conditions that I apparently couldn't actually replicatet (although I glimpsed the fault briefly on one occasion) had the effect of inappropriately activating the inscription field placeholder text as though the user has pasted it in. I've removed the developer convenience but that was only part of the problem - the inscription/notarisation facility uses OP_RETURN data and any such transactions should only ever be send-to-self, which wasn't being enforced --- but it is now. I took some time to rework that section completely and now OP_RETURN transactions MUST have an amount of 0, that should prevent any more coins going astray via that route.

I've sent M0ndialu 500 GAP, to reimburse his loss and as a token bug bounty.

To avoid the possibility of losing coins, please refrain from making transactions with the 0.16.3 client until you've switched to the new binaries/source code pre-released as 0.1rc-beta: https://github.com/gjhiggins/gapcoin-core/releases/tag/v0.1rc-beta

Sorry for the convenience.

Cheers

Graham