Technical Reference

SHIOFactory

Source updated:
Last updated:
Source Revision 0x889e3d1b…397a87
Property Value
Source Revision 0x889e3d1bb18d39a8235bd9117a4bb6caefc6c8655cc6785bfbf0117523397a87
Source URL https://raw.githubusercontent.com/busytoby/atropa_pulsechain/10e0bda9d99502c2d9125b37bbe56a111a5b2bb7/solidity/dysnomia/03c_shiofactory.sol
Source commit 10e0bda9d99502c2d9125b37bbe56a111a5b2bb7
Source Status Source snapshot; source hashes do not establish deployed bytecode equivalence.
Compiler solc 0.8.21; optimizer enabled with 200 runs
Compiler Configuration {"evmVersion":"compiler-default","optimizer":{"enabled":true,"runs":200},"version":"0.8.21+commit.d9974bed.Linux.g++"}
Compilation Closure Hash 0xd8ed6abda0f0b370c794fccf7789e9e7e19c035cd0543335f680ddc6db97357e
Compilation Closure Files 7
Hash Generated 2026-04-20T02:38:19Z

SHIOFactory is a factory contract for deploying new SHIO token instances with proper ownership configuration for both the SHIO and its underlying SHA tokens.

  • Kind: Contract
  • License: Sharia
  • Solidity: ^0.8.21
  • Source: 03c_shiofactory.sol
Contract address:
0x5063D2A97960DDE8dc5E3e5A69aAa379C6301F1C

No base contracts; this contract has no parents.

None (root of its hierarchy).

Plain English Summary: SHIOFactory assembles your paired lock system. It takes two SHA keys (Rod and Cone) and welds them together into a SHIO pair. This factory handles the complex wiring that lets your two keys work in harmony for chat, identity, and reactions.

Real-World Analogy: Imagine a locksmith who specializes in two-key safes. You bring them two separate keys, and they install them into a single lock mechanism that requires both keys to work together. That’s what SHIOFactory does with Rod and Cone tokens.

How It Affects Your Gameplay:

  • Pair creation - Your SHIO pair is assembled here during account creation
  • Integrated ownership - The SHIO automatically gets permission to use its Rod and Cone
constructorconstructor
constructor()
Newfunction
function New(address Rod, address Cone, address MathLib) public returns (SHIO Zeta)

Open this function to load its call form.

  • Visibility: public
  • Parameters: address Rod, address Cone, address MathLib
  • Returns: SHIO Zeta
  • SHIO - Contract being deployed
  • SHA - Rod and Cone tokens
  • YI - Uses factory to create SHIO pairs
1. Factory deploys SHIO(Rod, Cone, MathLib)
2. Factory adds msg.sender as SHIO owner
3. Factory adds tx.origin as SHIO owner
4. Factory renounces its ownership of SHIO
5. Factory adds SHIO address as owner of Rod SHA
6. Factory adds SHIO address as owner of Cone SHA

This ensures:

  • The calling contract and human initiator own the SHIO
  • The SHIO can manipulate its Rod and Cone tokens
  • The factory retains no control
// From YI contract
SHA Rod = SHAFactoryInterface.New("Shio Rod", "SROD", MathLib);
SHA Cone = SHAFactoryInterface.New("Shio Cone", "SCONE", MathLib);
SHIO Psi = SHIOFactoryInterface.New(address(Rod), address(Cone), MathLib);

The compiled ABI below is produced by solc 0.8.21 from the exact source bytes recorded in Source details. Consumers can paste it directly into ethers/web3/viem.

Click to expand JSON ABI
[
{
"inputs": [],
"stateMutability": "nonpayable",
"type": "constructor"
},
{
"inputs": [
{
"internalType": "address",
"name": "Rod",
"type": "address"
},
{
"internalType": "address",
"name": "Cone",
"type": "address"
},
{
"internalType": "address",
"name": "MathLib",
"type": "address"
}
],
"name": "New",
"outputs": [
{
"internalType": "contract SHIO",
"name": "Zeta",
"type": "address"
}
],
"stateMutability": "nonpayable",
"type": "function"
}
]