rust-simplicity
rust-simplicity copied to clipboard
ElementsProject
Calling `encode_to_vec` and then `RedeemNode::decode` on the following program leads to a type unification error. See https://github.com/BlockstreamResearch/simfony/issues/118 ``` Decode(Type(Bind { existing_bound: { tmr: fd75bcd8cb55a5e424e09288ac8eb42942534ec1099b72bece0ea2c5479bf3e7, bit_width: 64, bound: 2^64 } ×...
This PR generalizes `CaseTracker` to `ExecTracker` that now supports tracking jet calls (in addition to case branches). It is also now possible to run BitMachine with a custom tracker created...
In https://github.com/BlockstreamResearch/rust-simplicity/pull/266 (commit 10, 674b2725ce2a4a64c74c26db31883d31283844bf) we changed `Value::from_*bits` to take a `BitIter` rather than a generic boolean iter. However, our `Value::iter_*` methods return an opaque iterator type. This means that...
It makes no semantic sense to compare values of different types. Rather, `PartialOrd` could return `None` if `self.ty != other.ty`. > Yes -- I tried this, but we then lose...
It is impossible to debug program with lots of jets. Currently, we fail with generic ``` Jet failed during execution ``` Ideally, we want some position context. Just starting with...
At certain places, the name IMR is incorrect. We should call these values "Identity Hash" instead. See https://github.com/BlockstreamResearch/simplicity/pull/277
Automated update to Github CI workflow `rust.yml` by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action
Right now when the user adds an annex to their Elements transaction environment, it's silently dropped, causing sighash computations and other jets to provide incorrect results. There is a FIXME...
This is the blockhash of the parent chain. It should be a bitcoin::BlockHash I guess. (Though I suppose in principle it could be any chain, sa maybe it should just...
Maybe better off as a discussion. See https://smallcultfollowing.com/babysteps/blog/2025/10/07/the-handle-trait/ This describes a trait which is almost exactly our `shallow_clone` idiom which we use in this crate and others to try to...