# CaishenX for macOS — 2.12.72

Apple Silicon and Intel. macOS 13 Ventura or newer and a current Chrome-based browser are required. Chrome is the reference browser; Safari and iOS are not supported.

## Package and installation

The macOS bundle contains the unchanged CaishenX 2.12.72 extension, a universal arm64/x86_64 native update helper, and user-level install/uninstall scripts. The Windows MSI and extension ZIP are not rebuilt or changed.

1. Download the macOS disk image and compare its SHA-256 with the published checksum. Open the disk image and copy its CaishenX folder to a permanent location before installation. No administrator password is required.
2. Open Terminal, type `/bin/bash `, drag `install.sh` from the copied folder into Terminal, and press Return. The script installs only this user's CaishenX files and native-host registration. Do not run the Windows MSI on macOS.
3. Open `chrome://extensions`, enable Developer mode and choose Load unpacked. Select `~/Library/Application Support/CaishenX/extension`. This must be the folder containing manifest.json.
4. Check the extension ID is `aiaejpjdnmamjhjielkclibgkfklfnea`. Open Axiom, FOMO or GMGN. Only use the CaishenX paper-trading controls. No licence, admin approval or wallet connection is required.

The helper is registered at `~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.caishenx.update.json`. Its manifest allows only the unchanged extension ID. Other Chromium browsers need their own documented native-host manifest location; the extension ZIP remains usable without the helper.

## Files and updates

CaishenX's own files live under `~/Library/Application Support/CaishenX`. Browser profiles, paper positions and settings remain managed by Chrome. The scheduled check runs every three hours; it stages an update. Use the extension's update action to apply it and reload the trading page when prompted. Signatures and SHA-256 are checked before extraction. A failed update must preserve the existing extension and browser data.

The helper updates extension code, not itself. A later helper release requires installing the new macOS bundle. Keep the same browser profile, extension ID and extension folder. Never remove the browser extension to update it: removal can delete locally stored paper positions and settings. Back up before changing profiles or paths.

## Without the native helper

The unchanged extension ZIP also works by itself. Extract it into a permanent folder such as `~/Applications/CaishenX-extension`, then Load unpacked in Chrome. To update, close the relevant tabs, back up that folder, replace only the extension's code in the same folder with the verified new ZIP, reload the existing extension and reopen the tabs. Preserve the browser profile and do not uninstall the extension. Without the helper, native Apply is unavailable; the overlay offers the website download instead.

## Apple signing and Gatekeeper

Developer ID signing and Apple notarization are not available for this build. A local ad-hoc code signature may be required for execution on Apple Silicon; it does not identify a trusted publisher and is not Developer ID/notarization. The release metadata is separately RSA-signed with the existing CaishenX release key.

If macOS blocks the helper, first verify the download source and checksum. macOS may offer Open via the contextual menu, or System Settings > Privacy & Security > Open Anyway after a blocked launch. Follow Apple's instructions for your macOS version. Do not disable Gatekeeper, remove quarantine attributes or turn off browser security. A plain extension ZIP loaded through Chrome is not a native application and does not itself need this Gatekeeper exception.

## Uninstall

Run `/bin/bash /path/to/CaishenX/uninstall.sh`. It removes only owned native registration, scheduled check and helper files. Browser-profile data and the extension code/data remain unless you separately choose to remove them. Do not remove the Chrome extension when you want to preserve its paper data.

## Acceptance status

The macOS GitHub Actions build/tests and their artifact logs are the automated evidence. They must finish successfully before publishing this native download. A manual click test on a real Apple Silicon Mac and an Intel Mac remains open even after CI passes. No live trades or wallet actions belong in this test.

References:
- https://support.google.com/chrome/answer/95346
- https://developer.chrome.com/docs/extensions/get-started/tutorial/hello-world
- https://developer.chrome.com/docs/extensions/reference/manifest/key
- https://developer.chrome.com/docs/extensions/develop/concepts/native-messaging
- https://support.apple.com/en-us/102445