brenzi
brenzi
I've experienced the same: https://polkascan.io/polkadot/account/16XXocb76BpprdspsR7j5iWFHf4aTMnsVHxgGBXfixs1FFLb check this address on polkadot.js apps and the judgement is there
@MrishoLukamba any news on this issue? This blocks #12153 and we'd be happy to contribute if you no longer work on it
This shouldn't be a problem, you could use 'core::vec::Vec' in that case.
My targets would be both wasm and sgx. So using alloc is fine for me. nightly is fine too
@urschrei alloc is stable now, so my PR uses alloc. However, now the dependency on rstar is still an issue as they don't support no_std yet...
We have proposed a solution for this based on Intel SGX TEEs: https://github.com/w3f/Web3-collaboration/pull/234 * our solution targets on-premise Intel HW (although cloud-SGX would be possible) * Our grant proposal doesn't...
@jleni: Knowing and understanding what you sign is not enough. You need to be able to *verify* the payload. In the case of signing a block, you need to verify...
@DemiMarie-parity Very interesting! But wouldn't this require self-hosted signer HW? Even if cloud services would offer SeL4 VPS, why would you trust them? They still have access to all memory....
@volcano0dr any comment on this would be appreciated
We need "native" threshold multisig for account keys, not session keys. We wouldn't mind to do coordination of signature aggregation ourselves as long as we have some way to generate...