github.com/Uomi-network/uomi-node @v0.3.8

Empowering Ai Agents to Transform the Physical World through Economic Agency

Creating new forms of digital life capable of sustaining themselves by delivering value to humans.

Building From Source

This section assumes that the developer is running on either macOS or Debian-variant operating system. For Windows, although there are ways to run it, we recommend using WSL or from a virtual machine for stability.

# install Substrate development environment via the automatic script
$ curl https://getsubstrate.io -sSf | bash -s -- --fast

# clone the Git repository
$ git clone --recurse-submodules https://github.com/Uomi-network/uomi-node.git

# change current working directory
$ cd uomi-node

# setup hooks (for conventional commits)
$ sh ./scripts/setup-hooks.sh

# download ipfs clients required for building and store them on ./client/ipfs-manager/src/
wget https://storage.uomi.ai/ipfs_linux_amd64 -O ./client/ipfs-manager/src/ipfs_linux_amd64
wget https://storage.uomi.ai/ipfs_linux_arm64 -O ./client/ipfs-manager/src/ipfs_linux_arm64
wget https://storage.uomi.ai/ipfs_macOS -O ./client/ipfs-manager/src/ipfs_macOS

# compile the node
# note: you may encounter some errors if `wasm32-unknown-unknown` is not installed, or if the toolchain channel is outdated
$ cargo build --release

# show list of available commands
$ ./target/release/uomi --help

Running a node

You can run a node and connect to the Uomi network by running the following command:

./target/release/uomi \
--base-path <path to save blocks> \
--chain <chain name> \
--name <node display name>  \
--port 30333 \
--rpc-port 9944 \
--validator

Now, you can obtain the node's session key by sending the following RPC payload.

# send `rotate_keys` request
$ curl -H 'Content-Type: application/json' --data '{ "jsonrpc":"2.0", "method":"author_rotateKeys", "id":1 }' localhost:9944

# should return a long string of hex, which is your session key
{"jsonrpc":"2.0","result":"<session key in hex>","id":1}

After this step, you should have a validator node online with a session key for your node.

Workspace Dependency Handling

All dependencies should be listed inside the workspace's root Cargo.toml file. This allows us to easily change version of a crate used by the entire repo by modifying the version in a single place.

Right now, if non_std is required, default-features = false must be set in the root Cargo.toml file (related to this issue). Otherwise, it will have no effect, causing your compilation to fail. Also package imports aren't properly propagated from root to sub-crates, so defining those should be avoided.

Defining features in the root Cargo.toml is additive with the features defined in concrete crate's Cargo.toml.

Adding Dependency

1. Check if the dependency is already defined in the root Cargo.toml
   1. if yes, nothing to do, just take note of the enabled features
   2. if no, add it (make sure to use default-features = false if dependency is used in no_std context)
2. Add new_dependency = { workspace = true } to the required crate
3. In case dependency is defined with default-features = false but you need it in std context, add features = ["std"] to the required crate.

Further Reading

• Whitepaper
• Website

EVM / Frontier Smoke Tests

After starting a local development node (--dev), you can quickly verify EVM functionality and the Frontier upgrade:

1. Deploy and interact with a simple Solidity counter: bash cargo run --example deploy_counter Expected output (abridged):

   • "Deploying Counter..."
   • "Deployed at: 0x..."
   • "inc tx included in block ..."
   • "Success: Counter incremented."

2. (Experimental) Submit a raw EIP-7702 transaction (typed 0x04): bash cargo run --example eip7702_send # customize the ephemeral authorization code + RPC endpoint AUTH_CODE=0x6001600055 RPC_HTTP=http://127.0.0.1:9933 cargo run --example eip7702_send # let the helper auto-raise fees to satisfy the current base fee AUTO_ADJUST_GAS=1 cargo run --example eip7702_send # provide explicit EIP-1559 style fee caps (values in wei) MAX_PRIORITY_FEE=1500000000 MAX_FEE=60000000000 cargo run --example eip7702_send Layout encoded (type byte 0x04 + RLP list): [chainId, nonce, maxPriorityFeePerGas, maxFeePerGas, gasLimit, to, value, data, authorizationBytes, accessList] then signature fields [yParity, r, s].

   Environment variables (all optional): - RPC_HTTP: HTTP RPC endpoint (default http://127.0.0.1:9933) - AUTH_CODE: Hex bytecode injected ephemerally for this tx (default 0x6001600055 which sets storage slot 0 to 1) - NONCE: Override the sender account nonce (otherwise fetched via eth_getTransactionCount) - GAS_LIMIT: Hex or decimal gas limit (default 0x5208 = 21000) - MAX_PRIORITY_FEE: Tip (wei). If unset we default to a small constant (1 gwei unless auto-adjust bumps it) - MAX_FEE: Max fee per gas cap (wei). If unset we start with base heuristic (2 * priority or small default) - AUTO_ADJUST_GAS=1: Fetch latest block baseFee and, if (baseFee + priority) > MAX_FEE (or MAX_FEE unset), raise MAX_FEE to (baseFee * 2 + priority) so the tx isn't rejected with "gas price less than block base fee". - SILENT=1: Reduce logging noise (if implemented later; currently ignored)

   Notes: - authorizationBytes is a single ephemeral code blob (NOT a list of delegates) - yParity is stored as 0/1 (derived from signature.v - 27) - A rejection "gas price less than block base fee" means structural decoding succeeded; raise MAX_FEE or set AUTO_ADJUST_GAS=1 - If you see "decode transaction failed" verify your Frontier version still matches this field ordering and TxType=0x04; adjust if upstream changes.

3. Inspect the deployed contract code: bash curl -H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"eth_getCode","params":["<COUNTER_ADDRESS>", "latest"]}' \ http://127.0.0.144

4. (Optional) Verify storage / call path: Use eth_call with the ABI selector for value() to confirm the increment.

If you modify precompiles or upgrade Frontier again, re-run these examples to ensure no regressions in basic deployment / execution or in 7702 acceptance.

Development

Running node locally for development purposes is simple. After the node is compiled (see above), run the following command:

./target/release/uomi --base-path /tmp/alice --dev --alice 

To start multiple nodes you can use foreman. First, install it with gem install foreman. Then run the following command:

foreman start -f Procfile.dev

After the setup of nodes you need to insert keys inside the pallets using the following command:

curl -H "Content-Type: application/json" \
-d '{"id": 1, "jsonrpc":"2.0", "method": "author_insertKey", "params":["ipfs", "//Alice//stash", "0xbe5ddb1579b72e84524fc29e78609e3caf42e85aa118ebfe0b0ad404b5bdd25f"]}' \
http://localhost:9944 

curl -H "Content-Type: application/json" \
-d '{"id": 1, "jsonrpc":"2.0", "method": "author_insertKey", "params":["uomi", "//Alice//stash", "0xbe5ddb1579b72e84524fc29e78609e3caf42e85aa118ebfe0b0ad404b5bdd25f"]}' \
http://localhost:9944 

curl -H "Content-Type: application/json" \
-d '{"id": 1, "jsonrpc":"2.0", "method": "author_insertKey", "params":["uomi", "//Bob//stash", "0xfe65717dad0447d715f660a0a58411de509b42e6efb8375f562f58a554d5860e"]}' \
http://localhost:9945 

curl -H "Content-Type: application/json" \
-d '{"id": 1, "jsonrpc":"2.0", "method": "author_insertKey", "params":["ipfs", "//Bob//stash", "0xfe65717dad0447d715f660a0a58411de509b42e6efb8375f562f58a554d5860e"]}' \
http://localhost:9945 

curl -H "Content-Type: application/json" \
-d '{"id": 1, "jsonrpc":"2.0", "method": "author_insertKey", "params":["uomi", "//Charlie", "0x1e07379407fecc4b89eb7dbd287c2c781cfb1907a96947a3eb18e4f8e7198625"]}' \
http://localhost:9946 

curl -H "Content-Type: application/json" \
-d '{"id": 1, "jsonrpc":"2.0", "method": "author_insertKey", "params":["ipfs", "//Charlie", "0x1e07379407fecc4b89eb7dbd287c2c781cfb1907a96947a3eb18e4f8e7198625"]}' \
http://localhost:9946

Rotate key

curl -H "Content-Type: application/json" \
-d '{"id": 1, "jsonrpc":"2.0", "method": "author_rotateKeys", "params":[]}' \
http://localhost:9946