Next Milestone
Persistent wallet state, richer send confirmation, and deeper desktop-wallet style navigation are the next layer after the current public workspace.
CPH Core
Independent chain operations, public explorer access, and bootstrap-era network visibility.
Wallet Workspace
This workspace is the bridge between the current command-backed wallet MVP and the fuller standalone wallet app. It keeps receive, send, history, support, and public chain state in one calmer place while remaining honest about the current Core-backed workflow underneath.
Wallet Workspace Status
Wallet MVP Live
The first public wallet surface is active. You can create or load a wallet, generate receive addresses, inspect balances and maturity, stage labels and address book notes, and track the live public chain while the workspace keeps growing.
Workspace Focus
The wallet workspace is built to reduce context switching. Move from a receive address to a send review, then into history and public explorer checks without losing sight of the live chain state.
Next Milestone
Persistent wallet state, richer send confirmation, and deeper desktop-wallet style navigation are the next layer after the current public workspace.
Generate Receive Address
Move from wallet creation to a fresh bech32 receive slot, then confirm it on-chain.
Open ReceivePrepare a Send
Check trusted funds first, then use the current send flow with a small test output.
Open Send GuideReview Transactions
Inspect history, confirmations, and txids before or after each move.
Open HistoryGet Help Fast
Use the support lane when wallet state, sync, or rewards look confusing.
Open SupportWallet Session Snapshot
Public Chain
4 blocks
Public chain live. Connected to 5 public peers.Receive Slot
Load a receive slot
Load a real cph1... address to turn the receive desk into a live share surface.Send Draft
Draft not loaded
Stage a destination + amount to make the send workspace feel like a real review lane.History Anchor
Awaiting txid
Load a txid after send or use a receive slot for explorer-backed history review.Workspace Memory
This preview now remembers the current receive slot, send draft, label pack, and tx inspector locally so you can come back to the same flow without rebuilding every field by hand.
Saved Receive Slot
Not saved yet
Bech32 receive address staged in this browser.Saved Send Draft
Not saved yet
Destination and amount are restored into the send composer.Saved Label Pack
Not saved yet
Label and entry stay paired with the current wallet note.Saved Inspector
Not saved yet
Tx drill-down returns with the same explorer anchor.Workspace drafts are stored only in this browser and can be restored into the current wallet view.
Workspace Tabs + Draft Queue
Pin the current receive/send/history state as a tab, queue a draft for later review, or clear the local queue when the workspace is stable. Each saved session keeps the current label, entry, address, amount, favorite state, and tx inspector anchor together.
Saved tabs and queued drafts stay only in this browser until you restore, export, or clear them.
No saved workspace tabs yet
Save the current wallet session as a tab or queue a draft to build a multi-session wallet workspace.
Browser-local onlyWorkspace Backup Pack
The workspace can now export a browser-local pack with the current receive slot, send draft, labels, note, favorite state, tx inspector, and pinned address book entries. Import the same pack later or copy a support snapshot when you need another operator to inspect the same state.
Export keeps the current wallet workspace and local address book together in one browser-local handoff pack.
Workspace Backup Pack
Support Handoff Pack
Session Label
Wallet Session
Use this as the top-level shorthand when you describe the current wallet context to another operator or support contact.
Entry + Favorite
Address Book Pending / Standard Entry
Contact name and favorite state stay paired so pinned entries remain readable outside the wallet view.
Current Note
Add a short local note for destination, purpose, or support context.
Local context is carried into the handoff pack so support or treasury review can reference the same intent.
Wallet Anchor
Not loaded yet
A receive slot or destination makes the handoff concrete enough to inspect locally and publicly.
Transaction Anchor
Awaiting txid
Load a txid after send or inbound receipt to make the support handoff even stronger.
Explorer Path
https://cphcore.org/wallet/app
This is the public chain path that support can open alongside the wallet workspace.
Receive Desk
Bech32 Receive Slot
Load a real cph1... address to turn this desk into a live receive surface.
Receive Share Pack
Open receive screen
Use the dedicated receive desk when you want the full address, URI, QR, and explorer share surface.
Open ReceiveOpen QR-ready receive surface
Paste a real address from your wallet and turn it into a shareable receive request with QR export.
Build Receive ViewCross-check on explorer
Once funds arrive, verify the same address or txid on the public chain before you treat it as final proof.
Review Receive GuideLoad or create the wallet
Start by loading the wallet you want to use. If it does not exist yet, create it once and keep reusing that wallet name.
.\cli.cmd loadwallet mywallet
Generate a fresh receive address
Use a new bech32 address for each payout or transfer when possible. This keeps incoming activity easier to inspect.
.\cli.cmd -rpcwallet=mywallet getnewaddress "" bech32
Cross-check in the explorer
After an address is generated and later funded, inspect it in the public explorer to verify unspent outputs and chain visibility.
https://cphcore.org/address/<your_cph_address>
Send Composer
Destination
cph1q...paste-destination-address
Paste the exact bech32 destination you intend to fund.
Amount
0.25000000 CPH
Start with a small test amount before you stage larger spends.
Draft Mode
Outgoing test send
Stage a small outbound transfer first, then confirm the txid and destination before you scale up.
Wallet State
Track trusted vs immature
Trusted, pending, and immature buckets stay separate inside the workspace on purpose.
Send Review Rail
Trusted balance first
Do not send against immature mining rewards. Confirm the trusted bucket before you move funds.
Destination reviewed twice
Bech32 addresses are long. Recheck the first and last characters before you hit send.
Capture the txid
The txid is your proof path for history, explorer checks, and support follow-up if anything looks off.
Explorer confirmation pass
After sending, inspect the same txid on the public explorer so the wallet and public chain agree.
Send Confirmation Cards
Review Window
4 blocks
Keep the public chain height in sight while you prepare a spend or inspect a recent transfer.
Draft Status
Stage a destination first
The send composer becomes more concrete once a real destination is loaded.
Receive Cross-check
Load receive slot
Load the current receive slot so send/history review stays anchored to one wallet session.
History Anchor
Awaiting txid
Capture the txid after send so support and explorer checks point at the same transfer.
Send Confirmation Sheet
Spend Window
4 blocks
The send sheet stays anchored to the live public chain height so you know which confirmation window you are reviewing against.
Destination Anchor
Awaiting destination
Load a destination address before you treat the send sheet as a real transfer review.
Funding Bucket
Track trusted vs immature
Trusted, pending, and immature balances stay separate here so the send review does not blur spendable funds with reward state.
Explorer Handoff
Awaiting txid or receive anchor
Once you load a txid or receive slot, this send sheet can hand off directly into the public explorer.
Confirm matured balance first
Do not confuse immature mining rewards with spendable balance. Check trusted, untrusted, and immature buckets before sending.
.\cli.cmd -rpcwallet=mywallet getbalances
Send with an exact destination
Use sendtoaddress with the destination and amount. Start with a small test transfer first if you are moving funds to a new address.
.\cli.cmd -rpcwallet=mywallet sendtoaddress "<destination_cph_address>" 1.25000000
Capture the txid
The send command returns a transaction id. Keep it so you can inspect the transfer in both the wallet and the public explorer.
.\cli.cmd -rpcwallet=mywallet gettransaction "<txid>"
Verify confirmation state
Check the resulting txid against the explorer or your wallet history so you can see confirmations and final chain placement.
https://cphcore.org/tx/<txid>
Labels + Address Book
Add a short local note for destination, purpose, or support context.
Address Book Preview
Current Label
Stage a short label so receive slots and send drafts are easier to recognize later.
Wallet SessionAddress Book Entry
Use an entry name like Treasury Desk, Mining Wallet, or Payroll to keep repeat destinations readable.
Address Book PendingCurrent Anchor
Load a receive slot or destination to attach a real address to this staged entry.
Not loaded yetExplorer Pairing
Once you load a txid or receive slot, the address book view gains a public explorer handoff.
Waiting for explorer anchorPinned Metadata
Address Book Inspector
Session Label
Wallet Session
Use short human names that still make sense when you revisit the wallet days later.
Book Entry
Address Book Pending
A desk, person, or purpose tag keeps repeat destinations from blending together.
Linked Address
Not loaded yet
No concrete address is staged yet. Load a receive slot or destination to complete the book entry.
Explorer Match
https://cphcore.org/wallet/app
Cross-check the same label pack on the public chain when a txid or receive slot is available.
Pinned Address Book
Save the current receive or send context as a reusable wallet entry, then restore it back into the workspace later without rebuilding the same labels and addresses by hand.
Saved entries stay only in this browser and can be restored into the current wallet workspace.
No pinned entries yet
Save a receive slot or send draft here to build a small local wallet address book.
Browser-local onlyLabeling Guide
Keep labels short and human
Names like Mining Wallet, Treasury Desk, or Payroll are easier to scan than long free-form notes.
Attach one label to one active story
Use the same label across receive, send review, and history inspection so support checks stay coherent.
Fresh receive slots still matter
A clean label works best when it maps to a fresh receive slot instead of an address you reuse everywhere.
Cross-check labels with explorer anchors
Once you have a txid or receive address, confirm the same label pack against the public explorer before you assume the state is final.
History Desk
List recent wallet activity
Use listtransactions to see incoming, outgoing, and generated entries. This is the current live history surface for the wallet MVP.
.\cli.cmd -rpcwallet=mywallet listtransactions
Inspect detailed transaction metadata
Use gettransaction when you need confirmations, fee details, or raw transaction references for one specific item.
.\cli.cmd -rpcwallet=mywallet gettransaction "<txid>"
Track reward maturity
Mining rewards appear as immature first, then move into trusted balance once enough blocks pass.
.\cli.cmd -rpcwallet=mywallet getbalances
Activity Filters
Mining Rewards
Track trusted vs immature
Use this lane when you want to follow immature rewards until they graduate into trusted balance.
Incoming Receives
No receive slot loaded
Load a receive slot to filter history around one concrete inbound address.
Outgoing Sends
No destination staged
Stage a destination to turn the history desk into an outbound send review surface.
Explorer / Support
Waiting for anchor
Load a txid or receive slot before you hand this activity review to support or explorer cross-check.
Transaction Detail Cards
Current Focus
Stage a small outbound transfer first, then confirm the txid and destination before you scale up.
Outgoing test sendLoaded Txid
No txid is loaded yet. Use a real txid after send or after an inbound transfer lands.
Awaiting txidExplorer Match
Once you load a txid or receive slot, this history desk becomes the bridge to public chain detail.
Waiting for anchorMaturity Path
Use getbalances and the public chain height together when you want to understand reward maturity.
Track trusted vs immatureTransaction Inspector
Transaction ID
Awaiting txid
Load a txid after send or after an inbound payment so the inspector has a concrete anchor.
Direction + Amount
Outgoing test send / 0.25000000 CPH
Keeping the amount and direction together makes wallet history easier to compare against local notes.
Explorer Match
Waiting for txid or address
Load a txid or receive slot to generate a concrete public explorer cross-check path.
Session Anchor
Destination not staged
No receive or destination anchor is loaded yet.
Transaction Drill-Down
Inspector Stage
Load a txid to turn the inspector into a real drill-down surface.
Awaiting txidDirection Story
Direction, amount, and destination stay empty until you stage a concrete send or receive review.
Wallet SessionAddress Book Match
Attach a label or address book entry so the tx review reads like a real wallet note.
Address Book PendingPublic Explorer Drill-down
Load a txid or receive slot to unlock the public explorer drill-down.
Waiting for txidConfidence + Proof
Load the txid
The txid is the anchor that makes wallet history, support, and explorer review point at the same transfer.
Attach direction + label
Treat direction, amount, and your address book label as one story so future review stays readable.
Open the explorer match
Use the explorer handoff to confirm block placement and chain visibility for the same txid or receive slot.
Compare maturity and confirmations
The wallet and explorer should tell the same story about confirmations and immature versus trusted state.
Transaction Proof Drawer
Proof Mode
This workspace is still local-only until a txid or receive slot is loaded.
Workspace draftProof Anchor
Txid, receive slot, or destination anchor that defines the current review thread.
wallet-workspace-anchor-pendingExplorer Target
Once a txid or receive slot is present, the drawer points at a concrete public explorer page.
Workspace-only draftChain Witness
Use peers, height, and maturity together when you want a proof pack that stays grounded in the live network.
5 peers / 4 blocksProof Snapshot
Copy this handoff pack when you need to move a tx review, reward state, or explorer cross-check into support or another wallet desk.
CPH Wallet Proof Snapshot Label: Wallet Session Entry: Address Book Pending Direction: Outgoing test send Amount: 0.25000000 CPH Receive Slot: Not loaded Destination: Not staged Txid: Awaiting txid Explorer: https://cphcore.org/wallet/app Chain: 4 blocks Peers: 5 Maturity: Track trusted vs immature Favorite: Standard Entry Note: Add a short local note for destination, purpose, or support context.
Load a txid or receive slot to turn the proof drawer into a public-chain handoff pack.
Transaction Timeline
Draft Review
Wallet Session / Address Book Pending
The current wallet workspace is staged as a named review thread you can share, restore, or hand off.
Anchor State
wallet-workspace-anchor-pending
Load a txid, receive slot, or destination to turn this workspace into a concrete proof thread.
Confirmation Window
4 blocks
The proof pack records the public chain height visible when this review surface was assembled.
Maturity Track
Track trusted vs immature
Reward and transfer state stays attached so support can explain trusted, pending, or immature balance movement.
Proof Snapshot
Wallet Session / Address Book Pending
Session label and entry travel together so support, treasury, or explorer review all talk about the same wallet moment.
Wallet Anchor
Not loaded yet
Receive slot or destination that keeps the proof pack attached to a real wallet surface.
Transaction Story
Outgoing test send / 0.25000000 CPH
Direction, amount, and txid context are grouped here before you hand the proof pack to someone else.
Trust Window
Track trusted vs immature
Trusted, pending, and immature remain separate so the proof drawer does not blur spendable balance with draft or mining state.
Activity Rail
Mining rewards enter as immature first
Newly mined rewards appear in the wallet before they become trusted. This is expected and mirrors the network maturity rules.
Balance bucket transitionRecent transfers should be cross-checked by txid
After a send, keep the txid and inspect it with gettransaction and the explorer so the wallet and public chain tell the same story.
Wallet + explorer disciplineAddress reuse is optional, but fresh receive slots stay cleaner
Generating a new address for each payment makes future history and bookkeeping easier once the wallet surface grows further.
Receive hygieneNetwork + Maturity
Node Loaded
Your wallet surface starts from a live local node that is already done loading.
Public Peers Online
Stay attached to the shared public chain so balances, maturity, and explorer state match the same network.
Wallet Loaded
Use one named wallet consistently so receive, send, and history all land in the same place.
Explorer Cross-Check
When something matters, compare wallet state against the public explorer before assuming a bug.
Balance States
Trusted
Spendable balance currently recognized by the wallet as safe to use.
Untrusted Pending
Pending wallet activity that exists but is not yet considered fully settled.
Immature
Mining rewards that exist on chain but still need more blocks before they become spendable.
Explorer Cross-Check
Use the public explorer to verify the same address or txid against the chain the whole network can see.
Workspace Focus
A cleaner operating surface for public users while the deeper app continues to grow.
Receive Desk
Generate a fresh bech32 address locally, copy it into your workflow, and confirm the result in the explorer once funds arrive.
Address generation + explorer checkSend Desk
Check trusted balance first, send carefully, and keep the txid so you can confirm the payment on the public chain.
Destination + amount + txidHistory Desk
Use the live RPC-backed commands to inspect incoming funds, outgoing transfers, and mined rewards while a richer wallet UI is layered on top.
listtransactions + gettransactionAddress Book Desk
Stage labels, keep repeat destinations readable, and tie the same names into explorer checks and transaction review.
Labels + book entries + history anchorsSupport Desk
If anything looks wrong, open Troubleshooting or jump to Discord before assuming a wallet or chain bug.
Guides + community path