Jack Tanner
Jack Tanner
also getting this issue when trying to run a .wasm file with i64 types in nodejs. anybody found a way to get this working in javascript?
Solutions to these three issues can be found in the following PR https://github.com/Tonomy-Foundation/Tonomy-ID/pull/129/files
Perhaps it would be useful to know which dfuse services depend on each other, and then I can disable some of them.
for this query there are 4 tx results
sometimes this is taking 10+ seconds to respond. This is happening more when the blockchain has been left for 10+ minutes. In the few minutes after the dfuse container starts...
I have turned of the state history plugin, and state history plugin API. These are the measured response times for a simple search query **Request** Request and response are constand...
We are building this as a separate product. We show the original signer of the transaction by looking up the account that has the key. In addition, we ensure that...
The information exists inside the thrown error, just not printed. Maybe consider that it is printed to cater for ignorant devs (oops). Suggest this issue is closed.
Solved by adding the following to `package.json` ```json "resolutions": { "@veramo/credential-ld": "5.6.0" } ```
Also can be solved with package.json ```json "resolutions": { "jsonld": "link:./node_modules/@digitalcredentials/jsonld", } ```