Dmitry S

Upgrade `btcsuite` project-wise

2

We need to upgrade `btcsuite` in the node and in `go-tss` to enable Taproot scripts. Currently, we have several different `btcd` package versions, which creates a headache in BTC dependencies...

# Description This EPIC groups tasks toward integration of [TON](https://ton.org/) into testnet. Features: User Actions - `donate()` - `deposit()` - `deposit_and_call()` - `withdraw()` (on behalf of TSS) Governance actions -...

- Docker image - Scripts - Automatic TON funding for predefined wallets

Implement Gateway contract

1

- Implement Gateway contract on TON using [FunC](https://docs.ton.org/develop/func/overview) & [Blueprint](https://github.com/ton-org/blueprint) - Create `zeta-chain/protocol-contracts-ton` repository - Determine gas economics for TON integration (including storage fees) - Support TSS signature

Create RFC for Zetaclient V2

1

**Describe the Issue** We need a unified, simple, fault-tolerant, and efficient chain orchestration logic in zetaclientd for chain observation. Let’s design one and elaborate on this in the RFC docs....

Add routine for observing TON inbound trackers

Add compliance checks for TON deposits and withdrawals. We can reuse logic from Solana integration **UPD**: for revering withdrawals, we need to support `increase_nonce` commands on TON's smart-contract level similartly...

func: stdlib: compute_data_size description mismatch

1

Apparently `compute_data_size` and `compute_data_size?` docblocks/signatures are mixed up ``` ;;; A non-quiet version of [compute_data_size?] that throws a cell overflow exception (`8`) on failure. (int, int, int, int) compute_data_size?(cell c,...

https://github.com/zeta-chain/node/blob/1a9d185ddd0c58158872c7c59d561c041aa17362/zetaclient/chains/ton/observer/inbound.go#L23