Dave Huseby

Results 26 issues of Dave Huseby

While testing ion-bitcoin I slowed down my bitcoind so that RPC responses were really slow and the [BitcoinClient](https://github.com/decentralized-identity/sidetree/blob/54509a579029d086c8e61a10bab61a79447a8fe0/lib/bitcoin/BitcoinClient.ts#L813) quickly timed out and ion-bitcoin that uses sidetree died. This is a...

I recently ran into an issue where I was using rpcauth in my bitcoin.conf file. I was copying the salted hmac over to the *-bitcoin-config.json file for ion-bitcoin as the...

I think it is a good idea for us to use [Linked Data Proofs](https://w3c-dvcg.github.io/ld-proofs/) for the signatures that are stored in Git commits. This seems like the right thing to...

I've been thinking about the authentication process for walking through a git history and verifying that the governance rules, DID doc provenance, and commit signatures all check out. I keep...

## Description I am looking for a way to collect aggregate metrics for each stream/substream at the transport level. I *think* the best way to do this is to create...

difficulty:hard

I recently ran into an issue where I was using rpcauth in my bitcoin.conf file. I was copying the salted hmac over to the *-bitcoin-config.json file for ion-bitcoin as the...

While testing ion-bitcoin I slowed down my bitcoind so that RPC responses were really slow and the [BitcoinClient](https://github.com/decentralized-identity/sidetree/blob/54509a579029d086c8e61a10bab61a79447a8fe0/lib/bitcoin/BitcoinClient.ts#L813) quickly timed out and ion-bitcoin that uses sidetree died. This is a...

Hiya! 👋🏻 I'm trying to set up Github Discussions for all of the libp2p implementations so there is a place to direct users with technical questions. Do you have a...

I got the following error message while trying to build beta and haven't had the time to debug it yet: ``` Running `/usr/local/bin/rustc --crate-name bootstrap --edition=2021 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type...

Reading the spec I noticed that the code blocks in the beginning show a pseudo-wire protocol representation by just showing the contents of each message without explicitly showing the varint...