bh2smith

The following guide was coppied from ChatGPT 4o:

When managing multiple NEAR smart contracts within a single repository, it's common to structure the repository to facilitate organization, compilation, and deployment. Here’s a pattern you can follow for a multi-contract NEAR project in Rust:

Directory Structure

1. root directory: Contains common configuration files.
2. contracts: A directory containing individual subdirectories for each contract.
3. scripts: Contains scripts for building, testing, and deploying contracts.
4. tests: Contains integration tests that might involve multiple contracts.

bh2smith

Based on the instructions in Near Docs Here: https://docs.near.org/build/chain-abstraction/multichain-gas-relayer/relayer-gas-example

and related to resolution of the following issue:

BitteProtocol/near-ca#64

1. Registration / Storage Deposit:

near contract call-function as-transaction v2.nft.kagi.testnet \
  storage_deposit json-args {} \

bh2smith

Safe SDK Notes:

Use Case

Let us suppose our SIGNER_ADDRESS=0xf11c22d61ecd7b1adcb6b43542fe8a96b9328dc7 and that we do not have the private key, but we can produce signatures for this account.

Can't initialize the safe pack for usecase:

https://docs.safe.global/sdk/relay-kit/guides/4337-safe-sdk#initialize-the-safe4337pack

bh2smith

Runtime Arguments vs. Environment Variables

Runtime Arguments:

• Definition: These are parameters passed to a program at the time it is executed. They are typically specified in the command line.
• Usage:
  • Directly affect the program's behavior for a specific run.
  • Ideal for options or configurations that might change frequently.
  • Example: If you have a script that processes files, you might pass the filename as a runtime argument (python process_file.py input.txt).

bh2smith

import {
  createPublicClient,
  decodeFunctionResult,
  encodeFunctionData,
  http,
  parseAbi,
} from "viem";
import { mainnet } from "viem/chains";

const multicallAbi = [