Profit Sharing Owner Panel
Profit Sharing Owner Panel
Environment
Contract overview
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
Root wallets
User restrictions
Wallet replacement
Seize shares
Financial and referral controls
Telegram Signals
These values control signal sizing, leverage safety, staged exits, stop management, and position synchronization. Changes are validated, owner-signed, saved, and applied after a bot restart.
Risk and position sizing
Targets and stop management
Telegram source and cycle
Copy Trading Accounting
The accounting capital below is owner-published. The live Copy Trading balance is informational and is not used directly as profit or loss.
Trader accounts
| Name | Accounting capital | Live Copy Trading balance | Version | Status |
|---|---|---|---|---|
| No data loaded. | ||||
Add trader
Only a display name is required. The internal trader ID is generated by the system.
Draft accounting adjustment
The change remains a Draft until published by the owner. Changes above 10% require an additional confirmation.
Adjustment history
| Time | Trader | Operation | Previous | New | Transfer | Status | Action |
|---|---|---|---|---|---|---|---|
| No history loaded. | |||||||
Server settings
The server session is authorized by the current contract owner wallet. Secrets are never returned to this page.
Runtime settings
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
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
Action history
| Time | Actor | Action | Result |
|---|---|---|---|
| Audit API is not connected. | |||