Orbit-db: a 3Box SDK bug because OrbitDB

[aturX]

"Error: Could not append entry, key "did:3:bafyreig4trqtifolb3mw7b6elt5butfb23gj2n6dugtjm2gwt63s..." is not allowed to write to the log"

I have same problem , I can read data from 3box, but can't change or add new data into.

[aphelionz]

@aturX What version(s) of orbit-db and ipfs are you using?

[aturX]

"ipfs": "^0.46.0",
    "ipfs-did-document": "^1.2.3",
    "ipfs-log": "^4.6.1",
    "ipfs-pubsub-room": "^2.0.1",
    "ipfs-repo": "^3.0.2",
    "is-ipfs": "^1.0.3",
    "js-sha256": "^0.9.0",
    "levelup": "^4.4.0",
    "libp2p-pubsub": "^0.4.6",
    "lodash.merge": "^4.6.2",
    "muport-did-resolver": "^1.0.2",
    "node-fetch": "^2.6.0",
    "orbit-db": "^0.24.2",
    "orbit-db-cache": "^0.3.0",
    "orbit-db-identity-provider": "^0.3.0",
    "orbit-db-storage-adapter": "^0.5.3",

this is 3box's package.json, when I use 3box that I find I can not write data into 3box, and 3box's developer say that is not their SDK's error. You can see it 3box issues

[aphelionz]

@tabcat is this related to the secp256k1 bug?

[aphelionz]

@oed @zachferland looking into this now, any suggestions are welcome

[tabcat]

@aphelionz i wouldnt be surprised if this was related to https://github.com/orbitdb/orbit-db-keystore/issues/45

[aphelionz]

That's what I was thinking too... can we get a PR in?

[aphelionz]

Nevermind about the PR..

@aturX Can you give me the output of npm ls orbit-db-keystore?

[aturX]

Sure, This is result.

PS D:\app\Ldata\VUE\ant-cave> npm ls orbit-db-keystore
[email protected] D:\app\Ldata\VUE\ant-cave
`-- [email protected]
  +-- [email protected]
  | `-- [email protected]
  `-- [email protected]
    `-- [email protected]  deduped

@aphelionz

[aphelionz]

Hmm, ok. We just released OrbitDB 0.25.0, maybe that will help.

In the meantime, can you package up some code, either on codesandbox or in a git repo so I can reproduce and experiment?

[aturX]

I use it here

It maybe not useful, I am trying it to make sure that if I should update 3box 's package because it is now still 0.24.2 .

now it is..

+-- [email protected]
| `-- [email protected]
|   `-- [email protected]
+-- [email protected]
| `-- [email protected]  deduped
`-- [email protected]

[aphelionz]

Is this resolved from the update to 0.25.1?

[aturX]

@aphelionz Thanks! Problem solved. It worked
gooood!

[aphelionz]

Glad to hear. Closing this but don't hesitate to reach back out.