Solidity – Getting Error Message From require()

That account corresponds to using the empty string "" as a restore phrase. Are you sure you clicked on "create account" and not "recovery phrase" as described here: https://blog.parity.io/restoring-blank-seed-phrase/ ?

If you clicked the other button and then didn't specify a restore phrase, this is the account you will get every time (others have already accessed this account and sent the transactions you see). Unfortunately, before version 1.6.7 Parity didn't warn you that you were doing this. If you generate this address it is not a safe place to store funds! Anyone else can generate and access it easily.

On the other hand, if you did properly use the "new account" option this could be a bug. When you generated the account, did it give you a recovery phrase to write down? (And did you write it down?)

To elaborate for others: no, this is not a one in a bazillion chance collision. Ethereum is fine! What it is is either a misclick or an error in the Parity application.

It is included since Solidity 0.4.22. There is a merged branch adding this feature in the milestone.

The documentation states

There are two other ways to trigger exceptions: The revert function can be used to flag an error and revert the current call. In the future it might be possible to also include details about the error in a call to revert. The throw keyword can also be used as an alternative to revert().

In the past it was used like this

require(
    msg.sender == _account
);

And in Solidity 0.4.22 and newer it can be used like this

require(
    msg.sender == _account,
    "Sender not authorized."
);

Adding the reason as the second parameter