core-contracts
core-contracts copied to clipboard
near
Core contracts: reference staking pool, lockup, voting, whitelist, multisig.
closes #203 cc @esaminu does this fit the criteria for what wallet needs? What has changed: - interface changed from `'{"keys":["...", "..."]}'` to `'["...", "..."]'` to avoid redundant strings. -...
const MULTISIG_METHOD_NAMES: &str = "add_request,delete_request,confirm,add_and_confirm_request"; but need: const MULTISIG_METHOD_NAMES: &str = "add_request,delete_request,confirm,add_request_and_confirm"; fixed #212
access keys were being given access to call `add_and_confirm_request` which doesn't exist, the correct function name is `add_request_and_confirm`
For the lockup contract simulation tests https://github.com/near/core-contracts/blob/master/lockup/tests/spec.rs There's a `#[quickcheck] fn lockup` that fails when run on near-sdk-sim v4.0.0-pre.4; (it doesn't have any problem with near-sdk-sim v3.2.0). The error below...
Minor: build.sh outputs multisig2.wasm but README still refers to multisig.wasm, possibly due to copying from multisig folder.
Deployment costs per byte of code are going to be increased by a factor of ~5 with this change: https://github.com/near/nearcore/pull/6397 Probably this will happen with protocol version 53, which would...
Based on some comments made here: https://github.com/near/core-contracts/pull/171#pullrequestreview-767219536 There are a few things that can be done to make this smaller (without changing the interface at all): 1. Update to 4.0...