Merge casper-network#3106

3106: Initial support for private chain r=mpapierski a=mpapierski

This is backport of original casper-network#3029 on top of v1.4.6 with least amount of extra backported changes to make the original code from PR unchanged.


This PR brings preliminary support for private chains by introducing multiple chainspec configuration flags that change the behavior of a chain.

These settings are orthogonal to each other; any particular combination (and all other pre-existing settings) is valid for a given network, for a wide variety of possible permutations. 

- Administrator accounts: by specifying accounts in a `[[administrators]]` section of `accounts.toml` accounts with special privileges are created and later referred to as 'administrative accounts'
- `core.allow_auction_bids` disables add_bid, delegate entrypoints in auction contract if set to true
- `core.compute_rewards` rewards 0 tokens after each switch block. This means no new tokens are minted and validators aren't gaining more weight.
- `core.allow_unrestricted_transfers` if set to false, the normal user can't send tokens to other normal users; the normal user can transfer only to the administrator; either source or target has to be an admin.
- `core.refund_handling` defines how refunds are computed. 
  - `refund_handling = { type = "refund", refund_ratio = [1, 1] }` means 100% of `payment_amount - gas_spent` is refunded. 
  - `refund_handling = { type = "refund", refund_ratio = [0, 100 ] }` doesn't refund anything
  - `Refund` mode requires that the fraction specified is proper fraction (that is `refund_ratio <= 1`)
- `core.fee_handling` defines how gas spent is processed after deploy is executed.
  - `fee_handling = { type = "accumulate" }` creates special rewards purse in the mint system contract where fees are accumulated into
  - `fee_handling = { type = "pay_to_proposer" }` is a default setting for a public chain - rewards are transferred to block's proposer.
  - `fee_handling = { type = "burn" }` fees are burned.


Co-authored-by: Michał Papierski <michal@casperlabs.io>

Merge casper-network#2978

2978: Bump assembly script version for publish. r=sacherjj a=sacherjj

Bumping assembly script to 1.4.6


Co-authored-by: Joe Sacher <321623+sacherjj@users.noreply.github.com>

Merge pull request casper-network#2819 from TomVasile/ci_fixes_rel_145

CI/NCTL: Fixes for Release 1.4.5

Merge casper-network#2541

2541: version bumps r=sacherjj a=Fraser999

The PR includes a patch-level version bump of `casper-types`, `casper-hashing`, `casper-execution-engine` and `casper-node`.

Co-authored-by: Fraser Hutchison <fraser@casperlabs.io>

Merge casper-network#2521

2521: Increse contract_as package version backport r=mpapierski a=mpapierski

We already have the 1.4.2 release published to npmjs, and the code still specifies 1.4.1 as a version which is also published already. To avoid conflicts we need to bump the version before next release

Backport of casper-network#2520 

Co-authored-by: Michał Papierski <michal@casperlabs.io>

Merge casper-network#2264

2264: Bump to 1.4.1 r=sacherjj a=sacherjj



Co-authored-by: Joe Sacher <321623+sacherjj@users.noreply.github.com>

Merge casper-network#2251

2251: Adding setup-as prior to npm publish. r=sacherjj a=sacherjj

Due to changes in makefile, setup-as is no longer run as part of make deb.
This explicitly adds a drone step to run this prior to publish.

Co-authored-by: Joe Sacher <321623+sacherjj@users.noreply.github.com>

1.3.4 bump.

Merge casper-network#2068

2068: Version bump to 1.3.3 r=sacherjj a=sacherjj

Bump of version to 1.3.3 for publish.


Co-authored-by: Joe Sacher <321623+sacherjj@users.noreply.github.com>

Merge casper-network#1834

1834: CHANGELOG update and chainspec.toml final changes r=sacherjj a=sacherjj

Added CHANGELOG entries for 1.3.1 and 1.3.2 in node.
Correcting activation point and costs for add_bid and delegate in chainspec.toml

Co-authored-by: Joe Sacher <321623+sacherjj@users.noreply.github.com>