Affix deployment to BOT chain

Summary

The Affix contracts were deployed to BOT chain (chain ID 677) with Foundry's forge script. Both contracts are verified on the chain's Blockscout explorer, scan.botchain.ai. The first entity, "Affix Official", is registered, and its first agent has issued its first document.

Deployer, factory owner and registry owner: 0x9747098f57D9D7994fe416e4160F2aD1D15F2a99.

Build settings

• Compiler: Solidity 0.8.30
• Optimizer: 10,000 runs
• EVM version: shanghai

Factory deployment

script/DeployAffixFactory.sol deploys AffixFactory through the Safe Singleton Factory at 0x914d7Fec6aaC8cd542e72Bca78B30650d45643d7. Because it uses CREATE2, the address can be computed before the deployment. The script did not detect the network, so its logs show "Unknown Network" and "Unknown explorer".

First a dry run:

forge script script/DeployAffixFactory.sol --rpc-url $BOT_RPC

Then the broadcast, with verification on Blockscout:

forge script script/DeployAffixFactory.sol --rpc-url $BOT_RPC --broadcast \
  --verify --verifier blockscout --verifier-url $BOT_SCAN

The script checked that the deployed address matched the expected one and that ownership was set to the deployer.

Entity registration

script/RegisterEntity.s.sol was updated with the new factory address, then run as a dry run and as a broadcast:

forge script script/RegisterEntity.s.sol --rpc-url $BOT_RPC
forge script script/RegisterEntity.s.sol --rpc-url $BOT_RPC --broadcast

The factory owner called registerEntity, which deployed a new AffixRegistry:

After registration the factory reported 1 entity in total.

The second command did not pass --verify, but Blockscout verified the registry automatically on 2026-10-15 through its Ethereum Bytecode Database, matching it against the sources submitted with the factory. It shows as a partial match.

First document

Agent 0xA3bc3Bb144f1E1834a1b92245BF10F33EB331557 was added to the registry, then issued the first document from the Affix web app. The app checked that the agent can issue documents, then called issueDocument(cid) on the registry, with no metadata:

Next steps

• Add more agents with addAgent(address). It is payable and needs at least 0.000001 ETH.
• Issue documents with metadata through issueDocumentWithMetadata(cid, metadata).

Broadcast receipts are in broadcast/DeployAffixFactory.sol/677/ and broadcast/RegisterEntity.s.sol/677/.

Further reading

• Foundry book: deploying and verifying
• Blockscout docs
• EIP-1014: Skinny CREATE2