Harry Solovay

Ideally we could somehow encode the parallelism restriction in the `Rune` type. ```ts Rune.tuple([txA, txB]) // ~~~ // ^ // Argument of type 'ExtrinsicRune' is not assignable to parameter of...

I believe we should create a new error type `DuplicateAccountNonceError` which we could return and unhandle from `SignedExtrinsicRune`'s `sent` in the case that someone fires off a new sent with...

Ah, so this will retain the run state (aka. last position)? If so, is `watch` the correct method name? Perhaps we should rename this to `iter`?

I don't think utilizing `iter` for pagination is the right way forward. An example that illustrates why: Here, we would expect for the evaluated `page` to contain the keypages corresponding...

Do we want to throw a log into `DevRelaySpec` and `DevParachainSpec` at `spawnNet`? Something like... ```ts console.log(magenta("Launching"), this.name, gray(`with ${binary}`)) ```

WIP https://github.com/paritytech/capi-todo-app Tagging @statictype and @peetzweg to take a look

Malformed wouldn't imply not existing on chain either. Perhaps `BlockHashDneError`?

How would both errors be useful? I don't forsee different handling between invalid and DNE.

While it would be nice to have any error data in a type-safe manner, this isn't standard in JS. I sure do wish JS had an effect system :/ if...

> maybe a more interesting question is that do we even need events in Mina smart contracts? @yunus433 great question. @Trivo25 and I have discussed this a bit in #1569....