-
# Problem
Both metamask and implementation linked to EIP do not support arrays.
I skipped them when typed data was implemented initially.
# Implementation
EIP 712 defines how array and slice…
-
## Description
While try running some instrumented tests (or running the application), I run into an exception during the build.
I'm trying running the application on a Nexus 5 API 28 image witho…
-
Geth lacks an API to perform an EIP-191 conforming signature for a given unlocked account. An API should be implemented that allows for arbitrary data to be signed by a specified unlocked account. Thi…
tuxxy updated
5 years ago
-
`eth_sign`: https://github.com/ethereum/wiki/wiki/JSON-RPC#eth_sign. Signatures derived from `eth_sign` should take on this form: `sign(keccak256("\x19Ethereum Signed Message:\n" + len(message) + mess…
-
as [EIP191](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-191.md), all the signature should start with "\x19Ethereum Signed Message:\n"
nkbai updated
6 years ago
-
Previous discussions:
https://github.com/raiden-network/spec/issues/23
https://github.com/raiden-network/spec/issues/67
This was also brought up by @berndbohmeier in the internal audit, where he …
-
I'm wondering if there is an attack with EIP-155 style chainID-aware signatures.
The Python codebase [seems to accept](https://github.com/raiden-network/raiden-libs/blob/master/raiden_libs/utils/si…
-
Assess adding a message type identifier for each use case. This will be helpful when dealing with protocol upgradability.
This would mean that the channel participants would sign on:
```
signat…