Jaco

Ok, now I get your dilemma... Not a cryptographer, so it took me a while to get on the same page. I can only comment on a external use perspective...

Only one actually - all the Junction etc. stuff is implemented to do the derivation, however in the JS derive function, cannot call anything to adjust the key (as per...

yes, it looks like a single function, just not 100% sure how to jump through all the hoops since it operates on an actual pair - but basically, in the...

@burdges Gav did this - https://github.com/paritytech/substrate/blob/master/core/primitives/src/sr25519.rs#L368 which is used further on by https://github.com/paritytech/substrate/blob/master/core/primitives/src/sr25519.rs#L450 (i.e. here the soft derivation goes via `w3f/schnorrkel` and hard derivation via the first linked function) So...

Hacking around it by editing `schnorrkel_js` manually, basically this - ```js // const TextDecoder = require('util').TextDecoder; let cachedTextDecoder = new TextDecoder('utf-8'); ``` (And then included that locally again, not using...

The issues will go away soon-ish - see https://github.com/rustwasm/wasm-pack/issues/157 & https://github.com/rustwasm/wasm-pack/pull/523

Additionally - ``` Uncaught RangeError: WebAssembly.Compile is disallowed on the main thread, if the buffer size is larger than 4KB. Use WebAssembly.compile, or compile on a worker thread. at Object.eval...

Worked around the circular dep in https://github.com/polkadot-js/common/pull/306, made the WASM init async in https://github.com/polkadot-js/common/pull/307 and fixed dependency as expression in https://github.com/polkadot-js/common/pull/308 (For now, basically some adjustments to the generated files...

Last issue (that I don't have a work-around in for) is the `require` here - ```js module.exports.__wbg_require_86edd37cfda5f13d = function(arg0, arg1) { let varg0 = getStringFromWasm(arg0, arg1); return addHeapObject(require(varg0)); }; ```...

Yeap, it is a `wasm-pack` generation issue, nothing that is introduced elsewhere.