enigma-core
enigma-core copied to clipboard
scrtlabs
Enigma Core library. The domain: Trusted and Untrusted App in Rust.
A selected few validators have suggested that the large community wants a 1:1 swap between ENG:SCRT. I believe this to be a false narrative. In order to quantify my gut...
Changed naming. Error Handling. Removed unnecessary structs. made the code a bit more rustic. The Integration tests are failing, work is needed to be done in order to locate the...
- Renamed Baidu to apache. - Upgraded all crates depended on Apache crates. - Changed the order of flags in the makefile according to the apache release notes. - removed...
**Describe the bug** Decrypting the output of a computation includes a prefix, at least when he results are `Vec`. What is it used for? **To Reproduce** See example here: https://github.com/enigmampc/coinjoin-poc/blob/65350409f4dbf43eeb178904cec3ca25e7e5070e/enigma-coinjoin-operator/src/secretContractClient.js#L86...
I'm getting a compilation error when compiling a secret contract that references a smart contract. I followed an elimination process to determine what in the smart contract abi causes the...
This is more of a PoC for @AvishaiW or @moriaab to do in the future. ~~this should wait till after https://github.com/rust-bitcoin/rust-secp256k1/pull/115~~ https://enigmaco.atlassian.net/browse/EP-612 ~~Replacing libsecp256k1 with rust-secp256k1 makes it not compile...
Currently the `block_number` parameter of thSON-RPc is a string repressing a hexadecimal 32-bytes number. A more cleaner solution is using u256 type.
If wrong parameters are passed to secret contract deployment or computation, the "unreachable" exception occurs, which is unclear. To reproduce the behavior, call to any contract computation with wrong input....
**Describe the bug** KeyManagement node randomly failed to start. Is this the same as #98? @fredfortier, @elichai you can close it if it's a duplicate, but the backtrace looks different...
