Thane Thomson
Thane Thomson
The new required structure for signatories in v0.2, as discussed in #45, makes this explicit (currently on branch `prototype/v2`, soon to be merged to `master`). Hopefully this addresses this issue?
I'll look at integrating [Viper](https://github.com/spf13/viper) support here for Themis Contract configuration.
A simple way to implement this would be to: 1. Gather the Keybase IDs of all signatories on the contract. 2. Find the first local identity whose Keybase ID matches.
Is this exclusively relevant to v0.23.x, or should this feature still be available in newer versions of tendermint-rs?
@shravanshetty1 you're right. So right now there are two options here: 1. Use the [fetch](https://rustwasm.github.io/docs/wasm-bindgen/examples/fetch.html) API to do the low-level networking, and then figure out how to make the `async`...
An alternative approach here as suggested by @soareschen is to support multiple versions of Tendermint Core from within a single codebase. In other words, Tendermint Core version-specific code would live...
> To assess this meaningfully it would be helpful to understand which types/interfaces actually differ between the versions. This depends on the specific versions, whereas we need a somewhat generic...
Is this related to Tendermint Core or tendermint-rs?
Just to be clear, you're using tendermint-rs v0.27.0, right? If so, have you tried the latest release of tendermint-rs? (v0.31.1) Asking because we don't have capacity to support older releases...
@plafer do you perhaps have capacity to implement this?