OWNER ONLY
Profit Sharing Owner Panel
Connect the current contract owner wallet to continue.
OWNER CONTROL PLANE
Profit Sharing Owner Panel
Wallet not connected.
Environment
Contract overview
Owner
—
Pending owner
—
Automation bot
—
Bot wallet
—
System address
—
Token
—
Trading capital
—
Available liquidity
—
Unallocated referral shares
—
Profit split (I / S / R)
—
Deposit fee
—
Minimums (deposit / withdrawal)
—
Deposit lock
—
Safety flags (D / W / T)
—
Read contract state
These reads are safe and do not create a blockchain transaction.
| Read group | Available reads | Status |
|---|---|---|
| Ownership | owner(), pendingOwner() | Read-only |
| Accounting | tradingCapital(), totalShares(), availableLiquidity(), unallocatedReferralShares() | Read-only |
| Addresses | automationBot(), botWallet(), systemAddress(), token() | Read-only |
| Referral index | getReferralChildrenCount(), paginated getReferralChildren() | Read-only |
| Safety flags | depositsPaused(), withdrawalsPaused(), tradingPaused() | Read-only |
Contract actions
Each action is simulated against the current chain state before the wallet opens. A confirmed owner transaction is recorded in the server audit log.
Pause controls
Address rotation
Ownership
Ownership is two-step. The new wallet must accept on-chain.
Root wallets
Load contract to read roots.
User restrictions
Wallet replacement
Seize shares
Financial and referral controls
Server settings
Admin API is not connected.
The server session is authorized by the current contract owner wallet. Secrets are never returned to this page.
Bot service
Not connected
Database
Not connected
Exchange
Not connected
Last backup
Not connected
Current mode
Not connected
RPC health
Not connected
Runtime settings
Changes are validated and staged by the API. Use the owner-signed Restart bot action afterward to apply them to the running bot.
Server actions
Bot lifecycle
Backups
Approved read-only reports
These reports read current server, database, exchange, and contract state. They cannot change funds, orders, settings, or secrets.
Exchange balances
Referral status
Open positions
Recent settlements
Server settings policy
| Category | Examples | Change policy |
|---|---|---|
| Runtime | Intervals, reserve band, referral schedule | Validate, save, restart if required |
| Secrets | Bot key, exchange API, database password | Write-only rotation, never display |
| Dangerous actions | Live mode, close positions, key rotation | Second confirmation and audit log |
Secret rotation
Secrets are write-only. They are encrypted in a separate server volume, are never returned to this page, and take effect only after an owner-signed bot restart.
Bot private key
The derived wallet must already match both on-chain bot addresses.
Exchange credentials
The key and secret must be changed together. The values are not shown after saving.
Telegram alert token
Optional alert token rotation. Signal-login credentials remain server-managed until a dedicated safe flow is added.
Audit and safety
Wallet session
Owner signature required
Server session
Admin API required
High-risk actions
Confirmation required
Action history
| Time | Actor | Action | Result |
|---|---|---|---|
| Audit API is not connected. | |||