Open BingjieGao opened 6 years ago
Hi @BingjieGao --- We know that the Go driver isn't 100% working yet, but we haven't figured out how to fix it yet.
@BingjieGao thanks for listing the issue and trying out the driver; as @ttmc mentions, the driver is still a work in progress. The error you are getting is because the BDB server creates a different fullfilment URI from the driver. The go-interledger package that the go driver use seems to calculate it different from the python implementation that the bigchaindb server uses.
have fixed it? I had the same err!
Please see my pull request. I believe I have solved the problem. I am new to doing pull request on github so let me know if I am missing anything. Thanks. Philip Kwan
We are facing the same issue. When calling from client, returns 400 but from postman we get the error Invalid transaction (InvalidSignature): Fulfillment URI couldn't been parsed.
using Testnet with simple e2e test and encountering 400 Bad Request always, The error message shows: "Invalid transaction (InvalidSignature): Fulfillment URI couldn't been parsed"
Here is the generated txn: