Skip to content

feat(orders): the customer owns the token they paid for - #3

Merged
savvaniss merged 1 commit into
mainfrom
deep-research
Jul 29, 2026
Merged

feat(orders): the customer owns the token they paid for#3
savvaniss merged 1 commit into
mainfrom
deep-research

Conversation

@savvaniss

Copy link
Copy Markdown
Contributor

Summary

Part of an estate-wide remediation of the 49-ticket defect register in audit.md, sequenced by the phase plan in upgrade.md. Each ticket was resolved against its own Done when boxes, then handed to an independent reviewer told to assume it was not fixed and to walk the ticket's How it fails scenario through the new code.

Verification

  • pnpm typecheck passes across every workspace in this repo.
  • Each ticket carries a reproduction of its documented failure, then evidence that it no longer occurs.
  • Findings that survived adversarial review were sent back for a repair pass before landing.

What has NOT been verified

Stated plainly so review effort goes to the right places:

  • No end-to-end run of the assembled stack. Typechecks and unit tests are not the same as driving the feature. docker compose build returns exit 0 while cancelling every target, so a green build here would prove nothing anyway.
  • Some tickets in the wider programme came back partial or INCOMPLETE; where any of those touch this repo they are listed in the commit body rather than hidden.
  • Documentation corrections were verified against source, but the estate has a history of docs drifting from code — treat prose changes as claims to check, not conclusions.

🤖 Generated with Claude Code

CF-01 — take a customer-controlled ownerAddress on the order and pass it as
the constructor's owner_/recipient_ and as the SPL mint and freeze
authority. Every deployed token previously minted its whole supply to a
keyvault deployer address bound to the creation shape, which can sign
contract creations and nothing else — so the token the customer bought
existed at an address no signature would ever move. The deployer now only
pays gas and never holds value, which is what that shape is safe for.
CF-01a — the tiers were suspended as a stop-gap; superseded by the above.
CF-21 — a reverted or dropped deploy can be retried, instead of a set
txHash bricking the order for ever.
CF-43 — EVM_RPC_URL / SOLANA_RPC_URL no longer claim to do something they
cannot.

Co-Authored-By: Claude <noreply@anthropic.com>
@savvaniss
savvaniss merged commit 71d7aaf into main Jul 29, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant