Support

I got error in creating a new service. Even delete it and create again and found no luck. Please help and thanks.

I can see transaction links (via dragonglass) on the proof certificate do not show any results on dragonglass. Am i missing something? The transaction id is however searchable on other explorers.

tried using both collection level and database level proofs but same thing happen. Also purchased the developer plan but no luck. Here is the service(for a document level proof) & the error: dbObject.command( { submitProof: currentVersion, collections: ["provenDiamonds"], filter: newDocument, }, (error, res) => { if (error) { console.error(error); reject("Could not submitproof for version."); } else { console.log(res); resolve("New proof created.", res); } } ); ERROR => MongoServerError: UNAVAILABLE: io exception at MessageStream.messageHandler (F:\Builds\test\node_modules\mongodb\lib\cmap\connection.js:467:30) at MessageStream.emit (events.js:315:20) at processIncomingData (F:\Builds\test\node_modules\mongodb\lib\cmap\message_stream.js:108:16) at MessageStream._write (F:\Builds\test\node_modules\mongodb\lib\cmap\message_stream.js:28:9) at writeOrBuffer (internal/streams/writable.js:358:12) at MessageStream.Writable.write (internal/streams/writable.js:303:10) at TLSSocket.ondata (internal/streams/readable.js:719:22) at TLSSocket.emit (events.js:315:20) at addChunk (internal/streams/readable.js:309:12) at readableAddChunk (internal/streams/readable.js:284:9) { ok: 0, code: 125, codeName: 'CommandFailed' } the thing is those documents stored in the database without a proof and the request not get resolved or rejected either. Here I attached the output when I try to get the proof of such documents using getDocumentProof. { "collection": "provenDiamonds", "version": 25, "documentId": "61de71ac00c5985c343f70e3", "errmsg": "There is no proof for this version of the document" }

MongoDB Atlas: 409 A user with username "Test" already exists. { "message": "MongoDB Atlas: 409 A user with username "Test" already exists.", "code": "ATLAS_USER_ALREADY_EXISTS", "deletable": false, "humanInterventionNeeded": true } How to fix this issue? Delete functionality not available!

BSON field 'OperationSessionInfo.$clusterTime' is a duplicate field

{"message":"(Location51002) Role \"[email protected]\" already exists","code":"UNKNOWN","deletable":false,"humanInterventionNeeded":true} All the time I get this error when I am trying to create a new service

Update billing not working

I can't find in my dashboard where can i set my billing and credit card information, can you guide me please?

Hi, sorry for writing here but the add comment button was not working on my previous post. This is the answer to this post: https://provendb.readme.io/discuss/601dd3a16d2388007def3f93 Yes, you are right, I meant submitProof. So I created now again two documents in the database "xf1" in the collection "col_uploadedFiles" with the ids: 601e5125cf2db37b71deff4a, 601e5125cf2db37b71deff4b Then I submit this command: "{submitProof:45, collections:'col_uploadedFiles', filter: {_id: ObjectId('601e5125cf2db37b71deff4b')}, anchorType: 'ETH_MAINNET'}" Now just 601e5125cf2db37b71deff4b should be verified by the blockchain. But when I fo a getProof for 601e5125cf2db37b71deff4a, I get this response: "{ \"ok\" : 1, \"proofs\" : [{ \"collection\" : \"col_uploadedFiles\", \"scope\" : \"collection\", \"version\" : 45, \"documentId\" : { \"$oid\" : \"601e5125cf2db37b71deff4a\" }, \"versionProofId\" : \"9b4ce6f3-9955-4076-86ba-4763ef71b07f\", \"status\" : \"Pending\", \"documentHash\" : \"38a6d2b0bf681e43fb0186901a009955854a3af02c680223e3333a48cea9c80b\", \"versionHash\" : \"a3a27437f28b3c47a0c574f45d02dbc84cc1670c74c8ddedb7cca07e67c35d4b\", \"errmsg\" : \"The proof is not yet valid\" }] }" It would be nice if you can check.

When I create two documents in a collection in the mongo provendb these documents are at first not proofed in the blockchain. So far so good. When I now make the getProof request and use a filter for a single document (the second one) this document gets approved. Also fine. But when I check now the proof status of the first document it says that this document is also approved with the version number from the second document. The version number of this prove is the version of the second document. This is the first strange thing. When I then check the history of the first document I see that the newest version number is the one which it was created and not the one which will be shown in getProof. So I now have a document in the database which is approved but with a version number which is not existing for this document. When I use the verification command I see that the VersionHash and DocumentHash are the same for the second document. But for the fist document they differ. Nevertheless the command says that the document status is valid. Can you please explain me why the first document is valid even if I make a filter for just the second document. And I want to know also why the versionId which is shown in the getProof process does not exist in the history of the first document?