See this tweet for context.

The client should set the log-level themselves:

LoggerFactory.INST.logLevel('none'); // or any other level

Hi

I get this error when I run the following code. What could be the cause?

2023-08-05T11:54:06.505Z FATAL [HandlerBasedContract] Error while interacting
 with contract [
  {
    type: 'exception',
    error: 'Error: Database is not open\n' +
      '    at maybeOpened (hollowdb/node_modules/abstract-level/abstract-level.js:133:18)\n' +
      '    at hollowdb/node_modules/abstract-level/abstract-level.js:160:13\n' +
      '    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)'
  }
]

These codes causes an error.

• pattern1

  const keys = await sdk.getAllKeys();
  const values = await sdk.getMany(keys);

• pattern2

  const keys = await sdk.getAllKeys();
   keys.map(async key => {
    const value = await sdk.get(key);
  });

The same error occurred after deleting the cache directory.
Please response me.

We are not using del yet, as it may not completely remove every key in the cache there is delete function defined in SortKeyCache but it is not exported in KV yet.

Could we use the Base class with a generic <V = any> type argument, which later passes these into state, contract cache and KVstorage as generic? This is also because both Redis and LMDB take in a generic parameter. This should make most functions returns a type V rather than unknown.

If you are using the prover package with hollowdb 1.2.4, the underlying warp-snarkjs-plugin snarkjs and prover snarkjs has a mismatch and this causes plonks to not verify.

This is fixed, and will be merged soon.

Currently, one might have to use an external library such as poseidon-lite or run the circuit itself and get the key from the output. We could instead run a witness computation function, and provide this as a utility so that a client can generate the key without creating a proof itself.

We seem to be getting too much logs, although none is specified at:

https://github.com/firstbatchxyz/HollowDB/blob/master/src/sdk/base/index.ts#L35

We should make modifier functions more readable, especially the types and generics.

As per the warning:

Current object & {protocol: ProofSystem} is a bit annoying in frontend state management.

Parcel can't export for multiple targets while emitting types for each, so I've made a workaround explained here: parcel-bundler/parcel#8873 (comment)

See the issue itself here: parcel-bundler/parcel#8082

The workaround is very hacky and we should probably use a different bundler.

Possibly something related to Warp or Arweave is hanging in the background, thus we have to force.
Will look into it.

We can use Husky for this.

https://www.npmjs.com/package/husky

We can deploy a contract by giving it's sourceTxId instead of contract source code itself.

I'm a Cyber Security researcher and developer of PackjGuard [1] to address open-source software supply chain attacks.

Issue

During my research, I detected a deleted package in this repository.

Details

Specifically, the package hollowdb mentioned in file README at line 36 does not exist on the public PyPI registry. A bad actor can hijack this package to propagate malicious code.

Impact

Not only your apps/services using https://github.com/firstbatchxyz/hollowdb repo code are vulnerable to this attack, but the users of your open-source Github repo could also fall victim.

You could read more about such attacks here: https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610

Remediation

Please highlight this in file README and register a placeholder package for hollowdb on public PyPI soon to remediate.

To automatically fix such issues in future, please install PackjGuard Github app [1].

Thanks!

1. PackjGuard is a Github app that monitors your repos 24x7, detects vulnerable/malicious/risky open-source dependencies, and creates pull requests for auto remediation: https://github.com/marketplace/packjguard

• Will use package.json within as an isolated project
• Can be TS

Transfer should:

• Remove itself from whitelists and add the target address instead
• Change ownership