Sidiora

Asset Identity

Sidiora is the second official coin of Paxeer X. Its native denomination and ERC-20 interface represent one asset, giving wallets, contracts and Cosmos applications a consistent balance model.

PAX uses the base denom uhpx and eighteen decimals. Keep SID and PAX scaling separate in displays, approvals, transfer amounts, fee quotations and accounting. Read supply from the native bank state or ERC-20 totalSupply for a current value.

One Asset Across Native and EVM Interfaces

The native ERC-20 implementation reads balanceOf from the bank balance of the SID denom and totalSupply from its bank supply. Transfers move that denom through the bank precompile. A failed bank operation reverts the contract call. The pointer record resolves the denom to the same stable ERC-20 address.

The proxy address remains constant through implementation upgrades. Native token metadata and allowances use an ERC-7201 storage namespace that preserves legacy implementation slots. Applications query current allowances before building spending transactions and request the approval required by the current interface.

Bridge-Controlled Supply

The bridge module account administers the tokenfactory denom. Attested bridge-in credits mint SID and bridge-out operations burn the departing amount. Denom creation verifies the bridge-derived creator, expected admin and remote asset mapping. Ordinary holders and application contracts have no minting authority.

Two Ways to Pay Gas in SID

Sponsored Transaction Workflow

1. Build the application calls and request a sponsor quote for the declared gas cost.
2. Verify the configured sponsor, SID token, six-decimal units, chain ID, deadline, quoted amount and maximum.
3. Sign the account batch, covering its nonce, calls hash and quote digest, and authorize the EIP-7702 execution.
4. Execute through BatchCallAndSponsor; the account runs the calls and repays the sponsor in SID in the same transaction.

The sponsor signature binds chain ID, paymaster, sponsor, token, maximum amount, offered amount, deadline, quote nonce and declared gas cost. The account signature must recover to the account itself. Used quote nonces and account batch nonces prevent replay.

Pricing and Atomicity

The paymaster checks a positive, sufficiently fresh rate and requires the offered amount to fall within five percent of the amount implied by the declared gas cost. Expired quotes, zero amounts, an incorrect token or invalid sponsor are refused. A failed application call or SID repayment reverts the whole batch.

The gas station applies account, interval and quote budgets, a balance floor, and configured rate age, spread and margin limits. Missing or invalid pricing inputs produce a refusal. SDK signing helpers validate the returned quote and signatures locally before building executeSponsored.

Native Fee Preferences

The fee-token precompile at 0x0000000000000000000000000000000000001018 exposes the account preference:

function setFeeDenom(string calldata denom) external;
function getFeeDenom(address account) external view returns (string memory denom);
function clearFeeDenom() external;

Call setFeeDenom with the SID native denom to select it for the caller, query with getFeeDenom, or clear the preference to return to the network coin. Only allowed fee denoms can be selected. The precompile rejects value and delegatecall; static calls cannot change preferences.

Charging and Refunding

For EVM transactions, fee processing converts the maximum gas charge, including a blob fee when applicable, into the chosen denom. The account must have sufficient spendable SID for that charge and sufficient PAX for any transferred value. The fee debit replaces the PAX gas purchase.

The charge rounds up in the network's favor. Unused gas returns in the same denom, rounded in the payer's favor, while collection rounds down so refunds and collection cannot exceed the original debit. Cosmos transactions can offer allowed fee denoms, whose governed conversion is used for minimum-gas-price checks.

Governed Rates and Fee Routing

A native conversion rate is expressed in the fee denom's base units per whole network coin and records the block height at which it was set. Governance controls allowed denoms, enabled status, maximum rate age, spread and distribution policy. Unknown, nonpositive, future-dated or stale rates cause a refusal rather than a silent switch of fee asset.

Governance can route collected fee tokens into a named holding module account or retain them in the fee collector for distribution. PAX fees keep their ordinary collection path. Applications read current parameters before presenting a fee option, and re-estimate when a rate or policy changes.

Upgrade Authority

The Sidiora proxy timelock accepts only governance-scheduled upgradeToAndCall(address,bytes) operations targeting the proxy with zero value. The implementation must be a contract distinct from the proxy and timelock. Upgrade and initialization execute together.

A designated executor runs an operation after its delay and within its grace period. A guardian can cancel before readiness. The handover policy uses a two-day minimum delay, a one-day floor and a one-week execution window. These controls bound implementation changes while preserving the token address.

Integration Checklist

• Use six-decimal SID amounts and query the current balance and allowance.
• Resolve the native denom and stable ERC-20 address as the same asset.
• Display the signed sponsorship amount or estimated native fee in SID before approval.
• Distinguish gas from PAX value sent by the transaction.
• Refresh rates and quotes before submission and preserve transaction evidence for accounting.

Explore Unified Network, Contracts, Precompiles and xweb, which accepts SID for agent web requests.