Victor Wu

Debug polyfill buffer error

5

Error stems from fabric.http.js minified file. `WASM_BUFFER` is used in secp256k1 which is a wasm compiled dependency. Line producing the error `const WASM_BUFFER = new Uint8Array(wasm.memory.buffer);`

Migrate storage functions to LocalForage

1

Update types/storage feature used in fabric-browser-extension to be used in LocalForage - this is part of types/stash - types/store this.status.content is what should be stored. - _getPathForKey should be what...

All fabric types should be classes, types/encryption is currently functions, update it to be a class

example template in views/

1

in views/ folder, create example template websites using compiled webpack bundle.

Enable wasm in browser extension

2

- https://groups.google.com/a/chromium.org/g/chromium-extensions/c/5DJHT9TCy5M - https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/content_security_policy - used wasm-unsafe-eval, still same error https://support.google.com/chrome/thread/31687823/csp-content-security-policy-is-not-supported-wasm?hl=en - https://github.com/WebAssembly/content-security-policy/blob/main/proposals/CSP.md

Update the bech32m identity spec in Fabric Identity, to improve build when used in extension Bip44 is the current derivation path.

Move types/encryption functions to types/identity Other possible locations - types/actor - enables many other types to be able to use the encryption features - types/key - has encrypt and decrypt...

implementing encryption functions

Build/upgrade deps

1

related to #80

#Summary This feature integrates leveldb database storage functions into types/store. This would enable further account and identity storage, allowing users to have better profile management when accessing various fabric applications....