feat: update test to correctly expect fork promotion

.github/workflows/rust.yml

@@ -0,0 +1,63 @@
+name: Rust
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+
+env:
+  CARGO_TERM_COLOR: always
+
+jobs:
+  contract:
+    name: "Smart contract checks"
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: ./contract
+    steps:
+        - name: Checkout sources
+          uses: actions/checkout@v2
+
+        - name: Run rustfmt
+          uses: actions-rs/cargo@v1
+          with:
+            command: fmt
+            args: --manifest-path ./contract/Cargo.toml --all -- --check
+
+        - name: Run clippy
+          uses: actions-rs/clippy-check@v1
+          with:
+            token: ${{ secrets.GITHUB_TOKEN }}
+            args: --manifest-path ./contract/Cargo.toml --all-targets -- -D warnings
+
+        - name: Run tests
+          run: |
+            rustup target add wasm32-unknown-unknown
+            RUST_BACKTRACE=1 cargo test -- --skip test_setting_genesis_block --skip test_setting_chain_reorg
+
+  relayer:
+    name: "Relayer checks"
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: ./relayer
+    steps:
+      - name: Checkout sources
+        uses: actions/checkout@v2
+
+      - name: Run rustfmt
+        uses: actions-rs/cargo@v1
+        with:
+          command: fmt
+          args: --manifest-path ./relayer/Cargo.toml --all -- --check
+
+      - name: Run clippy
+        uses: actions-rs/clippy-check@v1
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          args: --manifest-path ./relayer/Cargo.toml --all-targets -- -D warnings
+
+      - name: Run tests
+        run: |
+          RUST_BACKTRACE=1 cargo test

contract/Cargo.toml

@@ -18,6 +18,7 @@ borsh = "1.5.0"
 bitcoin = { version = "0.32.0", features = ["serde"] }
 serde_json = "1"
 merkle-tools = { path = "../merkle-tools" }
+serde = { version = "1.0.200", features = ["derive"] }
 
 [dev-dependencies]
 near-sdk = { version = "5.1.0", features = ["unit-testing"] }

contract/README.md

@@ -24,11 +24,19 @@ If you want to test on a testnet follow next steps
 ```bash
 cargo-near near create-dev-account use-random-account-id autogenerate-new-keypair save-to-legacy-keychain network-config testnet create
 ```
+- Add nears to your test account if needed
+Go to https://near-faucet.io/ website and request Near for your account
 - Deploy contract to testnet
 ```bash
 near contract deploy <<ACCOUNT_NAME_FROM_PREVIOUS_COMMAND>> use-file ./target/wasm32-unknown-unknown/release/btc_light_client_contract.wasm without-init-call network-config testnet sign-with-keychain send
 ```
 
+Setup relayer service:
+
+```shell
+cat <<PATH_TO_THE_KEY_FILE_FROM_ACCOUNT_CREATION_COMMAND>> | jq -r '.private_key'
+```
+
 ## Useful Links
 
 In more detail, the verification component performs the operations of a Bitcoin SPV client. See this paper (Appendix D) for a more detailed and formal discussion on the necessary functionality.
@@ -40,3 +48,9 @@ In more detail, the verification component performs the operations of a Bitcoin
 * Transaction Inclusion Verification - given a transaction, a reference to a block header, the transaction’s index in that block and a Merkle tree path, determine whether the transaction is indeed included in the specified block header (which in turn must be already verified and stored in the Bitcoin main chain tracked by BTC-Relay).
 
 An overview and explanation of the different classes of blockchain state verification in the context of cross-chain communication, specifically the difference between full validation of transactions and mere verification of their inclusion in the underlying blockchain, can be found in this paper (Section 5).
+
+## FAQ
+What if somebody start to send older blocks than the genesis we used to initialize the relay?
+
+In this case we will ot insert those block headers, so we will not use storage for it. We also quickly check if prev_block is included into the contract, so
+we will not spend a lot of gas on it.