Create and activate an account

Node, CLI, and RPC examples target FullOn Core v0.9.2. Contracts, CDT, and wallets have independent versions; their stated verification scope does not automatically change with Core. See version baseline and migration.

Prerequisites

You need an existing creator account, a local signing wallet satisfying its authority, the target RPC, owner/active public keys for the new account, and sufficient funding/resources. Users should generate and confirm their public keys; do not collect private keys.

This source-supported fucli system newaccount command submits a write transaction. Use an isolated development chain or verified testnet and replace example accounts, keys, and amounts.

export FULLON_RPC='http://127.0.0.1:8888'
export OWNER_PUBLIC_KEY='REPLACE_WITH_VALID_OWNER_PUBLIC_KEY'
export ACTIVE_PUBLIC_KEY='REPLACE_WITH_VALID_ACTIVE_PUBLIC_KEY'
fucli -u "$FULLON_RPC" system newaccount creatoracct newaccount11   "$OWNER_PUBLIC_KEY" "$ACTIVE_PUBLIC_KEY"   --fund-gas '1.0000 FLON' -p creatoracct@active
fucli -u "$FULLON_RPC" get account newaccount11

1.0000 FLON demonstrates syntax; it is not a promised registration fee or minimum gas amount. Verify the core symbol, precision, and current gas rules. The reviewed CLI requires at least one positive --fund-gas or --fund-account: the former buys gas, while the latter transfers core assets and does not necessarily buy gas.

fucli create account exposes basic native creation without the same funding steps. System-contract resource/naming restrictions still apply. The example uses a 12-character name; short names and dotted names have additional rules.

What does activation mean?

Identify the missing step: no on-chain account, wallet not imported, insufficient resources, or incomplete application authentication. The general creation path is newaccount. fucli system activate activates protocol features; it does not activate user accounts.

RWID creation

Do not bypass authentication services by copying ordinary account creation. The reference path calls auth → DAO → owner → system contract and sets a specific owner authority. Services must verify administrator permissions, authentication type, recovery policy, and deployed ABI. See RWID accounts.

Completion check

Keep the creation transaction ID, confirm successful irreversible execution, query owner/active and resources, then perform a controlled operation using the user's active authority.

Sources and scope

Source 1, Source 2. Source review: 2026-11-02. This does not verify the version deployed on every network.