The documentation currently explains how to contribute a Driver in the form of a Docker container, but should also mention how to contribute a driver in the form of an HTTP Proxy (eg did:ipid, did:elem)
During the proof of fee integration, we found that the normalized fee being calculated in the testnet was too low and the bitcoin npm package was throwing exception that the min fee must be 554 (or something) satoshis. So we have added a hard-coded limit of 1000 satoshis as the fee for now. It seems that this shouldn't be a problem in mainnet as the
and verifiy it with an array of audience or just one audience it gives a matcherror. Let's say a DID document has audience 0x1 and 0x2 and now If i verify a JWT with audience 0x2. The verifyJWT function will gives
I assume that the idea is to use the authentication section and in particular any of the verification methods included in it to verify the JWT? It is not explicitly stated which part to use. We should stick with the DID spec terminology.