account-management

Dual-account fund management on the 0G Compute Network splits balances between a Main Account for deposits and Provider Sub-Accounts for locked service funds. This architecture isolates per-provider liquidity and enforces the 24-hour refund lock automatically during service usage.

To deposit funds and allocate them to provider sub-accounts, first transfer balances to the Main Account via the 0g-serving-broker client. Then, transfer specific amounts to individual Provider Sub-Accounts to enable on-demand service usage and provider acknowledgement.

Yes, managing 0G account transfers requires a configured wallet, an RPC URL, and environment variables. These components are necessary to authenticate with the network and operate the 0g-serving-broker client for executing ledger operations.

Funds are locked for 24 hours during 0G refund processing to enforce network governance and compliance. The 24-hour refund lock ensures auto-deductions from provider sub-accounts are verified before balances are released back to the main ledger.

The best way to monitor main and sub-account balances for 0G compliance is by executing balance checks through the 0g-serving-broker client. This verifies liquidity across the dual-account system and confirms provider acknowledgement before transactions.

No, transferring funds directly to a provider without using the Main Account is not supported. The 0G dual-account system requires depositing into the Main Account first, then allocating specific amounts to Provider Sub-Accounts to maintain ledger governance.