Brice

The alternative is to specify at the function definition level that a parameter does not need to be checked, like: ```clarity ;; #[trust(amount)] (define-public (send-to-contract (amount uint)) (stx-transfer? amount tx-sender...

We have added the `filter` option since I opened this issue, but don't think it solves this specific problem. I'd like to leave it open for now as a reminder...

Troubleshooting guide, suggestions, etc. could also go along with this.

Agreed. Sounds good to me. I opened https://github.com/stacks-network/stacks-blockchain/issues/3052 and will modify this issue to track that issue and make the corresponding changes in the REPL.

No, I haven't spent much time yet to figure out the root cause. It appears that the JS engine is targeting the wrong architecture, but I'm not sure about that....

This probably depends on hirosystems/clarinet#464.

This will be addressed by the combination of https://github.com/stacks-network/stacks-blockchain/pull/3150 and #474, since the comments are being parsed into new nodes in that implementation.

See #183 for another example that needs improved debugability. In this case, the type of one of the arguments was wrong and `mine_block` just silently fails, leaving no receipts in...

Thanks for reporting this @FriendsFerdinand. I see that the type-checker does not include the built-in reserved keywords when it does its checks, but during execution, this is checked. We should...

I submitted a PR to fix this in clarinet, but this should also be fixed in the clarity lib in stacks-blockchain. I will open a corresponding issue there.