profile
viewpoint
Illia Polosukhin ilblackdragon NEAR Protocol San Francisco, CA

ilblackdragon/django-themes 45

Application for django framework, provides flexible and configurable theming system.

ilblackdragon/adversarial_workshop 40

Adversarial Workshop code and presentation

ilblackdragon/django-blogs 35

Blog app for django. Provide blogging functionality for you django project. Multiblogging system, blog per user blog, one user blog are available for you in one app.

ilblackdragon/django-misc 16

Django-misc - module with different useful stuff for django. Here you'll find: couple decorators, like render_to and receive; json_encode module for simplify work with json, some usefull templatetags, like set, filter, get etc; some additional utilities; bbcode template tags; template tags that provide like and share for social sevices

ilblackdragon/GAN 5

GAN experiments

ilblackdragon/aiprog 4

AI programs

ilblackdragon/data-science-starter-kit 4

Data Science Starter Kit repository to organize your Data Science projects (Python-based mostly at this point of time)

ilblackdragon/django-localeurl 4

A Django application that allow you to specify the language of a page in the URL. Fork from https://bitbucket.org/carljm/django-localeurl

ilblackdragon/django-manager 4

Template for django project using our conventions

issue openednearprotocol/near-evm

Benchmark NEAR EVM vs native WASM contract vs Ethereum

There are two questions that come up:

  • How much slower contract in Solidity in near-evm compared to the same contract in WASM
  • What is the speed compared to Ethereum

We need to figure out what is an apple to apple comparison here and evaluate it.

For WASM vs NEAR EVM we can just have a simple contract written in both and evaluate it on the same node. Are there any default benchmarks for Ethereum @prestwich we can reuse?

created time in 26 minutes

issue commentnearai/torchfold

RuntimeError: bool value of Tensor with more than one value is ambiguous

@supriya-pandhre Sorry, we are not actively maintaining this repo right now as we shifted our work to https://github.com/nearprotocol development.

Probably the error is around the fact that you can not do in with tensors anymore. The solution is to change to not any([arg == x for x in self.cached_nodes[op]]) or something of this sort. I sadly don't even have pytorch installed right now so won't be able to repro. But if you make a PR with the test that fails and a fix I'll review it.

LemonMi

comment created time in 14 hours

issue commentnearprotocol/nearcore

Use master branch for development

So here are few questions + thoughts to this and #2174:

  • Do we want to allow people who check out master to join TestNet / MainNet? - If yes, there are two options: - (1) master is the most recent stable / MainNet release. And we only update it when we hard fork our network (current approach). Merging to master is major release. This should be tested ~14 days of replaying transactions, bombarding, security reviews, etc. - (2) master has latest code, but we maintain backward compatibility. Meaning we have CI that spins up new node, connects to the stable TestNet (that replicates MainNet), replays the chain and runs suite of tests. Without passing this, we can not merge into master. This should probably take ~1 day at least of testing. - (3) If no, we can have bleeding edge in master with less strict rules on merging. We can ban running start_mainnet.py and start_testnet.py in the master branch (they bork and say "You are on a wrong branch, switch to blah branch"). Note, that if we don't do that, the risk is that someone will run slightly different protocol that will get them slashed on MainNet. Moving from master to beta can take ~1 day of testing toward beta network and ~14 days of testing on beta network replaying production and stress testing loads to stable.

Previously we were targeting to go with (1) I think @damons you suggesting to go with (3) -- I don't mind just want to make sure we understand all things coming with it.

E.g. we need to make sure then that even if someone tries to run binary from master toward stable / and later MainNet - it should always fail with helpful error.

  • Toward #2174: a lot of "features" will be hard to disable with feature flags.

For example state without trie #2050 - even with somewhat scoped change, it still changes some APIs across other usages. Or even something simple as 170 lines biasable randomness PR #2177 is might be possible but would require flags on the data structure to ignore new field (because otherwise that's a hard fork of a feature) and 16 files of flags with prob multiple places in each file. I'm not even talking about the unbiasable randomness PR that is 1.5k+ lines across probably all chain components.

We have discussed upgradability as well, and @nearmax was suggesting to use different versions of the same cargo package in the same binary and change which one is used via runtime. I'm not 100% sure how that would work, but we can explore that as an alternative to feature flags and also allow us to upgrade network without downtime.

@damons In your latest table I'm not 100% sure if master is latest pushed code or latest "beta" and dev is latest pushed code?

Not exactly sure from your comment also the flow from branch to branch, I was expecting something like this:

  • master - latest pushed code, can contain hard fork from current stable, NEVER runs with testnet and mainnet. Runs suite of tests in background after PR submitted, and if there are regressions - we rollback that PR / PRs. Suite of tests, include spinning up large network of nodes, replaying production load of transactions and also stress testing with set of contracts & transactions.
  • every week we push upgrade to staging network, which is our TestNet. This is binary that runs with testnet. This has people testing it continuously: validators, developers, us, both because this is "free" network and all of our tooling supports it well. Additional testing / security reviews happen at this point as well. Tooling updates also "stage" here and test that everything works.
  • every month we have release into stable, which is MainNet release. This includes updates recorded in the spec release 1 month prior and any other relevant bug fixes and changes.
  • additional hot fixes and security fixes can be fast tracked into stable, but require additional process of approving & defining how that will be tested.
frol

comment created time in 14 hours

issue commentnearprotocol/near-explorer

Deleted account is not shown in the explorer at all

@icerove The bug is not that you can see old transaction. The bug is that you can not see deleted account.

ilblackdragon

comment created time in 21 hours

issue openednearprotocol/near-bindgen

Doc strings are lacking in promise.rs

There are no explanation for the arguments and their types in promise.rs for all the methods.

For example add_access_key takes method_names as Vec<u8> but examples are presented as strings. Also doesn't cover the case of empty string for allowing all methods to be called.

Having doc strings with per-argument types and explanations of arguments would be great for developers to understand.

created time in 21 hours

issue commentnearprotocol/near-explorer

Deleted account is not shown in the explorer at all

We should show transactions for deleted account. This bug is about not seeing deleted account (not that when I re-create it's still there).

ilblackdragon

comment created time in 21 hours

startednearprotocol/near-events

started time in 21 hours

issue closednearprotocol/near-linkdrop

send should add a key

Right now send doesn't add a key to the account, so you have to manually do this. Ideally it should attach a public key to the account within the same function.

closed time in a day

evgenykuzyakov

issue commentnearprotocol/near-linkdrop

send should add a key

Fixed.

evgenykuzyakov

comment created time in a day

push eventnearprotocol/near-linkdrop

Illia Polosukhin

commit sha 04f493a74f0668d9db18481ffcf51f3d866ad12b

Update lib.rs

view details

push time in a day

issue commentnearprotocol/NEPs

NEAR Spec and standards

Will be moving structure into here. Proposals here should update changes according to the structure if they changing spec. Discussion for changing spec should be happening here as well. We are working with Commonwealth to add PRs from this repo to the Commonwealth so we can cross-discuss + add in future bounty for implementation and others.

ilblackdragon

comment created time in a day

startednearprotocol/awesome-near

started time in 2 days

issue openednearprotocol/near-bindgen

Passing empty method_names in add_access_key fails

When creating promise with adding access key, there is no way to allow for no method name restriction. Passing empty bytes doesn't work, results in EmptyMethodName error.

Repro:

        Promise::new(env::current_account_id()).add_access_key(
            pk,
            ACCESS_KEY_ALLOWANCE,
            env::current_account_id(),
            vec![]
        );

created time in 2 days

issue openednearprotocol/near-bindgen

Add VMContext builder for easier tests

I keep copying my context builder to write tests easily with different contexts:


    pub struct VMContextBuilder {
        context: VMContext,
    }

    impl VMContextBuilder {
        pub fn new() -> Self {
            Self {
                context: VMContext {
                    current_account_id: "".to_string(),
                    signer_account_id: "".to_string(),
                    signer_account_pk: vec![0, 1, 2],
                    predecessor_account_id: "".to_string(),
                    input: vec![],
                    block_index: 0,
                    block_timestamp: 0,
                    account_balance: 0,
                    account_locked_balance: 0,
                    storage_usage: 10u64.pow(6),
                    attached_deposit: 0,
                    prepaid_gas: 10u64.pow(18),
                    random_seed: vec![0, 1, 2],
                    is_view: false,
                    output_data_receivers: vec![],
                },
            }
        }

        pub fn current_account_id(mut self, account_id: AccountId) -> Self {
            self.context.current_account_id = account_id;
            self
        }

        pub fn signer_account_id(mut self, account_id: AccountId) -> Self {
            self.context.signer_account_id = account_id;
            self
        }

        pub fn predecessor_account_id(mut self, account_id: AccountId) -> Self {
            self.context.predecessor_account_id = account_id;
            self
        }

        pub fn block_index(mut self, block_index: BlockHeight) -> Self {
            self.context.block_index = block_index;
            self
        }

        pub fn attached_deposit(mut self, amount: Balance) -> Self {
            self.context.attached_deposit = amount;
            self
        }

        pub fn account_balance(mut self, amount: Balance) -> Self {
            self.context.account_balance = amount;
            self
        }

        pub fn account_locked_balance(mut self, amount: Balance) -> Self {
            self.context.account_locked_balance = amount;
            self
        }

        pub fn signer_account_pk(mut self, pk: PublicKey) -> Self {
            self.context.signer_account_pk = pk;
            self
        }

        pub fn finish(self) -> VMContext {
            self.context
        }
    }

created time in 2 days

push eventnearprotocol/near-linkdrop

Illia Polosukhin

commit sha a557ac48883668c16fe5c73bf0a8a2e178f6d9f7

Update what access keys have access to

view details

push time in 2 days

issue openednearprotocol/near-explorer

Deleted account is not shown in the explorer at all

Steps to reproduce: Create account & delete account:

near create_account testtest --masterAccount someaccount
near delete_account testtest someaccount

Check in explorer that testest is not found. Re-create account back and see that transaction history from before is shown.

created time in 3 days

issue openednearprotocol/near-shell

Dev deploy gets rent unpaid due to not enough balance

When calling dev-deploy received an error that RentUnpaid: Probably not enough NEAR attached to the transaction:

near dev-deploy res/linkdrop.wasm --masterAccount illia.china --keyPath ../near-evm/neardev/default/illia.china.json
{
  networkId: 'default',
  nodeUrl: 'https://rpc.nearprotocol.com',
  contractName: 'near-hello-devnet',
  walletUrl: 'https://wallet.nearprotocol.com'
}
Loaded master account illia.china key from ../near-evm/neardev/default/illia.china.json with public key = ed25519:qSq3LoufLvTCTNGC3LJePMDGrok8dHMQ5A1YD9psbiz

Error:  TypedError: Transaction B4XPv4BMiuDX8fxjk79tqMeCquB2TFVFcjtxUqiRHPnP failed. The account dev-1582184616033 wouldn't have enough balance to pay required rent 10920
    at Account.signAndSendTransaction (/usr/local/lib/node_modules/near-shell/node_modules/nearlib/lib/account.js:84:23)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
    at async LocalAccountCreator.createAccount (/usr/local/lib/node_modules/near-shell/node_modules/nearlib/lib/account_creator.js:17:9)
    at async createDevAccountIfNeeded (/usr/local/lib/node_modules/near-shell/commands/dev-deploy.js:62:5)
    at async devDeploy (/usr/local/lib/node_modules/near-shell/commands/dev-deploy.js:34:23)
    at async Object.handler (/usr/local/lib/node_modules/near-shell/utils/exit-on-error.js:4:9) {
  type: 'ActionError::RentUnpaid'
}

created time in 3 days

create barnchnearprotocol/near-linkdrop

branch : master

created branch time in 3 days

created repositorynearprotocol/near-linkdrop

Contract to drop tokens via link

created time in 3 days

issue commentnearprotocol/NEPs

NEAR Spec and standards

Ok, here is the decision:

  • Rename this repo into specs.
  • This repo will be maintaining specs, processes and standards.
  • Moving the content of https://github.com/nearprotocol/nomicon to this repo.
  • Changing format for NEPs to either:
    • Modify spec (toward next planned release of the spec)
    • Add new standard (Fungible Token) or revise existing standard (e.g. Open Web v1.2)
    • Describe process for something (e.g. release process for specs)
ilblackdragon

comment created time in 3 days

issue commentnearprotocol/near-explorer

Show Chunk information in Block page

CC @jakestutzman @corwinharrell for design for this.

ilblackdragon

comment created time in 3 days

issue commentnearprotocol/near-explorer

Top level economic stats

For general stats:

  • Total supply -> block.header.total_supply
  • Epoch reward -> (0.05 / (total_blocks_in_the_year / epoch_length)) * block.header.total_supply
  • Fees burnt -> block.header.rent_paid + block.header.gas_price * sum(for each chunk -> chunk.header.gas_used)
  • Gas spent / limit -> sum(for each chunk -> chunk.header.gas_used) / sum(for each chunk -> chunk.header.gas_limit)
  • Gas price -> block.header.gas_price
  • State size -> ??? @bowenwang1996 rent_paid / rent_cost?
ilblackdragon

comment created time in 3 days

issue openednearprotocol/docs

[DOC] Document usage of EVM

Currently documentation are examples in the https://nearprotocol.com/blog/running-ethereum-applications-on-near/ - we should have it here as well.

created time in 3 days

Pull request review commentnearprotocol/nearcore

use blocks/chunks produced median

 mod tests {                 .iter()                 .map(|x| (x.0.account_id.clone(), x.1))                 .collect::<Vec<_>>(),-            vec![("test2".to_string(), false), ("test4".to_string(), false)]+            vec![+                // TODO Bowen do they should be sorted by account_id?

TODOs should have issue attached to them. Also @bowenwang1996 for actual question.

Kouprin

comment created time in 3 days

issue openednearprotocol/near-explorer

Top level economic stats

We need many different economics stats, but here are the most important:

  • Total supply over time
  • Epoch reward for given epoch
  • Amount of fees burnt over time (#186)
  • Gas spent / gas limit over time (also across shards?)
  • Gas price over time
  • State size over time (also across shards?)

Supply breakdown:

  • Liquid tokens
  • Staked tokens
  • Locked tokens
  • ? unclaimed / etc tokens

Note that locked tokens can be staked. Unclaimed tokens from airdrops, etc.

Validator stats:

  • Number of validator seats
  • Validator seat threshold
  • Amount of staked / delegated tokens, ratio to total supply
  • Reward %, inflation %
  • Number of blocks until next epoch

created time in 4 days

issue openednearprotocol/near-explorer

Use tooltip for full precision of balances

Anywhere where we show NEAR balance, we should add tooltip or click? to show full precision number.

This is important when we are charging for gas 1e-5 or less it's actually not visible at all. It's important for developers to be able to glean in the full information.

created time in 4 days

issue openednearprotocol/near-explorer

Show Chunk information in Block page

Currently there is absolutely no information about chunks / shards.

We should show summary of chunk information in the Block page: group tx by chunk in the details and show for each chunk total tx count, gas spent, gas limit, rent paid and other meta data available in ChunkHeader.

created time in 4 days

issue openednearprotocol/near-explorer

Display fees burnt

There are two components of fees that get burnt in every block:

  • State rent: total amount of bytes across all shards * state rent per byte price
  • Tx fees: total amount of gas spent across all shards * gas price in the block

Both of this info can be retrieved from ChunkHeader information within a Block.

We should show:

  • For every block how much burnt fees are there of each type
  • Total fees burnt in the some overall economic stats

created time in 4 days

issue openednearprotocol/nearlib

ReceiverMismatch error description is confusing and non actionable

Generally errors should be actionable (e.g. what do I change to make error go away).

Specifically it took me 10min to figure out ReceiverMismatch error by tracing into nearcore: "Transaction receiver_id {{tx_receiver}} doesn't match the access key receiver_id {{ak_receiver}}"

Something more actionable would be: "Transaction is sent to receiver_id={{tx_receiver}}, but is signed with function call access key that restricted to only use with receiver_id={{ak_receiver}}. Either switch to use FullAccessKey or change receiver_id in your transaction."

created time in 4 days

issue openednearprotocol/docs

[DOC] Tutorial for storing simple key/value

Is your feature request related to a problem? Please describe. There should be an easy example how to store from key/values from the nearlib.

Describe the solution you'd like Existing contract already deployed that can store key/values. And 3-4 line in JS to how to use this from client.

Additional context Ideally should be similar to firebase's example and provide a quick on ramp for developers to have "first app using crypto".

created time in 4 days

IssuesEvent

issue commentnearprotocol/nearcore

Rent paid is 0 in the block / chunk header

We should include pay rent based on the current state not on touched accounts.

The actual accounts don't need to be touched for us to charge the exact amount and put that into the block.

If we not really using this (to actually burn the right amounts of tokens), we should also drop this field.

ilblackdragon

comment created time in 4 days

Pull request review commentnearprotocol/nearcore

Expose genesis config and records via RPC

 fn test_health_ok() {     }); } +/// Retrieve genesis config via JSON RPC.+/// WARNING: Be mindful about changing genesis structure as it is part of the public protocol!+#[test]+fn test_genesis_config() {

@evgenykuzyakov the question is not clear here.

I agree that we should have RPC output checking, but also not convinced in belongs in the unittests. I was thinking nearlib is a better place for these tests.

I don't understand how splitting structures would help - RPC needs to return all of the data one way or another and we need to test that is consistently returned and if you change it - it should be painful (because the real pain is actually upgrading 100 other dependencies by us and community).

frol

comment created time in 4 days

push eventnearprotocol/awesome-near

Kendall Cole

commit sha 2c190ba6c06171bd76c3b7b1df994f4804f5ebcc

Add examples (#1)

view details

push time in 7 days

PR merged nearprotocol/awesome-near

Add examples
+11 -0

0 comment

1 changed file

kcole16

pr closed time in 7 days

push eventnearprotocol/near-bindgen

Illia Polosukhin

commit sha 478d039419d85305a8cb5b5f52778a22346b54f5

Switch fun tokens to use strings

view details

Illia Polosukhin

commit sha 4aca1e85601d94ae2d854c951d2eda7c5b8123f9

Fix tests

view details

Illia Polosukhin

commit sha af78d96b3013d64df160f747e6febbf67b3e018d

Merge remote-tracking branch 'origin/master' into deploy-fun-token

view details

Illia Polosukhin

commit sha f886a39b870bbcc25ea251748cb294515cb634bb

Merge pull request #78 from nearprotocol/deploy-fun-token Switch fun tokens to use strings for u128 arguments

view details

push time in 7 days

PR merged nearprotocol/near-bindgen

Switch fun tokens to use strings for u128 arguments

Currently Fun Token is not usable in the actual TestNet, because uses u128 arguments which are not parsable.

+108 -104

0 comment

2 changed files

ilblackdragon

pr closed time in 7 days

create barnchnearprotocol/awesome-near

branch : master

created branch time in 7 days

created repositorynearprotocol/awesome-near

Curated list of resources: examples, libraries, projects

created time in 7 days

push eventnearprotocol/near-bindgen

Evgeny Kuzyakov

commit sha 28f7f564953ffd708cd001e558141b41d59db55c

Add panic hook (#73) * Add panic hook * Add panic hook to initializer implementation

view details

Illia Polosukhin

commit sha 4ed1607a2f26609cbe8029919a43383f2f02c5c3

Bump bindgen to use vm-logic from staging, because we poisoned crates with 0.4.4 which is nowhere to be found

view details

nearmax

commit sha 043604cc3761cff7c7356dda01056cca3676921e

Fix master after 0.4.4 release

view details

Anton Bukov

commit sha 1f4f5eb1af55cf2a9b541530c5a2f18fffe21765

Merge pull request #83 from nearprotocol/fix_master2 Fix master after 0.4.4 release

view details

Anton Bukov

commit sha 03d5b5906d61b5b75f4db4eabb95bc897a5c0687

Expose keccak256 and keccak512 native support (#69)

view details

Maksym Zavershynskyi

commit sha 49e98e3af4391109e8ab26cb9ca2c5ee7fa5102d

Adding CoC (#84)

view details

Anton Bukov

commit sha 1329c5c7ec87d162bd4c5e058b0cd764ef9d4b4a

Bumping 0.3.11 version (#85)

view details

Maksym Zavershynskyi

commit sha 540bc170db978c47ca1b915f737ab1ebae4cb50e

0.4.0 Allow specifying serialization per input, output, callbacks (#74) * WIP switching to Borsh * Compiles * Fix regular tests * Fix callback tests * Extract AttrSignatureInfo * Refactor code generator structure * Refactor ExtContract code and fix tests * Little bit more of refactoring * Fix examples * Update documentation * Remove myproject * Remove wasm and wat from stats

view details

Maksym Zavershynskyi

commit sha 044bf9110051e14a2dfbaf3bc22750e555e63be4

Fixes #88 (#89) * Fixes #88 * Fix test * Bump to 0.4.1

view details

Maksym Zavershynskyi

commit sha 8222c45db14a69d75b32aede0d1b9f1a8c79a1d5

Update README.md

view details

Bowen Wang

commit sha c9476c9ab5663d00ca7b5d438f90003baff230ba

fix: Log str instead of bytes (#53) * Log str instead of bytes * update examples * Fix compilation error * Fix examples Fixes #52

view details

Illia Polosukhin

commit sha af78d96b3013d64df160f747e6febbf67b3e018d

Merge remote-tracking branch 'origin/master' into deploy-fun-token

view details

push time in 7 days

push eventnearprotocol/near-bindgen

Illia Polosukhin

commit sha 4aca1e85601d94ae2d854c951d2eda7c5b8123f9

Fix tests

view details

push time in 7 days

MemberEvent

issue openednearprotocol/nearcore

Rent paid is 0 in the block / chunk header

We have rent_paid field in block and chunk headers but it's always 0:

http post https://staging-rpc.nearprotocol.com jsonrpc=2.0 method=chunk id=123 params:='["9hUCw49PQyUcPiD7QTj3hK8VrC7S8j42enf5M6qDdmAD"]'
HTTP/1.1 200 OK
Alt-Svc: clear
Via: 1.1 google
content-length: 833
content-type: application/json
date: Fri, 14 Feb 2020 08:00:37 GMT

{
    "id": "123",
    "jsonrpc": "2.0",
    "result": {
        "author": "far",
        "header": {
            ...
            "rent_paid": "0", <----------------------------------
            ...
        },
        "receipts": [],
        "transactions": []
    }
}

created time in 9 days

pull request commentnearprotocol/near-evm

Adding Truffle + ERC20 example

Closing as this is outdated now.

ilblackdragon

comment created time in 9 days

create barnchnearprotocol/near-evm

branch : balance

created branch time in 9 days

issue commentnearprotocol/NEPs

NEAR Spec and standards

Here is my reasoning:

  • The more places we have, harder it is to keep track of things. I for example can not keep up already with all the different sources of truth for different parts of the ecosystem.
  • Standards are actually become part of the protocol. ERC-20 really is part of Ethereum, even if it's not enforced by code in geth, it's still something that lots of other tooling relies on, exchanges and wallets operate and etc. For example Wallet API which doesn't have anything to do with client, is still part of the protocol how apps and wallets will be interacting.
  • I don't see clear different between consensus changes and RPC changes. Obviously they touch different pieces of code, but both require coordination across many different teams to address the changes. In case of consensus it will be coordination between client teams, in case of RPC it will be all the tooling. Changes to economics may affect everyone across the board and will require massive coordination.
  • @fckt we should have different folders in the spec for different parts of the protocol / standards / etc.
  • It's unclear why development details of nearcore are not in the nearcore repo. Same for discussion about optimizations in the nearcore specifically. Vs if we are discussing optimization of the state trie which actually changes protocol - it should be change to the spec.
  • Processes should be documented in the spec, especially if they are involving the coordination between different clients / parties. For example Upgradability after discussion should be change to the spec providing both what do we need to change in the code and process that participants will need to be aware of.

@nearmax I didn't understand your "linear"/"sublinear". I want to have "releases" for spec, in similar way we are planning to have releases for clients. Ideally have trains with monthly release, which also includes some tests release. This way we can say which version clients target of the spec.

ilblackdragon

comment created time in 9 days

issue closednearprotocol/nearcore

Weekly Digest (31 January, 2020 - 7 February, 2020)

Here's the Weekly Digest for nearprotocol/nearcore:


ISSUES

Last week 55 issues were created. Of these, 21 issues have been closed and 34 issues are still open.

OPEN ISSUES

:green_heart: #2107 Use OsRng instead of OsRng::default() or StdRng. There is no benefit …, by abacabadabacaba :green_heart: #2106 Change VRF function names: check -> is_valid, check_vrf -> is_vrf_valid., by abacabadabacaba :green_heart: #2105 Investigate testnet slow restart, by bowenwang1996 :green_heart: #2104 Add some utilities for later crypto use., by abacabadabacaba :green_heart: #2103 Add support for a test storage that uses a real trie, by willemneal :green_heart: #2101 Sort near-crypto dependencies and remove unused dependency on criterion., by abacabadabacaba :green_heart: #2100 Check sum and improved bs58 encoding, by ilblackdragon :green_heart: #2099 archive flag for turning off GC, by Kouprin :green_heart: #2098 Fail to sync state on testnet, by bowenwang1996 :green_heart: #2097 Implemented functions to convert Ed25519 keys to Ristretto ones., by abacabadabacaba :green_heart: #2094 Add a flag for turning off GC, by Kouprin :green_heart: #2093 Epoch frontier state sync, by Kouprin :green_heart: #2092 Publish new nearcore 0.4.4 image to DockerHub, by k06a :green_heart: #2089 Update wasmer to 13.1, by fckt :green_heart: #2088 Expensive tests fail because of too many open files. , by bowenwang1996 :green_heart: #2086 Change state dump to binary format, by bowenwang1996 :green_heart: #2084 Trie cleaning, by Kouprin :green_heart: #2083 Remote pytest readme, by ailisp :green_heart: #2080 Move CI to github action, by bowenwang1996 :green_heart: #2078 Refactored *Configs into separate crates, by frol :green_heart: #2076 Contract state should provide proofs from state root, by ilblackdragon :green_heart: #2074 Define AccountId to hold a contract of being valid, by frol :green_heart: #2070 Fix performance of state dump process, by ilblackdragon :green_heart: #2069 Have a script on how to start/restart testnet and practice it multiple times, by nearmax :green_heart: #2068 epoch frontier state sync WIP, by Kouprin :green_heart: #2063 EthDenver Technical Preparation, by nearmax :green_heart: #2062 Expose epoch information to the smart contracts, by ilblackdragon :green_heart: #2060 Continuous State Sync, by Kouprin :green_heart: #2057 Replace actix-web for RPC, by nearmax :green_heart: #2056 Align economic incentives for partial seat pricing, by ilblackdragon :green_heart: #2055 Calling function prints unexpected log in nearcore binary, by ilblackdragon :green_heart: #2053 [Protocol Changing] Expose epoch id to contracts, by ilblackdragon :green_heart: #2052 get_key_value_changes can panic when processing a query, by bowenwang1996 :green_heart: #2050 State without trie, by mikhailOK

CLOSED ISSUES

:heart: #2102 Move some traits from near_crypto::vrf to a separate module., by abacabadabacaba :heart: #2096 [Wasm] Add test for out-of-gas in the start function, by fckt :heart: #2095 nightly runner doesn't run since Jan 12, by ailisp :heart: #2090 Investigate how to run docker without internet, by nearmax :heart: #2087 pytests are broken, by bowenwang1996 :heart: #2085 Move sysinfo fix from staging, by ailisp :heart: #2082 test issue, by nearmax :heart: #2081 master tests are broken, by nearmax :heart: #2079 Enable floats but prohibit some CPU architectures, by k06a :heart: #2077 Re-introducing minimum block production time, by SkidanovAlex :heart: #2075 Ref #2067: querying contract state, by ilblackdragon :heart: #2073 Refactored *Configs into separate crates, by frol :heart: #2072 Introduce keccak256 and keccak512 native support, by k06a :heart: #2071 Querying contract state fails, by ilblackdragon :heart: #2067 Querying contract state via RPC does not give any result, by frol :heart: #2066 Fix staking action in Testnet (master branch), by nearmax :heart: #2065 Allow floats in contracts on testnet, by nearmax :heart: #2064 Add keccak to host functions, by nearmax :heart: #2059 Update rand & dalek in crypto, by ilblackdragon :heart: #2058 Fix staking action in near-vm-logic, by ilblackdragon :heart: #2054 Return current account balance via RPC, by ilblackdragon

LIKED ISSUE

:+1: #2080 Move CI to github action, by bowenwang1996 It received :+1: x1, :smile: x0, :tada: x0 and :heart: x0.

NOISY ISSUE

:speaker: #2081 master tests are broken, by nearmax It received 9 comments.


PULL REQUESTS

Last week, 37 pull requests were created, updated or merged.

UPDATED PULL REQUEST

Last week, 22 pull requests were updated. :yellow_heart: #2107 Use OsRng instead of OsRng::default() or StdRng. There is no benefit …, by abacabadabacaba :yellow_heart: #2106 Change VRF function names: check -> is_valid, check_vrf -> is_vrf_valid., by abacabadabacaba :yellow_heart: #2104 Add some utilities for later crypto use., by abacabadabacaba :yellow_heart: #2103 Add support for a test storage that uses a real trie, by willemneal :yellow_heart: #2101 Sort near-crypto dependencies and remove unused dependency on criterion., by abacabadabacaba :yellow_heart: #2099 archive flag for turning off GC, by Kouprin :yellow_heart: #2097 Implemented functions to convert Ed25519 keys to Ristretto ones., by abacabadabacaba :yellow_heart: #2093 Epoch frontier state sync, by Kouprin :yellow_heart: #2089 Update wasmer to 13.1, by fckt :yellow_heart: #2086 Change state dump to binary format, by bowenwang1996 :yellow_heart: #2084 Trie cleaning, by Kouprin :yellow_heart: #2083 Remote pytest readme, by ailisp :yellow_heart: #2078 Refactored *Configs into separate crates, by frol :yellow_heart: #2068 epoch frontier state sync WIP, by Kouprin :yellow_heart: #2053 [Protocol Changing] Expose epoch id to contracts, by ilblackdragon :yellow_heart: #2050 State without trie, by mikhailOK :yellow_heart: #2049 Fix test bug, by mikhailOK :yellow_heart: #2031 adversary, by Kouprin :yellow_heart: #2004 Cross shard contract call, by ailisp :yellow_heart: #2003 Honeypot for catching lazy block producers, by bowenwang1996 :yellow_heart: #2002 Disable codecov status check, by ailisp :yellow_heart: #1876 Block production summary in 100 node, by ailisp

MERGED PULL REQUEST

Last week, 15 pull requests were merged. :purple_heart: #2102 Move some traits from near_crypto::vrf to a separate module., by abacabadabacaba :purple_heart: #2085 Move sysinfo fix from staging, by ailisp :purple_heart: #2079 Enable floats but prohibit some CPU architectures, by k06a :purple_heart: #2077 Re-introducing minimum block production time, by SkidanovAlex :purple_heart: #2075 Ref #2067: querying contract state, by ilblackdragon :purple_heart: #2072 Introduce keccak256 and keccak512 native support, by k06a :purple_heart: #2059 Update rand & dalek in crypto, by ilblackdragon :purple_heart: #2058 Fix staking action in near-vm-logic, by ilblackdragon :purple_heart: #2045 Add keccak native support, by k06a :purple_heart: #2038 RPC query account information and access keys by a specific block id, by frol :purple_heart: #2037 Remove warnings, by mfornet :purple_heart: #2032 Shuffle incoming receipts for each shard, by bowenwang1996 :purple_heart: #2026 Refactoring usage of Signer to ValidatorSigner, by ilblackdragon :purple_heart: #1999 GC old blocks / chunks, by Kouprin :purple_heart: #1932 Create code-of-conduct.md, by AnaisUrlichs


CONTRIBUTORS

Last week there were 4 contributors. :bust_in_silhouette: ilblackdragon :bust_in_silhouette: AnaisUrlichs :bust_in_silhouette: k06a :bust_in_silhouette: ailisp


STARGAZERS

Last week there were 4 stagazers. :star: HeyITGuyFixIt :star: Sija :star: smac89 :star: melekes You all are the stars! :star2:


RELEASES

Last week there were no releases.


That's all for last week, please <kbd>:eyes: Watch</kbd> and <kbd>:star: Star</kbd> the repository nearprotocol/nearcore to receive next weekly updates. :smiley:

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. :calendar:

closed time in 9 days

weekly-digest[bot]

issue closednearprotocol/nearcore

Weekly Digest (7 February, 2020 - 14 February, 2020)

Here's the Weekly Digest for nearprotocol/nearcore:


ISSUES

Last week 29 issues were created. Of these, 6 issues have been closed and 23 issues are still open.

OPEN ISSUES

:green_heart: #2137 collect_block_approval uses head, which is wrong, by SkidanovAlex :green_heart: #2136 feat(runtime): Add Helper Methods and Types for Mock VM, by willemneal :green_heart: #2135 Document nearcore Release Process, by damons :green_heart: #2134 script to simulate process of #2132 and #2133 in a separate node, by ailisp :green_heart: #2133 Automate reset testnet process, by ailisp :green_heart: #2132 Script to dump, migrate and upload state in test maintenance, by ailisp :green_heart: #2131 Release docker build, by ailisp :green_heart: #2130 Only kickout block / chunk producers if they are lower than threshold compared to the median, by SkidanovAlex :green_heart: #2129 Changes RPC should allow querying multiple accounts at once, by nearmax :green_heart: #2128 Allow querying accounts touched within the block, by nearmax :green_heart: #2127 feat: allow rpc to specify finality in query, by bowenwang1996 :green_heart: #2126 State dump split, by mikhailOK :green_heart: #2121 Randomness DKG would stall epoch switch if one shard is completely offline, by SkidanovAlex :green_heart: #2119 Reset testnet, by bowenwang1996 :green_heart: #2118 Dump only the latest state., by bowenwang1996 :green_heart: #2117 Distribute reward based on validator stake, by bowenwang1996 :green_heart: #2116 Negate the Need to Manually Lookup Latest-Stable-Release Tag, by lazaridiscom :green_heart: #2115 [Discussion] Refactoring of how to run a node, by Kouprin :green_heart: #2114 Nightly log on gcloud and cross reference test <> run, by ailisp :green_heart: #2113 Document timestamp, by bowenwang1996 :green_heart: #2111 block_timestamp doesn't document units, by vgrichina :green_heart: #2110 When reconstructing a chunk, receipts and encrypted secret shares are not stored into the cache entry, by SkidanovAlex :green_heart: #2109 Expose genesis config and records via RPC, by frol

CLOSED ISSUES

:heart: #2125 Enable overflow-checks for release, by evgenykuzyakov :heart: #2124 Add storage_paid_at check during apply_rent, by evgenykuzyakov :heart: #2123 apply_rent doesn't check for storage_paid_at value, by evgenykuzyakov :heart: #2122 Use BufWriter for state dump, by mikhailOK :heart: #2120 Add json state dump for debugging, by bowenwang1996 :heart: #2112 Broadcast block immediately after receiving it, by bowenwang1996

NOISY ISSUE

:speaker: #2136 feat(runtime): Add Helper Methods and Types for Mock VM, by willemneal It received 3 comments.


PULL REQUESTS

Last week, 26 pull requests were created, updated or merged.

UPDATED PULL REQUEST

Last week, 16 pull requests were updated. :yellow_heart: #2136 feat(runtime): Add Helper Methods and Types for Mock VM, by willemneal :yellow_heart: #2131 Release docker build, by ailisp :yellow_heart: #2127 feat: allow rpc to specify finality in query, by bowenwang1996 :yellow_heart: #2126 State dump split, by mikhailOK :yellow_heart: #2119 Reset testnet, by bowenwang1996 :yellow_heart: #2117 Distribute reward based on validator stake, by bowenwang1996 :yellow_heart: #2114 Nightly log on gcloud and cross reference test <> run, by ailisp :yellow_heart: #2113 Document timestamp, by bowenwang1996 :yellow_heart: #2109 Expose genesis config and records via RPC, by frol :yellow_heart: #2107 Use OsRng instead of OsRng::default() or StdRng. There is no benefit …, by abacabadabacaba :yellow_heart: #2106 Change VRF function names: check -> is_valid, check_vrf -> is_vrf_valid., by abacabadabacaba :yellow_heart: #2104 Add some utilities for later crypto use., by abacabadabacaba :yellow_heart: #2101 Sort near-crypto dependencies and remove unused dependency on criterion., by abacabadabacaba :yellow_heart: #2050 State without trie, by mikhailOK :yellow_heart: #2003 Honeypot for catching lazy block producers, by bowenwang1996 :yellow_heart: #1876 Block production summary in 100 node, by ailisp

MERGED PULL REQUEST

Last week, 10 pull requests were merged. :purple_heart: #2125 Enable overflow-checks for release, by evgenykuzyakov :purple_heart: #2124 Add storage_paid_at check during apply_rent, by evgenykuzyakov :purple_heart: #2120 Add json state dump for debugging, by bowenwang1996 :purple_heart: #2112 Broadcast block immediately after receiving it, by bowenwang1996 :purple_heart: #2099 archive flag for turning off GC, by Kouprin :purple_heart: #2093 Epoch frontier state sync, by Kouprin :purple_heart: #2089 Update wasmer to 13.1, by fckt :purple_heart: #2086 Change state dump to binary format, by bowenwang1996 :purple_heart: #2078 Refactored *Configs into separate crates, by frol :purple_heart: #2031 adversary, by Kouprin


CONTRIBUTORS

Last week there was 1 contributor. :bust_in_silhouette: bowenwang1996


STARGAZERS

Last week there were 11 stagazers. :star: tbrlpld :star: motxx :star: skv-headless :star: duncandean :star: lazaridiscom :star: FractalHQ :star: oparkins :star: lispc :star: NeoBeum :star: iximiuz :star: icerove You all are the stars! :star2:


RELEASES

Last week there were no releases.


That's all for last week, please <kbd>:eyes: Watch</kbd> and <kbd>:star: Star</kbd> the repository nearprotocol/nearcore to receive next weekly updates. :smiley:

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. :calendar:

closed time in 9 days

weekly-digest[bot]

issue closednearprotocol/nearcore

Weekly Digest (10 January, 2020 - 17 January, 2020)

Here's the Weekly Digest for nearprotocol/nearcore:


ISSUES

Last week 34 issues were created. Of these, 18 issues have been closed and 16 issues are still open.

OPEN ISSUES

:green_heart: #1971 Don't skip chunks if the chunk was received before the previous block, by SkidanovAlex :green_heart: #1969 setup_mock_all_validators should be redone, by Kouprin :green_heart: #1967 Remote transaction signing, by bowenwang1996 :green_heart: #1966 Transaction validity period should be larger, by bowenwang1996 :green_heart: #1964 Fix logs when view call panicks, by bowenwang1996 :green_heart: #1962 Restaking service + validator RPC improvement, by ilblackdragon :green_heart: #1961 Add more safe math to the Runtime , by evgenykuzyakov :green_heart: #1959 README includes incorrect link to create-near-app, by amgando :green_heart: #1953 Logs aren't captured if view calls panics, by vgrichina :green_heart: #1951 Progressive Updates for Validators, by potatodepaulo :green_heart: #1949 Change Receipt priority, by evgenykuzyakov :green_heart: #1945 seals implementation and testing chunks grieving, by Kouprin :green_heart: #1943 Merge master into staging, by bowenwang1996 :green_heart: #1942 Initial near run use too many open files, by ailisp :green_heart: #1940 Allow non-x86 platforms through NaN canonicalization, by nearmax :green_heart: #1938 Network crashed after Failed sending broadcast message:Mailbox has closed, by ailisp

CLOSED ISSUES

:heart: #1970 Fix setup_mock_all_validators, by bowenwang1996 :heart: #1968 Panic on running from staging branch, by k06a :heart: #1965 Allow coverage upload fails, by ailisp :heart: #1963 Remove dead code warnings from test, by mfornet :heart: #1960 update link to docs, by amgando :heart: #1958 Check for invalid shard id, by bowenwang1996 :heart: #1957 challenges_root, by Kouprin :heart: #1956 tests_all_chunks_accepted, by Kouprin :heart: #1955 Move network requests to ViewClient, by bowenwang1996 :heart: #1954 Don't crash on "Connection reset by peer", by mikhailOK :heart: #1952 Downgrade sysinfo to avoid too many open files bug, by ailisp :heart: #1950 Change the pool order to be randomized and continue from the last used key, by evgenykuzyakov :heart: #1948 Nearcore crashes on chunk RPC call requesting a shard id that does not exist, by frol :heart: #1947 Pytest util to compile rust snippet, by ailisp :heart: #1946 Fix u32 overflow during contract preparation, by nearmax :heart: #1944 Pytest deploy smart contract and call function, by ailisp :heart: #1941 Enable floats but prohibit some CPU architectures, by nearmax :heart: #1939 Error running localness node, by k06a

LIKED ISSUE

:+1: #1940 Allow non-x86 platforms through NaN canonicalization, by nearmax It received :+1: x1, :smile: x0, :tada: x0 and :heart: x0.

NOISY ISSUE

:speaker: #1938 Network crashed after Failed sending broadcast message:Mailbox has closed, by ailisp It received 4 comments.


PULL REQUESTS

Last week, 23 pull requests were created, updated or merged.

UPDATED PULL REQUEST

Last week, 6 pull requests were updated. :yellow_heart: #1962 Restaking service + validator RPC improvement, by ilblackdragon :yellow_heart: #1945 seals implementation and testing chunks grieving, by Kouprin :yellow_heart: #1943 Merge master into staging, by bowenwang1996 :yellow_heart: #1934 Fix TransactionOutcome Borsh deserialization by light client, by k06a :yellow_heart: #1915 Turn on deterministic wasmer runtime, by ailisp :yellow_heart: #1913 Runtime limiters, by evgenykuzyakov

MERGED PULL REQUEST

Last week, 17 pull requests were merged. :purple_heart: #1965 Allow coverage upload fails, by ailisp :purple_heart: #1963 Remove dead code warnings from test, by mfornet :purple_heart: #1960 update link to docs, by amgando :purple_heart: #1958 Check for invalid shard id, by bowenwang1996 :purple_heart: #1957 challenges_root, by Kouprin :purple_heart: #1955 Move network requests to ViewClient, by bowenwang1996 :purple_heart: #1954 Don't crash on "Connection reset by peer", by mikhailOK :purple_heart: #1952 Downgrade sysinfo to avoid too many open files bug, by ailisp :purple_heart: #1947 Pytest util to compile rust snippet, by ailisp :purple_heart: #1946 Fix u32 overflow during contract preparation, by nearmax :purple_heart: #1944 Pytest deploy smart contract and call function, by ailisp :purple_heart: #1941 Enable floats but prohibit some CPU architectures, by nearmax :purple_heart: #1933 limiting number of blocks / chunks per height + adversary tests, by Kouprin :purple_heart: #1930 Release 0.4.12, by bowenwang1996 :purple_heart: #1928 Diagnostics, by mfornet :purple_heart: #1897 Check max peer is not passed., by mfornet :purple_heart: #1751 Restructured Telemetry data and added agent (near-rs) name and version, by frol


CONTRIBUTORS

Last week there were 2 contributors. :bust_in_silhouette: amgando :bust_in_silhouette: bowenwang1996


STARGAZERS

Last week there were 7 stagazers. :star: lzehrung :star: MrCamelV :star: aguedob :star: arduino2018 :star: ChrisIhler :star: d0iasm :star: flada-auxv You all are the stars! :star2:


RELEASES

Last week there were no releases.


That's all for last week, please <kbd>:eyes: Watch</kbd> and <kbd>:star: Star</kbd> the repository nearprotocol/nearcore to receive next weekly updates. :smiley:

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. :calendar:

closed time in 9 days

weekly-digest[bot]

issue closednearprotocol/nearcore

Weekly Digest (24 January, 2020 - 31 January, 2020)

Here's the Weekly Digest for nearprotocol/nearcore:


ISSUES

Last week 31 issues were created. Of these, 6 issues have been closed and 25 issues are still open.

OPEN ISSUES

:green_heart: #2049 Fix test bug, by mikhailOK :green_heart: #2048 Failed to query account changes, by nearmax :green_heart: #2047 Retrieve all events based on the block hash, by nearmax :green_heart: #2046 Add Contribution Guidelines to Github: CONTRIBUTING.md, by damons :green_heart: #2045 Add keccak native support, by k06a :green_heart: #2044 Running a Local Node Documentation Fails, by damons :green_heart: #2043 Project Status Section of README.md is Misleading, by damons :green_heart: #2042 Update README.md To Include NEAR Mission, by damons :green_heart: #2041 README.md Badges Are Broken or Incorrect, by damons :green_heart: #2040 Routed transaction can be silently dropped , by bowenwang1996 :green_heart: #2039 Invalid transactions dropped from the pool don't have the error, by evgenykuzyakov :green_heart: #2038 RPC query account information and access keys by a specific block id, by frol :green_heart: #2037 Remove warnings, by mfornet :green_heart: #2036 expose balance-change events in a block, by bowenwang1996 :green_heart: #2035 Move unittest-specific code into separate modules, by abacabadabacaba :green_heart: #2034 Update changes RPC to operate with base64-encoded data instead of arrays of bytes, by frol :green_heart: #2032 Shuffle incoming receipts for each shard, by bowenwang1996 :green_heart: #2031 adversary, by Kouprin :green_heart: #2030 Add local flag, by mfornet :green_heart: #2028 Are some shards more equal than others?, by evgenykuzyakov :green_heart: #2027 Script to remove adversarial code., by mfornet :green_heart: #2026 Refactoring usage of Signer to ValidatorSigner, by ilblackdragon :green_heart: #2025 Expose genesis JSON via RPC, by frol :green_heart: #2022 Optimize the retain in Doomslug::set_tip, by SkidanovAlex :green_heart: #2021 State sync should happen only on epochs frontier, by Kouprin

CLOSED ISSUES

:heart: #2033 fix seat assingment + settlement -> assignment, by Kouprin :heart: #2029 Adversary behind feature, by mfornet :heart: #2024 settlement -> assignment + fix seats chosen in proposals_to_epoch_info, by Kouprin :heart: #2023 Check account id inside tx status query, by bowenwang1996 :heart: #2020 Rebuild schema to remove the cached removed field, by evgenykuzyakov :heart: #2019 test_kickout already working, by mfornet

NOISY ISSUE

:speaker: #2029 Adversary behind feature, by mfornet It received 6 comments.


PULL REQUESTS

Last week, 21 pull requests were created, updated or merged.

UPDATED PULL REQUEST

Last week, 13 pull requests were updated. :yellow_heart: #2049 Fix test bug, by mikhailOK :yellow_heart: #2045 Add keccak native support, by k06a :yellow_heart: #2038 RPC query account information and access keys by a specific block id, by frol :yellow_heart: #2037 Remove warnings, by mfornet :yellow_heart: #2032 Shuffle incoming receipts for each shard, by bowenwang1996 :yellow_heart: #2031 adversary, by Kouprin :yellow_heart: #2030 Add local flag, by mfornet :yellow_heart: #2003 Honeypot for catching lazy block producers, by bowenwang1996 :yellow_heart: #2002 Disable codecov status check, by ailisp :yellow_heart: #1999 GC old blocks / chunks, by Kouprin :yellow_heart: #1932 Create code-of-conduct.md, by AnaisUrlichs :yellow_heart: #1890 Allow rpc to query final result, by bowenwang1996 :yellow_heart: #1876 Block production summary in 100 node, by ailisp

MERGED PULL REQUEST

Last week, 8 pull requests were merged. :purple_heart: #2029 Adversary behind feature, by mfornet :purple_heart: #2023 Check account id inside tx status query, by bowenwang1996 :purple_heart: #2020 Rebuild schema to remove the cached removed field, by evgenykuzyakov :purple_heart: #2019 test_kickout already working, by mfornet :purple_heart: #2013 Safe math vm logic, by evgenykuzyakov :purple_heart: #1991 Doomslug, by SkidanovAlex :purple_heart: #1988 Test connection reset by peer, by mfornet :purple_heart: #1979 Empty state response, by Kouprin


CONTRIBUTORS

Last week there were no contributors.


STARGAZERS

Last week there were 4 stagazers. :star: awulkan :star: codetheweb :star: felixmacht :star: ujuc You all are the stars! :star2:


RELEASES

Last week there were no releases.


That's all for last week, please <kbd>:eyes: Watch</kbd> and <kbd>:star: Star</kbd> the repository nearprotocol/nearcore to receive next weekly updates. :smiley:

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. :calendar:

closed time in 9 days

weekly-digest[bot]

issue closednearprotocol/nearcore

Weekly Digest (17 January, 2020 - 24 January, 2020)

Here's the Weekly Digest for nearprotocol/nearcore:


ISSUES

Last week 45 issues were created. Of these, 17 issues have been closed and 28 issues are still open.

OPEN ISSUES

:green_heart: #2015 RPC query account information and access keys by a specific block id, by frol :green_heart: #2013 Safe math vm logic, by evgenykuzyakov :green_heart: #2012 ActionErrorKind doesn't provide index for ActionError, by evgenykuzyakov :green_heart: #2011 serde_with.rs in near-vm-logic can panic, by evgenykuzyakov :green_heart: #2010 Wrap StorageError in RuntimeExt into ExternalError, by evgenykuzyakov :green_heart: #2009 Fix FunctionCallError(WasmTrap("unknown")), by nearmax :green_heart: #2007 NearConfig in RPC, by nearmax :green_heart: #2006 Implement Safes, by evgenykuzyakov :green_heart: #2004 Cross shard contract call, by ailisp :green_heart: #2003 Honeypot for catching lazy block producers, by bowenwang1996 :green_heart: #2002 Disable codecov status check, by ailisp :green_heart: #1999 GC old blocks / chunks, by Kouprin :green_heart: #1998 Add "tail" and GC old blocks / chunks, by SkidanovAlex :green_heart: #1996 Events, by nearmax :green_heart: #1995 Runtime Config Cleanup, by nearmax :green_heart: #1994 Upgradability, by nearmax :green_heart: #1993 Runtime Safety, by nearmax :green_heart: #1992 Lockup and Vesting Contracts for Token Holders, by nearmax :green_heart: #1991 Doomslug, by SkidanovAlex :green_heart: #1990 Token Management Contracts, by nearmax :green_heart: #1989 Limiters for VMLogic and Runtime crates, by nearmax :green_heart: #1988 Test connection reset by peer, by mfornet :green_heart: #1987 NaN canonization, by nearmax :green_heart: #1982 Do not delay block production if only missing chunks for shards for which chunks were included in the previous block, by SkidanovAlex :green_heart: #1981 Node should recover from running out of disk space, by bowenwang1996 :green_heart: #1979 Empty state response, by Kouprin :green_heart: #1974 RPC: add actual_amount into account/ rpc call, by fckt :green_heart: #1972 [Epic] Tofu -- Rust to other languages mapping tool, by nearmax

CLOSED ISSUES

:heart: #2017 Add block hash to query result, by bowenwang1996 :heart: #2016 Merge master into staging, by bowenwang1996 :heart: #2014 Assigning RPC ownership to middleware, by nearmax :heart: #2008 RPC batching, by nearmax :heart: #2005 Cleanup lint warning in runtime, by evgenykuzyakov :heart: #2001 Fix RpcUser, by mikhailOK :heart: #2000 get 2000, by Kouprin :heart: #1997 Show fail output even with more than 5 test failed, by ailisp :heart: #1986 Upgrade sysinfo as too many open files is fixed, by ailisp :heart: #1985 Fix pytest, by bowenwang1996 :heart: #1984 Reset Testnet state, by bowenwang1996 :heart: #1983 Release v0.4.13, by bowenwang1996 :heart: #1980 fixing near_network::test_utils::wait_or_panic, by Kouprin :heart: #1978 Refactor Promise in vm-logic. Remove inner type, by evgenykuzyakov :heart: #1977 Added a README for nightly, by frol :heart: #1975 store partial encoded chunks, by Kouprin :heart: #1973 Node hangs on smart contract non-view call, by k06a

LIKED ISSUE

:+1: #2009 Fix FunctionCallError(WasmTrap("unknown")), by nearmax It received :+1: x1, :smile: x0, :tada: x0 and :heart: x0.

NOISY ISSUE

:speaker: #1972 [Epic] Tofu -- Rust to other languages mapping tool, by nearmax It received 13 comments.


PULL REQUESTS

Last week, 37 pull requests were created, updated or merged.

UPDATED PULL REQUEST

Last week, 12 pull requests were updated. :yellow_heart: #2004 Cross shard contract call, by ailisp :yellow_heart: #2003 Honeypot for catching lazy block producers, by bowenwang1996 :yellow_heart: #2002 Disable codecov status check, by ailisp :yellow_heart: #1999 GC old blocks / chunks, by Kouprin :yellow_heart: #1991 Doomslug, by SkidanovAlex :yellow_heart: #1988 Test connection reset by peer, by mfornet :yellow_heart: #1979 Empty state response, by Kouprin :yellow_heart: #1974 RPC: add actual_amount into account/ rpc call, by fckt :yellow_heart: #1932 Create code-of-conduct.md, by AnaisUrlichs :yellow_heart: #1890 Allow rpc to query final result, by bowenwang1996 :yellow_heart: #1876 Block production summary in 100 node, by ailisp :yellow_heart: #1771 using lzma to compress/decompress state_parts, by Kouprin

MERGED PULL REQUEST

Last week, 25 pull requests were merged. :purple_heart: #2017 Add block hash to query result, by bowenwang1996 :purple_heart: #2016 Merge master into staging, by bowenwang1996 :purple_heart: #2014 Assigning RPC ownership to middleware, by nearmax :purple_heart: #2005 Cleanup lint warning in runtime, by evgenykuzyakov :purple_heart: #2001 Fix RpcUser, by mikhailOK :purple_heart: #1997 Show fail output even with more than 5 test failed, by ailisp :purple_heart: #1986 Upgrade sysinfo as too many open files is fixed, by ailisp :purple_heart: #1985 Fix pytest, by bowenwang1996 :purple_heart: #1984 Reset Testnet state, by bowenwang1996 :purple_heart: #1980 fixing near_network::test_utils::wait_or_panic, by Kouprin :purple_heart: #1978 Refactor Promise in vm-logic. Remove inner type, by evgenykuzyakov :purple_heart: #1977 Added a README for nightly, by frol :purple_heart: #1975 store partial encoded chunks, by Kouprin :purple_heart: #1970 Fix setup_mock_all_validators, by bowenwang1996 :purple_heart: #1964 Fix logs when view call panicks, by bowenwang1996 :purple_heart: #1962 Restaking service + validator RPC improvement, by ilblackdragon :purple_heart: #1961 Add more safe math to the Runtime , by evgenykuzyakov :purple_heart: #1950 Change the pool order to be randomized and continue from the last used key, by evgenykuzyakov :purple_heart: #1949 Change Receipt priority, by evgenykuzyakov :purple_heart: #1945 seals implementation and testing chunks grieving, by Kouprin :purple_heart: #1935 Remove warning, by mfornet :purple_heart: #1913 Runtime limiters, by evgenykuzyakov :purple_heart: #1911 Disable-able runtime cache for params estimator, by ailisp :purple_heart: #1910 Queryable state changes, by nearmax :purple_heart: #1854 Error messages refactoring, by fckt


CONTRIBUTORS

Last week there was 1 contributor. :bust_in_silhouette: bowenwang1996


STARGAZERS

Last week there were 6 stagazers. :star: cleanappio :star: davearch :star: peizihui :star: rgrchen :star: andyjung-dev :star: Niputi You all are the stars! :star2:


RELEASES

Last week there were no releases.


That's all for last week, please <kbd>:eyes: Watch</kbd> and <kbd>:star: Star</kbd> the repository nearprotocol/nearcore to receive next weekly updates. :smiley:

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. :calendar:

closed time in 9 days

weekly-digest[bot]

push eventkcole16/near-evm-demo

James Prestwich

commit sha 868c0817d717db98830397edc29b8d21495c0bab

add from to truffle

view details

James Prestwich

commit sha ac7e1e3a0a1765e6fdcdd5bec1f2b21047cc7ee5

more truffle config

view details

Illia Polosukhin

commit sha 9ac21124347dfb23e3459b38eebbf1d14186b35f

Import nearlib from near-web3-provider

view details

Illia Polosukhin

commit sha a915049e73473379f1198725d599d01cb5a87640

Split config into Testnet and local for near. Update readme

view details

Illia Polosukhin

commit sha e0c7ef843cf21bb1031ad825ddd9c66d42eafc94

Add steps for running locally

view details

Illia Polosukhin

commit sha c5ee8e83648a2aed4ffdbe063b76c028eaa473ae

Merge pull request #2 from kcole16/initial-migration-work Initial migration work

view details

push time in 9 days

PR merged kcole16/near-evm-demo

Reviewers
Initial migration work
+9068 -1192

0 comment

4 changed files

prestwich

pr closed time in 9 days

push eventkcole16/near-evm-demo

Illia Polosukhin

commit sha e0c7ef843cf21bb1031ad825ddd9c66d42eafc94

Add steps for running locally

view details

push time in 9 days

push eventkcole16/near-evm-demo

Illia Polosukhin

commit sha a915049e73473379f1198725d599d01cb5a87640

Split config into Testnet and local for near. Update readme

view details

push time in 9 days

push eventnearprotocol/near-web3-provider

Illia Polosukhin

commit sha 194429a0a50d72f9c41b94666ea9f69a5e4a1dbc

Allow to customize the contract name for EVM

view details

push time in 9 days

push eventkcole16/near-evm-demo

Illia Polosukhin

commit sha 9ac21124347dfb23e3459b38eebbf1d14186b35f

Import nearlib from near-web3-provider

view details

push time in 10 days

push eventnearprotocol/near-web3-provider

Illia Polosukhin

commit sha 98bc5c6a3d0896ed7f90fa8443e2b84cc24c5fe9

Peer dependencies don't work very well. Exporting nearlib for now from the web3 provider.

view details

Illia Polosukhin

commit sha b2ccd092792e8d1599fdf7ab1d76d15f3556045a

Add more gas to the function calls

view details

push time in 10 days

push eventnearprotocol/near-web3-provider

Illia Polosukhin

commit sha 4bfceb905328563581ba91c6050aef4a935755dc

Move nearlib into peerDependencies to not create copy of nearlib for this package

view details

push time in 10 days

create barnchnearprotocol/near-web3-provider

branch : peer-dependency

created branch time in 10 days

push eventkcole16/near-evm-demo

Illia Polosukhin

commit sha d0197af6b5b9c1586c05d9cded2531d51671868d

Add NEAR section to README

view details

push time in 10 days

push eventkcole16/near-evm-demo

Illia Polosukhin

commit sha 2be096d7e2e993641f042e9ce5659c20014d1399

Adding NearProvider truffle config

view details

push time in 10 days

push eventnearprotocol/near-web3-provider

Illia Polosukhin

commit sha 7c61e94d09fc3c305c6bf67fb669d53872f9470d

Fix typo

view details

push time in 10 days

Pull request review commentsumma-tx/near-web3-provider

WIP: Hydrate all the things

+const utils = require('./utils');++const hydrate = {};++/**+ * Get chunks from a block+ * @param {Object} chunk NEAR chunk+ * @param {Object} block NEAR block that contains chunk+ * @param {Object} nearProvider NearProvider instance+ * @returns {Object} hydrated chunk with transactions and (sometimes) receipts+ */+hydrate.chunk = async function(chunk, block, nearProvider) {+  // NB: A chunk with no transactions is indicated by chunk.tx_root: '11111111111111111111111111111111'

yes, it is. we use 0x0 as hash for all empty sets. is there a better option?

barbaraliau

comment created time in 10 days

push eventnearprotocol/near-web3-provider

Illia Polosukhin

commit sha 4bf6db344c1fd7e910950593c89fd7074d6ecd19

Updated readme for using provider example

view details

push time in 11 days

push eventnearprotocol/near-web3-provider

Illia Polosukhin

commit sha ca83ed78ad59fd39c2fdedb06a4a8a6483b1c4d1

Adding basic keyStore/account management support

view details

push time in 11 days

push eventnearprotocol/near-web3-provider

Barbara Liau

commit sha 65126d75fb0912aa19ef9db7877f690fcd189a45

Adds doc block; returns Boolean false if no connection, instead of defaulting to error

view details

Barbara Liau

commit sha 8ff4870c744af7d01fb7c7f800142dfe7b21f4c5

net_version returns a string; doc block

view details

Barbara Liau

commit sha a0bc3663c98d450d9f837738684fa72e5627cc77

Reorder statements; add doc block and comments for eth_gasPrice

view details

Barbara Liau

commit sha a33a4ad6fadf8347bc3ff26b827efb05874b0a7c

Updates eth_accounts

view details

Barbara Liau

commit sha fc0ad4992bb68c1a3ad7b4063ab6bfd64de75ce4

Add bsert

view details

Barbara Liau

commit sha ad2f5f627349f3d4b9eea3f164c0c5b8796eb774

Add additional methods, docs, tests

view details

Barbara Liau

commit sha a9633b04057da7b331ad0d341e9ca8dd69ef050d

Initial commit

view details

Barbara Liau

commit sha 5401e9622ebc07a25a05a8ac427622eb48da7f9f

Stub the rest of the methods

view details

Barbara Liau

commit sha a49534435eeb8577e1c09de959eca96a1adc9023

Add notes and questions

view details

Barbara Liau

commit sha 571be28f2fb0a6be9fa059c7317baf088fbf1e2c

Add .notes to gitignore

view details

Barbara Liau

commit sha 65a9e144cac354ead6e520d464b2ea8dddc39198

Add another question

view details

Barbara Liau

commit sha 0841effd296f07b76d11e9113e9c6223ea1f0f86

Add getTransactionBlockByHashAndIndex; cleanup

view details

Barbara Liau

commit sha f71ca70626d1f102cad0ee564a295be4e135034e

Update transactionObj. Add TODO

view details

Barbara Liau

commit sha 34bd86df889cdcdead1f02e76ab5a328043445e6

Move variables to top level. Add test for getTransactionFromBlock

view details

Barbara Liau

commit sha 2a44dd84f6dfd2c7bc204bc7d103525c4836b2b1

Update nearlib

view details

Barbara Liau

commit sha 5241145d57b4db546ed73afecdbcf44879a20094

Add eth_getTransactionByBlockNumberAndIndex

view details

Barbara Liau

commit sha ca3dff24258cc3963f50329051bae06dab139847

Add more tests for getTransactionFromBlock

view details

Barbara Liau

commit sha 860607b791d86e92e8225c300657c50de4cc4670

Rearrange; update tab size

view details

Barbara Liau

commit sha cce4e9adfee2976ec5e749e6c1f328040418be05

Update information about transactions and chunks

view details

Barbara Liau

commit sha 91ae088ef7bdfd7757b8a4c8f9fa224ebe4830c7

Handle for accountId being passed in with txHash

view details

push time in 11 days

pull request commentnearprotocol/contribution

Updated readme

What is our plan here? I'm still not completely sure about separate repo for this and we also should improve contribution guidelines overall and for nearcore

AnaisUrlichs

comment created time in 12 days

push eventnearprotocol/stakewars

Illia Polosukhin

commit sha 08d98354b9f58ea25276e4ed97dd6d53a9b88b70

Deployable / usable version of the contract

view details

push time in 13 days

pull request commentnearprotocol/nearcore

Change state dump to binary format

@bowenwang1996 if you are saying it takes 2 minutes - we fixed the 20 minute delay in starting node / opening rocksdb?

bowenwang1996

comment created time in 14 days

issue openednearprotocol/NEPs

NEAR Spec and standards

Want to start discussion for where and how we are going to maintain NEAR Spec and standards.

The NEPs process is mostly around proposal to modify / add things, but we also need the final version that lists the overall specification for the protocol and also all the accepted / used standards.

My proposal, we actually rework this repository instead of been a list of proposals into maintaining the released version of Spec + all accepted standards.

E.g. if would be a combination of https://github.com/ethereum/eth2.0-specs and https://github.com/ethereum/EIPs.

Where as NEP gets accepted it modifies the staging version of the spec and gets released with the new version. Alternatively if NEP represents new standard and doesn't require changes to protocol - it goes to the standards list.

Why standards mixed with spec? Mostly because standards end up representing a big part of the protocol itself. If you think of ERC-20 specification - it actually is a core part of the Ethereum protocol, even though doesn't live on blockchain level itself. Same thing can go for any number of other protocols.

I also think we can repurprose https://nomicon.io/ to serve final version of spec. That website already maintains mostly the spec details with few implementation details that we currently have in Rust client. We can split Rust specifics into the docs inside Rust repo (which currently is not pointing to nomicon.io anyway).

created time in 14 days

pull request commentnearprotocol/NEPs

Split contract execution

@nearmax I'm thinking we should start policy for NEPs as well. Because we have super old PRs here still sitting.

nearmax

comment created time in 14 days

delete branch nearprotocol/nearcore

delete branch : fix-2071

delete time in 16 days

push eventnearprotocol/nearcore

Illia Polosukhin

commit sha 1c0ff7ce871dd5602cd278b927155a9b48ec41ec

Ref #2067: querying contract state (#2075) * Fix #2067: querying contract state * Change format to {key, value, proof} for state view. Proofs are empty for now

view details

push time in 16 days

issue closednearprotocol/nearcore

Querying contract state via RPC does not give any result

I have deployed studio-abd6fq9b5 contract via studio, and executed a method which set last_sender key on a storage to frol.near. Yet, query(contract/) API does not work:

$ http post https://rpc.nearprotocol.com/ jsonrpc=2.0 id=dontcare method=query 'params:=["contract/studio-abd6fq9b5","TsnowmMYMe3aWeM"]'

{
    "error": {
        "code": -32000,
        "data": "key must be a string",
        "message": "Server error"
    },
    "id": "dontcare",
    "jsonrpc": "2.0"
}

The second parameter is expected to be a base58-encoded key prefix, so I encoded "last_sender" with base58: "TsnowmMYMe3aWeM"

I have also tried to send an empty string (expecting to receive a whole state), that gives the same error. Providing just a substring of the base58 string, I could get the response, but it is always an empty value.

closed time in 16 days

frol

PR merged nearprotocol/nearcore

Reviewers
Ref #2067: querying contract state

Resulting output is key/value pairs in base64 encoding:

http post http://localhost:3030 jsonrpc=2.0 method=query id=123 params:='["contract/my_token", ""]'
HTTP/1.1 200 OK
content-length: 302
content-type: application/json
date: Mon, 03 Feb 2020 23:11:51 GMT

{
    "id": "123",
    "jsonrpc": "2.0",
    "result": {
        "block_height": 2440,
        "proof": [],
        "values": [
            {
                "key": "U1RBVEU=",
                "proof": [],
                "value": "AgAAAGFpAQAAAAAAAAACAAAAYWsBAAAAAAAAAAIAAABhdqCGAQAAAAAAAAAAAAAAAAA="
            },
            {
                "key": "YWkMAAAAbXlfdmFsaWRhdG9y",
                "proof": [],
                "value": "AAAAAAAAAAA="
            },
            {
                "key": "YWsAAAAAAAAAAA==",
                "proof": [],
                "value": "DAAAAG15X3ZhbGlkYXRvcg=="
            },
            {
                "key": "YXYAAAAAAAAAAA==",
                "proof": [],
                "value": "oIYBAAAAAAAAAAAAAAAAAAAAAAAAAAAA"
            }
        ]
    }
}
+56 -17

1 comment

3 changed files

ilblackdragon

pr closed time in 16 days

push eventnearprotocol/near-evm

Illia Polosukhin

commit sha f65fe1d8c5530c51236cf3e0f1819ed2fd939f94

Updating bindgen to master to get panics returned from WASM. Adding get_code for truffle support.

view details

push time in 16 days

issue commentnearprotocol/nearcore

test_validator_kickout is flaky

@SkidanovAlex Is these tests still flaky?

nearmax

comment created time in 16 days

issue commentnearprotocol/nearcore

Tests should use injectable fake timer

@SkidanovAlex is this fixed with your Doomslug work or still needed?

nearmax

comment created time in 16 days

push eventnearprotocol/nearcore

Bo Yao

commit sha 15753f48fc027a8193d45094e9e0f272f05efa94

Move sysinfo fix from staging (#2085) * Move sysinfo fix from staging

view details

Anton Bukov

commit sha d68cad0a8977debeba543ad90ad3a08721188481

Introduce keccak256 and keccak512 native support (#2072) * Introduce keccak256 and keccak512 native support * modify genesis Co-authored-by: Bowen Wang <bowenwang1996@users.noreply.github.com>

view details

AnaisUrlichs

commit sha d8c9f6a1d51e2020300a6b4be58677626d802b91

Create code-of-conduct.md (#1932) * Create code-of-conduct.md * Move code of conduct to proper name Co-authored-by: Illia Polosukhin <illia@nearprotocol.com>

view details

Illia Polosukhin

commit sha 217cf878c1f7f980ab031c315e0919160a58a9c2

Merge branch 'master' into fix-2071

view details

push time in 16 days

issue openednearprotocol/nearcore

Check sum and improved bs58 encoding

@abacabadabacaba suggested to use an improved bs58 scheme that encodes into fixed length representation by splitting sequence into 8 byte chunks.

Additionally to add check sum to verify that the full sequence was provided and wasn't corrupted.

Interesting note that Ethereum didn't have this originally and they added it by using capitalization of letters in base16.

created time in 16 days

Pull request review commentnearprotocol/nearcore

archive flag for turning off GC

 pub struct ClientConfig {     pub tracked_accounts: Vec<AccountId>,     /// Shards that this client tracks     pub tracked_shards: Vec<ShardId>,+    /// Not clear old data, set `true` for achieve nodes.

Archive

Kouprin

comment created time in 16 days

delete branch nearprotocol/nearcore

delete branch : randomness-with-keys

delete time in 17 days

push eventnearprotocol/nearcore

Illia Polosukhin

commit sha 9dd441cc90bd07a996c034d0d384852f0aa41506

Refactoring usage of Signer to ValidatorSigner (#2026) * Move Blake2b hashes to a separate module. * Sort crypto dependencies. * Universal ToScalar trait. * WIP * Revert "Proof-of-stake-time (#1848)" This reverts commit 2c7bf9cf0615b3cc7a441c418497a38461a904df. * Removing weight, replacing fork choice with score and height In preparation for implementing Doomslug, removing the concept of `weight` and replacing the fork choice rule to choose the chain with the highest score, and then height. Replacing score with the height of the last pre-voted block rather than the weight. * Doomslug the Destroyer Implementation and integration of Doomslug (see https://near.ai/doomslug). Doomslug itself is in `chain/doomslug.rs`, and doesn't depend on chain or any other code. It also always takes the current time as an argument. It significantly simplifies testing. Doomslug is stored on the client, not chain, because both block production and approvals processing happens on client. Instantiating on chain would require a slightly more complex interface (e.g. it would be impossible to pass `me`). Doomslug needs to know about the latest Tip. Instead of intercepting the lowest level tip-updating routine (which is in storage), I update the Tip in the client when we accept the new head. It could miss head changes related to syncing and challenges. To be safe I always update the head whenever I interact with Doomslug, so the head is guaranteed to be accurate whenever we do anything related to Doomslug, but it might get sent to Doomslug with a slight delay. This change also solves a problem that approvals before were in a cache hash map, therefore an adversary could have spammed a node with lots of invalid approvals and remove all valid approvals from the cache, resulting in a node not having enough approvals when producing the block. New logic is more complex, see `DoomslugApprovalsTrackersAtHeight` class. Test plan --------- 1. Sanity tests (basic invariants for `set_tip` and approval processing) 2. A fuzzy test that tests safety and liveness under different times to GST and deltas. 3. `test_catchup_sanity_blocks_produced_doomslug` verifies that heights are properly skipped. 4. Also added checking doomslug invariant into `cross_shard_tx`, which is known to evoke all kinds of weird structures (but `cross_shard_tx` operates without the requirement to have 50% approvals on the block, thus still causing lots of forkfullness). 5. A new version of `cross_shard_tx` that enables doomslug, but disables tampering with the finality gadget. Thus the vanilla version tests heavy forkfulness and tampers with FG, while the new doomslug version has practically no forfulness due to doomslug, and doesn't stress the FG as much, but does test block production with doomslug. * More WIP, some tests and fixes. * Better names. * Starting to add ValidatorSigner to abstract signage of different parts for validators * Adding ristretto curve to the ValidatorSigner as additional curve * Fix up warnings and config saving * Correct ristretto group from seed creation * Fix comment and failed test * Optimize imports * Fix doomslug tests * Sorted imports * Undo randomness branch here * Undo undo vrf * Addressing comments: adding telemetry types for clean API around signing and passing that information Co-authored-by: Evgeny Kapun <abacabadabacaba@gmail.com> Co-authored-by: Alexander Skidanov <skidanov.alexander@gmail.com>

view details

push time in 17 days

PR merged nearprotocol/nearcore

Reviewers
Refactoring usage of Signer to ValidatorSigner

The goal of this PR is to refactor how validator signs various objects.

Specifically, a new interface ValidatorSigner is created (replacing BlockProducer in client). It has methods for each object that needs to be signed by validator:

  • Block Header parts
  • Chunk Header
  • Approval
  • Json (for telemetry)
  • Challenge
  • Account Announce

Each of these types can define how exactly the information gets converted into digest and signed (for example Block Header parts are merkerlized and root is signed).

This unlocks:

  • Remote and HSM signing for validators
  • Easy switch to different curve (like BLS) in one place without changing any usage places.
+993 -696

4 comments

61 changed files

ilblackdragon

pr closed time in 17 days

push eventnearprotocol/nearcore

Anton Bukov

commit sha 05a82d8dd74531b21567623ab0e7e75946afea19

Add keccak native support (#2045) * Introduce keccak256 and keccak512 native support * Update comment * Cargo fmt * Add keccaks estimation code * Merge branch 'staging' into feature/keccak-native-support * Bumping 0.4.4 version * Add versions to near-rpc-error-macro * Nit * Merge branch 'staging' into feature/keccak-native-support * Merge branch 'feature/keccak-native-support' of github.com:nearprotocol/nearcore into feature/keccak-native-support

view details

Illia Polosukhin

commit sha 49770b8b8f2b8d0eb54b81e660e98395e283402d

Merge branch 'staging' into randomness-with-keys

view details

push time in 17 days

issue openednearprotocol/near-bindgen

Export basic types directly instead of vm-logic

Currently basic types like BlocmHeight used inside Bindgen but also client contracts need also import them from near-vm-logic It's very confusing and adds extra dependency that can be misaligned (like right now with crate.io having 0.4.4 whereas Bindgen depended on 0.4.3).

Ideally Bindgen should just export these types itself and client contracts don't need to depend directly on near-vm-logic.

created time in 17 days

push eventnearprotocol/near-bindgen

Illia Polosukhin

commit sha 4ed1607a2f26609cbe8029919a43383f2f02c5c3

Bump bindgen to use vm-logic from staging, because we poisoned crates with 0.4.4 which is nowhere to be found

view details

push time in 17 days

push eventnearprotocol/near-evm

Illia Polosukhin

commit sha 6b4a4cde36641adb7a1555b2c7e500aed2033c74

Fixing compilation for wasm by uncommenting crate-type. Removed sed from build.sh as it's not needed anymore with new clion. neardev is in gitignore to prevent leaking keys

view details

push time in 17 days

pull request commentnearprotocol/nearcore

Refactoring usage of Signer to ValidatorSigner

@frol FYI - https://github.com/nearprotocol/nearcore/pull/2026/commits/fb992b556573f4f010e03a12d715b88f0e72de69

ilblackdragon

comment created time in 17 days

Pull request review commentnearprotocol/nearcore

Refactoring usage of Signer to ValidatorSigner

+use std::path::Path;+use std::sync::Arc;++use borsh::BorshSerialize;++use near_crypto::{InMemorySigner, KeyType, PublicKey, Signature, Signer};++use crate::block::{Approval, BlockHeader, BlockHeaderInnerLite, BlockHeaderInnerRest};+use crate::challenge::ChallengeBody;+use crate::hash::{hash, CryptoHash};+use crate::network::{AnnounceAccount, PeerId};+use crate::sharding::{ChunkHash, ShardChunkHeaderInner};+use crate::types::{AccountId, BlockHeight, EpochId};++/// Validator signer that is used to sign blocks and approvals.+pub trait ValidatorSigner: Sync + Send {+    /// Account id of the given validator.+    fn validator_id(&self) -> &AccountId;++    /// Public key that identifies this validator.+    fn public_key(&self) -> PublicKey;++    /// Sign json (used for info).+    fn sign_json(&self, json: String) -> Signature;

Sadly it doesn't really help with security because "signer" still signs json directly (e.g. HSM will receive JSON). Which means to clean up this interface we actually need to move serialization inside this method and return serialized object.

ilblackdragon

comment created time in 17 days

push eventnearprotocol/nearcore

Illia Polosukhin

commit sha fb992b556573f4f010e03a12d715b88f0e72de69

Addressing comments: adding telemetry types for clean API around signing and passing that information

view details

push time in 17 days

issue commentnearprotocol/near-evm

Out of gas Err in callback

@prestwich we are for now not releasing new nearcore - we have few breaking changes that need to be tested extensively on large cluster machines. Also we overhauling the release process as well. It's fine to depend on staging for testing at this point.

prestwich

comment created time in 17 days

delete branch nearprotocol/nearcore

delete branch : add-code-of-conduct-1

delete time in 17 days

push eventnearprotocol/nearcore

AnaisUrlichs

commit sha d8c9f6a1d51e2020300a6b4be58677626d802b91

Create code-of-conduct.md (#1932) * Create code-of-conduct.md * Move code of conduct to proper name Co-authored-by: Illia Polosukhin <illia@nearprotocol.com>

view details

push time in 17 days

PR merged nearprotocol/nearcore

Reviewers
Create code-of-conduct.md
+76 -0

4 comments

1 changed file

AnaisUrlichs

pr closed time in 17 days

push eventnearprotocol/nearcore

Bo Yao

commit sha 15753f48fc027a8193d45094e9e0f272f05efa94

Move sysinfo fix from staging (#2085) * Move sysinfo fix from staging

view details

Anton Bukov

commit sha d68cad0a8977debeba543ad90ad3a08721188481

Introduce keccak256 and keccak512 native support (#2072) * Introduce keccak256 and keccak512 native support * modify genesis Co-authored-by: Bowen Wang <bowenwang1996@users.noreply.github.com>

view details

Illia Polosukhin

commit sha 957487b374a43e6a1fa05cb50cfe6c8c87ad8cb5

Merge branch 'master' into add-code-of-conduct-1

view details

push time in 18 days

push eventnearprotocol/nearcore

Anton Bukov

commit sha 4bc4b74aeaab3231866ddb7de822e8892a13d9dc

Enable floats but prohibit some CPU architectures (#1941) (#2079) * Enable floats but prohibit some CPU architectures * Merge branch 'staging' into enable_floats * Merge refs/heads/staging into enable_floats * Avoid overflowing u32 during contract preparation (#1946) * Update runtime/near-vm-runner/src/runner.rs Co-Authored-By: Evgeny Kuzyakov <ek@nearprotocol.com> * Merge branch 'staging' into enable_floats * Nit Co-authored-by: Maksym Zavershynskyi <35039879+nearmax@users.noreply.github.com>

view details

Illia Polosukhin

commit sha 603aaf570a39289c9e0a4e9c57ba043646e4763f

Move code of conduct to proper name

view details

Illia Polosukhin

commit sha 77148e1c2ddaa0eb50389d6c06d570744a473d6c

Merge remote-tracking branch 'origin/master' into add-code-of-conduct-1

view details

push time in 18 days

more