Aaron Blankstein

I will try this out in my branch. I used a workaround to get unblocked (basically just hardcoding signature values), but I'll see if this works. What are your thoughts...

Yep, it worked! ``` $ clarinet test ./tests/hyperchains/hyperchains_test.ts => Unit test the withdrawal leaf hash calculations using test vectors ... ok (21ms) ./tests/hyperchains/hyperchains_test.ts => Ensure that block can be committed...

I also experienced this issue, while working with ledgerjs -- and I think the issue lies there, not in the hw app. The transaction preparing code in `@ledgerhq/hw-app-btc` assumes that...

Something like: ``` ;; returns a copy of `iterable` with the entry at index set to value ;; returns `(ok iterable')` when successful ;; returns `(err 1)` if `index` is...

I agree -- using `set-` is probably confusing because no mutation occurs. Perhaps `replace-at` is a better name for this. `replace()` methods usually connote non-mutating methods in programming languages (and...

This is still something that would be useful for Stacks 2.1

Yeah, definitely. In fact, we won't have to simulate the events, we can just add new `print` statements to the `pox-2` contract. Do you have any ideas for the different...

> Isn't this essentially the STACKS_TRANSACTION_LOG feature? It's a little different -- the log messages would provide a log of every time a particular tx is _considered_, whereas the DB...

> I prefer the first option, because it is more foolproof. With the "many log points" approach, there is no clear pattern, and always the worry that some log points...

> Maybe we can do the "both" approach. I like the idea of forcing the interfaces to propagate these events, because I think it will clarify them. Yes -- one...