Lloyd Fournier

> `last_seen` is for conflict resolution of unconfirmed transactions (since we are a wallet and we cannot see the complete mempool). However, sometimes we would like to use when the...

So I was looking at this and to make the whole idea work we really need to block confirmation time to be communicated to the `TxGraph`. Some anchors will have...

I think there is almost nothing copy pasted between the bitcoind and electrum examples? In any case they are architecturally different. In the `bitcoind` example, your application has a thread...

Why do we need a trait for this. What's wrong with a struct that just has all the fields you need.

Sure I support reimplementing in terms of `derivation_of_spk`. Also there might be a better name for it.

> ``` > /// Finds how the wallet derived the script pubkey `spk`. > /// > /// Will only return `Some(_)` if the wallet has given out the spk. >...

Before introducing a way of notifying users of a state change we should have a way of determining the current state of a transaction more precisely. Right now we only...

I'm a little confused by the "over 50% boilerplate" comment because I don't really see much boilerplate there. You'd have to copy paste most of that main function somewhere in...

@danielabrozzoni it's looks great but when you fill in the `....` I have a feeling it won't any longer because of all the arguments you need to pass. Potentially, you...

We should be able to reason about this internally in the `TxGraph` if we have the transaction parents. The main design challenge is in coin selection. We have to have...