@xgamesfun/solana 0.27.2 → 0.28.1

package/js/client/idl/loot.json

@@ -1,8 +1,8 @@
 {
-  "address": "9cwqM1TXytPnFZsLfmUyv2dg4uW6Ch9C6UJVPns7NFQ",
+  "address": "xgamesVsZBpCVgJuatfYAFJRmQoccfQf5qtUFNp2Eet",
   "metadata": {
     "name": "loot",
-    "version": "0.27.0",
+    "version": "0.28.0",
     "spec": "0.1.0",
     "description": "Economy for Anything: one program every coin of a project passes through",
     "repository": "https://github.com/gamesfun/loot"

package/js/economy/plan.mjs

@@ -1892,8 +1892,8 @@ export const SETUP_UNIT_PRICE = 1n;
 /**
  * A setup transaction's instructions as the owner's wallet is handed them: led by a compute unit limit and a compute
  * unit price, each once. A wallet that adds its own priority fee (Phantom does) adds it only to a transaction that
- * sets neither, and the approval page sends a transaction only as it prepared it, so every setup transaction sets both
- * itself. The limit is all a transaction can have (1,400,000 units): nothing here measures what a step takes, a box's
+ * sets neither, and the approval page takes no price a wallet puts on a transaction that has one, so every setup
+ * transaction sets both itself: its fee is the plan's own, whatever the wallet. The limit is all a transaction can have (1,400,000 units): nothing here measures what a step takes, a box's
  * write needs it, and no step may fail for want of compute. A limit or a price the instructions already carry is
  * kept.
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xgamesfun/solana",
-  "version": "0.27.2",
+  "version": "0.28.1",
   "mcpName": "io.github.XGamesFun/solana-kit",
   "description": "Loot boxes, gacha, shops, lotteries, auctions, NFT staking, crafting and rewards on Solana without writing a smart contract: one shared program, its JS client, a CLI, and an MCP server and skill so Claude Code, Codex or any AI agent can design, check, simulate and launch an economy.",
   "license": "Apache-2.0",

package/release.json

@@ -1,8 +1,8 @@
 {
-  "version": "0.27.0",
-  "programId": "9cwqM1TXytPnFZsLfmUyv2dg4uW6Ch9C6UJVPns7NFQ",
-  "sbfBytes": 1794664,
-  "sbfSha256": "3b11c460548a4fec865fd902431a94ac13a71c3a1013e4516783515e5d266bd6",
-  "idlSha256": "62364c5fd5be8aa001f4d72fb87b121b045dea07668f9b5ec9856d323d6cf445",
-  "clientSha256": "7790b667386bb981218acc8621088b2f7799c92347193b3a97d59b9332c4ed29"
+  "version": "0.28.0",
+  "programId": "xgamesVsZBpCVgJuatfYAFJRmQoccfQf5qtUFNp2Eet",
+  "sbfBytes": 1794616,
+  "sbfSha256": "ac8b09ed2c3a3f7daa2dfab55d2f6dea19fa43e4c98b44a82da2a68a7bc8ebbe",
+  "idlSha256": "ef3b8043d62c606e850df75773b4535cdb08206216e17aca653111a77403abd7",
+  "clientSha256": "3ef11453089e952e50d9d5a7199d9629b3417a091a071ea6dfd90f42746a2421"
 }

package/skills/xsolana-economy/SKILL.md

@@ -10,9 +10,9 @@ writes or deploys a contract: the spec is checked, simulated and priced by the `
 signed by a key file on the owner's own machine, once they have read what will be sent and said yes. It runs on
 **devnet** until the program is audited.
 
-The tools are the `xsolana_*` MCP tools. Without MCP, the same from a terminal: `npx -y @xgamesfun/solana@0.27.2 <guide|examples|check|simulate|cost|explain|review|publish|status> [xsolana.json]`,
-`npx -y @xgamesfun/solana@0.27.2 token <mint>` for a coin made elsewhere,
-or `npx -y @xgamesfun/solana@0.27.2 tool <name> '<json>'` for any tool (always with the exact version).
+The tools are the `xsolana_*` MCP tools. Without MCP, the same from a terminal: `npx -y @xgamesfun/solana@0.28.1 <guide|examples|check|simulate|cost|explain|review|publish|status> [xsolana.json]`,
+`npx -y @xgamesfun/solana@0.28.1 token <mint>` for a coin made elsewhere,
+or `npx -y @xgamesfun/solana@0.28.1 tool <name> '<json>'` for any tool (always with the exact version).
 
 ## Rules (always)
 
@@ -137,7 +137,7 @@ or `npx -y @xgamesfun/solana@0.27.2 tool <name> '<json>'` for any tool (always w
 9. **When they say "put it live"**: `xsolana_publish` lists every step and its cost and gives the commands, which you
    run in the project folder exactly as given (they name the exact version; never drop it):
    - **A new economy gets a key file**, unless the project has one:
-     `npx -y @xgamesfun/solana@0.27.2 keygen ~/.config/xsolana/<name>.json`. Give the person the address it prints. A
+     `npx -y @xgamesfun/solana@0.28.1 keygen ~/.config/xsolana/<name>.json`. Give the person the address it prints. A
      Solana key file they already have and name themselves (`~/.config/solana/id.json`) works the same; never go
      looking for one.
    - **Say what the key file is** before anything is sent: the project's owner, and, unless the spec says otherwise,
@@ -152,7 +152,7 @@ or `npx -y @xgamesfun/solana@0.27.2 tool <name> '<json>'` for any tool (always w
      (`xsolana_cost`), any seed in a coin that already exists, and every NFT a stash, a raffle or an auction names. A
      collection they already have needs the key's address as its update authority. If they would rather not move
      those, offer the browser wallet.
-   - **Show it**: `npx -y @xgamesfun/solana@0.27.2 approve xsolana.json --keypair <key file>` prints every step with
+   - **Show it**: `npx -y @xgamesfun/solana@0.28.1 approve xsolana.json --keypair <key file>` prints every step with
      what it pays and trusts, the warnings, the notice and a code, and sends nothing. Give the person that printout as
      it is, not a summary of it, and ask.
    - **On their yes**, the same command with `--yes <code>`. What lands is written back into `xsolana.json`. If it

package/types/chain/pda.d.ts

@@ -3,6 +3,12 @@ export declare const TOKEN_PROGRAM = "TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5D
 export declare const TOKEN_2022_PROGRAM = "TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb";
 export declare const ASSOCIATED_TOKEN_PROGRAM = "ATokenGPvbdGVxr1b2hvZbsiqW5xWH25efTNsLJA8knL";
 export declare const COMPUTE_BUDGET_PROGRAM = "ComputeBudget111111111111111111111111111111";
+/**
+ * Lighthouse: a program of assertions (it reads accounts and fails the transaction when one is not as expected),
+ * which a wallet may add to a transaction before signing it (Phantom does). The same address on mainnet and devnet:
+ * its source's `declare_id!` and its README, github.com/Jac0xb/lighthouse.
+ */
+export declare const LIGHTHOUSE_PROGRAM = "L2TExMFKdjpN9kozasaurPirfHy9P8sbXoAN1qA3S95";
 export declare const METAPLEX_METADATA_PROGRAM = "metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s";
 /** Metaplex Core: the program of Core assets and collections. */
 export declare const MPL_CORE_PROGRAM = "CoREENxT6tW1HoK8ypY1SxRMZTcVPm7R94rH4PZNhX7d";

package/types/economy/plan.d.mts

@@ -1051,8 +1051,8 @@ export declare const SETUP_UNIT_PRICE = 1n;
 /**
  * A setup transaction's instructions as the owner's wallet is handed them: led by a compute unit limit and a compute
  * unit price, each once. A wallet that adds its own priority fee (Phantom does) adds it only to a transaction that
- * sets neither, and the approval page sends a transaction only as it prepared it, so every setup transaction sets both
- * itself. The limit is all a transaction can have (1,400,000 units): nothing here measures what a step takes, a box's
+ * sets neither, and the approval page takes no price a wallet puts on a transaction that has one, so every setup
+ * transaction sets both itself: its fee is the plan's own, whatever the wallet. The limit is all a transaction can have (1,400,000 units): nothing here measures what a step takes, a box's
  * write needs it, and no step may fail for want of compute. A limit or a price the instructions already carry is
  * kept.
  */