Hans Svensson

I wrote a simple QuickCheck property, basically starting a bunch of nodes (with a placeholder process that make sure `gproc` is started) and commands to do `monitor(..., follow)` and `ets:tab2list(gproc)`...

I'll see if I get time to cleanup that model into a non-embarrasing state, if so I will share it and it can be extended to do something useful :-)

Made a pull request (#144) For me the existing QuickCheck property failed horribly (made some changes in the pull request) but I guess that is expected?

It doesn't really include an already signed Tx, the GAMetaTx (including the calldata for the auth-function) is _equivalent_ to a signed TX - so for symmetry we don't allow those...

``` assert_id_type(account) -> ok; assert_id_type(channel) -> ok; assert_id_type(contract) -> ok; assert_id_type(oracle) -> ok. ``` From IRIS you can have up to 32 pointers registered for a name. The pointer key...

Note: there is no check that the provided value/id _actually_ points to something of its stated type - but it must have a type. Note2: I'm just reading the code...

@marc0olo I think it is also `oracle_pubkey` and I can't remember if also `contract_pubkey` is special, but probably not... Problematic... Well, it would be a bit of work as with...

The posted log has two transactions, one with nonce 6 and one with nonce 7, not sure what is expected. The one with nonce 6 can't be applied and the...

Sure, but an improved error messge does not make the Tx any more valid the issue is literally: _"PostTransaction return Invalid tx for correct transactions"_

Remeber that there are different checks in the TX-pool. A new transaction (pushed from the outside to the node via HTTP for example) is checked in more detail compared to...