> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/core-concepts/wallet-permissions-and-transaction-intent.md).

# Wallet, permissions & transaction intent

Role-based access, verified wallet ownership, signatures, transaction intent and Solana settlement.

A connected wallet proves availability of an address/session context; it does **not** authorize arbitrary transactions.

## Authority chain

```
SIGNED SESSION
  ↓ userId + tenantId
TENANT ACCOUNT
  ↓ role + permissions
VERIFIED WALLET LINK
  ↓ address ownership only
TRANSACTION INTENT
  ↓ recipient + mint + atomic amount + decimals + expiry
WALLET SIGNATURE
  ↓ evidence
SUBMITTED → PROCESSED → CONFIRMED → FINALIZED
  ↓ threshold-aware reconciliation
BUSINESS SETTLEMENT
```

`userId`, tenant identity, role and permissions are derived server-side. A client cannot self-assign a role, tenant, verified-wallet state or entitlement.

## Roles and permissions

SONIC currently models creator, producer, artist, manager, project-admin, finance, treasury, tenant-admin and super-admin roles. Sensitive capabilities such as fee-policy writes, treasury execution, reward allocation, transaction reconciliation and member-role changes require explicit permissions.

Wallet/token balance never creates Admin, Finance, Treasury or Super Admin authority.

## Validation contract

Before transaction preparation, validate:

* exact Solana public key: base58 decoded length **32 bytes**;
* exact Solana transaction signature: base58 decoded length **64 bytes**;
* expected cluster/network;
* verified source wallet ownership;
* recipient;
* mint/currency identity;
* **positive integer atomic amount**;
* explicit decimals;
* purpose, expiry and settlement threshold.

A signature cannot be silently rebound to another business intent. Chain state progresses monotonically through submitted, processed, confirmed, finalized or failed.

## No fabricated balances

If RPC is unavailable or returns malformed balance data, SONIC reports the balance as unavailable. It does not convert provider failure into a synthetic `0`. A real zero is valid only after a successful on-chain read.

## Reward claims

Claim creation requires the authenticated creator, the verified recipient wallet and a claimable/funded reward allocation. The resulting transaction intent uses threshold-aware reconciliation; production reward claims default to finalized unless explicitly configured otherwise.

## Commercial finality

Settled Marketplace payments are final. Public customer refund routes are disabled. Technical release of a held AI-credit reservation before settlement is a separate ledger behavior and is not a commercial refund.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/core-concepts/wallet-permissions-and-transaction-intent.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.