Benjamin Smith 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).

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

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:

Mintbase/near-ca#64

Registration / Storage Deposit:

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

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

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

Arak Quickstart

Arak is a very simple ethereum log indexing program found on github at: https://github.com/cowprotocol/arak

Create Postgres Instance

docker pull postgres

docker run --name erc721 -p 5432:5432 -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=postgres -d postgres

Curl Requests made as follows JSON files will be provided per section

 export ARCHIVE_NODE_URL=
 export JSON_FILE_PATH=
curl $ARCHIVE_NODE_URL -X POST -H "Content-Type: application/json" --data $JSON_FILE_PATH | jq

with solutions as (
  select 
    (json -> 'solutions' ->> -1)::jsonb as winning_solution
  from solver_competitions
  where id >= 4929771  -- The first batch containing the field `uninternalizedCallData`
)

select 100.0 * sum(case when winning_solution -> 'uninternalizedCallData' is null then 1 else 0 end) / count(*) as proportion_uninternalized
from solutions

0x064523df9bf2d9b907f20bbec50150d2ddd5721e66bd751c1f42447e96421bab

	#!/bin/bash

	# Space separated Array of Ethereum block numbers to fetch timestamps for
	blockNumbers=(18562256 18562257)

	ethRpc="https://rpc.ankr.com/eth"

	for blockNumber in "${blockNumbers[@]}"
	do
	data="{\"jsonrpc\":\"2.0\",\"method\":\"eth_getBlockByNumber\",\"params\":[\"0x$(printf '%x\n' $blockNumber)\", false],\"id\":1}"

	-- Dune Query for relevant views (postgres): https://dune.com/queries/1582621

	-- Below is a HiveSQL (pseudo code) schema with corresponding postgres types:

	-- TABLE 1: Order Rewards
	-- Update schedule: hourly
	-- Size: Currently 20k records this table will have approximately the same dimensions as number of trades on cow_prococol.

	-- The first three columns are on-chain verifyable,
	-- the json data field contains data from our orderbook DB.