Changelog

• phantasma-sdk-ts 0.7.0 adds signPrebuiltTransaction, which lets apps send an already-built transaction to the wallet for signing and get back signed hex ready for broadcast.
• Wallet error messages are now preserved instead of being collapsed into a generic signature failure.
• The SDK validates the returned signature against the connected account before handing back a signed transaction.
• This release builds on the 0.6.0 Link transport fixes and is mainly for apps that prepare transactions themselves before asking the wallet to sign.

phantasma-sdk-ts

npm update --save phantasma-sdk-ts

https://changelog.phantasma.info/

• TOMB 2.1.0 adds support for the token onAttach trigger, with compiler tests for both simple and stateful cases.
• pha-deploy 0.5.0 adds contract attach, so a compiled VM contract can be attached to an existing token without creating a new one.
• The CLI can now pin an exact pha-tomb binary through --compiler or PHA_TOMB_PATH, which matters on machines with multiple compiler builds.
• pha-deploy --version now reports both the CLI version and the pha-tomb binary that is actually being used.

pha-tomb | pha-deploy

dotnet tool install --global pha-tomb

dotnet tool update --global pha-tomb

npm i -g pha-deploy

• Added deterministic Phantasma-compatible NFT minting for the standard VM mint path: the chain now generates stable 256-bit _i ids from the public NFT payload and rejects duplicate deterministic replays.
• Disabled the old caller-provided explicit NFT id mint path: after the applied resolution, new NFT mints must use the deterministic chain-generated id flow.
• Restored VM contract lifecycle support for custom and token-backed contracts: Runtime.DeployContract, Runtime.UpgradeContract, and onUpgrade now work again, including contract-owned NFT flows.
• Restored VM token lifecycle hooks: onMint, onBurn, onSend, onReceive, onInfuse, and onSeries now run in the correct order and roll back cleanly on failure.
• Implemented Runtime.MintTokens for supported custom fungible tokens, including contract-context minting and contract-owned destinations, while keeping native/dangerous symbols such as SOUL and KCAL blocked from the VM mint path.
• Added Runtime.GetTokenOwner for reading persisted token ownership.
• Fixed VM table/list {count} tracking for imported contracts and newly created state, so VM reads now return correct counts for restored tables and fresh fields.
• Fixed inconsistent public RPC reads for accounts, balances, owned tokens, and NFTs: the affected queries now work reliably across supported clients and address formats.
• Fixed public InvokeRawScript multi-result responses, so RPC now returns the full VM result list instead of collapsing it into one item.
• Hardened public PHANTASMAVM execution: token-creation entrypoints are stricter, the minimal-PoW public ExecuteScript bypass is closed, and old partial-burn gas configs no longer crash validators on InvokeRawScript.
• Improved fresh validator and audit-node sync reliability: nodes now recover and continue replay correctly from partially downloaded state instead of getting stuck during startup.

• carbon-token-deployment-tool-cs now mints NFTs through the deterministic Phantasma path and requires phantasma_series_id for mint operations.
• NFT metadata passed by the caller is now treated as public payload only. Reserved fields such as _i and nested rom are created by the chain and should not be supplied in config.
• Phantasma-CPP now includes helper code for building deterministic NFT mint payloads and reading both the Phantasma NFT id and the Carbon instance id from the result.
• PhantasmaPhoenix.Protocol.Carbon received the same deterministic mint support on the C# side, so the C++, C#, and deployment tools now follow the same mint rules.

PhantasmaPhoenix.Protocol.Carbon

carbon-token-deployment-tool-cs | Phantasma-CPP

dotnet package update PhantasmaPhoenix.Protocol.Carbon