> For the complete documentation index, see [llms.txt](https://timechain.gitbook.io/neucron/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://timechain.gitbook.io/neucron/changelog.md).

# Changelog

Track meaningful changes to Neucron across product capabilities, APIs, SDKs, supported networks, assets, compliance requirements, and documentation.

Neucron is wallet infrastructure for fintechs. Changes can affect production payment flows, embedded wallets, treasury operations, approval policies, reconciliation, and agentic finance workflows. Use this changelog to understand what changed, whether action is required, and which docs to read next.

## How to read this changelog

Each entry should identify:

| Field           | Meaning                                                             |
| --------------- | ------------------------------------------------------------------- |
| Date            | The date the change became available or was documented.             |
| Area            | Product, API, SDK, network, asset, compliance, docs, or operations. |
| Change type     | Added, changed, deprecated, fixed, removed, or roadmap.             |
| Impact          | Who should care and what may need to be updated.                    |
| Action required | Migration, configuration, testing, review, or no action.            |
| Related docs    | Links to implementation docs, API reference, or use-case guides.    |

## Current release notes

### 2026-07-28: Documentation overhaul for fintech wallet infrastructure

**Area:** Docs\
**Type:** Added\
**Impact:** All builders evaluating or integrating Neucron\
**Action required:** Review the new conceptual and use-case docs before designing a production integration.

Neucron's master documentation was reorganized around fintech whitelabel wallet infrastructure. The new structure explains blockchains as payment rails, wallet custody models, MPC key shards, businesses and apps, payment workflows, treasury operations, network and asset support, compliance levels, and agentic wallets.

Added sections:

* [Core Concepts](https://timechain.gitbook.io/neucron/core-concepts/blockchains-as-rails)
* [Use-Case Guides](https://timechain.gitbook.io/neucron/use-case-guides)
* [Payments](https://timechain.gitbook.io/neucron/payments/invoices-and-payment-links)
* [Networks & Assets](https://timechain.gitbook.io/neucron/networks-and-assets/supported-networks)
* [Go-Live Checklist](https://timechain.gitbook.io/neucron/go-live-checklist)

### 2026-07-28: Use-Case Guides added

**Area:** Docs\
**Type:** Added\
**Impact:** Product, engineering, and implementation teams building end-to-end fintech workflows\
**Action required:** Start from the guide that matches your product, then follow linked concept and API pages.

Added end-to-end guides for:

* [Launch a Whitelabel Wallet App](https://timechain.gitbook.io/neucron/use-case-guides/launch-a-whitelabel-wallet-app)
* [Accept Stablecoin Payments](https://timechain.gitbook.io/neucron/use-case-guides/accept-stablecoin-payments)
* [Embed Non-Custodial Wallets](https://timechain.gitbook.io/neucron/use-case-guides/embed-non-custodial-wallets)
* [Automate Accounts Payable](https://timechain.gitbook.io/neucron/use-case-guides/automate-accounts-payable)
* [Deploy an Agentic Treasury Agent](https://timechain.gitbook.io/neucron/use-case-guides/deploy-an-agentic-treasury-agent)

### 2026-07-28: Network and asset support documentation added

**Area:** Networks and assets\
**Type:** Added\
**Impact:** Teams choosing rails, assets, and settlement policies\
**Action required:** Confirm live support and roadmap status before enabling an asset or rail in production.

Added dedicated docs for:

* [Supported Networks](https://timechain.gitbook.io/neucron/networks-and-assets/supported-networks)
* [Asset Protocols & Types](https://timechain.gitbook.io/neucron/networks-and-assets/asset-protocols-and-types)
* [Assets: Live & Upcoming](https://timechain.gitbook.io/neucron/networks-and-assets/assets-live-and-upcoming)

### 2026-07-28: API reference wording cleanup

**Area:** API and docs\
**Type:** Changed\
**Impact:** Developers reading generated API reference and Swagger docs\
**Action required:** No integration action required.

API reference wording was cleaned and generalized around supported blockchain rails and assets.

## Release-note categories

Use these categories when publishing future entries.

### Product

Use for changes to Neucron product capabilities, such as new business workflows, app capabilities, team permissions, treasury controls, invoice behavior, payout behavior, or agentic wallet patterns.

### API

Use for endpoint additions, request or response schema changes, authentication behavior, new webhooks, pagination changes, error semantics, deprecations, and breaking changes.

API entries should include:

* Endpoint or resource affected.
* Whether the change is backward compatible.
* Migration steps.
* Test cases fintechs should run.
* Deadline for deprecated behavior, if any.

### SDK

Use for TypeScript SDK releases and future SDKs.

SDK entries should include:

* Package name and version.
* New methods or changed method signatures.
* Minimum Node or runtime version, if relevant.
* Migration notes.
* Link to SDK docs.

### Networks and assets

Use for newly supported chains, asset protocols, assets, webhooks, testnet status, or roadmap changes.

Network and asset entries should include:

* Rail.
* Asset or protocol.
* Supported functions: balance, send, receive, webhook, issuance, payout, or payment-link clearing.
* Environment: testnet, mainnet, sandbox, or roadmap.
* Any operational limits.

### Compliance and verification

Use for changes to KYC, KYB, verification levels, fiat ramps, securities workflows, geographic availability, or review requirements.

Compliance entries should clearly separate:

* Live platform policy.
* Jurisdiction-specific requirements.
* Roadmap capabilities.
* Required customer action.

### Docs and guides

Use for new guides, rewritten pages, information architecture changes, and API reference improvements.

## Change types

| Type       | Meaning                                                            |
| ---------- | ------------------------------------------------------------------ |
| Added      | New capability, page, endpoint, SDK method, asset, rail, or guide. |
| Changed    | Existing behavior or documentation changed without removal.        |
| Deprecated | Still available, but should not be used for new integrations.      |
| Removed    | No longer available. Include migration path when possible.         |
| Fixed      | Bug fix, documentation correction, or behavior correction.         |
| Roadmap    | Planned capability that is not live yet.                           |

## Breaking-change policy

A breaking change is any change that can cause an existing integration to fail, produce different financial behavior, or require code, configuration, compliance, or operational updates.

Examples:

* Removing or renaming an API field.
* Changing webhook payload shape.
* Changing authentication or token behavior.
* Changing payment-link state semantics.
* Changing supported assets or rails for a function.
* Changing approval or MFA requirements for money movement.
* Changing SDK method signatures.

For breaking changes, release notes should include:

1. What changed.
2. Why it changed.
3. Who is affected.
4. Migration steps.
5. Test plan.
6. Deadline or rollout date.
7. Support path.

## Recommended release-note template

```markdown
### YYYY-MM-DD: Short title

**Area:** Product | API | SDK | Networks and assets | Compliance | Docs  
**Type:** Added | Changed | Deprecated | Removed | Fixed | Roadmap  
**Impact:** Who is affected and how  
**Action required:** What builders must do, or "No action required"

Short summary of the change.

#### Details

- Detail 1.
- Detail 2.
- Detail 3.

#### Migration

1. Step one.
2. Step two.
3. Test expected behavior.

#### Related docs

- [Relevant guide](https://timechain.gitbook.io/neucron/go-live-checklist)
```

## What should be announced here

Announce changes that affect how builders design, integrate, test, launch, or operate Neucron.

Include:

* New rails, assets, and asset protocols.
* New API endpoints or changed schemas.
* New SDK releases.
* New wallet custody options.
* New app permissions or team controls.
* New invoice, payment-link, vendor, bill, payout, or treasury behavior.
* New approval, MFA, velocity, allowlist, or policy controls.
* Verification and compliance requirement changes.
* Deprecations and removals.
* Major docs additions.

Do not use this page for minor typo fixes unless the correction changes integration behavior or risk interpretation.

## Related docs

* [Go-Live Checklist](https://timechain.gitbook.io/neucron/go-live-checklist)
* [Use-Case Guides](https://timechain.gitbook.io/neucron/use-case-guides)
* [Supported Networks](https://timechain.gitbook.io/neucron/networks-and-assets/supported-networks)
* [Apps & Whitelabel](https://timechain.gitbook.io/neucron/core-concepts/apps-and-whitelabel)
* [Bills, Payouts & Approvals](https://timechain.gitbook.io/neucron/payments/bills-payouts-and-approvals)