• [X] Missing variants of TransactionStatus` --> Sample Block
• [X] Missing variants of CoinBase: Two
• [X] ~~Missing variants of UserCommand: SnappCommand~~
• [X] ~~Missing variants of SignedCommandPayloadBody: Create_new_token Create_token_account Mint_tokens~~
• [X] Add Tests

Summary of changes Changes introduced in this pull request:

Add variants, refactor, update, fix, and lightweight the staged_ledger_diff.rs Originally posted by @jspada in https://github.com/ChainSafe/mina-rs/pull/94#discussion_r764134519 Here split into small PR #142 .

• [x] feat: Add struct Parties in UserCommand
• [x] feat: Update CoinBase variants
• [x] feat: Add variant in TransactionStatus
• [x] feat: Add variants in SignedCommandPayloadBody
• [x] feat: Add SnappCommand to UserCommand
• [x] feat: Add Parties in UserCommand
• [x] feat: Update variants in enum SignedCommandPayloadBody
• [ ] feat: Implement SnappCommand.rs
• [ ] feat: Implement party.rs for UserCommand
• [x] feat: Implement snapp_predicate.rs
• [x] refactor: staged_ledger_diff.rs with transaction_status.rs, coinbase.rs, signed_command.rs & user_command.rs
• [x] feat: Add variants in structs StakeDelegation, CreateNewTokenPayload, CreateTokenAccountPayload & MintTokensPayload
• [x] feat: CoinBaseV1 according to Mina Ocaml coinbase
• [x] docs: doc comment all above.

• The following test will be in the next PR test coverage #143 .

• [ ] test: StagedLedgerPreDiffOne
• [ ] test: Implement test_coin_base_fee_transfer().
• [ ] test: Implement test_coin_base_balance_data().
• [ ] test: Implement test_fee_transfer_balance_data().
• [ ] test: Implement test_snapp_command().

nce issue to close (if applicable)**

Closes

Other information and links

MinaProtocol staged_ledger_diff.ml MinaProtocol staged_ledger_diff.mli snapp_command.ml
user_command.ml Reference version aacfe04245d14b3331e89ed76a4b77bec902b290

Summary of changes Changes introduced in this pull request:

Now the updated workspace Cargo.toml after this refactor look like the following

[workspace]
members = [
	"base",
	"consensus",
	"crypto",
	# All crates related to bin prot wire protocol
	"protocol/bin-prot",
	"protocol/wire-type",
	"protocol/bin_prot_checker",
	"protocol/wire-type-derive",
	"protocol/test-fixtures",
	"protocol/test-serialization",
]

Reference issue to close (if applicable) Include the issue reference this pull request is connected to #77 Closes

Summary of changes Changes introduced in this pull request:

• Converts the single-page demo to multi-page so that more functionalities can be integrated, e.g. readme, send transaction, etc.
• Integrate with tailwindcss
• Make chrome extension without sandboxing (requires chrome canary for now)
• Render project readme.md on index page
• Create page skeleton for graphql demo
• Build chrome extension mv2 for chrome stable / edge and firefox
• Instructions on using the extension chrome canary/stable, edge and firefox

Reference issue to close (if applicable)

Closes

Other information and links

Summary of changes Changes introduced in this pull request:

• Fixed polyvar serialization
• Implemented Transaction Snark Data Structure
• Implemented base/serialization_type_conversions for snark work
• Implemented staged ledger pre diff one Data Structure

Reference issue to close (if applicable)

Closes #194 #143 except: test: Implement test_snapp_command().

Other information and links

Summary of changes Changes introduced in this pull request:

• Implement Base58Encodable trait for PublicKey2 Type
• Validate full byte vec for PublicKey2 Type Fields

Reference issue to close (if applicable) Closes #158

Other information and links

Some Mina data structures use a Polymorphic Variant (Polyvar) data structure. These are much like Sum types / enums but identify variants with a hash rather than an index when serialized. This hash needs to be stored along with the variant in a special data structure since Rust has no equivalent data type.

Summary of changes Changes introduced in this pull request:

• Adds deserialization support for Polyvars from loosely typed layouts
• Add serialization support for polyvars from loose types
• (TODO) Add data type to represent polyvars in Rust to strong type serialization and deserialization

Other information and links

Summary of changes Changes introduced in this pull request:

• Cleans up consensus crate and relocates a few items to common.rs.
• Moves the consensus constants under the Consensus trait as const, so APIs don't need to pass them around.
• We cover the following tests for short range fork as part of this PR:
  • Same chain
  • Chains that are more than 1 epoch apart
  • Chains that are 1 epoch apart but beyond the seed update range.
  • Chains that are 1 epoch apart but have same lock checkpoint

relevant section for ref: https://github.com/MinaProtocol/mina/blob/02dfc3ff0160ba3c1bbc732baa07502fe4312b04/docs/specs/consensus/README.md#532-short-range-fork-check

Reference issue to close (if applicable)

Closes #144

Other information and links

Summary of changes Changes introduced in this pull request:

• add data structure for private key
• key pair validation functionality

Reference issue to close (if applicable)

Closes #102

Other information and links

Summary of changes Changes introduced in this pull request:

• Merge 'check license' with 'cargo fmt check' into checks
• Remove stale working-bee branch in the setup
• Group jobs into checks, x86_64, wasm and codecov-x86_64
• Avoid allocating CI VM for every small job (although GH does not have rate limit atm)
• Run wasm tests for test-serialization against both node and headless chrome context
• Add dependency badge
• Replace/Remove insecure dependencies shown here: https://deps.rs/repo/github/ChainSafe/mina-rs
• Add cargo deny check to checks job
• Add benchmark tests for block(ExternalTransition) serde
• Add cargo bench to x86_64 job
• Upload benchmark (html) report as build artifacts

Reference issue to close (if applicable)

Closes

Other information and links

Summary of changes Changes introduced in this pull request:

Milestone 4 Store and Update account database Merkle-ledger

Reference issue to close (if applicable)

Closes #39 Closes #40

Other information and links

Issue summary

• [X] The NCN will get the best block from the pool of trusted providers, it will run chain selection and select the best block,
• [X] It will track n blocks behind that best block for stronger finality purposes (where n may = 20 (an arbitrary number) or the same number of blocks tracked by exchanges.)
• [ ] As a user I can specify how many blocks in history that the NCN will store so that I have flexibility over the finality confidence of my node
• [ ] Integration tests

Other information and links

Issue summary

• The user of an NCN can configure their own list of trusted service providers (usually will include nodes run by Bison Trails, Figment, etc. but can also be their own local node they’re running.) This can be done via the settings page for the web extension
• Support for multiple networks and switching between them (eg testnets and mainnet) The above two could be something like { “testnet” : { “figment” : “”, …}, “mainnet” : { “bison_trails” : “” }} and also configurable through the settings page

Other information and links

Issue summary

Validate transitions with the following checks (in this order):

• Checking for existence in the breadcrumb tree (we've already seen it)
• Checking for consensus errors
• Verifying the included SNARK

Also:

• [X] signatures (waiting on #231)
• [ ] snark proofs
• [ ] structure of block

Other information and links

Task summary

Mina uses its own unsigned numeric data type Nat.UInt32 for a number of internal types including AccountNonce and GlobalSlotNumber.

This has slightly different serialization to a bin_prot integer from what I can tell. For the most part they are compatible but in some edge cases they are not.

Our codebase uses i32 and coverts to u32 in order to maintain compatibility. This is a hack solution and can fail in certain cases (which are not covered properly by tests)

Tasks for this issue

• Explicitly support Nat.UInt32 as a serialization type. Currently we use ExtendedU32 wrapper around i32
• Add conversions from this to rust types (e.g. u32)
• Replace this in our other serialization-types where required
• Add test coverage for edge cases for ExtendedU32 (e.g. minvalue, maxvalue etc)

Specification reference

• https://github.com/MinaProtocol/mina/blob/develop/src/lib/mina_numbers/nat.ml

Other information and links