@neuraiproject/neurai-assets 1.7.1 → 1.8.0

package/README.md

@@ -37,6 +37,15 @@ Complete asset management library for Neurai blockchain. Supports creation, reis
 > (full name, owner `!` included: 31 mainnet / 121 testnet-regtest, validated
 > against a regtest node); peer `neurai-rpc ^0.6.0`.
 
+## 1.8.0: Reset testnet marker policy
+
+Testnet builders require the node's `getblockchaininfo.asset_marker` value
+(or an explicit override) and reject a missing marker instead of silently
+using `rvn` after the activation of `xna`. This release requires
+`@neuraiproject/neurai-rpc` `^0.7.0` as a peer and
+`@neuraiproject/neurai-create-transaction` `^0.9.2`. Development tests use
+`@neuraiproject/neurai-sign-transaction` `^3.0.3`.
+
 ## Features
 
 - ✅ **Non-custodial**: Library builds unsigned transactions, your wallet signs them
@@ -786,7 +795,7 @@ The library automatically validates that the owner token is returned in each ope
 
 Asset payloads open with a 3-byte marker that NIP-040 migrates from the
 Ravencoin-inherited `rvn` to `xna` at an activation height per network
-(testnet: 303000, already crossed; regtest: 1; mainnet: not scheduled yet).
+(reset testnet: 10; regtest: 1; mainnet: not scheduled yet).
 
 - Transactions built **through the node** (`createrawtransaction`) need
   nothing: the node stamps the marker itself.
@@ -797,10 +806,12 @@ Ravencoin-inherited `rvn` to `xna` at an activation height per network
      `'xna'` — offline builds or tests);
   2. otherwise the node's `getblockchaininfo.asset_marker` (node commit
      `347362b` or later);
-  3. `'rvn'` when the node predates that field — which matches what such a
-     node enforces.
+  3. On mainnet, `'rvn'` when the node predates that field. Testnet requires
+     the field or an explicit `assetMarker` override.
 
-No height tables and no network inference: the node (or you) decides.
+The node reports the marker for the next block. On the reset testnet it reports
+`rvn` with tip 8 and `xna` with tip 9. The builder does not infer a marker
+from the network name.
 
 ### Failure policy (`assetMarkerPolicy`, 1.5.0+)
 
@@ -811,16 +822,16 @@ not answer at all is a different situation, and `assetMarkerPolicy` decides it:
 const assets = new NeuraiAssets(rpc, {
   network: 'xna-test',
   addresses: [...],
-  assetMarkerPolicy: 'strict'   // default: 'legacy-fallback'
+  assetMarkerPolicy: 'strict'   // default on testnet
 });
 ```
 
 | Policy | `getblockchaininfo` fails | Field absent/null | Unknown value |
 | --- | --- | --- | --- |
-| `legacy-fallback` (default in 1.x) | resolves `'rvn'` | resolves `'rvn'` | throws |
-| `strict` | **throws** | resolves `'rvn'` | throws |
+| `legacy-fallback` (mainnet default) | resolves `'rvn'` | mainnet: `'rvn'`; testnet: throws | throws |
+| `strict` (testnet default) | **throws** | mainnet: `'rvn'`; testnet: throws | throws |
 
-Use `strict` in a connected wallet on a post-NIP-040 chain: guessing `'rvn'`
+The reset testnet defaults to `strict`. Guessing `'rvn'`
 there builds a transaction the node rejects with
 `bad-txns-legacy-asset-marker-after-nip040`, so "the node did not answer" must
 not silently become "the node said rvn". The rejection propagates out of the
@@ -893,8 +904,8 @@ Address types (every family is valid with the network label of its chain):
 
 The old `nq1p...` / `tnq1p...` encoding of generic AuthScript v1 is rejected, like
 in the node (same scriptPubKey: regenerate it as `nc1p...` / `tnc1p...`). The node
-only protects a witness family where it is active: today v1 on testnet and regtest,
-v2 / v3 only on regtest.
+only protects a witness family where it is active. All three families activate
+on the reset testnet from block 10 and on regtest from block 1.
 
 The library accepts these network names. A label only selects the chain: the
 address type always comes from the address itself.
@@ -1132,6 +1143,19 @@ remain available as `totalSats` / raw methods; never use a rounded display value
 as a new transaction input.
 
 
+## 1.7.2: CommonJS type declarations
+
+`require()` loads `dist/index.cjs`, but the package only published the ESM
+declarations (`index.d.ts`), so a CommonJS file compiled with
+`moduleResolution: "node16"` got `TS1471` and no types. The `require`
+condition now has its own declarations, `dist/index.d.cts`, written by the
+build from `index.d.ts` (both entry points export the same values, with
+`default === NeuraiAssets`). No runtime or API change. `npm run test:types`
+also compiles ESM, CommonJS and browser consumers against the declarations
+(NodeNext, Node16, Bundler; `skipLibCheck: false`), and `npm run
+test:package` checks the packed tarball in a clean project, with TypeScript
+4.7 too.
+
 ## 1.7.1: type declarations
 
 `index.d.ts` exported `AssetQueries` twice (`export class AssetQueries` plus

package/dist/NeuraiAssets.global.js

@@ -1931,8 +1931,8 @@ var NeuraiAssetsBundle = (function (exports) {
 		 * Every transfer / new / owner / reissue payload opens with a 3-byte marker
 		 * followed by the type byte. The marker is consensus: blocks below the NIP-040
 		 * activation height of a network only accept `rvn` on new asset outputs and
-		 * blocks at or above it only accept `xna` (mainnet: not scheduled; testnet:
-		 * 303000; regtest: 1). This library does NOT know chain state and never
+		 * blocks at or above it only accept `xna` (mainnet: not scheduled; reset testnet:
+		 * 10; regtest: 1). This library does NOT know chain state and never
 		 * infers the marker from a network or an address: the caller passes the
 		 * value reported by the node for the next block
 		 * (`getblockchaininfo.asset_marker`, node commit 347362b) — or, when building
@@ -8859,14 +8859,13 @@ var NeuraiAssetsBundle = (function (exports) {
 		   *   1. `params.assetMarker` (explicit caller override — offline builds,
 		   *      tests, or a node this library should not ask);
 		   *   2. `getblockchaininfo.asset_marker` from the connected node;
-		   *   3. `'rvn'` when the node predates the field (a node without it enforces
-		   *      the legacy marker, so that is the right answer, not a guess).
+		   *   3. On mainnet, `'rvn'` when the field is absent. Testnet requires
+		   *      the field or an explicit override.
 		   *
 		   * An RPC *failure* is a different case, and `params.assetMarkerPolicy`
 		   * decides it:
-		   *   - `'legacy-fallback'` (default in 1.x) resolves `'rvn'`, preserving the
-		   *     1.4.x behaviour;
-		   *   - `'strict'` propagates the failure. On a post-NIP-040 chain a build
+		   *   - `'legacy-fallback'` (mainnet default) resolves `'rvn'`;
+		   *   - `'strict'` (testnet default) propagates the failure. On a post-NIP-040 chain a build
 		   *     that guessed `'rvn'` produces a transaction the node rejects with
 		   *     `bad-txns-legacy-asset-marker-after-nip040`, so an online wallet
 		   *     should not treat "the node did not answer" as "the node said rvn".
@@ -8894,7 +8893,7 @@ var NeuraiAssetsBundle = (function (exports) {
 		  assetMarkerPolicy() {
 		    const policy = this.params.assetMarkerPolicy;
 		    if (policy === undefined || policy === null) {
-		      return 'legacy-fallback';
+		      return getNetworkConfig(this.network).baseNetwork === 'xna-test' ? 'strict' : 'legacy-fallback';
 		    }
 		    if (policy !== 'strict' && policy !== 'legacy-fallback') {
 		      throw new Error(
@@ -8932,7 +8931,9 @@ var NeuraiAssetsBundle = (function (exports) {
 		    }
 		    const marker = info ? info.asset_marker : undefined;
 		    if (marker === undefined || marker === null) {
-		      // A valid answer from a node that predates the field: legacy is correct.
+		      if (getNetworkConfig(this.network).baseNetwork === 'xna-test') {
+		        throw new Error('Testnet node did not report asset_marker; pass params.assetMarker for an offline build');
+		      }
 		      return 'rvn';
 		    }
 		    if (marker !== 'rvn' && marker !== 'xna') {
@@ -12632,14 +12633,11 @@ var NeuraiAssetsBundle = (function (exports) {
 		   * @param {string} config.toAddress - Default receiving address
 		   * @param {('rvn'|'xna')} [config.assetMarker] - NIP-040 marker for locally
 		   *   built raw transactions. Omit to use the node's
-		   *   getblockchaininfo.asset_marker (falls back to 'rvn' on nodes that do
-		   *   not report it). Per-operation params.assetMarker overrides this.
+		   *   getblockchaininfo.asset_marker. A missing field fails on testnet and
+		   *   falls back to 'rvn' on mainnet. Per-operation params.assetMarker overrides this.
 		   * @param {('strict'|'legacy-fallback')} [config.assetMarkerPolicy] - What to
-		   *   do when getblockchaininfo FAILS. 'legacy-fallback' (default in 1.x)
-		   *   resolves 'rvn'; 'strict' propagates the error instead, because on a
-		   *   post-NIP-040 chain a guessed 'rvn' builds a transaction the node
-		   *   rejects. A node that simply predates the field still resolves 'rvn'
-		   *   under both policies — that is an answer, not a failure.
+		   *   do when getblockchaininfo fails. Testnet defaults to 'strict'; mainnet
+		   *   defaults to 'legacy-fallback'. An absent field always fails on testnet.
 		   */
 		  constructor(rpc, config = {}) {
 		    if (!rpc || typeof rpc !== 'function') {